[SOLVED] Computer sometimes causes BSOD when shutting down

[hunterczech]

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.

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .

try running this on the ssd - https://www.samsung.com/semiconductor/minisite/ssd/product/consumer/magician/

what are the rest of specs of the PC?

 

[hunterczech]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .

try running this on the ssd - https://www.samsung.com/semiconductor/minisite/ssd/product/consumer/magician/

what are the rest of specs of the PC?

Thank you for reply. I already had Magician and it says, on every startup: "An error occured during execution of scanning. Please check and try again." then it says "Magnician can't verify SSD. Please check network connection". Maybe i got it outdated though.

 

[Colif]

it does say that 1 answer to that error is having an outdated magician so try downloading latest version

Fix: Samsung Magician doesn't recognize SSD

Some users are having trouble managing their SSDs with Samsung Magician. This Samsung utility is frequently reported to refuse to recognize SSD

appuals.com

 

[Colif]

However, first one is caused by intelppm.sys +

intelppm is part of windows designed to talk to CPU and do power management.

try updating intel management engine interface
Updating motherboard bios might also help

 

[hunterczech]

https://www.dropbox.com/s/4xn8sbfmxs2aa6i/dmp.zip?dl=0
Here's minidump of all bsod's i had since 20.3. i think

 

[Colif]

okay, I ask friend to convert dumps, he is likely asleep now.

 

[hunterczech]

okay, I ask friend to convert dumps, he is likely asleep now.

Thank you! I will now reset PC for chkdsk and then update SSD firmware in meantime . Maybe it'll help!

 

[hunterczech]

intelppm is part of windows designed to talk to CPU and do power management.

try updating intel management engine interface
Updating motherboard bios might also help

I have 1st generation Intel. So I don't think It's supported. I know It's old PC but still light and swift.

 

[Colif]

I have see Driver power state failure on GPU drivers so you could try updating those

What is a parts list of PC?

I might stop answering soon, getting tired.

 

[hunterczech]

Amd hd 6750 (with most recent drivers)
Intel i5 750
2x 4gb corsair 1600mhz ram i think
650w seasonic focus gold plus
Gigabyte p55 ultra durable
Samsung 860 EVO 500GB, wd blue 2tb, wd blue 1tb, wd passport 320gb
Windows 10 x64 home

 

[Colif]

wait and see what crashes reveal.

I don't see many old AMD GPU anymore (or new ones really)

do you have this off? it might help shutdown, it wouldn't really be helping a lot with an ssd - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

 

[hunterczech]

Yeah my main Nvidia gpu died (probably) so i am using friends' old backup gpu. One day while playing a game my PC blackscreened and restarted and since then it was starting only my second display=was ignoring my gpu and started intel's internal gpu. GPU fans were rotating, GPU was plugged and everything, but windows said its ignoring it on purpose due to error so i assumed it just died.

Btw where do i find results of how that startup chkdisk did and what happened? can't find it anywhere in event logs

EDIT: Found the chkdsk log.. https://jpst.it/2s-hp

 

[Colif]

GPU sounds pretty dead to me.

Btw where do i find results of how that startup chkdisk did and what happened? can't find it anywhere in event logs

How to find chkdsk results in Windows 10

Here is how you can view the detailed results of the disk check in Windows 10.

winaero.com

 

[hunterczech]

Read something about firmware update for my specific drive and seems lots of people have a problem with it so i might just stick with the old version i have.
https://us.community.samsung.com/t5/Monitors-and-Memory/860-EVO-Firmware-RVT04B6Q/td-p/992098/page/2

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/g3y07sLm/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.

Spoiler: Dump File Results

File information:	040221-10796-01.dmp (Apr 1 2021 - 19:07:39)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:	memory_corruption (Process: System)
Uptime:	3 Day(s), 7 Hour(s), 58 Min(s), and 48 Sec(s)

File information:	032921-11203-01.dmp (Mar 29 2021 - 11:08:07)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: Microsoft.Visual)
Uptime:	0 Day(s), 5 Hour(s), 44 Min(s), and 29 Sec(s)

File information:	032821-23343-01.dmp (Mar 27 2021 - 20:24:16)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:	memory_corruption (Process: System)
Uptime:	3 Day(s), 12 Hour(s), 59 Min(s), and 39 Sec(s)

