BSOD caused by ntoskrnl.exe

deathmetalscott · 17 Jan 2011

I can not put my computer into sleep or hibernate. If I do, I get a BSOD. I reinstalled and installed the nvidia driver, tested it, and was able to sleep/hibernate. Then I updated and get a BSOD. I'm pretty sure it is a Windows update error. I did google searches and really didn't find anything that matched my problem entirely. Thanks for the help.

zigzag3143 · 18 Jan 2011

deathmetalscott said:

I can not put my computer into sleep or hibernate. If I do, I get a BSOD. I reinstalled and installed the nvidia driver, tested it, and was able to sleep/hibernate. Then I updated and get a BSOD. I'm pretty sure it is a Windows update error. I did google searches and really didn't find anything that matched my problem entirely. Thanks for the help.

These were caused by your k57nd60a.sys driver. K57ND60A.SYS is related to Broadcom NetLink (TM) Gigabit Ethernet driver. Broadcom.com - Products

Update and re-install

Code:

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


Loading Dump File [C:\Users\K\Desktop\dump\011511-22776-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c510?
Symbol search path is: SRV*C:\SymCache*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.721) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17105.amd64fre.win7sp1_rc.100929-1730
Machine Name:
Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c9de90
Debug session time: Sat Jan 15 02:44:00.710 2011 (GMT-5)
System Uptime: 0 days 2:13:36.630
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800473fa10, fffff80000b9c528, fffffa80045b8620}

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

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: fffffa800473fa10, Physical Device Object of the stack
Arg3: fffff80000b9c528, Functional Device Object of the stack
Arg4: fffffa80045b8620, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80045b8620

DEVICE_OBJECT: fffffa800527a050

DRIVER_OBJECT: fffffa800525f490

IMAGE_NAME:  k57nd60a.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e2c1d

MODULE_NAME: k57nd60a

FAULTING_MODULE: fffff8800470a000 k57nd60a

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b49579 to fffff80002adecc0

STACK_TEXT:  
fffff800`00b9c4d8 fffff800`02b49579 : 00000000`0000009f 00000000`00000003 fffffa80`0473fa10 fffff800`00b9c528 : nt!KeBugCheckEx
fffff800`00b9c4e0 fffff800`02ad2e95 : fffff800`00b9c5d8 fffff800`00b9c5d8 fffff800`02c4d080 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35110
fffff800`00b9c580 fffff800`02ae7d1e : 00000012`aa48bca7 fffff800`00b9cc18 00000000`0007d75b fffff800`02c4dde8 : nt!KiProcessExpiredTimerList+0x105
fffff800`00b9cbf0 fffff800`02ae5f47 : 00000003`d18b80c2 00000003`0007d75b 00000003`d18b8079 00000000`0000005b : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02ad3a2a : fffff800`02c4ae80 fffff800`02c58cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_k57nd60a.sys

BUCKET_ID:  X64_0x9F_IMAGE_k57nd60a.sys

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

deathmetalscott · 18 Jan 2011

thanks! that fixed it. I wonder why that happened though? Now that I think about it, I did install the broadcom driver for this NIC in hopes to regain Jumbo frame functionality. Meh I guess that driver is unstable....