Driver Power state failure BSOD at very shotdown/restart


  1. Posts : 5
    Windows 10 ver. 2004 build 19041.630
       #1

    Driver Power state failure BSOD at every shutdown/restart


    Hello,

    I have an annoying problem with my pc, because almost everytime I shutdown or restart it gives BSOD screen with DRIVER_POWER_STATE_FAILURE error.

    I've tried lots of solutions found around the web, like adding a registry key named "MSIServer" and starting msiserver, disabling sleep mode, run sfc command for integrity scan (that found nothing wrong), tried updating all drivers (that were found all updated), launch Windows updates, but none of them solved the problem.

    In order to do a deeper check I launched Bluescreenview to scan the dump file, and it found BSOD errors were caused by ntoskrnl.exe file, that as far as I know, it's just related to Windows kernel, and it just means there's a faulty driver, but I have no idea of what it is.

    Can you please help to find the exact problem and solve this issue?

    Below you can fine my pc specs, I can give you any other information needed:

    Model: Asus S500CA
    O.S.: Windows 10 ver. 2004 build 19041.630
    CPU: Intel Core i5-3317U 1.70GHz, 1701 Mhz, 2 core, 4 CPU
    RAM: 4,00 GB
    Graphics card: Intel HD Graphics 4000

    Roberto
    Last edited by Blax; 19 Nov 2020 at 14:19.
      My Computer

  2. Lance1's Avatar
    Posts : 726
    Windows 10 Professional x64 21H1 Spectre
       #2

    Hi BIax and welcome to Ten Forums. Upload the dump file here. How to Upload To a Post At Ten Forums so we can look through it. Blue Screen Viewer is OK but doesn't tell the whole story.
      My Computers


  3. Posts : 5
    Windows 10 ver. 2004 build 19041.630
    Thread Starter
       #3

    Thanks for your reply Lance, and for moving my post to the right section.

    In attachment I give you the information obtained with LogCollector V2.

    Thanks for helping me
      My Computer

  4. Ztruker's Avatar
    Posts : 13,568
    Windows 10 Pro X64 21H1 19043.1055
       #4

    The log files are in a non-english language and some can not be analyzed. Please change the system language to English and post a new log collector zip. Use the V2 log collector shown in the Blue Screen of Death (BSOD) Posting Instructions link as it collects more information than the standard collector.

    Add, Remove, and Change Display Language in Windows 10
    How To Change Language In Windows 10 Operating System - YouTube

    You can put the language back to normal once done though you may have to do this multiple times if we need you to run the log collector script again in the future. Won't help with data that's already collected but newly generated data will be in English which can help.

    I'm especially interested in the system-events.txt in Event Logs collected by V2. Parts I need are in Italian I think.

    Dump shows:

    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: ffffc20cd7222040, The thread currently holding on to the Pnp lock.
    Arg4: fffffb00f5a29880, nt!TRIAGE_9F_PNP on Win7 and higher

    You can try using Driver Verifier to see if that shows us any drivers with problems:

    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 and post a link to it here.

    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.

    Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

    Enable and Disable Driver Verifier in Windows 10

    Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.
      My Computers


  5. Posts : 1,319
    Windows 8.1 Enterprise x64
       #5

    Update Intel Rapid Storage driver - Intel RST 11.x Serie
      My Computer

  6. Lance1's Avatar
    Posts : 726
    Windows 10 Professional x64 21H1 Spectre
       #6

    Here's the Windbg from the dump file. It points to pci.sys

    Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\111920-34359-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred .sympath cache*c:\MySymbols
    Deferred srv*https://msdl.microsoft.com/download/symbols
    Symbol search path is: .sympath cache*c:\MySymbols;srv*https://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 10 Kernel Version 19041 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0xfffff800`4f200000 PsLoadedModuleList = 0xfffff800`4fe2a3b0
    Debug session time: Wed Nov 18 15:54:08.897 2020 (UTC - 8:00)
    System Uptime: 0 days 1:34:00.768
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ............
    Loading User Symbols
    Loading unloaded module list
    ..............
    For analysis of this file, run !analyze -v
    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: ffffc20cd7222040, The thread currently holding on to the Pnp lock.
    Arg4: fffffb00f5a29880, nt!TRIAGE_9F_PNP on Win7 and higher

    Debugging Details:
    ------------------

    Implicit thread is now ffffc20c`d7222040

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec
    Value: 3

    Key : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on GIGABYTE-PC

    Key : Analysis.DebugData
    Value: CreateObject

    Key : Analysis.DebugModel
    Value: CreateObject

    Key : Analysis.Elapsed.Sec
    Value: 3

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 81

    Key : Analysis.System
    Value: CreateObject


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: 9f

    BUGCHECK_P1: 4

    BUGCHECK_P2: 12c

    BUGCHECK_P3: ffffc20cd7222040

    BUGCHECK_P4: fffffb00f5a29880

    DRVPOWERSTATE_SUBCODE: 4

    IMAGE_NAME: pci.sys

    MODULE_NAME: pci

    FAULTING_MODULE: fffff80050d40000 pci

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    STACK_TEXT:
    fffffb00`f5a29848 fffff800`4f706ff6 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffc20c`d7222040 : nt!KeBugCheckEx
    fffffb00`f5a29850 fffff800`4fbae926 : 00000000`00000000 00000000`00000002 00000000`000348a2 fffffb00`f5a29b10 : nt!PnpBugcheckPowerTimeout+0x76
    fffffb00`f5a298b0 fffff800`4f4bf682 : fffffb00`f60dd330 ffff9481`a2dec180 ffff9481`a2dec180 00000000`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
    fffffb00`f5a298e0 fffff800`4f4e4a2d : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`000348a2 : nt!KiProcessExpiredTimerList+0x172
    fffffb00`f5a299d0 fffff800`4f5f8d7e : ffffffff`00000000 ffff9481`a2dec180 ffff9481`a2df7140 ffffc20c`d5f99080 : nt!KiRetireDpcList+0x5dd
    fffffb00`f5a29c60 00000000`00000000 : fffffb00`f5a2a000 fffffb00`f5a24000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


    IMAGE_VERSION: 10.0.19041.606

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: 0x9F_4_iaStorA_IMAGE_pci.sys

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {7212c866-5074-b4e3-62ac-4a2152b4669f}

    Followup: MachineOwner
    ---------
      My Computers


  7. Posts : 5
    Windows 10 ver. 2004 build 19041.630
    Thread Starter
       #7

    Lance1 said:
    Here's the Windbg from the dump file. It points to pci.sys
    ---------
    I've checked what driver uses this pci.sys file and I found out it's some "PCI Express root Complex" driver under "System devices" folder.

    However, I tried updating this software but it says is already up-to-date, so, before doing any dangerous step (like reinstalling driver), can you advise me on what I should do with this driver, if it's the cause of the BSOD?

    Thank you.

    Roberto
      My Computer


  8. Posts : 5
    Windows 10 ver. 2004 build 19041.630
    Thread Starter
       #8

    Hello,

    I come back to my thread as my problem is still not solved.

    I've launched Driver Verifier as suggested in order to find the faulty driver, and then I run the V2 log collector.

    The first time I run Driver Verifier (with 3 tests activated) nothing happened for 2 days, then I run it a second time with all tests activated and my pc immediately freezed after powering on.

    After going to safe mode and restarting the system, the BSOD appeared.

    Attached you can find the V2 log output
    Driver Power state failure BSOD at very shotdown/restart Attached Files
      My Computer


  9. Posts : 5
    Windows 10 ver. 2004 build 19041.630
    Thread Starter
       #9

    I wonder if there is a solution for my problem, or I should accept to have a pc that keeps crashing at every restart/shutdown.
      My Computer

  10. Ztruker's Avatar
    Posts : 13,568
    Windows 10 Pro X64 21H1 19043.1055
       #10

    No new dumps and the language is non-english so the tools I use to debug with don't work.

    I suggest using Clean Boot to try to debug the problem and see if you can isolate the cause.

    How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
      My Computers


 

  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 08:51.
Find Us




Windows 10 Forums