Occasional DRIVER_POWER_STATE_FAILURE

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 10 Pro
       #1

    Occasional DRIVER_POWER_STATE_FAILURE


    Hi, this is my first post in TenForums.
    So I have this PC installed with Windows 10 Pro build 1909 for a year, an old Haswell build:
    Asus Z97 board with i7-4770, AMD RX580, 8 Gb rams.
    It runs great, except sometimes there's a slight issue that leads to BSOD DRIVER_POWER_STATE_FAILURE.

    It usually happens when I'm about to start a game(Monster Hunter World), it'll stuck in permanent black screen.
    I need to alt+F4 or force close from task manager, and in Event Viewer logs I can see it's register as event 1002 Application Hang(Hang type: Top level window is idle).
    At that point I can still do some browsing, opening videos or anything except starting the game(it'll stuck in black screen again guaranteed, even after restarting Steam)
    Now, if I attempt to do Sleep/Restart/Shutdown, Windows will stuck.
    Sometimes, after a few minutes, it will generates BSOD DRIVER_POWER_STATE_FAILURE & crash dumps , but sometimes it'll stay stuck for hours.
    The game and everything will work perfectly normal after reboot though.
    FYI, sometimes it just happened without me triggering the black screen. Means it'll be straight to Windows 10 cant shutdown/restart/sleep problem.

    This is really random. It can occur only once a month or sometimes twice a week.
    And its started since I installed Windows 10 last year. I was suspecting this is a bug on graphical card driver so I did the latest driver update before, but the issue persist. I already tried to update another drivers like audio,network card, chipset and updating the windows too, but to no avail.
    Do you think a BIOS update will help this kind of BSOD? Haven't touch BIOS update yet and I hope I don't need to.
    Please help me pinpoint the problem. Thank you!

    My V2 log collector:
    VEDA-(2021-03-12_22-52-45).zip - Google Drive
      My Computer


  2. Posts : 41,327
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    The logs were in a foreign language and could not be scanned.

    There was one collected mini dump file.

    Please perform the following steps:

    1) Run:

    Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.


    2) Kaspersky uninstall tool:
    https://support.kaspersky.com/common/uninstall/12783

    3) Kaspersky can be reinstalled or you can use Microsoft defender
      My Computer


  3. Posts : 12
    Windows 10 Pro
    Thread Starter
       #3

    Hello, thanks for the reply.
    Really sorry I missed the foreign language part.
    How about the minidump? Was it any useful for analysis or its messed up too?
    And one more, I'd like to apologize that I did some clean up to my system, so the relevant logs has been erased but I still keep the minidump and memory dump just in case

    Although it won't hurt to check, so here I uploaded another V2 logs (after clean up):
    VEDA-(2021-03-13_08-06-55).zip - Google Drive

    Tuneup.bat result:
    Code:
    ###########################################################
    # The following commands will be run in sequence.         #
    # The first 5 will take quite a while to run, be patient. #
    ###########################################################
    
    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    
    chkdsk /scan
    
    wmic recoveros get autoreboot
    wmic recoveros set autoreboot = false
    wmic recoveros get autoreboot
    wmic recoveros get DebugInfoType
    wmic recoveros set DebugInfoType = 7
    wmic recoveros get DebugInfoType
    
    wmic pagefile list /format:list
    wmic Computersystem where name="VEDA" get AutomaticManagedPagefile
    wmic Computersystem where name="VEDA" set AutomaticManagedPagefile=True
    wmic Computersystem where name="VEDA" get AutomaticManagedPagefile
    
    bcdedit /enum {badmemory}
    
    
    C:\Windows\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\Windows\system32>dism /online /cleanup-image /scanhealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1316
    
    Image Version: 10.0.18363.1316
    
    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.
    
    C:\Windows\system32>dism /online /cleanup-image /restorehealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1316
    
    Image Version: 10.0.18363.1316
    
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    
    C:\Windows\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\Windows\system32>chkdsk /scan
    The type of the file system is NTFS.
    
    Stage 1: Examining basic file system structure ...
      558848 file records processed.
    File verification completed.
      15663 large file records processed.
      0 bad file records processed.
    
    Stage 2: Examining file name linkage ...
      189 reparse records processed.
      829890 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
      189 reparse records processed.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      135522 data files processed.
    CHKDSK is verifying Usn Journal...
      39458312 USN bytes processed.
    Usn Journal verification completed.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
     243603455 KB total disk space.
      40963728 KB in 405084 files.
        274752 KB in 135523 indexes.
             0 KB in bad sectors.
        674667 KB in use by the system.
         65536 KB occupied by the log file.
     201690308 KB available on disk.
    
          4096 bytes in each allocation unit.
      60900863 total allocation units on disk.
      50422577 allocation units available on disk.
    
    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    TRUE
    
    
    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\VEDA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE
    
    
    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\Windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\VEDA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\Windows\system32>wmic pagefile list /format:list
    
    
    AllocatedBaseSize=5632
    CurrentUsage=31
    Description=C:\pagefile.sys
    InstallDate=20200124144247.789288+480
    Name=C:\pagefile.sys
    PeakUsage=33
    Status=
    TempPageFile=FALSE
    
    
    
    
    C:\Windows\system32>wmic Computersystem where name="VEDA" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\Windows\system32>wmic Computersystem where name="VEDA" set AutomaticManagedPagefile=True
    Updating property(s) of '\\VEDA\ROOT\CIMV2:Win32_ComputerSystem.Name="VEDA"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic Computersystem where name="VEDA" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\Windows\system32>bcdedit /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
    
    C:\Windows\system32>Echo off
       ###################################################################################
       #    How to capture batch file data and post in your thread in the BSOD forum     #
       #                                                                                 #
       #      Batch files and instructions for use in BSOD debugging[Part Two-Four]      #
       #                                                                                 #
       #        Press [V] to visit the above web page for detailed instructions.         #
       #        Press [C] to close this window.                                          #
       ###################################################################################
    
    
    Press any key to continue . . .
    Um, I did it with Kaspersky protection turned off.
    Not a problem, right? Unless you insist it to be uninstalled for better analysis result or determined it was the culprit, then I'd rather keep it for now.
      My Computer


  4. Posts : 41,327
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    There was a misbehaving Kaspersky driver.
    So uninstall the software with the applicable uninstall tool.

    You can reinstall immediately or monitor for a week before reinstalling.
      My Computer


  5. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #5

    I am unable to look at the dump files - access to the files you provided is denied. Please make them available by sharing.
    Last edited by philc43; 13 Mar 2021 at 07:47.
      My Computers


  6. Posts : 12
    Windows 10 Pro
    Thread Starter
       #6

    philc43 said:
    I am unable to look at the dump files - access to the files you provided is denied. Please make them available by sharing.
    Hi there,
    I thought nobody will try to do further checking since I already got some answer so I removed the link access. Anyway, if you still interested to help then please, I already made them available again.
    The first link kind of messed up because I took V2 logs in non English locale, but there's mini dump included.
    In second link there's no mini dump because I took the logs after I've done some clean up, so the relevant error logs may not exist yet.
    For time being I uninstalled Kaspersky as instructed and see how it goes. Hopefully it does the trick.
    Thanks kindly!
      My Computer


  7. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #7

    Thank you for making them available again.

    I have looked at the crash dump for the Driver Power State Failure and it reveals that the driver causing the crash was the XBOX 360 wireless receiver driver: xusb22.sys

    I don't know if you can confirm that the problem only happens when you are using the xbox? Is this something you can remove for testing purposes?

    There was only the one crash dump file that I could look at so it's not a lot to go on but hopefully it will help.
      My Computers


  8. Posts : 12
    Windows 10 Pro
    Thread Starter
       #8

    philc43 said:
    Thank you for making them available again.

    I have looked at the crash dump for the Driver Power State Failure and it reveals that the driver causing the crash was the XBOX 360 wireless receiver driver: xusb22.sys

    I don't know if you can confirm that the problem only happens when you are using the xbox? Is this something you can remove for testing purposes?

    There was only the one crash dump file that I could look at so it's not a lot to go on but hopefully it will help.
    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.
      My Computer


  9. Posts : 41,327
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    For this BSOD there was a Kaspersky misbehaving driver in the dump file raw stack.

    This should fix the BSOD unless there is more than one driver (only one seen in the collected dump file).

    The logs dated 3/13/2021 displayed Kaspersky reinstalled with no crashes.

    Options now are:
    a) monitor the computer for one week > if there is a crash then post a new V2 for any BSOD
    b) proactively use a tool that stress tests drivers and causes misbehaving drivers to crash > the same dump files are collected for debugging but the process is accelerated

    Please indicate your preference.



    Search for: C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20210211-2145.dmp

    Post a share link into this thread.
    (Use as needed: voidtools


    The computer has Windows 18363 (19H2).
    Indicate your preference regarding upgrading to 20H2.
      My Computer


  10. Posts : 12
    Windows 10 Pro
    Thread Starter
       #10

    zbook said:
    For this BSOD there was a Kaspersky misbehaving driver in the dump file raw stack.

    This should fix the BSOD unless there is more than one driver (only one seen in the collected dump file).

    The logs dated 3/13/2021 displayed Kaspersky reinstalled with no crashes.

    Options now are:
    a) monitor the computer for one week > if there is a crash then post a new V2 for any BSOD
    b) proactively use a tool that stress tests drivers and causes misbehaving drivers to crash > the same dump files are collected for debugging but the process is accelerated

    Please indicate your preference.



    Search for: C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20210211-2145.dmp

    Post a share link into this thread.
    (Use as needed: voidtools


    The computer has Windows 18363 (19H2).
    Indicate your preference regarding upgrading to 20H2.
    Hi,
    I'm more than willing to wait but if there's a way to speed up the process then I'm in.
    Is there any bad risk I should know about this stress test? Is it completely safe?

    I'd like to stay on current Windows 10 version for now.

    I'm sorry, but now I have other things need to be done, if you don't mind.
    I'll do it as soon as I get back to my PC.
    Thanks again!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 17:19.
Find Us




Windows 10 Forums