Windows 7 BSOD DRIVER_POWER_STATE_FAILURE ntoskrnl.exe

mwyeoh

New Member
Hi

Recently my computer has occasionally 'hanged' when I go to hibernate it.
It takes a long time and then BSOD's (Or I press the power button before it happens)

It doesnt happen all the time, but often enough that it is not coincidence

I have attached the requested files (From seven forums, cpu-z and rammon), or here is a link Link Removed due to 404 Error

I hope someone can help!
 

Attachments

  • BSOD files.zip
    1.6 MB · Views: 946
Hello and welcome to the forum.
All three dump files are identical blaming hamachi in the stack trace and memory corruption but the raw stack suggests maybe something different.
Code:
[U][B]BugCheck 1000009F[/B][/U], {4, 258, fffffa800c80f660, fffff80000b9c3d0}
Unable to load image \SystemRoot\system32\DRIVERS\    [U][COLOR=#ff0000][B]hamachi.sys[/B][/COLOR][/U]    , Win32 error 0n2
*** WARNING: Unable to verify timestamp for     [U][COLOR=#ff0000][B]hamachi.sys[/B][/COLOR][/U]        
*** ERROR: Module load completed but symbols could not be loaded for hamachi.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[U][COLOR=#ff0000][B]Probably caused by : memory_corruption[/B][/COLOR][/U]
Followup: [B]memory_corruption[/B]
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: fffffa800c80f660, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0
DRVPOWERSTATE_SUBCODE:  4
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
STACK_TEXT:  
fffff880`0377e0c0 fffff800`0348bbd2 : 00000000`00000000 fffffa80`0c80f660 00000000`00000000 00000000`0000000b : nt!KiSwapContext+0x7a
fffff880`0377e200 fffff800`0349cf8f : 00000000`40b50089 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`0377e290 fffff880`0193e84e : fffffa80`1395dd00 fffff800`00000000 00000000`00000000 fffffa80`1395dd00 : nt!KeWaitForSingleObject+0x19f
fffff880`0377e330 fffff880`0bd5debf : 00000000`00000000 00000000`00000000 00000000`0000007e 00000000`00000000 : ndis!NdisMSleep+0x5e
fffff880`0377e3b0 00000000`00000000 : 00000000`00000000 00000000`0000007e 00000000`00000000 fffffa80`15b2bd44 : [COLOR=#ff0000][U][B]hamachi[/B][/U][/COLOR]+0x3ebf
STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800034993a2 - nt!SwapContext_PatchXSave+2
    [ 01:21 ]
    fffff80003499486 - nt!SwapContext_PatchXRstor+2 (+0xe4)
    [ 09:29 ]
    fffff80003499642 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bc)
    [ 01:21 ]
    fffff80003499728 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe6)
    [ 09:29 ]
4 errors : !nt (fffff800034993a2-fffff80003499728)
MODULE_NAME: [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
IMAGE_NAME: [COLOR=#ff0000][U][B] memory_corruption[/B][/U][/COLOR]
FOLLOWUP_NAME:  [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT_LARGE
FAILURE_BUCKET_ID:  X64_[COLOR=#ff0000][U][B]MEMORY_CORRUPTION[/B][/U][/COLOR]_ONE_BIT_LARGE
BUCKET_ID:  X64_[U][B][COLOR=#ff0000]MEMORY_CORRUPTION[/COLOR][/B][/U]_ONE_BIT_LARGE
Followup: [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
Let's start by completely removing your Norton / Symantec software. Use the programs uninstaller if available or use the programs and features applet in the control panel to uninstall it. Follow that up by running this vendor specific proprietary removal tool from here https://www-secure.symantec.com/nor...t=home&pvid=f-home&version=1&lg=english&ct=us
After it's completely removed replace for the time being with MSE from here Link Removed due to 404 Error
If Blue Screens persist update your thread by attaching your new dump files to your next post.
Good Luck and keep us posted
Randy
 
Hamachi? Thats unexpected. Can you tell whether it is the hamachi.exe program itself? Or the hamachi network adapter?

I basically only use hamach once a week. After Ie used it, I manually disable the network adapter afterwards until the following week
 
Back
Top