blue screen "driver_power_state_failure.

Similar Questions

• Windows 7 blue screen DRIVER_POWER_STATE_FAILURE ntoskrnl.exe

  Hi community

  I'm having a problem with my installation of Windows 7. When I try to shut down my pc, it still shows the blue screen with the message "DRIVER_POWER_STATE_FAILURE. I did research on the internet and discovered that this blue screen is above all connected to a driver problem. Then I updated some drivers at random, but it has not solved the problem for me. Could someone help me to analyze my Minidump file? I put it on OneDrive:

  https://onedrive.live.com/redir?RESID=A57FDA7761102DB1! 154 & authkey =! ALphxLeHKGmn8fM & ithint = the file % 2cdmp

  Thank you!

  A site shows the same stop error messageand it points to 5U877.sys camera Ricoh drivers, can cause this stop error

  This file is 5 years on your system. See if there is an update for it

• Many errors blue screen (DRIVER_POWER_STATE_FAILURE) 0x9f.

  Hi all!

  I get frequent 0x9f blue screen errors. I wonder if someone could kindly have a look to this dmp file?

  http://sdrv.Ms/18BCO18

  Very much appreciated.

  Darryl

  Hello

  The attached file of the DMP is the bugcheck DRIVER_POWER_STATE_FAILURE (9f).

  This error occurs if the drivers do not manage applications of transition from State power properly, usually during one of the following procedures: stop, suspend or exit from sleep, suspend or resume from hibernation mode.

  To your credit, I see 2 possible drivers problem.

  Cannot load the image \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys, 0n2 error Win32
  WARNING: Unable to verify timestamp for GEARAspiWDM.sys
  ERROR: Module load completed but symbols can be loaded for GEARAspiWDM.sys
  WARNING: Unable to verify timestamp for nvstor64.sys
  ERROR: Module load completed but symbols can be loaded for nvstor64.sys
  Probably caused by: nvstor64.sys

  GEARAspiWDM.sys also shows in the blocked address of PRI ~.

  GEARAspiWDM.sys = class by Gear Software CD-ROM filter driver. It also comes with iTunes.

  Update here - http://www.gearsoftware.com/support/drivers.php

  nvstor64.sys = nVidia storage (nForce chipset driver).

  Update here - http://www.nvidia.com/Download/index.aspx

  Keep me updated on the behavior of the system after doing the following.

  Kind regards

  Patrick

• Windows 7 blue screen: DRIVER_POWER_STATE_FAILURE STOP: 0x0000009f (0 x 00000003,... ntkrnlpa.exe)

  Hi all

  I got a blue screen today with my Windows 7 which is something disappointing and I don't want to do it again, can someone check the dump for me file and tell me what is the cause?

  ********************************************************************************
  The problem seems to be caused by the following file: ntkrnlpa.exe

  DRIVER_POWER_STATE_FAILURE

  Technical information:

  STOP: 0X0000009F (0 X 00000003, 0X8903B458, 0X83133AE0, 0X88B16008)

  Ntkrnlpa.exe - address 0x830eaf1c base at 0x8300c000 DateStamp 0x4f5583be

  ********************************************************************************

  I have:

  Intel i5 760
  4 GB of ram
  Windows 7 32 bit
  Comodo 5.10.228257.2253
  NOD32 4.2.71.2

  In case there is something wireless (I read something on this, but not sure!), I have:

  Device USB of TP-link wireless (& TP-link utility)
  SecurityKISS tunnel software
  proXPN vpn software

  Drivers:
  Microsoft virtual Wifi Miniport adaprot
  Realtek PCIe GBE controller (disabled)
  TP - LINK 150Mbps Wireless N adapter Lite
  Unknown device
  TP - LINK 150Mbps Wireless N adapter Lite

  VirtualBox has been running a win XP version that has Avast & Comodo

  At the point of issue, virtualbox was operating in full screen, Firefox open and no one to the PC (no action)

  I downloaded the dump file to:
  http://DepositFiles.com/files/q4ebw15vb
  Password: win7win

  Thank you

  Hello

  You have made any changes to your computer recently?

  I suggest you to follow the steps and check if it helps.

  Method 1: Disconnect all external devices except your mouse and your keyboard and check what is happening.

  Method 2:

  Step 1: Login to the Safe Mode and then check if it helps.

  Start your computer in safe mode

  Step 2: Perform a clean boot Hardware and a software clean boot, and then check if it helps.

  (a) click "Start" and type "DEVMGMT. MSC"in the search text box and press enter

  (b) develop "audio, video and game controllers".

  (c) right click on your sound card, select "Properties".

  (d) 'Pilot' click, click Disable the selected device. Click OK

  (e) Please use the same method to disable other devices such as: Modem, network card, CD - R drive. Please note that some devices such as the video card are not available should be disabled.

  (f) Please restart the computer.

  Note: do not forget to activate the devices to return after you complete your troubleshooting.

  Method 3: You can also check out the link and then check if it helps.

  Resolve stop (blue screen) error in Windows 7

