[Bug]: Latest stable release causing NVIDIA driver restarts at boot on Windows 11 24H2 #173
Assignees
Labels
bug
Something isn't working
Comments
|
Investigating this. Thank you so much for the detailed writeup and logs/info. |
Apparently even in other repositories have problem with 24H2 fresh install but not if was an update. DuoStream/Duo#165 Hope this can give you some clues :P |
|
Sorry for the delay! Just got a fresh install of 24H2 on my laptop and will be testing tonight. If I can reproduce it, I can probably figure out the exact KB/Update version. |
|
Same Problem here! win11 24h2 release preview |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which OS?
Win11 Pro
Which release?
24H2
Describe the bug
The latest stable release (23.12.2.1) causes Event 219 errors (driver failed to load) at boot on a clean install on W11 24H2. This will manifest as the display dropping out momentarily right as the login screen appears, but in more severe cases the screen will not return from black until the driver is reloaded via the hotkey (Ctrl + Windows + Shift + B). This issue is immediately resolved by uninstalling the Virtual Display driver through device manager, the 219s are gone and the display does not flicker at boot. I also get "LKD_0x1A8_10_OSGraphicsMonitorNoModeSetTSDD_dxgkrnl!DISPLAYSTATECHECKER::CreateBlackScreenLiveDump
" errors in Reliability Monitor, so it looks like it's Windows freaking out when the Virtual display is initialized. NVIDIA also has many issues with multiple monitors in 24H2, so it could also be that, to be fair. I'll keep checking as NVIDIA and Microsoft issue updates in the coming weeks. Opened this here for awareness in case it isn't resolved by Microsoft/NVIDIA.
219 error:
The driver \Driver\WUDFRd failed to load. Device: ROOT\DISPLAY\0000 Status: 0xC0000365Steps to reproduce
Install the driver and reboot, then check Event Viewer for 219 error codes.
Expected behavior
Display does not flicker/crash at boot.
Log File (Beta Only)
No response
Contact Details
[email protected]
The text was updated successfully, but these errors were encountered: