Driver Power State Failure on restart, shutdown, sleep

Ztruker · 27 Jan 2020

What I need is a dump, mini or full, created by Driver Verifier that points to a failing driver. This can take a couple days to get and sometimes you won't get one at all.

I don't see where you ran the V2 log collector after Driver Verifier caused a BSOD so no DV generated dump has been collected.
If you removed the probable cause of that specific BSOD with DV then please try Driver Verifier again following the directions I gave you. See what we get. If another BSOD occurs, please run V2 log collector as soon as possible to get the mini dump. If there is a C:\MEMORY.DMP copy it to another location to save it. You can then decide if you are willing to share that or not later if we need it.

JDubbedN · 27 Jan 2020

Ztruker,

Please see V2 Log collector. This is after I removed the ASUS suite which was causing a BSOD during Driver verifier. Now, when I run Driver verifier no BSOD occurs so no memory dump is created. However, when I run Driver Verifier my operating system is slowed. Everything takes a long time to open Windows Explorer, a word document, the whole computer is just dirt slow compared to when Driver Verifier is not running. I don't know what that means. Unfortunately I can't get anything done while Driver Verifier is running and it is not practical to let it run for several days while we wait for a memory dump that may never happen. I did let it run for over 8 hours and other then the computer running dirt slow no BSOD's occurred and no memory dumps were formed.

Will Driver Verifier create memory dumps if no BSOD's occur? Are memory dumps from Driver Verifier saved somewhere else besides the Windows directory?

I've also attached a mini dump which was the last mini dump that was created on the 25th. None others have been created.

MrPepka · 28 Jan 2020

Driver Verifier does not create memory dumps by itself (although it is possible to configure it to create logs). Turn it off and watch if you still have BSODs

JDubbedN · 29 Jan 2020

Here is my most recent full memory dump.

I could not get a BSOD while driver verifier was turned on. However, I still receive the Driver Power State Failure on restart, shutdown, sleep BSOD.

MEMORY1.rar - Google Drive

MrPepka · 29 Jan 2020

Enable Driver Verifier again with all standard settings and 3 additional settings (force pending i/o request, irp logging and ndis/wifi verification) and for verify tick all 3rd party drivers and 2 Microsoft drivers (NDIS.sys and raspppoe.sys)

JDubbedN · 29 Jan 2020

Oddly when I setup Driver Verifier as you stated and then restarted pc, fully expecting to have to force shutdown, the computer rebooted on its own. I am shocked. But anyways I am continuing with Driver Verifier as requested. What should I be waiting to see from Driver Verifier?

While using Driver Verifier my computer runs dirt slow. Is this to be expected?

Ztruker · 29 Jan 2020

the computer rebooted on its own.

Did you run V2 log collector? The reboot may have generated a Driver Verifier generated mini dump that we would very much like to see. Run it and upload the zip please.

JDubbedN · 29 Jan 2020

Here you go.

Ztruker · 29 Jan 2020

Both the minidump and the full system dump pointed to raspppoe.sys as the point of failure, which I doubt. It's always possible that it's corrupted but unlikely.

Run the following in sequence from a Elevated Command prompt. If there are any errors in any of the commands, run all 3 again. Repeat up to 3 times, see if you get a clean run.

Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow

If you prefer you can make the following into a bat or cmd file and run it from a Elevated Command Prompt.

@echo off
date /t & time /t
echo Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /StartComponentCleanup
echo ...
date /t & time /t
echo Dism /Online /Cleanup-Image /RestoreHealth
Dism /Online /Cleanup-Image /RestoreHealth
echo ...
date /t & time /t
echo SFC /scannow
SFC /scannow
date /t & time /t
pause

JDubbedN · 30 Jan 2020

All 3 commands completed successfully on first attempt. SFC did not find any integrity violations.

What would you like me to do next?

- - - Updated - - -

I went ahead and turned off driver verifier, rebooted which worked without having to force shutdown.

I then tested shutdown, restart and sleep. All worked properly this time. So currently it is working as intended. However, nothing that I did immediately fixed the problem or was noticeably the solution. It was either a delayed fixed from a previous step or something else. Do you see anything that would explain what fixed the problem?

Computer started shutting down properly after performing this step...

"Enable Driver Verifier again with all standard settings and 3 additional settings (force pending i/o request, irp logging and ndis/wifi verification) and for verify tick all 3rd party drivers and 2 Microsoft drivers (NDIS.sys and raspppoe.sys)"