I could only fit four dumps in the 100k file limit.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfdfdf7f7, 0x00000000, 0xfdfdf7f7, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini061805-02.dmp.

There's that.

Attached Files

Reavance Minidump.zip (85.9 KB, 9 views)

Two minidumps are inacessible which are the symptoms of the severe hardware error. One minidump with 107 memory corruption errors and other minidump crashes with bugcheck code 24. I believe that this is the ram problem.

Reseat the memory stick to another memory slot. If it still crashes, take out a memory stick and diagnostic which memory stick is bad.

Attach more minidumps here.

CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
806b5f7f-806b5f8d 15 bytes - hal!KeGetCurrentIrql+a5b
[ 00 00 00 00 00 00 00 00:07 44 03 44 03 5a 13 44 ]
806b5f8f-806b5f91 3 bytes - hal!KeGetCurrentIrql+a6b (+0x10)
[ 00 00 00:05 41 65 ]
806b5f94-806b5f9a 7 bytes - hal!KeGetCurrentIrql+a70 (+0x05)
[ 00 00 00 00 00 00 00:6c 08 06 32 d4 03 40 ]
806b5f9e-806b5fa0 3 bytes - hal!KeGetCurrentIrql+a7a (+0x0a)
[ 00 00 00:6c 08 44 ]
806b5fa2-806b5fb7 22 bytes - hal!KeGetCurrentIrql+a7e (+0x04)
[ 00 00 00 00 00 00 00 00:5a 13 44 03 44 03 5a 13 ]
806b5fb9-806b5fc1 9 bytes - hal!KeGetCurrentIrql+a95 (+0x17)
[ 00 00 00 00 00 00 00 00:02 c4 03 44 04 5a 13 44 ]
806b5fc3-806b5fc9 7 bytes - hal!KeGetCurrentIrql+a9f (+0x0a)
[ 00 00 00 00 00 00 00:02 c4 03 46 32 0e 4f ]
806b5fcd-806b5fcf 3 bytes - hal!KeGetCurrentIrql+aa9 (+0x0a)
[ 00 00 00:f0 df ff ]
806b5fd2-806b5fd8 7 bytes - hal!KeGetCurrentIrql+aae (+0x05)
[ 00 00 00 00 00 00 00:6c 08 06 32 02 08 44 ]
806b5fda-806b5fde 5 bytes - hal!KeGetCurrentIrql+ab6 (+0x08)
[ 00 00 00 00 00:5a 13 44 04 4c ]
806b5fe0 - hal!KeGetCurrentIrql+abc (+0x06)
[ 00:4c ]
806b5fe2-806b5ff0 15 bytes - hal!KeGetCurrentIrql+abe (+0x02)
[ 00 00 00 00 00 00 00 00:5a 13 69 64 44 04 1f 03 ]
806b5ff2-806b5ff6 5 bytes - hal!KeGetCurrentIrql+ace (+0x10)
[ 00 00 00 00 00:e0 e5 bf 0c 72 ]
806b5ff8 - hal!KeGetCurrentIrql+ad4 (+0x06)
[ 00:14 ]
806b5ffa - hal!KeGetCurrentIrql+ad6 (+0x02)
[ 00:1b ]
806b5ffc - hal!KeGetCurrentIrql+ad8 (+0x02)
[ 00:38 ]
806b5ffe-806b5fff 2 bytes - hal!KeGetCurrentIrql+ada (+0x02)
[ 00 00:1f 03 ]
107 errors : !hal (806b5f7f-806b5fff)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .trap ffffffffbab9eaa4 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE

I moved the ram to the other slot, and it froze again. I haven't had any BSOD's since yesterday but I have had a whole lot of freezing during games. These dumps are .rar inside .zip

Attached Files

	Dumps 1.zip (84.0 KB, 1 views)
	Dumps 2.zip (96.8 KB, 1 views)
	Dumps 3.zip (91.1 KB, 2 views)
	Dumps 4.zip (82.5 KB, 1 views)

You have 8 minidumps which are inaccessible. 4 minidumps has memory corruption. 1 minidump fails at IRQL 18. All the evidence shows that it is hardware problem. Your XP is at base level but your Norton AV, Zone Alarm are most current. nVidia Display card driver is out-dated.

I suggest you should update XP to SP2. Upgrade nVidia Display card driver. I would expect your PC have less BSOD. If it is acceptable, it is no need to replace the RAM.

Alright, thanks, I guess that means I gotta pick up some more RAM, and hopefully that will fix the problem.

1. Upgrade XP tp SP2
2. Afeter upgradeif BSOD still exists, replace the RAM.

Don't send private message to me as I cannot relate which problem that you are referring. I have multiple problem on hand. You are one of them. I have to spend almost ten minutes to find your original url. If you want faster feedback, post your message here and I will get your message.

Do you follow my instruction? Upgrade to SP2 and nVidia Display card driver. Zip 4 to 5 minisumps and attach the zip file here.

Okay, you previously said that it was likely to be a ram problem, I replaced the ram and my problems persist, I've updated my nVidia drivers to the latest from the website. I cannot upgrade to SP2. If the evidence points to a hardware problem, what are the other possible devices that could have failed?

I looked through the error reports, and I've got the following stop codes.

0x50
0x8e
0xBE
0x24
0x9c

New dumps

5 of your latest minidumps are inaccessible and one minidump has memory corruption. Especially the number of bytes of corrupted memory is the sames as your previous dump. They are symptoms of hardware problem. As you replaced the RAM and the CPU L2 cache memory may be culprit.

Your XP SP1 is almost 4 years behind. If you cannot upgrade to SP2, you should apply latest patch to XP SP1. It will make your system more stable.

Okay, you and are I almost positive it's a hardware problem, what should I replace? I reinstalled windows, and I had BSOD's during a few failed setup attempts and my game freezes with nothing else installed. I have previously ran this game on the same system, without fault, with the exception of certain items have been removed now (extra lan card, dialup modem). I myself have narrowed it down to being either the video card, motherboard, or processor. Of those three which do you think I should replace. Motherboard and processor can be got in a package and thus kill 2 birds with one stone.


Edit: Also, do you of any programs I can use to test the motherboard or processor for faults?

Problem has been resolved. Interestingly enough I cleaned a crapload of dust off of the heat sink and fan and applied new thermal compound and my problems disappeared.

Thanks for sharing your experience with us. You are a good guy.

Do you have an idea of how hot your cpu is?

i get the same isssues.

There has a lot of enquiry about bugcheck 9C and most of them have no known solution. For this problem report by Reavance, one minidump was crashed with bugcheck code 9C.

Mini062805-05.dmp BugCheck 9C, {3, 3beee698, f6000000, 843}
Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ff8 )

This problem is confirmed relating to overheat. I hope this thread can provide hints to determine overheat problem.

2 years laters......
It was an overheating issue. I cleaned the heatsink and fan of dust and reseated them with new thermal paste and the issue disappeared.