Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: 0x0000009f after cold start

16 Oct 2015   #1

Windows 7 Prof 64bit
0x0000009f after cold start

Hi Community,

I'll receive regular BSOD while starting the machine from a cold boot.
It's not happen always but most times.
0x0000009f driver_power_state_failure

MemTest shows no errors
Several hw diagnostic tools showed no errors
I've replaced the SSD but still getting the same BSOD.

Maybe one of you could help ?
Windows 7 Professional SP1
Lenovo W530
Intel 520 SSD 180GB
8Gb Ram Ramaxel

* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006cd1660, fffff80004c823d0}

Probably caused by : memory_corruption

Followup: memory_corruption

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

A driver is causing an inconsistent power state.
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006cd1660, The thread currently holding on to the Pnp lock.
Arg4: fffff80004c823d0

Debugging Details:


FAULTING_THREAD: fffffa8006cd1660






LOCK_ADDRESS: fffff800030dbda0 -- (!locks fffff800030dbda0)

Resource @ nt!PiEngineLock (0xfffff800030dbda0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

Lock address : 0xfffff800030dbda0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff80002edb0f2 to fffff80002ed869a

fffff880`03bd3520 fffff800`02edb0f2 : fffffa80`06cd1660 fffffa80`06cd1660 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`03bd3660 fffff800`02edd90f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiCommitThreadWait+0x1d2
fffff880`03bd36f0 fffff800`02f97a95 : 00000000`00000000 fffffa80`00000000 00000000`00000000 fffff800`032c5200 : nt!KeWaitForSingleObject+0x19f
fffff880`03bd3790 fffff800`0327a3ee : fffff800`030dbb60 fffff880`03bd3864 00000000`00000000 00000000`00000001 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x35
fffff880`03bd37e0 fffff800`032c7768 : fffffa80`06cebd90 fffffa80`06cebd90 00000000`00000002 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x5e
fffff880`03bd3810 fffff800`032c7b3c : fffff800`030d9720 00000000`00000000 00000000`00000001 fffff800`03143628 : nt!PipProcessDevNodeTree+0x378
fffff880`03bd3a80 fffff800`02fd9ab2 : 00000001`00000003 fffff800`0307d2d8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`03bd3ad0 fffff800`02edfa95 : fffff800`02fd97b0 fffff800`0307d201 fffffa80`06cd1600 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`03bd3b70 fffff800`03174b8a : 00000000`00000000 fffffa80`06cd1660 00000000`00000080 fffffa80`06c59210 : nt!ExpWorkerThread+0x111
fffff880`03bd3c00 fffff800`02ec78e6 : fffff880`03989180 fffffa80`06cd1660 fffff880`039940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03bd3c40 00000000`00000000 : fffff880`03bd4000 fffff880`03bce000 fffff880`03bd15f0 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: .thread 0xfffffa8006cd1660 ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80002ed89c2 - nt!SwapContext_PatchXSave+2
[ 01:21 ]
fffff80002ed8aa6 - nt!SwapContext_PatchXRstor+2 (+0xe4)
[ 09:29 ]
fffff80002ed8c62 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bc)
[ 01:21 ]
fffff80002ed8d48 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe6)
[ 09:29 ]
4 errors : !nt (fffff80002ed89c2-fffff80002ed8d48)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption





Followup: memory_corruption

My System SpecsSystem Spec
16 Oct 2015   #2

Windows 10 Pro

Hi snibbels,

Welcome to the 7forums.

As you describe you have had multiple crashes, but only 1 has been recorded in the logs.
The crash was caused by drivers from Symantec.
Please update Symantec or remove it
*** WARNING: Unable to verify timestamp for SRTSPX64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSPX64.SYS
*** WARNING: Unable to verify timestamp for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
*** WARNING: Unable to verify timestamp for Ironx64.SYS
*** ERROR: Module load completed but symbols could not be loaded for Ironx64.SYS
*** WARNING: Unable to verify timestamp for BHDrvx64.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
My System SpecsSystem Spec
18 Oct 2015   #3

Windows 7 Prof 64bit

Thanks for your quick findings and response.

Uninstalling Symantec Endpoint Protection is not an option. It's a mandatory software of my business laptop. I cannot even uninstall it at all.

Could I ask with which tool you were able to get the information about the actual modules which weren't loading correctly ? As I tried a few myself but couldn't strip it down to actual file names.

My System SpecsSystem Spec

18 Oct 2015   #4

Windows 10 Pro

I use mainly Windbg for this.
If you are interested in this, you might want to read Windbg setup | Windows 10 Help Forums

Date information about 1 of the flagged drivers
0: kd> lmvm BHDrvx64
start             end                 module name
fffff880`05a30000 fffff880`05bc5000   BHDrvx64 T (no symbols)           
    Loaded symbol image file: BHDrvx64.sys
    Image path: \??\C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.4013.4013.105\Data\Definitions\BASHDefs\20151005.011\BHDrvx64.sys
    Image name: BHDrvx64.sys
    Timestamp:        Sat Jul 11 06:11:26 2015 (55A0976E)
    CheckSum:         0019DF0B
    ImageSize:        00195000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec

 0x0000009f after cold start

Thread Tools

Similar help and support threads
Thread Forum
BSOD From cold start WIN 7 X 64 Ultimate
Hi everyone, From my title you can guess I'm having problems from cold start. If I switch my PC on first thing in the morning I get a lovely BSOD "What Joy" , when I eventually get past the BSOD by reset and selecting start in normal mode it starts up ok. When I've finnished using it I always...
BSOD Help and Support
PC will not start from cold boot but ok on restsrt
Hello. 8 days ago i turned on the pc and then my a cup of tea. When i came back the pc had a flashing cursor in the top left screen. I turned it off and then on and then it went as far as the windows progress flash screen and stopped so i rebooted again and after nearly an hour of this i got it...
Hardware & Devices
BSOD after cold start.
Hello all, I made my own computer in the summer, everything went fine until i turned it off for a night and it took around 20 restarts until it would come back on, just from BSOD's right after the "Windows is loading" black screen with the emblem on it. Here are my system specs DxDiag.txt | Game...
BSOD Help and Support
Warm/Cold Start
When I ask my system to do a warm start i.e. a restart not a shut down it always does a cold start ie as if I had just pressed the start button on the desktop to start my computer. I seem to remember that on XP there was a differance between cold start (boot up) and a warm start. Or am I...
General Discussion
Cold Start Problems
I'm going to post this in the General Discussion forum because I don't know where else to start. If it needs to be moved, somebody please tell me. Several times a week, upon morning start up, my computer fails to recognize me. Boot up takes a long time then I get a message "Preparing your...
General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:01.
Twitter Facebook Google+