Windows 8 and 8.1 Forums


Driver_Power_State_Failure - Recurring every few hours

  1. #1


    Posts : 1
    Windows 8.1 64 bit

    Driver_Power_State_Failure - Recurring every few hours


    Hi all,

    New to the forum, but I have seen you guys help with similar driver power state failure issues. So thanks for looking!

    BSOD occurring every few hours, seemingly at random. It doesn't seem to matter whether the computer is idling or whether I am running a lot of applications.

    Tried some of the other self-help guides for this issue and haven't been able to find anything (for example, no issues appear under Device Manager).

    Windows 8.1, 64-bit, running two nvidia cards in sli (would not be surprised if the issue is related to either/both graphic cards). I will attach the SF diagnostic file. Please let me know if there is any other info I can provide.

    Thanks again for looking!

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Dhartun1 & Welcome to the forums ^_^,

    I have analyzed your dump files and below has been given an analysis to it :-
    Code:
    **************************Tue Jul 29 19:08:44.702 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
     
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe001ce8bd2a0, fffff8011098d930, ffffe001cf13b820}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jul 29 08:21:52.997 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
     
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe00162550060, fffff8014f58d930, ffffe00161360090}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jul 28 07:07:33.071 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe0015be5e060, fffff802a6594c80, ffffe00160631130}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  EoCApp.exe
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 06:12:12.818 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
     
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe00034de0060, fffff801f538d930, ffffe00034f849a0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jul 24 18:41:11.572 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
     
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe0000dafd610, fffff80365b8d930, ffffe0000bc5c010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jul 24 12:34:39.367 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
     
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe00033b16610, fffff801a8b8d930, ffffe00034ca59c0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jul 23 04:08:25.283 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
     
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe00024ff8610, fffff803f058d930, ffffe00020bb8310}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jul 22 22:01:34.107 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe001bd70f610, fffff803def8d930, ffffe001bde9cc10}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jul 21 19:45:00.436 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
     
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe000ffbe8060, fffff8021438d930, ffffe000ff17d090}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jul 20 15:02:52.678 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atapi.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
     
    Probably caused by : atapi.sys
     
    BugCheck 9F, {3, ffffe0007d87f060, fffff803f778d930, ffffe0007fbb6680}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
     
    BUGCHECK_STR:  0x9F
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_atapi.sys
     
    MaxSpeed:     3300
     
    CurrentSpeed: 3310
     
      BIOS Version                  F1
     
      BIOS Release Date             05/20/2011
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  Z68XP-UD4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Below is a list of 3rd party drivers present on your system :-
    Code:
    **************************Tue Jul 29 19:08:44.702 2014 (UTC + 5:30)**************************
    wdcsam64.sys                Wed Apr 16 14:09:08 2008 (4805BB2C)
    LVUSBS64.sys                Sat Jul 26 20:36:36 2008 (488B3D7C)
    HECIx64.sys                 Wed Oct 20 05:03:43 2010 (4CBE2AD7)
    GEARAspiWDM.sys             Fri May  4 01:26:17 2012 (4FA2E2E1)
    igdkmd64.sys                Thu Dec 13 06:12:26 2012 (50C92472)
    Rt630x64.sys                Fri May 10 15:29:08 2013 (518CC4EC)
    dtsoftbus01.sys             Thu Jun 20 12:52:51 2013 (51C2ADCB)
    intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
    ctxusbm.sys                 Mon Sep  9 21:32:22 2013 (522DF10E)
    avkmgr.sys                  Mon Sep 16 16:44:23 2013 (5236E80F)
    nvhda64v.sys                Thu Nov 28 19:08:09 2013 (52974741)
    WinDivert.sys               Tue Dec  3 09:16:09 2013 (529D5401)
    xusb22.sys                  Tue Mar 18 13:48:41 2014 (53280161)
    avipbb.sys                  Thu Mar 20 13:16:51 2014 (532A9CEB)
    nvvad64v.sys                Fri Mar 28 19:02:06 2014 (533579D6)
    avgntflt.sys                Wed Apr 30 22:04:29 2014 (53612615)
    NvStreamKms.sys             Thu May 22 22:13:14 2014 (537E2922)
    nvlddmkm.sys                Fri Jun 13 05:48:13 2014 (539A4345)
    http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
    http://www.carrona.org/drivers/driver.php?id=LVUSBS64.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.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=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
    http://www.carrona.org/drivers/driver.php?id=avkmgr.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    WinDivert.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=xusb22.sys
    http://www.carrona.org/drivers/driver.php?id=avipbb.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=avgntflt.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

    Further analysis reveals that the components blamed are the "disk.sys", "partmgr.sys" & "atapi.sys" which are drivers related to the Storage.
    Please follow the instructions below, one step at a time and checking if BSOD's stop or not :-

    1. I have highlighted a driver in RED as it is very popular to cause BSOD's. It belongs to the Western Digital Software. Please remove any Western Digital software from your system. If you are not able to find the software then delete this driver by manually searching for it in your system.
    2. Update your Logitech Web Camera Driver.
    3. If the problem is still not solved then remove Avira using this **TOOL**.


    Let me know how it goes ^_^.
      My System SpecsSystem Spec

Driver_Power_State_Failure - Recurring every few hours
Related Threads
Recurring multiple BSODs, almost every day in BSOD Crashes and Debugging
Hello, For years my asus laptop is giving me bsods. I've tried everything - hardware check (everything is ok, says the service, memory was tested for 12 hours - also ok). I've updated every driver using multiple software (driver navigator, driver detective, etc.). Tried rerolling nvidia driver...
Solved Recurring BSODs on new 8.1 64 build in BSOD Crashes and Debugging
Please help! I just put together a new 8.1 system and it seems to randomly BSOD me every few hours. It also has had issues with Windows Update - still not updating KB2919907. ...not sure if they are related. I've update all the MoBo drivers as well as the BIOS. Thanks!
Recurring BSOD: whea_uncorrectable_error in BSOD Crashes and Debugging
For some months ago I bought a Samsung 9 series (NP900X3D) and I've been having some problems with it from the start. I'm not currently residing in the country where I bought it, so there's problems with the warranty - also I need it for school, so sending it in is not an option (yet). I keep...
In the past I have gotten this same BSOD on rare occasions (and was too busy/not bothered enough to troubleshoot in-depth outside of updating my GPU drivers), but recently (perhaps right when I hooked up my new 22" monitor to replace my old 19", but I'm not exactly sure) it has started happening a...
Recurring Watchdog Violation in BSOD Crashes and Debugging
Hi guys, I'm at my wit's end with the SAME BSOD. I've already run memtest (for 8 passes, overnight), chkdsk, removed drivers and updated others, Intel processor check utility (yes I know it's not so good but I just wanted to cover everything). I'm pretty sure it more of a driver issue since...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook