Windows 8 and 8.1 Forums

Driver Power State Failure

  1. #1


    Posts : 1
    Windows 8 Pro with Media Canter

    Driver Power State Failure


    Whenever my computer goes to sleep overnight and i try to wake it up the following morning it does not wake up at all and pressing the power button doesn't wake it up either. I had to open up my computer take out my ram and put it back and pressed the power again to power the computer back up again and when i do i get a bsod error driver power state failure ntoskrnl.exe. Attached is the dmp files and everything appreciate the help

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    You have a NETGEAR WNDA4100 N900 Wireless Dual Band USB Adapter:
    I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
    These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
    Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
    An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
    - Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
    05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cras...ing-sleep.html
    27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.
    These devices are disabled:
    Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64 ROOT\NET\0000 This device is disabled.
    ASUS PCE-N10 11n Wireless LAN PCI-E Card PCI\VEN_10EC&DEV_8176&SUBSYS_84B51043&REV_01\4&BA882FD&0&0020 This device is disabled.
    Based on my previous experiences with this sort of combination, I suggest:
    - Temporarily uninstalling the Cisco AnyConnect software
    - Enabling the Asus wireless LAN PCI-E card and updating it's drivers
    - uninstalling the NETGEAR wireless USB network card and physically removing it from the system
    - test to see if this stops the BSOD's (and the wakeup problem).

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [S] DuplexSecure - FAQ [/S] Link broken as of 21 Jul 2012
    New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
    Alternate link: Disc-Tools.com
    Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    The last 4 memory dumps blame netr28ux.sys - a wireless driver
    While the first 2 blame atikmpag.sys - a video driver
    I suspect that the wireless USB/Cisco stuff is the main cause, while Daemon Tools and AMD OverDriver are also to blame.
    Please follow the advice above to fix these issues.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
    Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys

    vrtaucbl.sys Mon Feb 15 12:07:10 2010 (4B797F3E)
    Virtual Audio Cable (WDM)
    http://www.carrona.org/drivers/driver.php?id=vrtaucbl.sys

    RTKVHD64.sys Tue May 24 08:32:39 2011 (4DDBA567)
    Realtek High Definition Audio Function Driver
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys

    Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    Realtek PCI/PCIe Adapters
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Wed Apr 24 14:50:05.982 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042413-10530-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:0 days 15:51:33.167
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa80089773c0, fffff80369e99770, fffffa800b041660}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80089773c0, Physical Device Object of the stack
    Arg3: fffff80369e99770, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800b041660, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      BIOS Version                  P1.70
      BIOS Release Date             10/12/2012
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Apr 23 12:13:34.655 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042313-12885-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:5 days 13:47:33.936
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa8008962060, fffff80370cac770, fffffa800b05b150}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8008962060, Physical Device Object of the stack
    Arg3: fffff80370cac770, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800b05b150, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr 17 21:06:11.830 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041713-9796-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:1 days 23:12:51.892
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa8008984060, fffff803cf8c0b40, fffffa800af2e880}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8008984060, Physical Device Object of the stack
    Arg3: fffff803cf8c0b40, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800af2e880, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr  3 11:27:45.068 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\040313-9921-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 13:40:03.527
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa8007ca2060, fffff801dcfb9760, fffffa80117d6610}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8007ca2060, Physical Device Object of the stack
    Arg3: fffff801dcfb9760, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa80117d6610, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Mar 31 18:40:44.148 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\033113-8860-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:1 days 0:15:54.983
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by :atikmpag.sys ( atikmpag+9410 )
    BugCheck 116, {fffffa800aee5010, fffff88007ace410, 0, d}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa800aee5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88007ace410, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Mar 27 21:39:51.031 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032713-8486-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 1:22:04.799
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by :atikmpag.sys ( atikmpag+9410 )
    BugCheck 116, {fffffa8007fe14d0, fffff88007e3b410, 0, d}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa8007fe14d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88007e3b410, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Wed Apr 24 14:50:05.982 2013 (UTC - 4:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    vrtaucbl.sys                Mon Feb 15 12:07:10 2010 (4B797F3E)
    RTKVHD64.sys                Tue May 24 08:32:39 2011 (4DDBA567)
    Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)
    AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)
    GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
    netr28ux.sys                Fri Sep 28 06:54:34 2012 (506581EA)
    AtihdW86.sys                Tue Jan 15 15:41:28 2013 (50F5BEF8)
    dump_storahci.sys           Fri Mar  1 21:15:44 2013 (513160D0)
    hiber_storahci.sys          Fri Mar  1 21:15:44 2013 (513160D0)
    rzendpt.sys                 Mon Mar  4 01:48:30 2013 (513443BE)
    rzudd.sys                   Mon Mar  4 01:48:31 2013 (513443BF)
    rzvkeyboard.sys             Mon Mar  4 01:48:38 2013 (513443C6)
    rzdaendpt.sys               Mon Mar  4 01:48:41 2013 (513443C9)
    atikmpag.sys                Wed Mar 20 21:25:59 2013 (514A61A7)
    atikmdag.sys                Wed Mar 20 22:39:42 2013 (514A72EE)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Apr 23 12:13:34.655 2013 (UTC - 4:00)**************************
    acsock64.sys                Tue Jan 24 11:07:18 2012 (4F1ED736)
    X6va012                     Wed Jan 30 00:34:19 2013 (5108B0DB)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr 17 21:06:11.830 2013 (UTC - 4:00)**************************
    AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
    intelide.sys                Wed Jul 25 22:29:52 2012 (5010ABA0)
    X6va011                     Tue Sep 11 01:16:02 2012 (504EC912)
    atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
    atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr  3 11:27:45.068 2013 (UTC - 4:00)**************************
    hiber_storahci.sys          Wed Jul 25 22:30:35 2012 (5010ABCB)
    dump_storahci.sys           Wed Jul 25 22:30:35 2012 (5010ABCB)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Mar 31 18:40:44.148 2013 (UTC - 4:00)**************************
    rtwlane.sys                 Thu Jun 21 00:45:30 2012 (4FE2A6EA)
    rzendpt.sys                 Wed Nov  7 02:49:46 2012 (509A129A)
    rzudd.sys                   Wed Nov  7 02:49:47 2012 (509A129B)
    rzvkeyboard.sys             Wed Nov  7 02:49:55 2012 (509A12A3)
    rzdaendpt.sys               Wed Nov  7 02:49:58 2012 (509A12A6)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=vrtaucbl.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=netr28ux.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=hiber_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
    http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    acsock64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    X6va012 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
    http://www.carrona.org/drivers/driver.php?id=intelide.sys
    X6va011 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=hiber_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    rtwlane.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
    http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 474
    Win 8 (64) : Win 7 (64) : Vista (64) : Android JB 4.2 : iOS 6


    Quote Originally Posted by usasma View Post
    You have a NETGEAR WNDA4100 N900 Wireless Dual Band USB Adapter:
    I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
    These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
    Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
    An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
    - Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
    05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cras...ing-sleep.html
    27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.
    These devices are disabled:
    Based on my previous experiences with this sort of combination, I suggest:
    - Temporarily uninstalling the Cisco AnyConnect software
    - Enabling the Asus wireless LAN PCI-E card and updating it's drivers
    - uninstalling the NETGEAR wireless USB network card and physically removing it from the system
    - test to see if this stops the BSOD's (and the wakeup problem).

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [S] DuplexSecure - FAQ [/S] Link broken as of 21 Jul 2012
    New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
    Alternate link: Disc-Tools.com
    Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    The last 4 memory dumps blame netr28ux.sys - a wireless driver
    While the first 2 blame atikmpag.sys - a video driver
    I suspect that the wireless USB/Cisco stuff is the main cause, while Daemon Tools and AMD OverDriver are also to blame.
    Please follow the advice above to fix these issues.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
    Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys

    vrtaucbl.sys Mon Feb 15 12:07:10 2010 (4B797F3E)
    Virtual Audio Cable (WDM)
    http://www.carrona.org/drivers/driver.php?id=vrtaucbl.sys

    RTKVHD64.sys Tue May 24 08:32:39 2011 (4DDBA567)
    Realtek High Definition Audio Function Driver
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys

    Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    Realtek PCI/PCIe Adapters
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Wed Apr 24 14:50:05.982 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042413-10530-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:0 days 15:51:33.167
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa80089773c0, fffff80369e99770, fffffa800b041660}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80089773c0, Physical Device Object of the stack
    Arg3: fffff80369e99770, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800b041660, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      BIOS Version                  P1.70
      BIOS Release Date             10/12/2012
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Apr 23 12:13:34.655 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042313-12885-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:5 days 13:47:33.936
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa8008962060, fffff80370cac770, fffffa800b05b150}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8008962060, Physical Device Object of the stack
    Arg3: fffff80370cac770, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800b05b150, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr 17 21:06:11.830 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041713-9796-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:1 days 23:12:51.892
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa8008984060, fffff803cf8c0b40, fffffa800af2e880}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8008984060, Physical Device Object of the stack
    Arg3: fffff803cf8c0b40, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800af2e880, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr  3 11:27:45.068 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\040313-9921-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 13:40:03.527
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    Probably caused by :usbhub.sys
    BugCheck 9F, {3, fffffa8007ca2060, fffff801dcfb9760, fffffa80117d6610}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8007ca2060, Physical Device Object of the stack
    Arg3: fffff801dcfb9760, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa80117d6610, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_netr28ux_IMAGE_usbhub.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Mar 31 18:40:44.148 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\033113-8860-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:1 days 0:15:54.983
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by :atikmpag.sys ( atikmpag+9410 )
    BugCheck 116, {fffffa800aee5010, fffff88007ace410, 0, d}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa800aee5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88007ace410, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Mar 27 21:39:51.031 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032713-8486-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 1:22:04.799
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by :atikmpag.sys ( atikmpag+9410 )
    BugCheck 116, {fffffa8007fe14d0, fffff88007e3b410, 0, d}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: fffffa8007fe14d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88007e3b410, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
      BIOS Version                  P1.20
      BIOS Release Date             11/17/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Wed Apr 24 14:50:05.982 2013 (UTC - 4:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    vrtaucbl.sys                Mon Feb 15 12:07:10 2010 (4B797F3E)
    RTKVHD64.sys                Tue May 24 08:32:39 2011 (4DDBA567)
    Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)
    AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)
    GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
    netr28ux.sys                Fri Sep 28 06:54:34 2012 (506581EA)
    AtihdW86.sys                Tue Jan 15 15:41:28 2013 (50F5BEF8)
    dump_storahci.sys           Fri Mar  1 21:15:44 2013 (513160D0)
    hiber_storahci.sys          Fri Mar  1 21:15:44 2013 (513160D0)
    rzendpt.sys                 Mon Mar  4 01:48:30 2013 (513443BE)
    rzudd.sys                   Mon Mar  4 01:48:31 2013 (513443BF)
    rzvkeyboard.sys             Mon Mar  4 01:48:38 2013 (513443C6)
    rzdaendpt.sys               Mon Mar  4 01:48:41 2013 (513443C9)
    atikmpag.sys                Wed Mar 20 21:25:59 2013 (514A61A7)
    atikmdag.sys                Wed Mar 20 22:39:42 2013 (514A72EE)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Apr 23 12:13:34.655 2013 (UTC - 4:00)**************************
    acsock64.sys                Tue Jan 24 11:07:18 2012 (4F1ED736)
    X6va012                     Wed Jan 30 00:34:19 2013 (5108B0DB)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr 17 21:06:11.830 2013 (UTC - 4:00)**************************
    AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
    intelide.sys                Wed Jul 25 22:29:52 2012 (5010ABA0)
    X6va011                     Tue Sep 11 01:16:02 2012 (504EC912)
    atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
    atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr  3 11:27:45.068 2013 (UTC - 4:00)**************************
    hiber_storahci.sys          Wed Jul 25 22:30:35 2012 (5010ABCB)
    dump_storahci.sys           Wed Jul 25 22:30:35 2012 (5010ABCB)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Mar 31 18:40:44.148 2013 (UTC - 4:00)**************************
    rtwlane.sys                 Thu Jun 21 00:45:30 2012 (4FE2A6EA)
    rzendpt.sys                 Wed Nov  7 02:49:46 2012 (509A129A)
    rzudd.sys                   Wed Nov  7 02:49:47 2012 (509A129B)
    rzvkeyboard.sys             Wed Nov  7 02:49:55 2012 (509A12A3)
    rzdaendpt.sys               Wed Nov  7 02:49:58 2012 (509A12A6)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=vrtaucbl.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=netr28ux.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=hiber_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
    http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    acsock64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    X6va012 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
    http://www.carrona.org/drivers/driver.php?id=intelide.sys
    X6va011 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=hiber_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    rtwlane.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
    http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
    I wanted to rep you but I couldn't... just wann say very impressive response. Cheers!
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Thanks! It's nice to hear!
      My System SpecsSystem Spec

  5. #5


    Posts : 250
    Windows 7 Home Premium 64 Bit


    Quote Originally Posted by fourthofjuly View Post
    I wanted to rep you but I couldn't... just wann say very impressive response. Cheers!
    I've done that... on your behalf
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Thanks koolkat77!
      My System SpecsSystem Spec

  7. #7


    Posts : 250
    Windows 7 Home Premium 64 Bit


    Quote Originally Posted by usasma View Post
    Thanks koolkat77!
    You're always welcome
      My System SpecsSystem Spec

