[SOLVED] Computer sometimes causes BSOD when shutting down

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

hunterczech

Reputable
May 29, 2019
85
8
4,545
My computer is running fine and all, but now had two BSOD's when shutting down on 28.3. and 2.4. with Bug Check DRIVER_POWER_STATE_FAILURE. However, first one is caused by intelppm.sys + 7e0b, second one by ntoskrnl.exe + 3f5c50. Computer goes black screen when shutting down for like 5 minutes and then shut downs, however after powering on it was same in both cases - computer boots up, after being on desktop computer shows Message Box that boot failed and restarts after like 10sec automatically. Only software i updated / installed in that time period was Visual Studio update.

After such thing happens, in event log, there is new event "The computer has been restarted from the error checking process. Error checking: 0x0000009f (0x0000000000000003, 0xffff9c017eb41b40, 0xfffff8031646c990, 0xffff9c017ebb7010). The dump was saved to: C: \ WINDOWS \ MEMORY.DMP. Report ID: 0278d5eb-a514-40c2-a5d9-446eb3136ee3"
Also saw this one in event viewer: "Windows Fast Launch failed. Error status: 0xC0000001"

Also tried running sfc and chkdsk, in sfc no violations, however chdsk found problems but as it was found on my system disk (just 1 year old Samsung 860 EVO SSD -> HD sentinel & crystaldiskinfo found no errors though, ) i will do disk check upon startup tommorow.

In meantime just had one BSOD which i have for years by MEMORY_MANAGEMENT, but that's just some faulty memory address in memory stick which randomly pops once per month no big deal.

So I'm asking if there is some app to collect dump from bsod if some diagnostic guy can check it up for me please? Or how should I proceed further? Thanks in advance.
 
Solution
Why would the problem start just now?

Possibly a Windows Update that conflicts with an old driver.
Possibly a driver update that conflicts with newer Windows.
Possibly hardware going bad (heat can cause this over years).
Possibly hardware being knocked slightly loose (RAM not all the way connected properly).
Etc.

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/f9sjw4d3/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:040521-16171-01.dmp (Apr 4 2021 - 18:21:32)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Driver...

hunterczech

Reputable
May 29, 2019
85
8
4,545
Shouldn't sfc scan if everything Windows related is ok?

EDIT: Yeah and prior to that incident I've had only 1 BSOD per 1-2 months related to some corrupted bits in RAM.
 
Last edited:

Colif

Win 11 Master
Moderator
SFC checks the files are okay, it doesn't know if the file associations are right. Or if windows itself is running right.

To start the Windows Registry Checker tool, click Start, click Run, type scanregw.exe in the Open box, and then click OK.

Scanreg /fix (In command prompt (admin)) should make it try to fix any problems in registry

https://support.microsoft.com/en-us...nreg-exe-aaae4323-daa2-8477-5a4e-2a273779fdf0

myself from 3 years ago shows scanreg runs auto,- https://forums.tomsguide.com/thread...ows-registry-checker-tool-scanreg-exe.184295/

I assume you didn't create a backup of the registry before you changed it... cause you could roll back that change but that wouldn't fix the file associations you run fix to correct

Gardenman may know what registry fix did, he may not. I find I can fix most problems in windows without going into registry.
 

gardenman

Splendid
Moderator
It looks like the registry file just restores the .EXE file extension back to correctly working order. I see similar versions of that registry elsewhere (and on these forums).

It's my guess that is has nothing to do with your BSODs.

Restore points usually save the registry too so use that if needed in the future.