Blue death screen in Win11 after exit game

[Matez]

Hi guys it always when I pressed Exit Diablo automaticaly show blue error screen in Win11 and auto restart computer. Anyone else have this issue? It is not big problem, but still if anyone? Thanks

[kyhd]

I do. No idea how to fix this.

[CHANCHO]

me to / win 10

[Matez]

It must be something with trying to sync savegame? I dont know maybe with some patch it stop restarting machine.

[TeknoBug]

I'm on Linux, client hangs forever, I had to xkill it a couple times.

[mimizukari]

Do you guys meet the hardware requirements for this game? you could be going way beyond the 16GB RAM limit or your VRAM limits.

Also a BSOD always has an error that tells you the 'exact' problem occurring, did y'all not write it down?

[kyhd]

Originally posted by mimizukari:

Do you guys meet the hardware requirements for this game? you could be going way beyond the 16GB RAM limit or your VRAM limits.

Also a BSOD always has an error that tells you the 'exact' problem occurring, did y'all not write it down?

I'm pretty sure I do. Also, I didn't have this issue on Battle.net.
I didn't have the chance, cause it doesn't even stay on that screen for a second.

Edit: KERNEL_SECURITY_CHECK_FAILURE
QR code is crossed out, so I couldn't use that.

-5800X3D
-RTX 4080
-32GB @ 3600Mhz

[Matez]

yes this is the same like me, it is game issue not our comp… it is weird that on steam deck it is ok…

[Vrotappel]

Upgrade your PC.

[Ave]

Originally posted by Matez.cz:

yes this is the same like me, it is game issue not our comp… it is weird that on steam deck it is ok…

if its a game issue then everyone would be having it.

its your pc.

[kyhd]

Okay, I've checked for corrupt files, my pc is running the latest updates and drivers.

I've installed the game on Battle.net and that doesn't crash when I exit the game.

Any ideas?

[Flamesh]

Hi,
The game is exiting fine too with B.Net Launcher (no BSOD when exiting the game).
But with same PC, it's exiting with BSOD when started with Steam.
I requested for a refund as that's not something related to requirements of computer but to their adaptatation of the game without launcher.
Those who don't face the issue are lucky ones, and others like me just have to pray for someone from their technical team to reproduce the issue on their computer if we wan't to be read....
Good luck!

[kyhd]

Originally posted by Flamesh:

Hi,
The game is exiting fine too with B.Net Launcher (no BSOD when exiting the game).
But with same PC, it's exiting with BSOD when started with Steam.
I requested for a refund as that's not something related to requirements of computer but to their adaptatation of the game without launcher.
Those who don't face the issue are lucky ones, and others like me just have to pray for someone from their technical team to reproduce the issue on their computer if we wan't to be read....
Good luck!

Thanks for sharing. Hopefully it'll get fixed soon.

[mimizukari]

Originally posted by kyhd:

Originally posted by mimizukari:

Do you guys meet the hardware requirements for this game? you could be going way beyond the 16GB RAM limit or your VRAM limits.

Also a BSOD always has an error that tells you the 'exact' problem occurring, did y'all not write it down?

I'm pretty sure I do. Also, I didn't have this issue on Battle.net.
I didn't have the chance, cause it doesn't even stay on that screen for a second.

Edit: KERNEL_SECURITY_CHECK_FAILURE
QR code is crossed out, so I couldn't use that.

-5800X3D
-RTX 4080
-32GB @ 3600Mhz

This gives a good amount of information.

This specific BSOD isn't caused by games, it's caused by outdated drivers, faulty hardware or corrupted system files. Run SFC/DISM, make sure all your hardware is properly seated & running fine (use benchmark tools to stress test them) and update all your drivers. Most likely if it's a hardware issue then it's specifically your RAM, you may need to test different sticks and/or replace them entirely.

As a last resort you should try resetting your OS entirely. This specific BSOD can not be caused by games, but rather your own PC.

[kyhd]

Originally posted by mimizukari:

Originally posted by kyhd:

I'm pretty sure I do. Also, I didn't have this issue on Battle.net.
I didn't have the chance, cause it doesn't even stay on that screen for a second.

Edit: KERNEL_SECURITY_CHECK_FAILURE
QR code is crossed out, so I couldn't use that.

-5800X3D
-RTX 4080
-32GB @ 3600Mhz

This gives a good amount of information.

This specific BSOD isn't caused by games, it's caused by outdated drivers, faulty hardware or corrupted system files. Run SFC/DISM, make sure all your hardware is properly seated & running fine (use benchmark tools to stress test them) and update all your drivers. Most likely if it's a hardware issue then it's specifically your RAM, you may need to test different sticks and/or replace them entirely.

As a last resort you should try resetting your OS entirely. This specific BSOD can not be caused by games, but rather your own PC.

Thanks for the reponse.

I've already ran scans and verified system and game files. All my drivers are up-to-date.
Per your suggestion, I removed the ram and installed both sticks again. Also ran WMDT. No errors.

(Just a quick note, no OC's on anything).

If this isn't caused by the Steam version, then why is this the only game that does this? Like I said; it closes normally on B.net.

I'd argue Cyberpunk is a more demanding game, with the new expansion even more so and I have no issues running that game. It never crashes, it never goes to bsod unlike Diablo on Steam.

[mimizukari]

Originally posted by kyhd:

Originally posted by mimizukari:

This gives a good amount of information.

This specific BSOD isn't caused by games, it's caused by outdated drivers, faulty hardware or corrupted system files. Run SFC/DISM, make sure all your hardware is properly seated & running fine (use benchmark tools to stress test them) and update all your drivers. Most likely if it's a hardware issue then it's specifically your RAM, you may need to test different sticks and/or replace them entirely.

As a last resort you should try resetting your OS entirely. This specific BSOD can not be caused by games, but rather your own PC.

Thanks for the reponse.

I've already ran scans and verified system and game files. All my drivers are up-to-date.
Per your suggestion, I removed the ram and installed both sticks again. Also ran WMDT. No errors.

(Just a quick note, no OC's on anything).

If this isn't caused by the Steam version, then why is this the only game that does this? Like I said; it closes normally on B.net.

I'd argue Cyberpunk is a more demanding game, with the new expansion even more so and I have no issues running that game. It never crashes, it never goes to bsod unlike Diablo on Steam.

Diablo IV is a very dermanding game, more demanding than Cyberpunk for hardware, D4 itself does not cause system issues, but if you have system issues then due to how stressful the game it, it will bring them to the surface. That specific error 'literally' can not be caused by a game, but instead one of the things I listed, which is why those BSOD error codes are so useful ^^