BSOD, mostly 0x3's

[Frank123]

BSOD, mostly 9f and a single 4e

Hi, I've been getting blue screens every once and awhile when I put my computer to sleep or make it hibernate. Most of these are 9f's, though I had a 4e that happened while I was using the computer, not after putting it to sleep. The error message I usually get with the blue screen after putting to sleep says: DRIVER POWER STATE FAILURE. Can anyone help me resolve this issue?

Here is my Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML file as a zip file: View attachment 153815

Additionally, some of the keys on my keyboard intermittently stop working so well. Not sure if this is related, but it sure is annoying.

HP HDX 16 1040us
Windows 7 Ultimate with a 64-bit operating system
4.00 GB Ram
Intel(R) Core(TM)2 Duo CPI P8400 @ 2.26 GHz 2.27 GHz.

 

[zigzag3143]

Hi, I've been getting blue screens every once and awhile. It happens after I put my computer to sleep or make it hibernate. Most of these are 0x3's, though I've had some 0x0's and an 0x7 that happened while I was using the computer, not after putting it to sleep. The error message I usually get says: DRIVER POWER STATE FAILURE. Can anyone help me resolve this issue?

Here is my Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML file as a zip file: View attachment 153815

Additionally, some of the keys on my keyboard intermittently stop working so well. Not sure if this is related, but it sure is annoying.

HP HDX 16 1040us
Windows 7 Ultimate with a 64-bit operating system
4.00 GB Ram
Intel(R) Core(TM)2 Duo CPI P8400 @ 2.26 GHz 2.27 GHz.

Two problems your network driver and Symantec.


1- remove Symantec and replace with microsoft security essentials

ftp://ftp.symantec.com/public/english_us_canada/removal_tools/Norton_Removal_Tool.exe

http://www.microsoft.com/security_essentials/


2these were caused by your network driver in conjunction with SYM. Please re-install with the newest version

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\BSOD\Windows_NT6_BSOD_jcgriff2\050911-48656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e9ee90
Debug session time: Mon May  9 15:30:50.716 2011 (GMT-4)
System Uptime: 0 days 21:58:27.542
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80046d5a10, fffff80000b9c518, fffffa8004590260}

*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
[COLOR=Red][U][I][B]Probably caused by : NETw5s64.sys[/B][/I][/U][/COLOR]

Followup: MachineOwner
---------

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80046d5a10, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8004590260, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8004590260

DEVICE_OBJECT: fffffa80052f0050

DRIVER_OBJECT: fffffa8005314ca0

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

MODULE_NAME: NETw5s64

FAULTING_MODULE: fffff88005649000 NETw5s64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d45b52 to fffff80002cd9640

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02d45b52 : 00000000`0000009f 00000000`00000003 fffffa80`046d5a10 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ce5062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02ce4f06 : fffffa80`0552be80 fffffa80`0552be80 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ce4dee : 000000b8`2fc510f6 fffff800`00b9cc58 00000000`004d6073 fffff800`02e4f0e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ce4bd7 : 00000028`b19685c2 00000028`004d6073 00000028`b196858a 00000000`00000073 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cd136a : fffff800`02e4be80 fffff800`02e59cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys

BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys

Followup: MachineOwner
---------

 

[Frank123]

@zigzag3143: Thanks for your speedy and relevant reply! I have not yet gone through with your proposed solutions, as I'm trying to finish a final term paper by the fast approaching deadline. Just for my own benefit and understanding, I wonder how you determined from the code you posted that the network driver and Symantec were the issues. It must have something to do with NETw5s64.sys (which you have highlighted in red). For me, though, novice that I am, moving from NETw5s64.sys to Symantec and network driver is a bit of a non sequitur. So, I'm still unsure how you determine the network driver and Symantec were the issues based on Probably caused by : NETw5s64.sys

Also, you just looked at MEMORY.DMP. Report Id: 050911-48656-01, the most recent dump file, correct? Is there any way you could also check out MEMORY.DMP. Report Id: 042711-52104-01, when the bugcheck was: 0x0000004e (0x0000000000000007, 0x000000000013f113, 0x0000000000000001, 0x0000000000000000)?