Driftkel May 21, 2020 @ 6:02pm
Blue Screen of Death (BSoD) in 2020
I have been lately getting these BSoDs (or Blue Screen of Death). At this point, it doesn't matter what I do: download a game, watch a video, listen to music, etc. my computer would freeze and then crash with a blue screen of death.

Afterwards, the computer shuts down and restarts. This is really frustrating because with this year's Steam Spring Event going on, I'd download games to play for a badge, but these BSoDs are preventing me from doing so.

Is there a working fix for this?
Last edited by Driftkel; May 21, 2020 @ 6:21pm

Something went wrong while displaying this content. Refresh

Error Reference: Community_9721151_
Loading CSS chunk 7561 failed.
(error: https://community.fastly.steamstatic.com/public/css/applications/community/communityawardsapp.css?contenthash=789dd1fbdb6c6b5c773d)
Originally posted by Horrible Orbit:
Sorry to double post again, but I've figured out the actual cause of my problem, which might be the same thing wrong with OP's computer - random seek/read/write speeds too slow to function properly.

Apparently, Western Digital drives with SMR are so slow to respond that they've been breaking RAID arrays without warning. Luckily, I'm not using SMR drives. Far less luckily, I made the mistake of selecting a very large stripe size (128kb) and it's having a similar effect on my computer. Mechanical drives like a long, continuous read with as few requests to reposition the 'needle' as possible, and I found the idea of trying to optimize for random speeds untenable, given that no mechanical HDDs perform adequately in this regard. That's why it seemed to make sense to select such a huge stripe size.

I could've literally spent the entire shelf life of my computer running diagnostic and maintenance procedures and never found the real problem, because slow speeds don't display as errors even when they're directly causing them. If OP is using Western Digital HDDs in a RAID array, and if their non-sequential performance is too slow (even by HDD standards) for whatever reason, that's probably what's wrong with his computer too.
< 1 2 >
Showing 1-15 of 30 comments
wuddih May 21, 2020 @ 6:03pm 
reinstall windows. fresh drivers. install what you need and if it still bsod, hardware failure.
emoticorpse May 21, 2020 @ 6:18pm 
check ram with memtest
Driftkel May 21, 2020 @ 6:26pm 
Turns out that doing a system restore point might have solved this problem. However, this is temporarily, as the BSoD would come back in a long time. I'm certain that it's not a hardware failure because this isn't an old desktop that I'm using (been using it for around 8 months now since purchasing it).
Mad Scientist May 21, 2020 @ 6:29pm 
Originally posted by wuddih:
reinstall windows. fresh drivers. install what you need and if it still bsod, hardware failure.
You should try to actually find the problem and solution instead of reinstalling windows (or recommending such) everytime something goes wrong.

OP - What does the BSOD message specifically say? Do you also know the CPU/GPU temperatures before the BSODs?
Driftkel May 21, 2020 @ 6:32pm 
Originally posted by Dr.Coomer:

OP - What does the BSOD message specifically say? Do you also know the CPU/GPU temperatures before the BSODs?

BSoD message:

Your PC ran into a problem and needs to restart. We're just collecting some error info, and then you can restart.

For more information about the issue and possible fixes, visit https://www.windows.com/stopcode

If you call a support person, give them this info:
Stop code: KMODE_EXCEPTION_NOT_HANDLED


Unfortunately, I wasn't able to get my cpu/gpu temperatures before the BSoDs.
Last edited by Driftkel; May 21, 2020 @ 6:33pm
DarthSidious666 May 21, 2020 @ 6:38pm 
A quick search on that stop code points towards a driver issue.
Check Device Manager for any yellow exclamations and reinstall the drivers.

It could also be caused by overclocking too aggressively.
Weaponized Autism May 21, 2020 @ 6:47pm 
Originally posted by wuddih:
reinstall windows. fresh drivers. install what you need and if it still bsod, hardware failure.
could be a BIOS issue... doesn't all boil down to Windows.
What changed before it started to happen?
iceman1980 May 21, 2020 @ 11:39pm 
KMODE_EXCEPTION_NOT_HANDLED

Means there was an unhandled exception at the kernel level. Something was running at the kernel level resulting in a crash when it couldn't recover from an unmaskable interrupt.
Last edited by iceman1980; May 21, 2020 @ 11:39pm
Driftkel May 22, 2020 @ 5:50pm 


I found this quick video that I tried and it works. Also, turning off fast startup under the Power Options work. So far, everything appears to be fine.
Clan Wolf May 23, 2020 @ 5:05pm 
yeah their just a hardware conflict. simple: find the conflict and remove. ♥♥♥♥♥♥♥ windows, and despite the name they do NO HARM. just ignore them. they are an annoying windows feature. would get these when on just about anything. new hardware new install. windows is ♥♥♥♥. duno your specs but the arrangement of hardware you have must have something it doesnt like. use linux mint, way better
Driftkel May 23, 2020 @ 5:08pm 
Originally posted by Clan Wolf:
duno your specs but the arrangement of hardware you have must have something it doesnt like.

-Windows 10 Home (64-bit OS)
-NVIDIA GeForce GTX 1660 Ti
-Intel Core i7-9700 CPU @ 3.00GHz
-16 GB of RAM

I was able to go a day without any BSoDs after I posted the fixes that worked for me, so it's all good.
Last edited by Driftkel; May 23, 2020 @ 5:09pm
You have a hp computer?

Its caused by the latest win 10 update. Its the defender.
Replace it with a recommended free antivirus until its fixed. To keep it disabled.
If that is not enough, read how to fix it with registry. Be carefull then and note what you did.
Clan Wolf May 24, 2020 @ 5:04pm 
its a interesting thing about pc's or just any device that you download and install software onto. Do it a 1000 times on a 1000 devices and you will not get the same result. it varies alot
Horrible Orbit May 27, 2020 @ 7:41pm 
Better to necro this thread than to start a new one on the exact same topic, I reckon.

So, I've been having the same problems as OP, but I'm using Windows 7 and my fast boot is disabled in BIOS. Tried all sorts of things, from memtest (100% error-free) to scanning for hard drive errors (which took forever and supposedly left me error-free), even installed a totally new antivirus program and rolled back my video drivers to the last completely stable version. Still having BSODs when running Steam, but not when Steam's off. They include 'driver_irql_not_less_or_equal' and 'driver exception' (heavily paraphrasing).
Last edited by Horrible Orbit; May 27, 2020 @ 7:42pm
< 1 2 >
Showing 1-15 of 30 comments
Per page: 1530 50

Date Posted: May 21, 2020 @ 6:02pm
Posts: 30