The first of these commands uses the Windows Deployment Image Servicing and Management (DISM) command to check the components of the current running Windows image, and attempt repairs on any components that come up short during its integrity and checksum tests. This means running an administrative Command Prompt or PowerShell session and running the following commands:ĭism /online /cleanup-image /restorehealth If your driver maneuvers don’t restore things to normal operation and stop the DRIVER_POWER_STATE_FAILURE errors, it’s time to run the usual Windows repairs to see if they help. If so, please give it a try: it may fix your problem. Be sure to visit the vendor’s website to see if a newer driver is available for the problem device. Thus, if what Windows supplies by default doesn’t work (DRIVER_POWER_STATE_FAILURE BSODs continue) you’ll need to find a driver that works, or forgo use of the offending device until a working driver becomes available. And indeed, a BSOD is about as troublesome as a driver gets. It’s not always necessary to update device drivers – except, that is, when the current driver causes trouble. If the problem recurs after that, you’ll need to find a different driver instead. The next time you plug that device in, Windows will install the latest driver it knows about for that device. In most cases, this maneuver will fix the DRIVER_POWER_STATE_FAILURE problem.

Right-click the target device, then click Uninstall device in the pop-up menu.

Asus driver power state failure