DMP File: Help me decode

What am I looking at?


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


Loading Dump File [C:\Documents and Settings\wallacsm\Desktop\DMp\Mini112910-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\websymbols\Debug 2
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Machine Name:
Kernel base = 0x80400000 PsLoadedModuleList = 0x80485b00
Debug session time: Mon Nov 29 17:37:05.619 2010 (UTC - 6:00)
System Uptime: not available
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 D1, {14, 2, 0, f2080875}

Unable to load image ADM9X.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ADM9X.sys
*** ERROR: Module load completed but symbols could not be loaded for ADM9X.sys
Probably caused by : ADM9X.sys ( ADM9X+875 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f2080875, address which referenced memory

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


READ_ADDRESS: unable to read from 80484220
unable to read from 80483ea4
unable to read from 80483e34
unable to read from 8047a7d8
unable to read from 80483e38
unable to read from 80483ea8
unable to read from 8047a7dc
unable to read from 80483f80
unable to read from 80484224
00000014

CURRENT_IRQL: 2

FAULTING_IP:
ADM9X+875
f2080875 ?? ???

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 00000000 to 8046b12c

STACK_TEXT:
80475e00 00000000 00000000 8552f0a8 8552f30c nt!RtlInitStackTraceDataBaseEx+0xa1


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
ADM9X+875
f2080875 ?? ???

SYMBOL_NAME: ADM9X+875

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ADM9X

IMAGE_NAME: ADM9X.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d92c1b7

FAILURE_BUCKET_ID: 0xD1_ADM9X+875

BUCKET_ID: 0xD1_ADM9X+875

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

 

As with most crash dumps it is not always obvious what the problem is, this one does suggest a driver issue but it could also be caused by a faulty memory module.

Could you please complete your system details so we can all see what PC and type of system we are dealing with.

Could you include a bit of history concerning the crashes, how often they happen, what software you use when it happens, and anything else that may help us to narrow down the cause. Also tell us if there have been any other problems occuring.

 

Hi,

Adm9x.sys refers to a network-card linked to ADMtek. Most likely a built-in network card, but might also be an extra card.

0x00000014, is a system error referring to that a driver is trying to access a device/unit that is not available. Thus accessing invalid memory, and therefore giving you a BSOD.

If you can still use the system, uninstall your motherboards drivers (If you have a built-in network card). Otherwise uninstall the network card, and see if the BSOD still appears. If you can't access the system regularly, run SafeMode without networking.

 

The system is still usable. I have uninstalled and reinstalled the driver for the network card. I will watch it over night and let you know if there are any additional problems.

Thanks everybody for the help!