Windows 7: BSOD ntoskrnl.exe and driver_power_state_failure

icyrainz · 27 Sep 2012

Hi,

I have recently installed a SSD into my laptop and re-installed everything. I also switch the SATA mode to AHCI to improve the performance. But there is one problem that did not occur before is that after a long period of using the laptop, I cannot plugin any devices to the USB ports. Then I scan for hardware changes, and the finding window keep doing forever. So I try to shutdown and it fails to do so, after about 30 min it says BSOD with DRIVER_POWER_STATE_FAILURE.

This does not occur instantly when starting windows, only after a period of using.

I have attached the SF Diagnostic Data.

Thanks in advance !!

koolkat77 · 27 Sep 2012

Welcome
Have you updated to the latest firmware for your SSD?

icyrainz · 27 Sep 2012

My SSD is the Crucial M4 128GB. I just checked the website and there is a new firmware 010G which was just released on Sep 25th. I am updating the firmware right now to see if they fix this problem.

Also, I found that this thread http://www.sevenforums.com/crashes-d...-shutdown.html have similar issue with me but they fix by installing the AHCI driver. In my case, I don't have any AMD AHCI driver since my laptop is a Dell Vostro 3550 using the Intel chipset.

koolkat77 · 27 Sep 2012

Firmware must be updated.
In case you're using any third party drivers for SSD controllers, its best to use native windows AHCI drivers.

icyrainz · 27 Sep 2012

I am not using any third party AHCI controller for the SSD.
The BSOD is not frequent but it is very annoying since when it occurs, I just don't have any option but to hold power button to power off and then restart it again.

I will report back with new diagnostic data when the problem occurs again ! Thanks !!

koolkat77 · 27 Sep 2012

Sure, take your time

icyrainz · 09 Oct 2012

Hi, the problem occurred again. This time it is more fatal. Sometimes the system does not recognize the SSD in the BIOS. I have to follow the power cycle instruction of the manufacturer that is to put the system idle in BIOS for more than 20 minutes in order to reset the SSD power.

Any chance that I am experiencing wrong driver SATA controller or something ?

I have attached the latest SF diagnostic file of my system !!

koolkat77 · 09 Oct 2012

The dump shows memory corruption

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

→ RAM - Test with Memtest86+
→ Guide to using Memtest86+ - Geeks to Go Forums

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8004ef6040, fffff800043633d0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8004ef6040, The thread currently holding on to the Pnp lock.
Arg4: fffff800043633d0

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8004ef6040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c76bd2 to fffff80002c8407a

STACK_TEXT:  
fffff880`033c4750 fffff800`02c76bd2 : fffffa80`04ef6040 fffffa80`04ef6040 00000000`00000000 fffffa80`00000000 : nt!KiSwapContext+0x7a
fffff880`033c4890 fffff800`02c87f8f : fffffa80`04ef7b50 fffff800`02df3e80 fffff880`000000ab fffff800`02df3e80 : nt!KiCommitThreadWait+0x1d2
fffff880`033c4920 fffff800`02c6110e : 00000000`00000000 fffff800`0000001b 00000000`00000000 fffff880`03165100 : nt!KeWaitForSingleObject+0x19f
fffff880`033c49c0 fffff800`02c863ac : ffffffff`fd9da600 fffffa80`059766f0 fffff800`02e7cb80 fffff800`02dacfbd : nt!ExpWaitForResource+0xae
fffff880`033c4a30 fffff800`02fb7bc2 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`04f31760 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`033c4aa0 fffff800`02d7abf0 : 00000000`00000000 fffff800`02e1e2d8 00000000`00000001 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1c44c
fffff880`033c4ad0 fffff800`02c8a841 : fffff800`02d7abb0 fffff800`02f73601 fffffa80`04ef6000 00000000`00000000 : nt!PnpDeviceActionWorker+0x40
fffff880`033c4b70 fffff800`02f17e6a : 00000000`00000000 fffffa80`04ef6040 00000000`00000080 fffffa80`04ee5040 : nt!ExpWorkerThread+0x111
fffff880`033c4c00 fffff800`02c71ec6 : fffff880`031d7180 fffffa80`04ef6040 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033c4c40 00000000`00000000 : fffff880`033c5000 fffff880`033bf000 fffff880`033c4470 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8004ef6040 ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002c843a2 - nt!SwapContext_PatchXSave+2
	[ 01:21 ]
    fffff80002c84486 - nt!SwapContext_PatchXRstor+2 (+0xe4)
	[ 09:29 ]
    fffff80002c84642 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bc)
	[ 01:21 ]
    fffff80002c84728 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe6)
	[ 09:29 ]
4 errors : !nt (fffff80002c843a2-fffff80002c84728)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------

koolkat77 · 31 Oct 2012

Were you able to resolve the blue screen problems?

icyrainz · 31 Oct 2012

Sorry for not replying. I tried checking the RAM but I think it is not the problem. I revert back to the earlier firmware of the SSD so that the problem is not too critical that I have to wait 20 min in BIOS to do the power cycle thing. Now everytime the problem appears, I just hard shutdown the laptop and power on and ignore the BSOD.

I think this problem comes from the SSD vendor. So I will be waiting for the next firmware update !!

Thanks very much on your support !!!

Windows 7: BSOD ntoskrnl.exe and driver_power_state_failure

BSOD ntoskrnl.exe and driver_power_state_failure problems?