• Windows 8 blue screen - DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

  I have a new Sony Vaio Pro and have experienced outages of system 3 times.  All the accidents that happened after I've restored from hibernation and were related to the bug check DRIVER_POWER_STATE_FAILURE.  After the first two accidents, I ran Sony diagnostics on the memory and hard drive SSD and they passed the test.  I even sent my Vaio Pro to the repair depot to Sony for a test on the memory, hard drive and other hardware and they all passed.

  I found my Vaio Pro last Wednesday and updated the Windows 8 from scratch.  This morning, after the resumption of hibernation, I realized my Bluetooth mouse did not work.  So I stop the laptop hoping a restart could solve the problem.  However, it took almost 5 minutes before they would stop and restart Windows gave a warning:

  "Experienced problem with closed Windows.  Your PC fell on problem.  This problem case your PC to restart.

  BlueScreen Viewer it pointing DRIVER_POWER_STATE_FAILURE caused by driver ntoskrnl.exe.

  BlueScreen details as follows:

  A problem has been detected and Windows has shut down to prevent damage to your computer.

  The problem seems to be caused by the following file: ntoskrnl.exe

  DRIVER_POWER_STATE_FAILURE

  If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

  Check to make sure any new hardware or software is installed correctly.

  If it is a new installation, ask your hardware manufacturer or software, the Windows updates, you might need.

  If problems continue, disable or remove any newly installed hardware or software. Disable the BIOS memory options such as implementing caching or shading.

  If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options and then

  select Safe Mode.

  Technical information:

  STOP: 0X0000009F (0X000000000000012C, 0XFFFFFA80196707C0, 0 X 0000000000000004, 0XFFFFF880009EC810)

  Ntoskrnl.exe - address 0xfffff80189072106 base at 0xfffff8018901e000 DateStamp

  0x51a966cd

  Here's my minidump file:

  https://DL.dropboxusercontent.com/u/1928780/093013-7531-01.dmp

  File Msinfo32.NFO:

  https://DL.dropboxusercontent.com/u/1928780/Msinfo32.nfo

  Dump file memory (do not know why this file is nearby big 550MO):

  https://DL.dropboxusercontent.com/u/1928780/memory.dmp

  p.s. I think this may have something to do with my Bluetooth driver I had experienced many times the Bluetooth driver has been disabled by Windows and the event viewer reported "the Local Bluetooth is not indeterminate way and will not be used.  The driver has been unloaded. "

  Thanks in advance,

  William

  Hi William,.

  The attached file of the DMP is the error checking DRIVER_POWER_STATE_FAILURE (9f) .

  This bug check indicates that the driver is in an inconsistent or invalid power state.

  9F, {4, 12 c, fffffa80196707c0, fffff880009ec810} error checking

  Parameter 1 of the bugcheck is 4 , which indicates that the transition of power over waiting to synchronize with the Pnp subsystem.

  The 2nd setting is 12 c , which indicates that it is exceeded for a total of 12 seconds.

  By default, the crash dump is failing UsbHub3.sys who is the pilot of HUB-USB3 (System driver and not the true cause, and is due to the fault by something else).

  If we look further into the dump:

  ERROR: Module load completed but symbols could not be loaded for btmhsf.sys

  FAILURE_BUCKET_ID: 0x9F_4_btmhsf_IMAGE_UsbHub3.sys

  Implicit thread is now fffffa80 196707 c 0

  ^^ If we run one! thread on the address fffffa80 196707 c 0:

  Child-SP RetAddr: Args to child: call Site
  fffff880 '20b42f20 fffff801' 890bb7cb: fffffa80'00000001 00000000'00000000 00000000'00000003 00000000'00000000: nt! KiSwapContext + 0 x 76
  fffff880 '20b 43060 fffff801' 890ba60f: fffffa80'18b23ef8 fffff880 '0115a 178 00000000 00000000' fffff880' 0622a 202: nt! KiCommitThreadWait + 0x23b
  fffff880'20 b 43120 fffff880'06114700: fffffa80 '16115fd8 fffff880' 00000001 00000000' 00000000 00000000'00000000: nt! KeWaitForSingleObject + 0x1cf
  "fffff880 '20b431b0 fffff880' 06117ef0: 00000000 ' 00000018 fffff880 ' 0622a2f8 00000000'00000000 00000000'00000018: btmhsf+ 0 x 33700
  fffff880 '20b431f0 fffff880' 060fb1e4: fffffa80'17 has 00030 fffff880 '20b433b0 fffff880' 0622a2f8 00000000' 00000000: btmhsf+ 0x36ef0
  fffff880 '20b 43260 fffff880' 060e2b84: 0000057f 'e9eaddd8 00000000' 00000127 fffff880 '0622a2f8 fffff880' 0115 has 178: btmhsf+ 0x1a1e4
  fffff880 '20b432b0 fffff880' 060e2cce: 00000000'00000008 fffff880 '20b 43370 00000000'00000008 fffff880' 20b 43378: btmhsf+ 0x1b84
  fffff880 '20b432e0 fffff880' 0114ecb0: fffffa80'16153860 00000000 00000000' fffff8a0 '04c3a748 fffff801' 89403cfe: btmhsf+ 0x1cce
  "fffff880 '20b 43310 fffff880' 010e881d: 00000000 ' 00000127 fffff880 ' 20b433b0 00000000'00000119 fffffa80'16153860: Wdf01000! FxPkgPnp::PnpEventSurpriseRemoveIoStarted + 0x2c
  "fffff880 '20b 43340 fffff880' 010e9032: fffffa80 ' 16153980 fffffa80' 16153988 fffffa80 ' 16153860 fffff880 ' 20b434c0: Wdf01000! FxPkgPnp::PnpEnterNewState + 0x1a1
  "fffff880 '20b433e0 fffff880' 010e8cdd: 00000000 ' 00000000 fffff880 ' 20b434c0 fffffa80 ' 16153970 fffffa80' 16153860: Wdf01000! FxPkgPnp::PnpProcessEventInner + 0 x 122
  fffff880'20 b 43450 fffff880'0114 701 d: 00000000 00000000' fffffa80 '16153860 fffff880' 00000000 00000000 00000000': Wdf01000! FxPkgPnp::PnpProcessEvent + 0x18d
  fffff880 '20b434f0 fffff880' 010d1ecf: fffffa80'16141 b 30 fffff880 '20b 43570 00000000 00000000' fffffa80' 1615d1d0: Wdf01000! FxPkgFdo::_PnpSurpriseRemoval + 0 x 25
  fffff880 '20b 43520 fffff880' 010c99da: fffffa80'197 b 9010 fffffa80 '197b 9010 fffffa80' 197b 9010 00000000 00000000': Wdf01000! FxPkgPnp::Dispatch + 0x18f
  "fffff880 '20b 43580 fffff880' 010c9aa6: fffffa80' 197b 9010 00000000'00000005 fffffa80 ' 161531 c 0 fffff880 ' 062fca20: Wdf01000! FxDevice::Dispatch + 0x19a
  fffff880 '20b435c0 fffff880' 062e3cbe: fffffa80 '197b 9010 00000000 00000005' fffffa80' 1615e190 00000000' 00000000: Wdf01000! FxDevice::DispatchWithLock + 0xa6
  fffff880 '20b 43600 fffff880' 062e3484: fffffa80 '197b 9010 00000000 00000000' fffffa80' 1615e190 00000000' 00000000: bthport! BthDefaultPnpHandler + 0x2a
  fffff880 '20b 43630 fffff880' 062e2cc1: fffffa80 ' 1615e190 fffff880 '062fca17 fffffa80' 1615e190 fffffa80 ' 197b 9010: bthport! BthHandleSurpriseRemoval + 0xc4
  fffff880 '20b436b0 fffff880' 062e2b04: fffffa80' 197b 9010 00000000'00000701 fffff880 '062fca20 fffff880' 20b 43800: bthport! BthHandlePnp + 0x16d
  fffff880 '20b 43700 fffff801' 8940a8f7: fffffa80 '1615e040 00000000' c00000bb 00000000 00000000' fffff880' 00a 82180: bthport! BthDispatchPnp + 0 x 68
  "fffff880'20 b 43750 89526 fffff801 39 d: 00000000 ' 00000017 fffff880 ' 20b 43819 fffffa80 ' 16137710 fffffa80' 16137060: nt! IopSynchronousCall + 0xc7
  fffff880 '20b437c0 fffff801' 895265e6: fffff8a0 ' 04069710 00000000'00000308 fffffa80' 16137060 00000000 00000000': nt! IopRemoveDevice + 0xd9
  fffff880'20 b 43880 fffff801'89526501: fffffa80'16137710 00000000 00000000' fffff8a0 '0c432a01 fffff880' 20b 43930: nt! PnpSurpriseRemoveLockedDeviceNode + 0xaa
  fffff880'20b438d0 fffff801'89526468: fffff8a0 00000000'00000000 00000000'00000000 ' 0c432a70 fffffa80'16137710: nt! PnpDeleteLockedDeviceNode + 0x5d
  fffff880 '20b 43910 fffff801' 89525bcb: 00000000 00000000' fffff880 '20b43a70 fffff8a0' 0b89e6f0 00000000'00000005: nt! PnpDeleteLockedDeviceNodes + 0 x 98
  fffff880 '20b 43970 fffff801' 893b52e5: fffff880'20b43b88 00000000 00000000' fffff8a0 ' 05764100 fffff8a0' 00000000: nt! PnpProcessQueryRemoveAndEject + 0x2c3
  fffff880'20b43ae0 fffff801'89418346: fffff8a0'04069710 00000000'00000000 00000000'00000001 00000000'00000000: nt! PnpProcessTargetDeviceEvent + 0x9d
  "fffff880 '20b43b20 fffff801' 890b62a1: fffffa80 ' 196707 c 0 fffff8a0 ' 0b89e6f0 fffff801 ' 8941805 c fffffa80' 16748130: nt! PnpDeviceEventWorker + 0x2ea
  "fffff880 '20b43b80 fffff801' 8904afd9: fffffa80 ' 00180000 00000000 00000080' fffff801 ' b 890, 6160 fffffa80 196707 c 0: nt! ExpWorkerThread + 0 x 142
  fffff880 '20b43c10 fffff801' 890ff7e6: fffff880 ' 00a 82180 fffffa80 ' 196707 c 0 fffffa80 ' 06741b 00 fffffa80' 06765940: nt! PspSystemThreadStartup + 0 x 59
  fffff880'20b43c60 00000000' 00000000: fffff880 '20b 44000 fffff880' 20b3e000 00000000'00000000 00000000'00000000: nt! KiStartSystemThread + 0x16

  We can see the various routine calls BTHUSB Device bthport.sys (Bus Bluetooth driver) who then finally enter various before btmhsf.sys some error checking.

  btmhsf.sys is the Intel Proset Bluetooth HighSpeed filter driver and probably the culprit here. Update this driver ASAP - http://downloadcenter.intel.com/default.aspx?iid=gg_support-EN_01+home_downloadctr
  or uninstall it if you do not plan to use BlueTooth.

  ---------------------------------------------------------------------

  If after doing the above, you are still blocked, remove and replace AVG with built-in Windows Defender from Windows 8 for temporary troubleshooting purposes:

  -AVG removal tool http://www.Avg.com/us-en/utilities

  In addition, to answer your question as to why the MEMORY. DPM is so important because it's a dump of memory rather than a small kernel. Kernel memory dumps contain all the kernel memory was working with and that was in use at the time of the accident, that is why it is larger and provides much more information.

  Kind regards

  Patrick

