BSOD on Win 2000 Pro

hellraiser357 · 10-07-2005, 11:25 AM

My dad's PC flashed the BSOD while running defrag yesterday. I am trying to troubleshoot the proble, but the only MS KB article that I think applies is pretty much Greek to me. The PC flashed the BSOD three times in a row. First time during defrag, and the second and third times during reboot. After the third reboot, it came up fine. Any ideas?

Microsoft KB Article

1st message during defrag:

***STOP: 0X000000IE (OX00000ID, 0XBC7808B4,0XE3ED74C8,0X85D47020)
KMODE_EXCEPTION_NOT_HANDLED
BEGINNING DUMP OF PHYSICAL MEMORY
PHYSICAL MEMORY DUMP COMPLETE. CONTACT YOUR SYSTEM ADMINISTRATION OR TECHNICAL SUPPORT GROUP.

TURNED OFF AND BACK ON # 1 -

0X000000IE (0XC0000005, 0X00000000, 0X00000000, 0X00000000)

TURNED OFF AND BACK ON # 2 -

0X000000IE (0XC0000005, 0X00000000, 0X00000000, 0X00000000)

TURNED OFF AND BACK ON # 3 -

SYSTEM BOOTED OK

Any help would be very much appreciated as this is a business PC.

**Ha-y-n** · 10-07-2005, 01:33 PM

hello,

did you install anything new (hardware or software) before the bsods started?

You could test your RAM and Harddrive

I use memtest86 to test my RAM

for the harddrive i download the diagnostic tools from the manufacturers website(ex. Maxtor, western digital, etc.)

good luck

hellraiser357 · 10-08-2005, 04:40 AM

Before the BSOD's, we had a game on the PC that would cause it to reboot while playing. We figured it was that particular game, because it would only reboot while playing that game. So, we uninstalled it, and the BSOD's started. My dad say's it did okay until he got online to check his e-mail today, and bam it hit again. I am going to run a RAM check on it, and see if it comes up with any thing.

In the KB article I linked to, there is metion of a file called ntstatus.h that is supposed to list the drivers and where they are located in memory by hex addy. This is apparently how the BSOD error codes are supposed to be translated. Since 2000 is NT based, should I be able to locate this file and how?

**Ha-y-n** · 10-08-2005, 08:59 PM

was there a driver listed in your bsod?

this was the example M$ had in the article:

Quote:

For example, in the following STOP error message, an access violation (0xC0000005) occurred in module Srv.sys, which is the kernel mode server service:
STOP: 0x0000001E (0xC0000005, 0xFCA733B9, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED 0xC0000005 from 0xFCA733B9 (0x0, 0x0)Address FCA733B9 has base at FCA70000 - SRV.SYS

Paladin-X · 10-08-2005, 09:32 PM

Overheating possibly? I had the same kind of problem once. My power supply fan had apparently died, which I wasn't aware of. I ran a disk defrag, it blue screened and killed my hd. :S

hellraiser357 · 10-14-2005, 09:09 PM

well, the ole man went and bought some cleanup/tuneup utility the other day, and ran it on his PC. Since then, he has had no probs. Wish he'd have left it alone so I could get to what was ailin' it, but but he got a little ancey (sp?). I do appreciate the help anyway.

10-07-2005, 11:25 AM	#1 (permalink)
hellraiser357 Registered User Join Date: Aug 2004 Location: Texas Posts: 66 OS: Win2000	BSOD on Win 2000 Pro My dad's PC flashed the BSOD while running defrag yesterday. I am trying to troubleshoot the proble, but the only MS KB article that I think applies is pretty much Greek to me. The PC flashed the BSOD three times in a row. First time during defrag, and the second and third times during reboot. After the third reboot, it came up fine. Any ideas? Microsoft KB Article 1st message during defrag: ***STOP: 0X000000IE (OX00000ID, 0XBC7808B4,0XE3ED74C8,0X85D47020) KMODE_EXCEPTION_NOT_HANDLED BEGINNING DUMP OF PHYSICAL MEMORY PHYSICAL MEMORY DUMP COMPLETE. CONTACT YOUR SYSTEM ADMINISTRATION OR TECHNICAL SUPPORT GROUP. TURNED OFF AND BACK ON # 1 - 0X000000IE (0XC0000005, 0X00000000, 0X00000000, 0X00000000) TURNED OFF AND BACK ON # 2 - 0X000000IE (0XC0000005, 0X00000000, 0X00000000, 0X00000000) TURNED OFF AND BACK ON # 3 - SYSTEM BOOTED OK Any help would be very much appreciated as this is a business PC.

10-07-2005, 01:33 PM	#2 (permalink)
Ha-y-n 12-0, GO WARRIORS! Join Date: Oct 2004 Location: Hawaii Posts: 682 OS: WinXP Pro	hello, did you install anything new (hardware or software) before the bsods started? You could test your RAM and Harddrive I use memtest86 to test my RAM for the harddrive i download the diagnostic tools from the manufacturers website(ex. Maxtor, western digital, etc.) good luck __________________ bRiAn Harddrive Diagnostic Tools, MemTest86

10-08-2005, 04:40 AM	#3 (permalink)
hellraiser357 Registered User Join Date: Aug 2004 Location: Texas Posts: 66 OS: Win2000	Before the BSOD's, we had a game on the PC that would cause it to reboot while playing. We figured it was that particular game, because it would only reboot while playing that game. So, we uninstalled it, and the BSOD's started. My dad say's it did okay until he got online to check his e-mail today, and bam it hit again. I am going to run a RAM check on it, and see if it comes up with any thing. In the KB article I linked to, there is metion of a file called ntstatus.h that is supposed to list the drivers and where they are located in memory by hex addy. This is apparently how the BSOD error codes are supposed to be translated. Since 2000 is NT based, should I be able to locate this file and how?

10-08-2005, 09:32 PM	#5 (permalink)
Paladin-X Member Join Date: Sep 2005 Location: Edmonton Posts: 53 OS: Windows XP	Overheating possibly? I had the same kind of problem once. My power supply fan had apparently died, which I wasn't aware of. I ran a disk defrag, it blue screened and killed my hd. :S

10-14-2005, 09:09 PM	#6 (permalink)
hellraiser357 Registered User Join Date: Aug 2004 Location: Texas Posts: 66 OS: Win2000	well, the ole man went and bought some cleanup/tuneup utility the other day, and ran it on his PC. Since then, he has had no probs. Wish he'd have left it alone so I could get to what was ailin' it, but but he got a little ancey (sp?). I do appreciate the help anyway.