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.
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.