• Error on blue screen DRIVER_POWER_STATE_FAILURE

  Whenever I try to play a game, my computer hangs and goes the BSOD, DRIVER_POWER_STATE_FAILURE, fifteen minutes by playing 'Minecraft', I don't know how to solve this problem. I have the files of dump, according to me, if that would help. I'm not completely sure how to access it.

  Can someone help me solve this problem?

  Hello

  Well it is possible but just not very likely.

  Since it is a laptop, I think the main problem of the lack of power in
  the video device.

  Rob - SpiritX

• Ntoskrnl.exe causing blue screen saying "DRIVER_POWER_STATE_FAILURE" in Windows Vista

  At random intervals (and I mean, it may happen by week or 1This 2This every 2 months) I get a blue screen.  I said "DRIVER_POWER_STATE_FAILURE" and made a dump.  It doesn't happen ever if I'm doing something important, like writing a paper for school or by downloading a video for a class online.

  So far, I have:

  • Analysis of material of Ran
  • New Windows Vista installation with all updates for the OS and programs
  • Installed on another hard drive with all the updates to the OS and core programs

  Nothing has worked so far.

  My Info to the computer:

  http://S217.Photobucket.com/albums/cc205/psychobarbiehaxor/?action=view¤t=Compinfo.jpg

  The file of errors:

  http://S217.Photobucket.com/albums/cc205/psychobarbiehaxor/?action=view¤t=ErrorInfo.jpg

  Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE

  DRIVER_POWER_STATE_FAILURE bug control has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.

  http://msdn.Microsoft.com/en-us/library/ff559329%28VS.85%29.aspx

  Please copy the files of the dmp to the C:\Windows\Minidump folder first on your desktop, zip dmp all in 1 zip file and download the zipfile to your Skydrive [1] and post a link here, so that I can look at landfills.

  André

  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 [1]

  "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• Blue screen in Windows 7 DRIVER_POWER_STATE_FAILURE

  Over the last few weeks I've seen 'The death' blue screen for something about 5 times. His mistake is about "DRIVER_POWER_STATE_FAILURE. I don't know why this happens, but this is the "technical information" mentioned in:
  ...........

  //////////////////////////////////////////////////////////////////////

  STOP: 0X0000009F (0XFFFFFA800672E980, 0XFFFFF80000B9C3D8, 0 X 0000000000000003, 0XFFFFFA800C765E10)

  We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
  Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here
  If you have any questions regarding the procedure, please ask

