Help Understanding Vista Minidump

[DSF]

I've been having occasional blue screens while playing Left4Dead in Vista64.

Hardware:
E4500 @ 2.93 GHz (11x266)
4GB DDR2-800
XFX 8800GT
Corsair 520W PSU
Samsung Spinpoint 500GB
Gigabyte GA-P35-DS3L

Finally I installed WinDbg and here's one of the recent crash dumps:


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


Loading Dump File [C:\Windows\Minidump\Mini122008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`01a55000 PsLoadedModuleList = 0xfffff800`01c1adb0
Debug session time: Sat Dec 20 14:47:01.140 2008 (GMT-5)
System Uptime: 0 days 4:39:01.216
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8003af9060, fffffa8005d40050, fffffa8004a7bc10}

*** WARNING: Unable to verify timestamp for Rtlh64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
Probably caused by : Rtlh64.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: fffffa8003af9060, Physical Device Object of the stack
Arg3: fffffa8005d40050, Functional Device Object of the stack
Arg4: fffffa8004a7bc10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffffa8004a7bc10

DEVICE_OBJECT: fffffa8005d40050

DRIVER_OBJECT: fffffa8005cc83f0

IMAGE_NAME: Rtlh64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45190cf7

MODULE_NAME: Rtlh64

FAULTING_MODULE: fffffa6002c72000 Rtlh64

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80001b0905e to fffff80001aaa350

STACK_TEXT:
fffff800`02ab49f8 fffff800`01b0905e : 00000000`0000009f 00000000`00000003 fffffa80`03af9060 fffffa80`05d40050 : nt!KeBugCheckEx
fffff800`02ab4a00 fffff800`01ab28b3 : fffff800`02ab4af0 00000000`00000000 00000000`00000001 fffff800`01bfaf01 : nt! ?? ::FNODOBFM::`string'+0x18318
fffff800`02ab4a70 fffff800`01ab3238 : fffff800`02ab4cd0 fffffa80`05eaaf02 fffff800`02ab4cc8 fffffa60`00000010 : nt!KiTimerListExpire+0x333
fffff800`02ab4ca0 fffff800`01ab3a9f : 00002c8c`f877cf5a 00000000`00000000 fffffa80`00000010 fffff800`01bcca80 : nt!KiTimerExpiration+0x1d8
fffff800`02ab4d10 fffff800`01ab4b62 : fffff800`01bc9680 fffff800`01bc9680 00000000`00000000 fffff800`01bceb80 : nt!KiRetireDpcList+0x1df
fffff800`02ab4d80 fffff800`01c825c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`02ab4db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_IMAGE_Rtlh64.sys

BUCKET_ID: X64_0x9F_IMAGE_Rtlh64.sys

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

Sounds like it was a driver issue? Is there any way to know which driver specifically?

 

[AnonymouseUser]

"Rthl64.sys" appears to be associated with the onboard Realtek gigabit network controller. See if you can find updated drivers for it.

 

[DSF]

Thanks! I updated the onboard LAN drivers last night. We'll see how it goes.