cancel
Showing results for 
Search instead for 
Did you mean: 

BSOD caused by power manipulation?

Reyals
Level 7
So Ive setup my new system, Haswell 7440k, corsair h100i (using the corsair link software), Maximus VI Hero motherboard. Intel 520SSD and a few samsung SSDs.

Things seemed fine but I got a BSOD after coming back from being afk for 40 min.

Upon analyzing I got the following which indicates it has something to do with not enough power to the drive?

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: fffffa8026e58b00, The thread currently holding on to the Pnp lock.
Arg4: fffff8030c5b5800, nt!TRIAGE_9F_PNP on Win7


I used the default settings for the motherboard, APM is off. Is there something that I'm missing? I'd like to use the features where power is managed by the motherboard but not if it will cause crashes.

Any help is appreciated. The rest of the dump after analysis can be found here:


0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: fffffa8026e58b00, The thread currently holding on to the Pnp lock.
Arg4: fffff8030c5b5800, nt!TRIAGE_9F_PNP on Win7

Debugging Details:
------------------

Can't retrieve thread context, Win32 error 0n30

DRVPOWERSTATE_SUBCODE: 4

IMAGE_NAME: ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: 0000000000000000

DEVICE_OBJECT: fffffa802bf58050

DRIVER_OBJECT: fffffa802bf905f0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8030d0bef7c to fffff8030d0bd4a6