• Blue screen 0x0000009f DRIVER_POWER_STATE_FAILURE death in newly acquired ASUS laptop computer g750JM

  Hi, I get a blue screen of death every time in a while for no discernible reason. I've had this laptop for about 2 weeks, I just received my third blue screen of death about an hour ago. The location of the address is the same, bug control code, the driver is ntoskrnl.exe

  Landfills are:

  https://www.dropbox.com/sh/w7k1x6zs8c7i4bz/AADWTHwEluQNtq1gExw2rgB3a

  I hope someone can help

  Hello

  I've been scouring the internet for weeks looking for help with my BSOD problems.  I finally made a discovery that fixed it all and thought I'd share it with as many people as possible.

  Some background on my question:

  I installed the 337,88 and the beta drivers but kept on getting random BSOD due a DRIVER_POWER_STATE_FAILURE.  I watched the dump file and debugged myself as BlueScreenviewer offered no answers for me.  He showed a driver ntoskrnl.exe and dig more pci.sys has shown to be the culprit, but this may not be true.  More digging in the minidump gave nviddmkm.sys, so naturally I thought it was a driver problem. (I have a background inproramming, so I was able to do a pretty thorough analysis of the file).  I installed the 332,50 drivers and no more problems.  However, I was not satisfied with this solution.  I did more research on the internet and several other cases have been solved by powering down of overclocking.  I had already uninstalled GPUTweak, so what else could it be?

  Well, the BIOS has the answers.  Here is my solution:

  1. turn off your laptop.  (Full stop)
  2. press the power button.
  3. quickly and repeatedly hit the F2 key to enter the BIOS setup.
  4. go to the "Advanced" tab
  5 scroll down to "Graphical Configuration" and press the Enter"" key.
  6. highlight "Turbomaster setting" and press the Enter"" key.
  7. you will see two options, 'Activate' and 'Disable', choose 'disable '.
  8. Finally, press the "Esc" key and go to the tab "Quit" and "save changes and exit".

  You can now install the latest drivers without experiencing a BSOD.  I hope I helped.  If you guys have any questions be sure to ask me, I'l answer to the best of my ability.

• Blue screen on stop ntoskrnl.exe DRIVER_POWER_STATE_FAILURE

  My computer blue screened twice now having been to "Shutting down" screen for a few minutes.

  I downloaded the 2 .dmp files that I found using BlueScreenView onedrive here:

  http://1drv.Ms/1ElvK85

  Can someone tell me what is the cause, or how I might solve this problem?

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You need not run memtest again unless you want to.
  

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  
  2-Memtest. (You can learn more about running memtest here)

  
  

