driver power state failure bsod

Page 1 of 3 123 LastLast

  1. Posts : 12
    windows 7 64 bit
       #1

    driver power state failure bsod


    Hi

    i recently bought a second hand alienware and i am constantly getting driver power state failure bsod

    is this the code you need for someone clevere than me to tell me whats causing the problem

    9f
    BCP1: 0000000000000003
    BCP2: FFFFFA800D619A10
    BCP3: FFFFF80000B9C3D8
    BCP4: FFFFFA801392F560
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    thanks in advance
      My Computer


  2. Posts : 12
    windows 7 64 bit
    Thread Starter
       #2

    btw iv updated drivers and bios from dell and ran the diagnostics checks the last bluescreen analyzer is this




    0x0000009F_0x0000000000000003__0xFFFFFA800D595A10__0xFFFFF80000B9C3D8__0xFFFFFA8012C68A90_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D5B3A10__0xFFFFF80000B9C3D8__0xFFFFFA801265FB40_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D5D5060__0xFFFFF80000BA2748__0xFFFFFA80125D4490_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800F9F1E10__0xFFFFF80000B9C3D8__0xFFFFFA8012AB9C60_C__Windows _system32_drivers_hdaudbus_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D618060__0xFFFFF80000B9C3D8__0xFFFFFA8011AFE1B0_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D614A10__0xFFFFF80004157748__0xFFFFFA8013485400_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D5D9A10__0xFFFFF80000B9C3D8__0xFFFFFA8012A47CA0_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D617060__0xFFFFF80000BA2748__0xFFFFFA80128E54D0_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D597A10__0xFFFFF80000B9C3D8__0xFFFFFA801262B200_C__Windows _system32_drivers_pci_sys, 0x0000009F_0x0000000000000003__0xFFFFFA800D610A10__0xFFFFF80000B9C3D8__0xFFFFFA800D7FA800_C__Windows _system32_drivers_pci_sys
      My Computer


  3. Posts : 12
    windows 7 64 bit
    Thread Starter
       #3

    stats from the dm tool
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #4

    chris76 said:
    stats from the dm tool
    No .dmp file present to look at the issue.

    Please do the following:

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode

    Do NOT run CCleaner until further notice - it deletes the .dmp files.
      My Computer


  5. Posts : 12
    windows 7 64 bit
    Thread Starter
       #5

    iv ran the verifier and it kept crashing before windows had a chance to load so i manged to use system restore to get it working again.

    hopefully iv done it right this time iv ran the dm tool and results should be attached

    thank you:)
      My Computer


  6. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #6

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800f9be970, fffff80000b9c3d8, fffffa80125e0820}
    
    Probably caused by : HDAudBus.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa80125e0820
    Irp is active with 9 stacks 7 is current (= 0xfffffa80125e0aa0)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [ 16, 0]   0  0 fffffa800f9be970 00000000 fffff88004d69510-fffffa800f9c4d00    
    	       \Driver\HDAudBus	portcls!PowerIrpCompletionRoutine
    			Args: 00000000 00000000 00000000 00000002
    >[ 16, 2]   0  1 fffffa800f9c4bb0 00000000 00000000-00000000    pending
    	       \Driver\HdAudAddService
    			Args: 00014400 00000001 00000001 00000002
     [ 16, 2]   0 e1 fffffa800da51e30 00000000 00000000-00000000    pending
    	       \Driver\ksthunk
    			Args: 00014400 00000001 00000001 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8013674a10
    Ensure all available Windows updates are installed.

    Code:
    fffff800`00b9c508  00000000`00000011
    fffff800`00b9c510  fffff880`0487ae80Unable to load image \SystemRoot\system32\DRIVERS\iusb3xhc.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for iusb3xhc.sys
    *** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
     iusb3xhc+0x7ae80
    fffff800`00b9c518  00000000`00000000
    .
    fffff880`04800000 fffff880`048c4000   iusb3xhc T (no symbols)           
        Loaded symbol image file: iusb3xhc.sys
        Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
        Image name: iusb3xhc.sys
        Timestamp:        Fri Jan 27 20:05:28 2012 (4F226FE0)
        CheckSum:         000C193B
        ImageSize:        000C4000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Update the Intel USB driver from here:
    https://downloadcenter.intel.com/
      My Computer


  7. Posts : 12
    windows 7 64 bit
    Thread Starter
       #7

    many thanks golden

    i have ran the updater,it updated 2 drivers bluetooth and wireless,it did say some componanants were not installed.

    do i now run verifier again?
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #8

    Yep.
      My Computer


  9. Posts : 12
    windows 7 64 bit
    Thread Starter
       #9

    hi golden,iv ran the verifier again and it kept crashing before windows would load so i had to restore again.

    iv attached the new file

    ps thanks for your help with this
      My Computer


  10. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #10

    OK. There aren't any new .dmp files, so I can't add much. All I can suggest is to see whether you can update the drivers for this device:

    Code:
    Name	Bluetooth Audio
    Manufacturer	Intel Corporation
    Status	OK
    PNP Device ID	BTHENUM\{747413E4-F767-414F-A0C1-6CC1AA9D054C}_LOCALMFG&0000\8&3128DDFC&0&000000000000_00000002
    Driver	c:\windows\system32\drivers\btmaud.sys (2.0.0.128, 50.50 KB (51,712 bytes), 30/11/2011 11:19)
    Then use the system as normal. If it BSOD's again, re-run the DM Log Collector Tool and upload a fresh ZIP file.
      My Computer


 
Page 1 of 3 123 LastLast

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

© Designer Media Ltd
All times are GMT -5. The time now is 01:42.
Find Us