STACK_TEXT:
fffff880`09e28e90 fffff803`0d0bef7c : 00000000`00000001 00000000`00000000 fffff880`00000002 fffffa80`26e58b00 : nt!KiSwapContext+0x76
fffff880`09e28fd0 fffff803`0d0be793 : fffffa80`26e58b00 fffff880`09e29478 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x23c
fffff880`09e29090 fffff880`0b7eb47c : fffffa80`2bf56098 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeDelayExecutionThread+0x1d3
fffff880`09e29110 fffff880`0b7eb089 : 00000000`00000000 ffffffff`ff63c000 ffffa079`c4c62b24 fffff8a0`00000010 : mslldp!lldpWaitForValueToZero+0x30
fffff880`09e29140 fffff880`0b7e9094 : fffffa80`2bf56000 00000000`00000000 fffffa80`2bb246a0 00000000`00000000 : mslldp!lldpWaitForTxCompletion+0x5d
fffff880`09e29180 fffff880`0154f492 : fffff880`009f0180 fffffa80`27c483b0 00000000`00000008 fffffa80`1f5c36f0 : mslldp!lldpProtNetPnPEvent+0x31c
fffff880`09e291b0 fffff880`0154f567 : fffffa80`2bb246a0 fffffa80`1f5c36f0 fffff880`09e29330 fffff880`09e29478 : ndis!ndisInvokeNetPnPEvent+0x42
fffff880`09e291f0 fffff880`01582988 : fffffa80`27c483b0 fffffa80`2bf581a0 fffff880`09e29338 fffff803`0d2a00d0 : ndis!ndisDeliverNetPnPEventSynchronously+0x47
fffff880`09e29230 fffff880`015828d0 : fffffa80`27c483b0 fffff880`09e293a0 00000000`00000008 fffffa80`2bf581a0 : ndis!ndisPnPNotifyBinding+0x84
fffff880`09e292a0 fffff880`0154fc7c : 00000000`00000000 fffff880`09e29490 00000000`00000000 00000000`00000000 : ndis!ndisPnPNotifyAllTransports+0x3b0
fffff880`09e29440 fffff880`0158bae7 : fffffa80`2bf581a0 fffffa80`19e57d28 fffffa80`2bd71920 fffffa80`19e57bb0 : ndis!ndisPauseMiniportStack+0x94
fffff880`09e294d0 fffff880`015703a4 : fffffa80`2bf581a0 fffffa80`2bf581a0 fffffa80`28daa340 fffffa80`2bf58050 : ndis!ndisPnPRemoveDevice+0x1f7
fffff880`09e29660 fffff880`0158d320 : fffffa80`28daa340 fffffa80`2bf58050 00000000`00000000 fffffa80`2bf58100 : ndis!ndisPnPRemoveDeviceEx+0x84
fffff880`09e29690 fffff880`0157f8a7 : fffffa80`28daa340 fffff880`09e29720 fffffa80`2bf581a0 00000000`00000000 : ndis!ndisPnPIrpRemoveDevice+0xd8
fffff880`09e296f0 fffff803`0d3a4337 : fffffa80`2bf58001 fffffa80`2bf58050 00000000`00000001 fffff880`01d4b180 : ndis!ndisPnPDispatch+0x2f8b7
fffff880`09e29750 fffff803`0d4b471c : 00000000`00000002 fffff880`09e29819 fffffa80`2b6de4b0 fffffa80`2bead080 : nt!IopSynchronousCall+0xc7
fffff880`09e297c0 fffff803`0d123f01 : fffff8a0`17c8b1c0 00000000`00000000 fffffa80`2b6de4b0 00000000`00000000 : nt!IopRemoveDevice+0x100
fffff880`09e29880 fffff803`0d4b4544 : fffffa80`2bead080 fffffa80`2b6de4b0 00000000`00000016 fffff8a0`097aa601 : nt!PnpRemoveLockedDeviceNode+0x22d
fffff880`09e298d0 fffff803`0d4b4415 : 00000000`00000000 00000000`00000000 fffff8a0`097aa600 fffffa80`2b6de4b0 : nt!PnpDeleteLockedDeviceNode+0x78
fffff880`09e29910 fffff803`0d4b2c88 : 00000000`00000000 fffff880`09e29a70 fffff8a0`1cc76750 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa1
fffff880`09e29970 fffff803`0d4a6acd : fffff880`00000000 00000000`00000000 fffff8a0`2cb2c000 fffff8a0`00000000 : nt!PnpProcessQueryRemoveAndEject+0xbd8
fffff880`09e29ae0 fffff803`0d3a06e5 : fffff8a0`17c8b1c0 00000000`00000000 00000000`00000001 fffff803`0d2a0000 : nt!PnpProcessTargetDeviceEvent+0xa1
fffff880`09e29b20 fffff803`0d0cf391 : fffffa80`26e58b00 fffff8a0`1cc76750 fffff803`0d3a0400 fffffa80`1a1c1b50 : nt!PnpDeviceEventWorker+0x2e5
fffff880`09e29b80 fffff803`0d03e521 : fffffa80`001a001a 00000000`00000080 fffff803`0d0cf250 fffffa80`26e58b00 : nt!ExpWorkerThread+0x142
fffff880`09e29c10 fffff803`0d07cdd6 : fffff880`01c65180 fffffa80`26e58b00 fffff880`01c70f40 fffffa80`18881040 : nt!PspSystemThreadStartup+0x59
fffff880`09e29c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_4_IMAGE_ntkrnlmp

BUCKET_ID: 0x9F_4_IMAGE_ntkrnlmp

Followup: MachineOwner

3,259 Views
3 REPLIES 3

HiVizMan
Level 40
Post your full specifications list of your system please.
To help us help you - please provide as much information about your system and the problem as possible.

Reyals
Level 7
Here's the system build:

  • Fractal Design Define R4 Cases, Black Pearl (FD-CA-DEF-R4-BL)
  • ASUS MAXIMUS VI HERO DDR3 1600 LGA 1150 Motherboard
  • Corsair Hydro Series Extreme Performance Liquid CPU Cooler H100i
  • Intel Core i7-4770K Quad-Core Desktop Processor 3.5 GHZ 8 MB Cache BX80646I74770K
  • Corsair Vengeance 32GB (4x8GB) DDR3 1600 MHz (PC3 12800) Desktop Memory (CMZ32GX3M4X1600C10)
  • Intel 520 Series Solid-State Drive 240 GB SATA 6 Gb/s 2.5-Inch - SSDSC2CW240A310 (Drive Only)
  • Seasonic PLATINUM-860 ATX 860 Power Supply
  • LG Electronics 12x SATA Blu-Ray Disc Combo Internal Drive with 3D Playback and M-DISC (Black)
  • Radeon HD 7950 3GB DDR5 HDMI / DVI-I / Dual Mini DP PCI-Express OC Version Graphics Card
  • 830 Series 2.5-Inch 256GB SATA III MLC Internal Solid State Drive (SSD)
  • Seagate Barracuda 3 TB HDD SATA 6 Gb/s NCQ 64MB Cache 7200 RPM
  • Windows 8 Professional System Builder OEM DVD 64-Bit

Praz
Level 13
This is not a drive issue. The dump references the NT Kernel trapping a driver that is in an invalid power state. I would recommend complete stability testing at stock settings and if all checks out OK a fresh install followed by installing drivers and updates one at a time to isolate the offending driver.