• Blue Screen Server 2008 R2 sp1

  My main DC server 2008 r2 sp1 guard blue screening every time that I reboot it. My other servers (a backup domain controller and exchange) blue screen occasionally. All with the same Memory.dmp. Everything seems to point to highlight words:

  FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_msisadrv_IMAGE_pci.sys

  Except that I have no idea what it means. I speculate its our new antivirus, but my colleagues are not all blue screening on their servers.

  Any ideas?

  *****************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  DRIVER_POWER_STATE_FAILURE (9f)
  A pilot was not a power of the PRI ends in a moment.
  Arguments:
  Arg1: 0000000000000003, a device object has been blocking an Irp for too long
  Arg2: fffffa8006e52a30, physical device from the stack object
  Arg3: fffffa8006e5c8d0, nt! TRIAGE_9F_POWER on Win7 and higher, otherwise the functional device object of the stack
  Arg4: fffffa80105f4010, blocked IRP

  Debugging information:
  ------------------

  DRVPOWERSTATE_SUBCODE: 3

  Nom_image: pci.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 49e024a5

  MODULE_NAME: pci

  FAULTING_MODULE: fffffa6000b98000 pci

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  BUGCHECK_STR: 0X9F

  Nom_processus: System

  CURRENT_IRQL: 2

  ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

  DPC_STACK_BASE: FFFFF800087F2FB0

  STACK_TEXT:
  fffff800 '087ec9f8 fffff800' 06d09fcd: 00000000' 0000009f 00000000 00000003' fffffa80 '06e52a30 fffffa80' 06e5c8d0: nt! KeBugCheckEx
  fffff800 '087eca00 fffff800' 06cb0ddd: fffff800'087ecad8 00000000'00000000 00000000'00000001 00000000'00000000: nt! : FNODOBFM: 'string' + 0x17dac
  fffff800 '087eca70 fffff800' 06cb0518: fffff800 '087eccd0 00000000'00000002 fffff800' 087eccc8 00000000 00000001': nt! KiTimerListExpire + 0x30d
  "fffff800 '087ecca0 fffff800' 06cb142f: 0005786d ' 9859f4df 00000000 00000000' fffff800 ' 00000001 fffff800 ' 06dcca80: nt! KiTimerExpiration + 0x1d8
  fffff800 '087ecd10 fffff800' 06cb15e2: fffff800'06dc9680 fffff800 '06dc9680 00000000 00000000' fffff800' 06dceb80: nt! KiRetireDpcList + 0x1df
  fffff800 '087ecd80 fffff800' 06e81860: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiIdleLoop + 0 x 62
  fffff800 '087ecdb0 00000000' fffff800: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! zzz_AsmCodeRange_End + 0x4
  fffff800 '087e60b0 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00680000'00000000: 0xfffff800

  STACK_COMMAND: kb

  FOLLOWUP_NAME: MachineOwner

  IMAGE_VERSION: 6.0.6002.18005

  FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_msisadrv_IMAGE_pci.sys

  BUCKET_ID: X64_0x9F_3_POWER_DOWN_msisadrv_IMAGE_pci.sys

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_msisadrv_image_pci.sys

  FAILURE_ID_HASH: {4e4cdde5-e9bc-4287-9ca9-0975bad2a519}

  Follow-up: MachineOwner
  ---------

  Hi Jenny,

  The question you have posted is related to Windows Server 2008 and would be better suited to the TechNet community. Please visit the link below to find a community that will provide the best support.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  Thank you.

• STATE of POWER FAILURE DRIVER Blue Screen of Death

  I m getting error after reboot please help me...

  http://www.techsupportforum.com/forums/f299/DRIVER_POWER_STATE_FAILURE-600594.html#post3437627

  PLS, get the files from this dump... Pls in the case where no update more... .pls answer...

  where to download the files, though these could not get?

  Hello

  We cannot access the minidump here unless we partner who I don't want to do. Please download the minidumps
  to your SkyDrive or other file sharing sites.

  Analyses on this site watch dwvkbd.sys was the CAUSE.

  ------------------------------------------------------

  Hello

  Check this KB:

  The shutdown process does not terminate and you receive an error message on a computer that is
  running Windows Vista or Windows Server 2008: "Stop 0x0000009F"
  http://support.Microsoft.com/kb/972109

  ----------------

  You use Roxio or Nero programs? They have been known to cause this problem even
  If they worked well for a long period of time. If so check with their support.

  Check this thread for more information on using BlueScreenView, MyEventViewer and other methods of
  Troubleshoot BlueScreens - answers top 3 (+ 1 more).

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/blue-screen-plug-and-play-detected-an-error-most/3deab2fa-4000-4136-8c78-a3d22b1db009

  We can analyze the minidumps if make you it available to the SkyDrive or another file
  sharing sites.

  ZIP or download the content of the C:\Windows\minidump

  Use SkyDrive to upload collected files.
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  ----------------------------------------------------------

  References to Vista also apply to Windows 7.

  This "might" be a power problem, even if this isn't the most common cause - in this case
  It seems that the PSU could be the fault.

  9F is probably a driver issue. Security/antivirus/antispware programs can also cause these issues.
  Have you added the recent devices or the updated drivers - don't forget to check in the Windows updates to see
  If a driver has been updated before this happen. This can also be caused by a loose card or cable
  and even a weak power supply.

  This error means that a driver does not properly support the power state. Check in Control Panel - device
  Manager to ensure that the drivers are not stop during sleep - double-click adapter - NETWORK adapter
  and WIFI - healthy and others - tab power management - uncheck allow the computer to turn off.
  Maybe the only has a problem.

  Start - type in the search - find MSCONFIG in top - right, click on – RUN AS ADMIN

  General tab - tick this box start Diagnostic - APPLY / OK - REBOOT

  Try it now. If the computer still blue screens thinks that video driver. Otherwise think the card NETWORK, Wifi, sound, or...
  (and it might still be video interacts with something else). See following message for my
  generic driver update methods.

  BCCode: 9F 0x0000009F<-- read="" this="">
  * 1167.html? order = date http://www.faultwire.com/solutions-fatal_error/Driver-Power-State-Failure-0x0000009F-

  ==========================================

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  -------------------------------------------------------------------------

  Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
  info that would help. Such as ITC and 4 others entered at the bottom left. And all others
  error information such as codes of STOP and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

  As examples:

  BCCode: 116
  BCP1: 87BC9510
  BCP2: 8C013D80
  BCP3: 00000000
  BCP4: 00000002

  or in this format:

  Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during 'blue screen of death '.
  hangs and displays information about all accidents of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
  There are other causes.

  You can do without if needed fail or the Vista DVD or recovery command prompt mode
  Options if your system was installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  You can try a system restore to a point before the problem started when one exists.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

  -------------------------------------------------------------------------

  Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

  Enter this at the command prompt - sfc/scannow

  How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
  generates in Windows Vista cbs.log
  http://support.Microsoft.com/kb/928228

  The log can give you the answer if there is a corrupted driver. (Says not all possible
  driver problems).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

  -------------------------------------------------------------------------

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

  -------------------------------------------------------------------------

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting, STOP error blue screen Vista
  http://www.chicagotech.NET/Vista/vistabluescreen.htm

  Understanding and decoding BSOD (blue screen of death) Messages
  http://www.Taranfx.com/blog/?p=692

  Windows - troubleshooting blue screen errors
  http://KB.wisc.edu/page.php?id=7033

  -------------------------------------------------------------------------

  In some cases, it may be necessary.

  The Options or Vista recovery disk Startup Repair

  How to do a startup repair
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

  .

