Windows 8 and 8.1 Forums


BSOD, seems to be random, POWER STATE FAILURE

  1. #11


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


    How you progress is based on how confident you are with your ability to flash the BIOS.
    There's no harm in waiting, so it'd be safer to just update the Intel Management Engine and then wait.

    While waiting, you can also work on updating these drivers to the latest, Win8.1 compatible versions:

    Code:
    aar81xx.sys          Thu Feb 23 16:53:54 2012 (4F46B572) 
    lvrs64.sys           Mon Oct 22 22:11:24 2012 (5085FCCC) 
    lvuvc64.sys          Mon Oct 22 22:12:08 2012 (5085FCF8) 
    Rt630x64.sys         Fri May 10 05:59:08 2013 (518CC4EC)
    aar81xx.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. Most likely associated with an Adaptec Serial ATA controller driver.
    http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
    http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys

      My System SpecsSystem Spec

  2. #12


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


    Just a thought here, but check and see which ports the hard drives/SSD's are plugged into.
    If any are plugged into the port that uses the Adaptec controller (the one that uses the aar81xx.sys driver) - that might be a cause for a compatibility issue
      My System SpecsSystem Spec

  3. #13


    Posts : 13
    Windows 8.1 Pro


    Attempted to update the intel driver I got from your one drive. downloaded twice and got this result attempting to install

    ---------------------------
    Error
    ---------------------------
    C:\Drivers\Intel Management Engine Interface\data1.cab

    An error occurred while trying to copy a file:
    The source file is corrupted.

    Click Retry to try again, Ignore to skip this file (not recommended), or Abort to cancel installation.
    ---------------------------
    Abort Retry Ignore
    ---------------------------


    So I went to the Intel website and found a drive I believe to be new than the one I have, but not the latest driver.

    BIOS was updated to the latest non-beta update.

    At this point the only thing left is to run the Hardware diagnostics correct? So far so good, If it happens again, I will copy the Dump File in another location.

    I will update with results from the HW diagnostics when I complete them.

    Thanks for the assistance

    - Aeronerd
      My System SpecsSystem Spec

  4. #14


    Posts : 13
    Windows 8.1 Pro


    Looks like Adaptec doesn't have a driver for windows 8, I had the win 7 version. Ohh well, guess I will settle for 6 HDD drives.... Pulling the hardware, Updated all the drivers you listed. rechecked windows update. We will see if Adaptec was the culprit.

    - Aeronerd
      My System SpecsSystem Spec

  5. #15


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


    Good work! Now we wait and see...............
      My System SpecsSystem Spec

  6. #16


    Posts : 13
    Windows 8.1 Pro


    My apologies for not getting back sooner,

    Still pretty random, Where do you think we should go from here?

    -Aeronerd
      My System SpecsSystem Spec

  7. #17


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


    Have you had any further BSOD's?
    If not, wait for a week or two to be sure that they're gone

    If you have had more, then zip up the contents of C:\Windows\Minidump and upload it with your next post (you may have to copy it to the Desktop in order to zip it up).
      My System SpecsSystem Spec

  8. #18


    Posts : 13
    Windows 8.1 Pro


    Here ya go!
      My System SpecsSystem Spec

  9. #19


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


    The Adaptec driver (aar81xx.sys) showed up on 18 May, but hasn't been seen since.
    Probably a good thing!

    The problem here is if these were 2 separate, unrelated events - or if they were related.
    If related, the only thing left in common between them is Logitech and nVidia drivers (the others either aren't present, or have been updated)

    Here's what to do for the related stuff:
    So, let's start with the Logitech drivers. They are for a video camera.
    Either update them (and check to make sure that there is a later version) - or uninstall them and physically unplug the camera from your system (this is temporary until the BSOD's are stopped).

    As for the nVidia drivers, I'd suggest:
    - downloading a fresh copy of the latest, Win8.1 compatible drivers for your video card
    - uninstalling the current nVidia video card related stuff from your system
    - install the freshly downloaded drivers.
    If not related, then there's several more drivers to consider.
    It's also possible that there are further, hidden drivers (actually drivers that exited already) that are at the bottom of this.
    But more about that later on.

    Here's the other drivers to consider:
    nm3.sys - Network Monitor 3 NDIS 6.0 Monitoring Filter Driver
    vmm.sys - Virtual Machine Monitor driver
    leaslayr.sys - Windows Fabric Lease Layer Device Driver
    npf.sys - NetGroup Packet Filter Driver, part of the WinPcap packet capture library
    vhdparser.sys - Native VHD Parser (part of Windows)

    What virtual device programs do you have installed?
    Please uninstall them.
    If you don't have any, then please disable Hyper-V in Control Panel...Programs and Features...Turn Windows Features on and off (in the left sidebar).

    Please uninstall Network Monitor and the program that uses the NetGroup Packet Filter driver/WinPcap packet capture library

    I have no clue about the Windows Fabric thing - it's a server process that isn't used for much anything on users systems (although Lync Server does use it). We'll see what happens and will figure out then if we need to mess with it.

    Please double check that you have all applicable Windows Updates. Visit several times in order to be sure.

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Wed May 21 00:20:00.864 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052114-32765-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:55:31.561
    *** 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, ffffe0015b3ed060, fffff8031abdd930, ffffe001663b5980}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0015b3ed060, Physical Device Object of the stack
    Arg3: fffff8031abdd930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001663b5980, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 20 23:23:05.316 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052014-33078-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:56.012
    *** 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, ffffe0015d1b2060, fffff802527dd930, ffffe00162caf3c0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0015d1b2060, Physical Device Object of the stack
    Arg3: fffff802527dd930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00162caf3c0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 20 17:21:49.164 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052014-32296-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:07:24.860
    *** 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, ffffe0016a422060, fffff80078a03930, ffffe0016f4935b0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0016a422060, Physical Device Object of the stack
    Arg3: fffff80078a03930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0016f4935b0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 20 14:11:30.501 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052014-35671-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:11:03.197
    *** 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, ffffe001c4a44610, fffff8011efdd930, ffffe001ce6b4dc0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001c4a44610, Physical Device Object of the stack
    Arg3: fffff8011efdd930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001ce6b4dc0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 20 05:02:46.769 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052014-35328-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:55:54.465
    *** 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, ffffe0004f9ff060, fffff80081fe4c80, ffffe00053a16b00}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0004f9ff060, Physical Device Object of the stack
    Arg3: fffff80081fe4c80, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00053a16b00, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 20 02:56:49.865 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051914-41578-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:34:30.561
    *** 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, ffffe0008fa24060, fffff803441dd930, ffffe00095b06dc0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0008fa24060, Physical Device Object of the stack
    Arg3: fffff803441dd930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00095b06dc0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 20 02:20:18.264 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051914-42703-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:10:47.954
    *** 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, ffffe0017e7ef060, fffff8004afdd930, ffffe001842277d0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0017e7ef060, Physical Device Object of the stack
    Arg3: fffff8004afdd930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001842277d0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 18 10:19:12.322 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051814-32875-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 4:03:14.018
    *** 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, ffffe000991bb060, fffff8030e7dd930, ffffe0009e23a260}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000991bb060, Physical Device Object of the stack
    Arg3: fffff8030e7dd930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0009e23a260, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 18 06:14:28.348 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051814-42718-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 3:35:08.046
    *** 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, ffffe000bba26610, fffff803232c5930, ffffe000c4ef4810}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000bba26610, Physical Device Object of the stack
    Arg3: fffff803232c5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000c4ef4810, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 18 02:37:15.091 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-33296-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:53:33.789
    *** WARNING: Unable to verify timestamp for aar81xx.sys
    *** ERROR: Module load completed but symbols could not be loaded for aar81xx.sys
    Probably caused by :aar81xx.sys ( aar81xx+4933 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_aar81xx+4933
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 18 00:32:30.911 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-41640-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:26:56.608
    *** 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, ffffe001a5b2a610, fffff80356cc5930, ffffe001b312f160}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001a5b2a610, Physical Device Object of the stack
    Arg3: fffff80356cc5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001b312f160, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 12:11:16.090 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-35046-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:52.787
    *** 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, ffffe0011f627060, fffff802594c5930, ffffe001239f9a80}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0011f627060, Physical Device Object of the stack
    Arg3: fffff802594c5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001239f9a80, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 11:05:37.662 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-35062-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:52.360
    *** 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, ffffe001e1826060, fffff802c3ec5930, ffffe001e569f850}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001e1826060, Physical Device Object of the stack
    Arg3: fffff802c3ec5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001e569f850, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 09:59:58.714 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-36125-02.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:51.412
    *** 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, ffffe00106426060, fffff800e12c5930, ffffe0010a4047d0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00106426060, Physical Device Object of the stack
    Arg3: fffff800e12c5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0010a4047d0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 08:54:20.815 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-36265-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:53.512
    *** 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, ffffe0006c7f5060, fffff80291ac5930, ffffe00070531490}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0006c7f5060, Physical Device Object of the stack
    Arg3: fffff80291ac5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00070531490, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 07:48:40.860 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-36156-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:53.557
    *** 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, ffffe0008f7ba610, fffff802b3ac5930, ffffe0009490de10}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0008f7ba610, Physical Device Object of the stack
    Arg3: fffff802b3ac5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0009490de10, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 06:43:00.290 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-35234-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:55.987
    *** 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, ffffe000f5415060, fffff8023e4c5930, ffffe000f9723e10}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000f5415060, Physical Device Object of the stack
    Arg3: fffff8023e4c5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000f9723e10, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 05:37:18.058 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-36937-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:03:52.756
    *** 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, ffffe000e1634060, fffff800f78c5930, ffffe000e58498d0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000e1634060, Physical Device Object of the stack
    Arg3: fffff800f78c5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000e58498d0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 17 04:32:02.176 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051714-36125-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:45:56.874
    *** 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, ffffe001e2819060, fffff80215cc5930, ffffe001e596cac0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001e2819060, Physical Device Object of the stack
    Arg3: fffff80215cc5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001e596cac0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri May 16 11:55:50.085 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051614-53843-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 11:20:46.671
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :nvlddmkm.sys ( nvlddmkm+1a07f5 )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+1a07f5
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  F9
      BIOS Release Date             03/21/2012
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 15 07:05:25.154 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051514-50953-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 1:35:15.850
    *** 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, ffffe00033dc6610, fffff800246c5930, ffffe00033ef5dc0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00033dc6610, Physical Device Object of the stack
    Arg3: fffff800246c5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00033ef5dc0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  F2
      BIOS Release Date             03/25/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed May 14 07:43:19.418 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051514-54296-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:49:30.114
    *** 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, ffffe001029c5610, fffff800ec8c5930, ffffe00107eb5010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001029c5610, Physical Device Object of the stack
    Arg3: fffff800ec8c5930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00107eb5010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  F2
      BIOS Release Date             03/25/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 13 21:03:35.087 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051414-30453-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 1:03:15.783
    *** 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, ffffe000599cd060, fffff803364c1930, ffffe00059f55220}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000599cd060, Physical Device Object of the stack
    Arg3: fffff803364c1930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00059f55220, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  F2
      BIOS Release Date             03/25/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  P67X-UD3-B3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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 May 21 00:20:00.864 2014 (UTC - 4:00)**************************
    nm3.sys                Wed Jun  9 20:05:51 2010 (4C102C5F)
    HECIx64.sys            Thu Sep 22 12:38:44 2011 (4E7B6494)
    vmm.sys                Wed Dec 28 08:28:47 2011 (4EFB198F)
    leaslayr.sys           Mon Jul 23 23:07:45 2012 (500E1181)
    lvrs64.sys             Mon Oct 22 22:11:24 2012 (5085FCCC)
    lvuvc64.sys            Mon Oct 22 22:12:08 2012 (5085FCF8)
    npf.sys                Thu Feb 28 20:31:24 2013 (513004EC)
    intelppm.sys           Thu Aug 22 04:46:35 2013 (5215CFEB)
    Rt630x64.sys           Mon Sep  9 02:47:07 2013 (522D6EEB)
    nvhda64v.sys           Thu Nov 28 08:38:09 2013 (52974741)
    vhdparser.sys          Mon Jan 27 14:51:04 2014 (52E6B8A8)
    nvlddmkm.sys           Tue Mar  4 06:07:52 2014 (5315B408)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue May 20 05:02:46.769 2014 (UTC - 4:00)**************************
    Rt630x64.sys           Fri May 10 05:59:08 2013 (518CC4EC)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 18 06:14:28.348 2014 (UTC - 4:00)**************************
    aar81xx.sys            Thu Feb 23 16:53:54 2012 (4F46B572)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri May 16 11:55:50.085 2014 (UTC - 4:00)**************************
    HECIx64.sys            Tue Oct 19 19:33:43 2010 (4CBE2AD7)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 15 07:05:25.154 2014 (UTC - 4:00)**************************
    gdrv.sys               Thu Mar 12 23:22:29 2009 (49B9D175)
    cxbu0x64.sys           Thu Mar 20 08:00:07 2014 (532AD847)
    
    http://www.carrona.org/drivers/driver.php?id=nm3.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=vmm.sys
    leaslayr.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=lvrs64.sys
    http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
    http://www.carrona.org/drivers/driver.php?id=npf.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    [color]Driver Reference Table - vhdparser.sys[/COLOR]

    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    aar81xx.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=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=gdrv.sys
    cxbu0x64.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.
      My System SpecsSystem Spec

  10. #20


    Posts : 13
    Windows 8.1 Pro


    Just an update:

    nm3.sys - Network Monitor 3 NDIS 6.0 Monitoring Filter Driver - > Removed
    vmm.sys - Virtual Machine Monitor driver - > Uninstalled Hyper V
    leaslayr.sys - Windows Fabric Lease Layer Device Driver - > Not sure what this would apply to
    npf.sys - NetGroup Packet Filter Driver, part of the WinPcap packet capture library - >
    vhdparser.sys - Native VHD Parser (part of Windows) - > Not sure what to do on this one.

    As for the drives for Logitech, according to the website, is up to date. So I unplugged the web cam
      My System SpecsSystem Spec