Driver Power State Failure
Related Threads
Power Driver State Failure in BSOD Crashes and Debugging
Turning on the computer or after some time of use sometimes gives the BSOD power_driver_state_failure. after resetting it usually enters the windows. Could anyone help me with this problem?
Hey, I got some BSOD problems. Do you got time & experience to help me? :) I got Windows 8 at the moment, I will install 8.1 shortly. Had 8.1 before i re-installed OS when the first BSOD showed up, so I doubt that 8.1 will fix things completely. My problems ATM! - Driver Power State...
Hello.I am new here so please excuse me for any mistake i might make. Just when i sing in my account i get an error and my laptop restarts. My operating system is windows 8. I have collected all the information you might need with SF diagnostic tool. 48873 Hope you help me.
Driver Power State Failure in BSOD Crashes and Debugging
I shut down my laptop as I usually do, but I was short in time, so I didn't watch it turn off. When I came back home a few hours later, I found it turned on, showing the lock screen. Apparently it had a BSOD while it was shutting down and then restared. I ran bluescreen view and it said it was a...
Driver Power State Failure in BSOD Crashes and Debugging
I just got a BSoD with the error as DRIVER_POWER_STATE_FAILURE. I have attached the logs. Also, I was googling for this and one site told to run sigverif. The output for that is also attached. The second and third one are okay because I allowed them to install. They are a custom trackpad...
power driver State failure in Drivers & Hardware
Hello I m using Intel base pc but after installation of windows 8 I m facing a problem...... when I start my pc after boot it's show blue screen " power driver State failure" what is men pleases help me any one my system configuration is below and I am put the link of my sky Drive there is...
Driver Power State Failure in BSOD Crashes and Debugging
Hey all, I just put Windows 8 Professional 32-Bit on my Gateway M100-E laptop. It seems to crash when it is restarted and it's power state has changed. As in from battery to power cord and vice-versa. The BSOD tells me the error is called a driver power state failure. This laptop is 100% stock...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook