Repeated Driver Power State Failure on shutdown


  1. Posts : 4
    Windows
       #1

    Repeated Driver Power State Failure on shutdown


    I have had this issue for a few weeks now. My PC will start stuttering, I can fix it temporarily by rebooting, however it hits the BSOD when I try to shut down. As it only bluescreens on shutdown when it is stuttering, I assume they are linked in some way, but that's for later. I have attempted to run Driver Verifier multiple times, it seems to have worked, I have got the Driver Verifier Detected Violation BSOD, but it has not told me what driver it detected. I may just not know where to look. I could use some help. included V2 log collector zip, would be nice someone could point me in the right direction. Thanks.
    Windows version 2004
      My Computer


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

    Hello @brailecortex and welcome to TenForums

    Please can you upload the V2 log collector output to your post. Many thanks!
      My Computers


  3. Posts : 4
    Windows
    Thread Starter
       #3

    I tried to, guess I didn't attach the files correctly. How's this?
    https://cdn.discordapp.com/attachmen...1_22-24-28.zip
      My Computer


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

    Thanks! That worked

    Working backwards through your dump files we can see the following two problems:

    1. Verifier caught a problem with SteamStreamingMicrophone.sys - please try to update or remove this driver for testing purposes. Try this link for more details: how to get rid of the Streaming Microphone and Steam Speakers on the Device Manager :: Steam Link General Discussions

    2. Driver Power state failure: FAILURE_BUCKET_ID: 0x9F_4_amd_sata_IMAGE_pci.sys
    Please try to update the chipset drivers for your motherboard.
    TUF GAMING X570-PLUS|Motherboards|ASUS Global

    Hope this helps!
      My Computers


  5. Posts : 4
    Windows
    Thread Starter
       #5

    Seemed to work for a bit, but just had it happen again. I removed the Steam Link drivers and updated all AMD chipset drivers, but it seems to not have fixed things. New log collector files: https://cdn.discordapp.com/attachmen...8_19-05-04.zip
    I tried to take a look at them myself, but there's a ton there and I don't know what to look for. Some pointers might be nice.
      My Computer


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

    You still seem to be getting the same power state failures associated with the PCI bus.

    It would seem that new drivers did not help. ASUS are currently working on a new BIOS for your system but it is only available as a beta version at the moment. Hopefully it will be released for mainstream use soon. It may help.

    In the meantime please list all the cards that are attached to the PCI bus - i.e. the cards inserted onto the motherboard.

    It might be worth updating all the drivers associated with these cards.
      My Computers


  7. Posts : 4
    Windows
    Thread Starter
       #7

    okay, updated all I could and now replaced the motherboard. Ran verifier, it detected something. I'd really like to be able to find out what it detected on my own at some point. It's doing a similar thing as before but to a much lesser extent. https://cdn.discordapp.com/attachmen...6_22-09-59.zip
      My Computer


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

    The Driver Verifier has detected the nordlwf.sys driver as a problem. The easiest way for you to find out the answer on your own is to install WinDBG Preview from the Microsoft Store and use it to analyse the crash dump. Once you have installed the software double click on the crash dump file and it will start to analyse. it. There will be a prompt to select analyse -v in order to carry out the automated analysis. When you have done this you will see the following output and towards the end will be the Failure Bucket ID that lists which driver was implicated. The Driver Verifier bugchecks are often the 0xC4 code.

    Code:
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
    Arg2: fffff806962d2b0b, The address in the driver's code where the error was detected.
    Arg3: 0000000000000000, Pool Type.
    Arg4: 0000000064726f4e, Pool Tag (if provided).
    
    BUGCHECK_CODE:  c4
    
    BUGCHECK_P1: 2000
    
    BUGCHECK_P2: fffff806962d2b0b
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 64726f4e
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    STACK_TEXT:  
    ffffde82`3be06598 fffff806`6bde8e14     : 00000000`000000c4 00000000`00002000 fffff806`962d2b0b 00000000`00000000 : nt!KeBugCheckEx
    ffffde82`3be065a0 fffff806`6b9b7335     : fffff806`6c02dc70 00000000`00002000 fffff806`962d2b0b 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xe0
    ffffde82`3be065e0 fffff806`6bddfdd4     : 00000000`64726f4e fffff806`6c02dc70 fffff806`962d2b0b 00000000`00000000 : nt!VfReportIssueWithOptions+0x101
    ffffde82`3be06630 fffff806`6bded0ad     : 00000000`00000000 00000000`00000060 00000000`00000010 ffff868a`58010000 : nt!VfCheckPoolType+0x90
    ffffde82`3be06670 fffff806`962d2b0b     : 00000000`00000000 ffffde82`3be067f0 ffff868a`5cffbb90 00000000`00000000 : nt!VerifierExAllocatePoolWithTagPriority+0x6d
    ffffde82`3be066c0 00000000`00000000     : ffffde82`3be067f0 ffff868a`5cffbb90 00000000`00000000 00000000`00000200 : nordlwf+0x2b0b
    
    
    SYMBOL_NAME:  nordlwf+2b0b
    
    MODULE_NAME: nordlwf
    
    IMAGE_NAME:  nordlwf.sys
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  2b0b
    
    FAILURE_BUCKET_ID:  0xc4_2000_VRF_nordlwf!unknown_function
    
    OS_VERSION:  10.0.19041.1
    
    BUILDLAB_STR:  vb_release
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {02d61e47-087d-ce7e-7b80-23a13513a21b}
    
    Followup:     MachineOwner
    ---------

    The Driver Power state failures are the same as before. Your AMD Sata drivers are still quite old. Did you update the AMD SATA/RAID drivers that are listed on the MSI website for your motherboard?

    I also noticed that since changing the motherboard it has not automatically activated Windows - you will need the retail product key for your Windows or a phone call to Microsoft to explain about the motherboard swap. This is because your digital license is hardcoded to the motherboard.
      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 23:19.
Find Us




Windows 10 Forums