That’s right, Windows will panic and throw a bluescreen if your monitors take a little too long to wake up. Had the pleasure of dealing with this suddenly becoming an issue and causing wide bluescreens on wakeup after an update back in mid-2024, on any Surface Dock using DisplayPort with specific Acer monitors.
It gets logged in the event viewer, yeah. That’s how I discovered it, on account of the screens not waking up in time to show the actual bluescreen. The users were only reporting that their computers were deleting all their windows when waking up. From their perspective, all they saw was their computer taking a mildly longer time to wake up from deep sleep and then losing their entire session, but what it was actually doing was hard rebooting.
Headless is fine, the bug was specifically triggered when a computer woke up and detected a monitor exists, but the monitor took some unspecified amount of time too long to wake up. It was also fixed at some point, I’m not sure when, but it went on long enough that we swapped dozens of cables because it specifically only happened on the ones using DisplayPort, not HDMI.
Fun fact about monitors turning on slowly: did you know Windows has a bluescreen code for that?
~ https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x19c--win32k-power-watchdog-timeout
That’s right, Windows will panic and throw a bluescreen if your monitors take a little too long to wake up. Had the pleasure of dealing with this suddenly becoming an issue and causing wide bluescreens on wakeup after an update back in mid-2024, on any Surface Dock using DisplayPort with specific Acer monitors.
Woah woah… is there someplace in the event logs where this would show? Does this mean that you cannot run a windows computer headless?
It gets logged in the event viewer, yeah. That’s how I discovered it, on account of the screens not waking up in time to show the actual bluescreen. The users were only reporting that their computers were deleting all their windows when waking up. From their perspective, all they saw was their computer taking a mildly longer time to wake up from deep sleep and then losing their entire session, but what it was actually doing was hard rebooting.
Headless is fine, the bug was specifically triggered when a computer woke up and detected a monitor exists, but the monitor took some unspecified amount of time too long to wake up. It was also fixed at some point, I’m not sure when, but it went on long enough that we swapped dozens of cables because it specifically only happened on the ones using DisplayPort, not HDMI.
Wow… I feel like I might have ran into this issue dozens of times. So cool the kinds of things I learn here
Oh shit, this may be the problem I’ve been having with my laptop dock at work