Page 2 of 3 FirstFirst 123 LastLast
BSOD, seems to be random, POWER STATE FAILURE
Related Threads
BSOD Driver State Power Failure in BSOD Crashes and Debugging
Hi, I've been getting this BSOD error quite frequently now and I'm not sure what the problem is. I've attached the zip from the SF Debug Tool. Note: I have a modded BIOS for lower GPU voltages from L502X modded bioses download (GPU voltages and more!) and also have my GPU underclocked if...
I noticed https://www.eightforums.com/bsod-crashes-debugging/47857-bsod-driver-state-power-failure-randomly-new-asus-g750jm.html and decided I needed to come here and report my own error with my G750JM. It's only happened twice, but the second time sparked me to try and figure out whats causing the...
BSOD Power State Driver Failure in BSOD Crashes and Debugging
I just got my ASUS G750 from Bestbuy a few weeks ago. I've been encountering this same BSOD since I got it (after installing programs). Lately it seems to be happening when I close a game from the battle.net app and attempt to open another. Other than that it almost seems to happen completely at...
Driver Power State Failure BSOD in BSOD Crashes and Debugging
Hi I just recently got a BSOD on my laptop DRIVER_POWER_STATE_FAILURE. I'm also guessing this is the reason that my computer seems to not sleep consistently. Thanks
BSOD- Driver State Power Failure in BSOD Crashes and Debugging
After having to do a complete system restore (automatic repair loop) my computer now comes up with the Driver Power State Failure BSOD when restarting, shutting down and turning on normally works fine. I don't really want to try and navigate through all the windows updates as that requires a...
Driver power state failure (BSOD) in BSOD Crashes and Debugging
Hello, I made a thread about this already but no one would reply can someone help me please? I really want to get rid of this BSOD :cry: I want to know what the problem is, thanks http://sdrv.ms/14ltYEj edit: windows 8
Solved BSOD Driver Power State Failure (Win 8 x64) in BSOD Crashes and Debugging
I performed a clean install of Win 8 x64 from Win 7 x86. I have had freezes or bsods at the Metro screen if the computer sits unattended for awhile or goes to sleep. I have updated the BIOS to the latest version, am running defaults and not overclocked. I think it is a driver issue but I cant seem...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook