Need help reading minidumps

[poohgc]

Hello all,

I have a Windows 2000 pro machine with service pack 4 and all the patches, that randomly gives BSOD and freezes up. I have tried to read the minidumps, but I am having problems with the symbol part. I have attached the minidumps in hopes that someone would take a look at them and advise me regarding what the problem may be. Thank you for any help you can give.

gmc

 

[raybay]

Your Minidump does not open for us.
You likely have a memory error or a hard drive failing...

 

[poohgc]

OOO great, the hard drive is less than a year old!! Thanks anyway.

gmc

 

[poohgc]

OK, I have ignored the symbol message this thing gives me and below is one of the minidumps. Does this state anything?

Thanks

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: 55444648, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 804321a1, address which referenced memory

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

WRITE_ADDRESS: unable to read from 8047edb4
unable to read from 8047e864
unable to read from 8047e738
unable to read from 8046a85c
unable to read from 8047e750
unable to read from 8047e860
unable to read from 80471038
unable to read from 8047e8dc
unable to read from 8047ed80
55444648

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiWaitTest+50
804321a1 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 00000000 to 80467e07

STACK_TEXT:
804716d0 00000000 55444648 00000002 00000001 nt!MiAllocatePoolPages+0x5fd


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiWaitTest+50
804321a1 ?? ???

SYMBOL_NAME: nt!KiWaitTest+50

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45ec3c8f

FAILURE_BUCKET_ID: 0xA_W_nt!KiWaitTest+50

BUCKET_ID: 0xA_W_nt!KiWaitTest+50

Followup: MachineOwner