File information:	032021-15734-01.dmp (Mar 19 2021 - 19:05:19)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 46 Min(s), and 13 Sec(s)

Motherboard : P55-US3L
I am unable to tell which revision of the motherboard that you are using so I can't determine if there are BIOS updates or not. You are using BIOS version F1 (08/04/2009).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[hunterczech]

There are updates for my BIOS i checked years ago. But I also know that BIOS shouldn't be updated if it's working and I don't think these BSOD's are anyhow related to BIOS as the computer is working fine for more than a decade. Updating BIOS on these old MOBO's is always risky usually with more risk than actual benefit.

 

[Colif]

BIOS updates don't help on old PC unless you changed a part recently.

top bsod has something to do with audio
mentions HDAudioBus.sys & portcls.sys which are both parts of windows that are associated with audio.
you don't seem to have much audio

May 19 2015

amdkmafd.sys

AMD Audio Bus Lower Filter driver http://support.amd.com/

Apr 13 2016	AtihdWT6.sys	AMD High Definition Audio Function driver http://support.amd.com/
May 14 2016	ScreamingBAudio64.sys	Screaming Bee Audio driver http://www.screamingbee.com/

I assume the 2 AMD ones are for GPU card. No Idea about Screaming Bee

you could try running DDU, remove the AMD drivers and put same versions on again - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

Other 3 BSOD aren't so obvious although if the cause of above is GPU drivers, it might fix number 3 as well. They could all be same driver.

 

[hunterczech]

I didn't change any part for about year. Regarding GPU i have these drivers over year without any problem. Why would the problem start just now?
And I've had another BSOD today. Minidump here https://easyupload.io/g7iuka (Password: bsod)

I'll try the driver update soon - maybe should I try more recent beta drivers or something?

�

Dump File	Crash Time	Bug Check String	Bug Check Code	Parameter 1	Parameter 2	Parameter 3	Parameter 4	Caused by driver	Caused by address
040521-16171-01.dmp	05.04.2021 0:21:32	SYSTEM_SERVICE_EXCEPTION	0x0000003b	00000000c0000005[/TD] [TD]fffff80705d21f12	ffffed02b20d7600[/TD] [TD]0000000000000000	FLTMGR.SYS	FLTMGR.SYS+1f12

 

[gardenman]

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 warnings:	*** WARNING: Unable to verify timestamp for klif.sys
Probably caused by:	memory_corruption (Process: FileCoAuth.exe)
Uptime:	0 Day(s), 13 Hour(s), 30 Min(s), and 23 Sec(s)

Crashing driver:

Feb 19 2021

klif.sys

Kaspersky Lab Intruder Filter driver

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[hunterczech]

U think it would be more reasonable to go for Crimson ?

And the last BSOD is caused by kaspersky?

 

[Colif]

And the last BSOD is caused by kaspersky?

yes. remove all kasperksy and see if it keeps happening.

Possibly hardware going bad (heat can cause this over years).

if you haven't changed anything and problem keeps moving to another driver, it is likely hardware

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.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it
bad ram can finger perfectly good drivers as being bad. Check it out.

 

[hunterczech]

Can't be these problems also related to my recent problem with this?
https://forums.tomshardware.com/thr...-cant-open-any-exe-file.3694210/post-22256477

Because it started few days after this date.

 

[Colif]

Ran the registry file all fixed now thank god. You can close.

its times like these i wish i knew registry. I know enough about it to stay out.

Is this registry file code safe to do ? I don't want to screw things more than they already are

I would have waited for a reply, I don't know how long you waited but given how fast people are to answer questions on here, it can't have been long

You might want to think about a clean install of Win 10 and see if they fixes it all.

you can try running system restore and see if you have one prior to the change you accidentally made -

1. type "restore" then open "create a restore point"
   create a new Restore Point now for C-drive
   then open the newest restore point that is prior to the problem happening (if you have one)

 

[hunterczech]

AFAIK i waited almost whole day and I required that computer for work.

I'm sometimes surprised how stupid Windows 10 is that it can essentially break itself any minute. I literally changed file association of random shortcut to app and my entire computer went down the toilet. But I dunno about that, I tried removing kaspersky so now i will be without AV for few days (god save me), so i'll report in few days.