Driver Power State Failure on restart, shutdown, sleep

JDubbedN · 24 Jan 2020

I attempted to re-enable verifier with your specific steps and this time when I rebooted the computer and logged back in no BSOD. But then I went into verifier and saw that verifier wasn't running. I tried several times and I could not get verifier to load.

So I logged into safe mode and started it there, rebooted and then the long windows load processed started so I knew it was working then. I am now logged into the computer and working on it with no Failed AsUpIO.sys BSOD. I checked verifier and it is indeed turned on. I can also tell my computer is very sluggish. It takes loading up Firefox 4-5 times longer then it should and, just anything I try to open like Explorer or Windows settings takes much longer to load. I am not sure if this is because verifier is running.

I tried to reboot but problem still persists. Computer will not properly shutdown or restart.

What should I do next?

Ztruker · 24 Jan 2020

Nothing useful in the mini-dump. It's from

Debug session time: Fri Jan 24 00:38:50.182 2020 (UTC - 5:00)

The V2 data was collected prior to that time and no BSODs were indicated in the WER data found in msinfo32.nfo, so please run V2 log collector again and upload the zip file. That should include data that does include the BSOD:

Code:

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffd00dedd7b040, The thread currently holding on to the Pnp lock.
Arg4: ffff9e88cb6458e0, nt!TRIAGE_9F_PNP on Win7 and higher

The full MEMORY.DMP may be useful but then again may not contain any more useful data. No way to know unless you provide it. I think you're the first person I've run into who was concerned about what data a full dump may contain. Bottom line is, if you want to improve the chances of getting your problem resolved, you have to provide the data needed to do so.

I'll say again though: The full MEMORY.DMP may be useful but then again may not contain any more useful data.

JDubbedN · 24 Jan 2020

Would you guys mind if I DM'd you a Google Drive link to my full memory dump rather then it be publicly accessible on this thread?

Ztruker · 24 Jan 2020

No problem, but I'm not sure you can do that yet, not enough posts. Try it.

JDubbedN · 25 Jan 2020

Ztruker said:

No problem, but I'm not sure you can do that yet, not enough posts. Try it.

I sent you a test message. It said it sent. No response from you yet. Did you receive it?

Ztruker · 25 Jan 2020

Yes, I just now sent you a reply.

JDubbedN · 26 Jan 2020

Please see new V2 log as requested.

MrPepka may I send you a DM with a Google drive link to my full memory dump?

MrPepka · 26 Jan 2020

I don't see a problem with that. You can do the most

Ztruker · 26 Jan 2020

There is a problem with trying to handle this offline via PM. There are 5 or 6 people who regularly work on BSOD problems. Not having all the debug data available means they will not look at your problem so you will not get the level of help you may need.

You need to decide if you want the problem fixed or not. If yes then you need to provide the data for all the BSOD debuggers to be able to look at.

I'm not seeing anything additional in the full dump, so now we need to enable Driver Verifier and try to have it induce a dump that will tell us what driver is causing a problem.

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive, Google Drive, Dropbox or Amazon Cloud Drive (US) (UK) and post a share link.
To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

If you have questions, see this additional tutorial which may help to clear things up.

Enable and Disable Driver Verifier in Windows 10

JDubbedN · 26 Jan 2020

Thank you for the reply Ztruker. I wasn't aware there would be others assisting in troubleshooting the BSOD since you and MrPepka have been the ones that have participated in this thread thus far. I do want to get to the bottom of this problem but without the risk of publicizing information like a full memory dump that could potentially contain sensitive information. I am actually surprised it is a common practice to publicize full memory dumps given the fact that it could contain sensitive information like passwords, pictures and really anything in memory at the time of the dump. But I am not here to debate the security right now and I appreciate your continued assistance.

I had already run Driver Verifier per MrPepka's instructions on the first page of this thread. A BSOD was received, pertaining to the ASUS Suite software. I uninstalled it, rebooted and there is now no BSOD from running Driver Verifier. However, the problem still persists that the computer will not shutdown, restart or sleep without a forced shutdown. I provided a new V2 log just a couple posts up from this one as requested. A new memory dump is not being created because the BSOD is no longer happening during the driver verifier because I removed the ASUS Suite software. But it did not fix the problem. The full memory dump I sent to you was after all of this happened so it is the newest memory dump available.

Were you wanting me to try something else or go through another Driver Verifier even though I have already done so twice?