• Blue Screen Error Code Caused by hal.dll and ntkrnlpa.exe 9F.

  original title: BSOD error Code Caused by hal.dll and ntkrnlpa.exe 9F.

  Currently, I'm having a problem on a Fujitsu T1010 with Windows Vista x 84 installed tablet. At a random time that I use my computer, I get a generic blue screen with information DRIVER_POWER_STATE_FAILURE. The error code is 0x0000009F (0 x 00000003, 0x86f692e0, 0x86f692e0, 0x865a6598). BlueScreenView.exe, I see that the root causes are hal.dll + 997f and ntkrnlpa.exe + f5b28. So far, I've had 14 accidents. I run the driver verifier and the causes are hal.dll + 726c and ntkrnlpa.exe + 2ea5a7 windrvr6.sys + 0. Any help is appreciated! Thank you.

  Timothy

  Hello

  References to Vista also apply to Windows 7.
  
  Updated drivers, BIOS and software control (if any) is a good idea.

  This is my generic how updates of appropriate driver:

  For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common.
  Control Panel - device - Graphics Manager - note the brand and complete model
  your video card - double - tab of the driver - write version information. Now, click on update
  Driver (this can do nothing as MS is far behind the certification of drivers) - then right-click.
  Uninstall - REBOOT it will refresh the driver stack.

  Repeat this for network - card (NIC), Wifi network, sound, mouse, and keyboard if 3rd party
  with their own software and drivers and all other main drivers that you have.

  Now in the system manufacturer (Dell, HP, Toshiba as examples) site (in a restaurant), peripheral
  Site of the manufacturer (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Look for
  BIOS, Chipset and software updates on the site of the manufacturer of the system here.)

  Download - SAVE - go to where you put them - right click - RUN AD ADMIN - reset after each
  installation.

  Always check in the Device Manager - drivers tab to be sure the version you actually install
  presents itself. This is because some restore drivers before the most recent is installed (sound card drivers
  in particular that) so to install a driver - reboot - check that it is installed and repeat as
  necessary.

  Repeat to the manufacturers - BTW on device at the DO NOT RUN THEIR SCANNER - manually check by model.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  If you update the drivers manually, then it's a good idea to disable the facilities of driver in the Windows updates,
  This leaves ONE of Windows updates, but it will not install the drivers who are generally older and cause
  questions. If updates offers a new driver and then hide it (right click on it) and then go look for new ones
  manually if you wish.

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

  Hope these helps.

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• BSOD Shut-down on blue screen Code 9f

  I also encounter this everyday, several times, as the PC goes into sleep mode.  Here are the basic BSOD report:

  Dump File	Crash Time	Bug Check String	Bug check code	Parameter 1	Parameter 2	Parameter 3	Parameter 4	Caused by the driver	Caused by address	Description of the file	Name of the product	Company	Version of the file	Processor	Name of the computer	Full Path	Number of processors	Major version	Minor version
  031510-37343 - 01.dmp	2010-03-15 20:08:47	DRIVER_POWER_STATE_FAILURE	0x0000009F	0 x 00000003	0x86a18b60	0x80d8adb0	0x874462f8	Ntoskrnl.exe	Ntoskrnl.exe + d1574	NT kernel & system	Microsoft® Windows® operating system	Microsoft Corporation	6.1.7600.16481 (win7_gdr.091207 - 1941)	32 bit		C:\Windows\minidump\031510-37343-01.dmp	2	15	7600

  What is frustrating is that I have only one device (NIC) with a status of power tab and is disabled.  Also, when I did a search on the Internet for each of these four parameter codes reported, none of them have been found. I guess the stamped are perhaps the spell name of
  special devices in the order more likley to less likely candidate as the cause of the closure.

  It is an older machine, but all the drivers and BIOS are the latest available. (GigaByte 8I1000PE). I built it myself and there work very well under WinXP SP1 - SP3. Feeding is 550W. All cards are 'green', and less than half of the locations are full. MS has had a few KB patches for problems of closure. Installed, but no difference. Nothing wrong with my 4 GB RAM DDR800 Corsair, bonus either. I understand that there is a problem with NTOSKTNL.exe for over ten years.

  Other ideas that the few valuable I see here and on the TechNet site appreciated.  Curiously, however, most of the concerns has to do with laptops. Mine is a desktop - which should have far fewer problems of POV material.

  THX.

  P.S. If anyone really wants another 10 pages of dump diagnostic, let me know.

  Hello

  This answer is for Vista and Windows 7, but XP is very similar. If you need specific
  See the XP forums XP Help.

  XP answers forums
  http://social.answers.Microsoft.com/forums/en-us/category/WindowsXP

  This "might" be a power problem, even if it's not the most common cause.

  9F is probably a driver issue. Security/antivirus/antispware programs can also cause these issues.
  Have you added the recent devices or the updated drivers - don't forget to check in the Windows updates to see
  If a driver has been updated before this happen. This can also be caused by a loose card or cable
  and even a weak power supply.

  This error means that a driver does not properly support the power state. Check in Control Panel - device
  Manager to ensure that the drivers are not stop during sleep - double-click adapter - NETWORK adapter
  and WIFI - healthy and others - tab power management - uncheck allow the computer to turn off.
  Maybe the only has a problem.

  Start - type in the search - find MSCONFIG in top - right, click on – RUN AS ADMIN

  General tab - tick this box start Diagnostic - APPLY / OK - REBOOT

  Try it now. If the computer still blue screens thinks that video driver. Otherwise think the card NETWORK, Wifi, sound, or...
  (and it might still be video interacts with something else). See following message for my
  generic driver update methods.

  BCCode: 9F 0x0000009F
  * 1167.html? order = date http://www.faultwire.com/solutions-fatal_error/Driver-Power-State-Failure-0x0000009F-

  MyEventViewer and BlueScreenViewer utilities may provide additional information to help.

  ==========================================

  To solve the problems of the side sleep/wake extended.

  Shoot sleep problems - hibernation
  http://www.computerperformance.co.UK/Vista/vista_hibernate.htm

  How to solve a problem of Mode for Vista and find a Solution
  http://www.Vistax64.com/tutorials/63567-power-options-sleep-mode-problems.html

  How to enable and disable Hibernation
  http://www.Vistax64.com/tutorials/165508-hibernation-enable-disable.html

  How to restore the default power in Vista (and then go back and change as you wish)
  http://www.Vistax64.com/tutorials/198047-power-plan-restore-default-settings.html

  How to troubleshoot performance problems with sleep, hibernation and resume in Windows Vista
  http://support.Microsoft.com/kb/950686

  May need to reset all to default power settings and then place back as you prefer.

  ===========================================

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  -------------------------------------------------------------------------
  Also this, so you can see the probable bluescreens.

  Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
  http://www.winvistatips.com/disable-automatic-restart-T84.html

  -------------------------------------------------------------------------

  Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
  info that would help. Such as ITC and 4 others entered at the bottom left. And all others
  error information such as codes of STOP and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

  As examples:

  BCCode: 116
  BCP1: 87BC9510
  BCP2: 8C013D80
  BCP3: 00000000
  BCP4: 00000002

  or in this format:

  Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during 'blue screen of death '.
  hangs and displays information about all accidents of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
  There are other causes.

  You can do without if needed fail or the Vista DVD or recovery command prompt mode
  Options if your system was installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  You can try a system restore to a point before the problem started when one exists.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

  -------------------------------------------------------------------------

  Start - type this into the search-> find COMMAND to top box and RIGHT CLICK-
  RUN AS ADMIN

  Enter this at the command prompt - sfc/scannow

  How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe)
  program generates in Windows Vista cbs.log
  http://support.Microsoft.com/kb/928228

  The log can give you the answer if there is a corrupted driver. (Says not all possible
  driver problems).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.
  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

  -------------------------------------------------------------------------

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

  -------------------------------------------------------------------------

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting, STOP error blue screen Vista
  http://www.chicagotech.NET/Vista/vistabluescreen.htm

  Understanding and decoding BSOD (blue screen of death) Messages
  http://www.Taranfx.com/blog/?p=692

  Windows - troubleshooting blue screen errors
  http://KB.wisc.edu/page.php?id=7033

  -------------------------------------------------------------------------

  In some cases, it may be necessary.

  The Options or Vista recovery disk Startup Repair

  How to do a startup repair
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.
  Rob - bicycle - Mark Twain said it is good.

