XP Memory Dump

[Guest]

I have a computer that is continuing to blue screen. First it was on HAL.DLL
then the network driver e100?.sys now on NTOSKRNL.EXE the latest dump is
below. Does anyone have any ideas on what to do?

Thanks,

Tom


Loading Dump File [C:\Documents and Settings\tsteinman\Desktop\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Product: Server
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Mon Apr 4 20:51:19.427 2005 (GMT-5)
System Uptime: 0 days 2:07:26.186
WARNING: Process directory table base 0589D000 doesn't match CR3 00030000
WARNING: Process directory table base 0589D000 doesn't match CR3 00030000
Loading Kernel Symbols
..............................................................................................
Loading unloaded module list
...........
Loading User Symbols
.............................................................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, 0, a2000000, 84010400}

Probably caused by : ntoskrnl.exe ( nt!CmpComputeHashValue+59 )

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

 

[Guest]

reinstall, the workarounds to install files that are missing is almost non
existent,
Win 98 2nd ed( dos), you could renistall any file, Not true with Win XP,
they have
limited access to file recopying and reinstalling, you may try to dump the
system
files and recopy these in, this almost never works for most people, though,
the fastest
way is to reinstall and then call in to get your new activation number.
Cheers
Rho_1r(VIP) Not MVP

 

[Ron Martell]

I have a computer that is continuing to blue screen. First it was on HAL.DLL
then the network driver e100?.sys now on NTOSKRNL.EXE the latest dump is
below. Does anyone have any ideas on what to do?

Thanks,

Tom

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, 0, a2000000, 84010400}

The actual STOP error code, plus the 4 parameters and the additional
data, from the Blue Screen are more useful than the memory dump data
for these newsgroups.

If I am reading this information correctly the BugCheck 9C would be
the same as a STOP: 0x0000009C and that is a MACHINE_CHECK_EXCEPTION
which is primarily a hardware related item.

Prime suspects would include:
- Overheating. A cooling fan failure, inadequate size cooling fan,
fan and heatsink not properly mounted onto CPU, etc.
- Overclocking. Easy to fix. Just restore the machine to factory
specs for CPU and bus speeds.
- Other hardware failures, including RAM defects, CPU malfunction,
power supply failing, etc.

Hope this is of some assistance.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm