Please help me analyze this minidump

[ch33zw1z]

So I got a BSoD 0x0000000A, loaded up the debugger and ran the windbg. There's an error loading ntoskrnl.exe, not sure what that is. Since the BSoD, I've updated the only downlevel driver, Realtek's high def driver is now at the latest. I'm at all the latest firmwares, Memtest86+ tests clean for 5 passes (~8-9 hours IIRC). So far I'm BSoD free since, but you never know..

Thanks!!

**************************

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


Loading Dump File [c:\windows\minidump\mini090709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\windows\symbols
Executable search path is: g:\i386
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Sep 7 10:34:59.890 2009 (GMT-4)
System Uptime: 1 days 18:36:34.879
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {8592a8, 2, 0, 8051bb93}

Probably caused by : ntoskrnl.exe ( nt!IoReadDiskSignature+b5 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 008592a8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8051bb93, address which referenced memory

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


READ_ADDRESS: 008592a8

CURRENT_IRQL: 2

FAULTING_IP:
nt!IoReadDiskSignature+b5
8051bb93 8b00 mov eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 804e39f9 to 8051bb93

STACK_TEXT:
afc60a40 804e39f9 d2d00000 08945778 00000000 nt!IoReadDiskSignature+0xb5
afc60ad0 804e17ee 89b02008 08945778 afc60b04 nt!KeWaitForMultipleObjects+0x2f
afc60ad0 afc60bf0 89b02008 08945778 afc60b04 nt!KiTrap0E+0x1a2
WARNING: Frame IP not in any known module. Following frames may be wrong.
b7d0e150 00000000 b7d4c503 ffffffff b7d4c6fb 0xafc60bf0


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IoReadDiskSignature+b5
8051bb93 8b00 mov eax,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!IoReadDiskSignature+b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

FAILURE_BUCKET_ID: 0xA_nt!IoReadDiskSignature+b5

BUCKET_ID: 0xA_nt!IoReadDiskSignature+b5

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

 

[dfnkt]

The several dumps i've seen where the IRQL_ BSOD game up ended up being faulty RAM. Since yours passes memtest86 pretty well it would almost have to be something else. The few issues I've seen where "unable to load image" for ntoskrnl was brought up (both times I've seen it was with an XP->Vista upgrade) there was a realtek HD audio driver that was corrupt or at least incompatible.

I'm guessing your newest realtek driver is WHQL certified so this leaves me puzzled. Anyone else?? Sounds like a good issue to send to Paul Thurrott @ http://www.winsupersite.com/ -- He is pretty solid in this area and you might either get help or be able to find something to help yourself.

 

[ch33zw1z]

Thanks for the reply. I'll shoot Paul an email and continue PD.