• Bluetooth, causing the blue screen with error message: out of State driver

  Hello

  I am posting this in the other thread here but it was closed before I could solve the problem.
  Background:
  I left on vacation for 4 weeks and I left my computer.  When I came back, my computer was giving me the following problems:
  • Video playback of my SIN was rough and freezing - I fixed that by finding out one of the drives died on RAID-1
  • After 30 minutes, the computer would give me a Blue Screen of Death (BSOD) and reboot - I have updated every driver I could, each piece of software, update the BIOS and then finally solved the problem by updating the firmware on my boot drive: a Crucial 128 GB SSD m4

  These two problems have been resolved, but can be useful to understand the current problem

  Current problem:
  After trying to use the webcam for video chat via Gtalk or Skype, my Bluetooth Logitech MX5500 keyboard and mouse stop responding.  About 10-15 minutes after the call is completed, my computer gives a Blue Screen of Death with the message of STATE FAILURE of PILOT.
  The minidump file is available here, and I understand that the cause is due to my Bluetooth driver: http://dl.dropbox.com/u/30633232/052212-24429-01.dmp
  What I tried:
  • I've updated all the drivers available on the Asus site for my motherboard Asus P8P67 EVO, including Bluetooth and the BIOS driver
  • I've updated my HD Audio integrated system with the drivers available on the Web from Realtek site
  • I've updated all my drivers webcam and Logitech software
  • I uninstalled, restart and reinstalled my Bluetooth drivers
  • I have not matched and repaired my Logitech MX5500 keyboard and mouse
  • I uninstalled, restart and reinstalled both Skype and Gtalk for Chrome, Firefox and Internet Explorer plugin
  The ask:
  I'm out of ideas... would like to get the genius of someone on these boards help me please!

  The problem may be with the c:\windows\system32\drivers\sptd.sys:

  ******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  DRIVER_POWER_STATE_FAILURE (9f)
  A driver is causing an inconsistent power state.
  Arguments:
  Arg1: 0000000000000003, a device object has been blocking an Irp for too long
  Arg2: fffffa8009d73060, physical device from the stack object
  Arg3: fffff80004c093d8, functional device object of the stack
  Arg4: fffffa800e0c3190, blocked IRP

  Debugging information:
  ------------------

  DRVPOWERSTATE_SUBCODE: 3

  Nom_image: usbhub.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15

  MODULE_NAME: usbhub

  FAULTING_MODULE: fffff88008c06000 usbhub

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  BUGCHECK_STR: 0X9F

  Nom_processus: System

  CURRENT_IRQL: 2

  STACK_TEXT:
  "fffff800'04 c 09388 fffff800'03502702: 00000000' 00000000'00000003 fffffa80 ' 09 0000009f d 73060 fffff800 ' 04c093d8: nt! KeBugCheckEx
  "fffff800 ' 04 c 09390 fffff800 ' 034a2e4c: fffff800 '04c094c0 fffff800' 04c094c0 00000000'00000000 00000000'00000003: nt! : FNODOBFM: 'chain' + 0 x 34050
  "fffff800 ' 04 c 09430 fffff800 ' 034a2ce6: fffffa80 '06cdf5b0 00000000'01642618 00000000'00000000 fffffa80' 097aa901: nt! KiProcessTimerDpcTable + 0x6c
  fffff800 '04c094a0 fffff800' 034a2bce: 0000034f 'c591e29e fffff800' 04c09b18 00000000'01642618 fffff800'0360 d 588: nt! KiProcessExpiredTimerList + 0xc6
  "fffff800 '04c09af0 fffff800' 034a29b7: 0000011a ' 68920ac3 ' 01642618 0000011 0000011a has ' 68920 has 32 00000000'00000018: nt! KiTimerExpiration + 0x1be
  fffff800 '04c09b90 fffff800' 0348feca: fffff800 '0360ae80 fffff800' 03618cc0 00000000'00000002 fffff880' 00000000: nt! KiRetireDpcList + 0 x 277
  fffff800'04c09c40 00000000' 00000000: fffff800 ' 04c0a000 fffff800'04 c 04000 fffff800 ' 04c09c00 00000000' 00000000: nt! KiIdleLoop + 0x5a

  STACK_COMMAND: kb

  FOLLOWUP_NAME: MachineOwner

  FAILURE_BUCKET_ID: X64_0x9F_3_btfilter_IMAGE_usbhub.sys

  BUCKET_ID: X64_0x9F_3_btfilter_IMAGE_usbhub.sys

  Follow-up: MachineOwner
  ---------

  0: kd >! devobj fffffa8009d73060
  Object Device (fffffa8009d73060) is:
  Can not read information from nt shift! ObpInfoMaskToOffset
  \Driver\usbhub DriverObject fffffa80094ffa50
  Current PRI 00000000 RefCount 2 Type 00000022 Flags 00003040
  DevExt fffffa8009d731b0 DevObjExt fffffa8009d73bb0 DevNode fffffa8009d7b550
  ExtensionFlags (0 x 00000800)
  Unknown flags 0 x 00000800
  AttachedDevice (top) fffffa8009663880 * WARNING: unable to verify timestamp for c:\windows\system32\drivers\sptd.sys
  ERROR: Module load completed but symbols can be loaded for c:\windows\system32\drivers\sptd.sys
  \Driver\ACPI
  Queue is not busy.

  I would say to uninstall the application that has installed the driver c:\windows\system32\drivers\sptd.sys, maybe it is Daemon Tools or Alcohol 120%.

  Then, uninstall the c:\windows\system32\drivers\sptd.sys - see "How can I remove driver SPTD on 64-bit operating system?" in the following link:

  http://www.duplexsecure.com/en/FAQ

  Similar question in the following thread:

  http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-hardware/the-computer-has-rebooted-from-a-bugcheck-the/2a0b354e-4FEA-4349-b88f-eb4b10199380