BSOD 0x9F - also a strange timestamp on dmp report

snadge · 07 Jun 2014

Hi

I have just turned on my PC this morning too find that whilst sleeping during the night it BSOD, WHO CRASHED program reports the crash time as 22:13 on 6/6/14 but thing is I was actually using the computer at that time until 23:15 hours? the clock is the correct time too, I sent an email dead on 22:13 and have it in my sentbox??

anyway, I have attached the report file as advised on your BSOD thread and WC says its something to do with nostkrnl:

thanks in advance

Crash dumps are enabled on your computer.

On Fri 06/06/14 22:13:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060714-5397-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800703D060, 0xFFFFF80000B9C3D8, 0xFFFFFA801200B670)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 06/06/14 22:13:57 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800703D060, 0xFFFFF80000B9C3D8, 0xFFFFFA801200B670)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Arc · 07 Jun 2014

Hi snadge.

Download and install Intel® PROSet/Wireless Software and Drivers for Windows.

Then put the computer to sleep and wake it up. Do it for a few times.

Does it BSOD still? Let us know.
_____________________________________

Code:

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8010ed1050 00000000 fffff80002ec8210-fffffa801380b090 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\netw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
 \Driver\netw5v64    nt!PopSystemIrpCompletion

Code:

fffff880`05e29000 fffff880`06364000   netw5v64 T (no symbols)           
    Loaded symbol image file: netw5v64.sys
    Image path: \SystemRoot\system32\DRIVERS\netw5v64.sys
    Image name: netw5v64.sys
    Timestamp:        Thu Mar 26 21:51:24 2009 (49CBAB84)
    CheckSum:         00533DE3
    ImageSize:        0053B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

snadge · 07 Jun 2014

thanks I will try - i have slept the computer with the current driver for a while and since my post and its been fine, just that once, I have upgraded the driver from v12 to v13 though to be sure

thanks again, I will let you know if it happens again, thanks for looking at my dmp files