Occasional DRIVER_POWER_STATE_FAILURE

The tool is Windows Driver Verifier.

It causes crashes when there are identified misbehaving drivers.

The end user must run commands to turn off the tool and return to the desktop.

The tool is used frequently in the BSOD forum.

It is not completely safe as the end user must adjust to the crashes and learn how to recover from using the tool.

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Koushirou said:

Hello,
Ah, so there's a chance my gamepad was the culprit.
I have Logitech F310 as gamepad, its wired and connected to an USB hubs.
At Device Manager, this game controller will register itself as Xbox 360 Controller for Windows.

I remember that sometimes ago, I wanted to troubleshoot the issue myself and found out an article about what to do when Windows stuck at shutdown/restart, the solution was to unplug peripherals attached.
So when I got stuck on shutting down screen, I unplugged them all including the usb hubs-gamepad, but it still stucks.
At next blackscreen, I tried to unplugged them before initiating restart/shutdown, nope, it still stucks.
I still need to figure out what to do when the next blackscreen happens. Maybe just unplug then plug it back? Doubt it haha.

Oh, I've Logitech Gaming Software installed too. This is more related to my mouse, Logitech G400 though.
For now, I have set this software disabled at startup just in case.

Anyway, I thank you guys for the inputs! I'll update when somethings up.
Have a good day.

Unplugging the gamepad will not change things because the drivers will still be loaded. You might need to completely remove the device and driver and reboot to see if it has an effect.

zbook said:

The tool is Windows Driver Verifier.

It causes crashes when there are identified misbehaving drivers.

The end user must run commands to turn off the tool and return to the desktop.

The tool is used frequently in the BSOD forum.

It is not completely safe as the end user must adjust to the crashes and learn how to recover from using the tool.

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Hi there,
Sorry for the delays.

Here's another file that you requested.
ResourceTimeout-20210211-2145.dmp - Google Drive

And sorry, I think I'll skip the strest test afterall.
My PC is somewhat old and I feel a bit uncomfortable. It might cause another problem to surface and I don't want to fry something if I do it.
Can't afford to buy a replacement hardware now.
A bit exaggerated excuses here, yeah I know haha.

So, I'm going to wait and monitor things. I'll post another V2 logs if the problem still arises.
Thanks!!

philc43 said:

Unplugging the gamepad will not change things because the drivers will still be loaded. You might need to completely remove the device and driver and reboot to see if it has an effect.

Hello,
A bit lost here. You mean remove the device & driver from Device Manager, right?
Either disable the device or uninstall the device?
Or do you mean I should directly deletes the driver from directory C:\Windows\System32\drivers\xusb22.sys ?
What is the proper steps, should I disable the device first and delete the driver or vice versa?
I'll give it a try next time!
Thanks for the advice!

If there were no unexpected shutdowns or restarts you can mark the thread solved.

The computer can be monitored using:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

Hello,
A bit lost here. You mean remove the device & driver from Device Manager, right?
Either disable the device or uninstall the device?
Or do you mean I should directly deletes the driver from directory C:\Windows\System32\drivers\xusb22.sys ?
What is the proper steps, should I disable the device first and delete the driver or vice versa?
I'll give it a try next time!
Thanks for the advice!

Hello Koushirou,

Sorry for not being clearer. The correct process to remove a device and driver is from within Device Manager. You uninstall the device and also tick the box to remove the driver. When you plug the device back in you will, of course, get the opportunity to reinstall it again.

As zbook said for now it looks as if you have had no further problems but do keep us informed.

zbook said:

If there were no unexpected shutdowns or restarts you can mark the thread solved.

The computer can be monitored using:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

philc43 said:

Hello Koushirou,

Sorry for not being clearer. The correct process to remove a device and driver is from within Device Manager. You uninstall the device and also tick the box to remove the driver. When you plug the device back in you will, of course, get the opportunity to reinstall it again.

As zbook said for now it looks as if you have had no further problems but do keep us informed.

Hello,
It's been 2 weeks.
A week ago, I encountered a single stuck at restart/sleep/shutdown(don't remember which), but sadly its just stuck, no BSOD, so no generated crash dump.
Before stuck, I started a game, there was no black screen but there's this weird delay before game ran successfully.
Since then, I tried to troubleshoot another suspected cause, the gamepad driver.

I tried philc43 solution to remove the device & driver.
I found there's no option to remove the driver when I tried to uninstall my gamepad.
Maybe because its not a third party driver, but windows 10 built in driver.
No use updating it either, since its already the latest(xusb22.sys driver date 2019/03/18, version 10.0.18362.1).
Idk if there's newer version, or I'll get newer version if I upgrade to Windows 10 version 20H2.

From google search, I found many cases related with xusb22.sys but without any solution.
Then I tried my own preventative measure.
I planned to plug the gamepad only when game already started, and I'll unplug it when I'm done gaming.
Seems a good work around, but eventually no.
Today, after a gaming session, I recognize there's no sound when I unplug the gamepad.
And following that, it doesnt produce the usual sound when I plug it back.
Weird, could it be the xbox driver acting up? So I navigate to Settings > Bluetooth & other devices , I found there's "driver error" in my gamepad.
Tried to remove it from there, but it stuck at "Removing device".
Then I go to Device Manager, it'll stuck when I try to uninstall my gamepad.
Worse, when I press scan for hardware change, Device Manager stuck too.
Even after I unplug the gamepad, Device Manager still showing Xbox 360 controller.
Also, it shows "No drivers are installed for this device" in properties.
Lastly, I run sfc command and dism commands. Device manager still broken.
Then I shutdown the PC. Thank God it safely land on BSOD page and creates dump files after waiting few minutes.

So, here's the new V2 logs collector:
VEDA-(2021-03-31_13-44-29).zip - Google Drive

Please help, any work around or solution for this?
Thanks!

Please run:
https://www.tenforums.com/attachment...dump_files.bat


Uninstall Malwarebytes using the applicable uninstall tool:
https://downloads.malwarebytes.com/file/mb_clean

If there are no BSOD during the next week you can reinstall malwarebytes.

Code:

MbamChameleon.sys Fri Jan 29 19:30:17 2021 (6014B6A9)

Alright, here's the additional file you asked:
LiveKernel Reports 2021-03-31 (19-19-09).zip - Google Drive

Uninstalled Malwarebytes for now.
I'll monitor things & reports back soon.

Thank you!

zbook said:

If there are no BSOD during the next week you can reinstall malwarebytes.

Hi, its been a while.
I got a Driver Power State Failure BSOD just now.
Here's the logs:
VEDA-(2021-04-11_11-12-37).zip - Google Drive

I was tinkering with my PC network name.
So I was following a guide to use secpol.msc and changed the name.
Then I got BSOD when I'm turned the PC to sleep.

Oh, I need to mention that few days ago I upgraded my Windows version to 20H2.
It was a success, I just need to uninstall a few apps from Microsoft Store that got corrupted blank desktop icon(deleting db cache did not work)

Thank you!!

Please post a share link for the memory dump.

Code:

LastWriteTime         Size (MB) FullName             
-------------         --------- --------             
4/11/2021 11:07:23 AM    817.82 C:\WINDOWS\MEMORY.DMP

Perform these steps in sequence:

a) Use the built-in troubleshooter:
In Device Manager, double-click Xbox 360 Controller for Windows.
Select Troubleshoot, and then follow the steps provided.


b) Remove and then redetect the controller:
Right-click Xbox 360 Controller for Windows, and then select Uninstall.
In the Action menu, select Scan for hardware changes.


c) Try updating the driver:
Double-click Xbox 360 Controller for Windows.
On the Driver tab, select Update Driver.