Battlefield 6 session followed by delayed Windows black-screen
Subject: Battlefield 6 session followed by delayed Windows black-screen/display-loss event (Nov. 5, 2026)
I am reporting a repeatable user-observed pattern: after Battlefield 6, I leave Windows idle and later the displays fail to wake; the tower remains on and recovery may require a power cycle. For the Nov. 5 instance, Steam records Battlefield 6 (AppID 2807960) and its tracked EAAntiCheat launcher exiting with code 0 at 5:26:39 p.m. EST. The automatic settings capture at 5:27:11 shows two multiplayer profile files changed shortly before exit. Windows black-screen diagnostics and a LiveKernelEvent 1B8 were recorded about 1 hour 57 minutes later, at 7:23:35–41 p.m.
No Battlefield application fault was identified in the accessible event window, and the game exit was logged as normal. The only Application log IDs 1000/1002 in that window were Information-level Codex sandbox service lifecycle messages, unrelated to the Battlefield process. Windows WER referenced a WATCHDOG4401 dump, but the source file was not present when checked; the corresponding protected preserver path was inaccessible to this session. The evidence therefore does not show that Battlefield or Easy Anti-Cheat caused the Windows display loss.
Could EA advise whether the post-session profile writes, game/anti-cheat process shutdown, or any supported diagnostic logs are relevant to a delayed display failure after the game has exited? The attached focused package includes timing and profile-change metadata only; it excludes the raw BF6 profile binaries and Windows dump.
