Windows Server 2000 hardware issue? [DUMP DATA]

Not sure why this server crashed but this dump file suggests it was a irq to a driver that shows a referenced address in memory being to high? Can anyone help me on this? Thank you!

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


Loading Dump File [E:\memdump\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer
Kernel base = 0x80400000 PsLoadedModuleList = 0x80485b80
Debug session time: Thu Apr 6 11:09:48.713 2006 (GMT-4)
System Uptime: 4 days 10:01:54.873
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {63, 1c, 0, 80415c1c}

*** ERROR: Module load completed but symbols could not be loaded for cdm.sys
Probably caused by : cdm.sys ( cdm+3ad64 )

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

0: 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: 00000063, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 80415c1c, address which referenced memory

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


READ_ADDRESS: 00000063

CURRENT_IRQL: 1c

FAULTING_IP:
nt!ExpBoostOwnerThread+2c
80415c1c 8a4063 mov al,[eax+0x63]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80415c1c to 8046b1ac

STACK_TEXT:
bec58a70 80415c1c ffffffff 881c21c8 bec58aa0 nt!KiTrap0E+0x210
bec58ae4 80415e9a 00000001 8675ab08 8675aae8 nt!ExpBoostOwnerThread+0x2c
bec58b10 8041547c 00000000 beb2b940 86969008 nt!ExpWaitForResource+0x166
bec58b28 beb22d64 8675aa00 881c21c8 bec58b60 nt!ExAcquireResourceSharedLite+0xc6
WARNING: Stack unwind information not available. Following frames may be wrong.
bec58b38 beb2359e 86969008 00000000 00000001 cdm+0x3ad64
bec58b60 beb14563 8696904c 00000000 beb1345a cdm+0x3b59e
bec58b90 beb15023 8669ab28 00000000 00000000 cdm+0x2c563
bec58be8 beb1558d 8668ba08 8669ab28 00000000 cdm+0x2d023
bec58c40 beb14950 88018948 bec58c6c 00000002 cdm+0x2d58d
00000000 00000000 00000000 00000000 00000000 cdm+0x2c950


STACK_COMMAND: kb

FOLLOWUP_IP:
cdm+3ad64
beb22d64 eb06 jmp cdm+0x3ad6c (beb22d6c)

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 4

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: cdm+3ad64

MODULE_NAME: cdm

IMAGE_NAME: cdm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43d94e24

FAILURE_BUCKET_ID: 0xA_cdm+3ad64

BUCKET_ID: 0xA_cdm+3ad64

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

 

Hardware problem

Hi,

Your windows is crash at IRQL x'1c' which is timer routine. This is the sign of hardware error. According to record, 40% is ram, 26% is CPU and 13% is M/B.

 

so what do i do?

How can i narrow down the faulty hardware?

 

The faulty hardwar may be ram, CPU or Motherboard.

The following problem matches your problem and the culprit is faulty motherboard.
http://www.techspot.com/vb/topic16994-pg9.html&pp=20