Thread: Windows XP memory dump PROBLEM

Too blurry to read the details

try booting into the xp recovery console from the original cd and type "fdisk /mbr"0 at the prompt

Your pic must be blurry, cause I haven't opened a bottle today and I can't read it.

Post what it says, paticularly from the technical specifications onwards

On that screen, there is one line like this:

STOP 0x0000 (0x0000, 0x0000, 0x0000, 0x0000)


Tell me what those numbers are, and I can tell you where your problem is.

Originally Posted by Giuliano

On that screen, there is one line like this:

STOP 0x0000 (0x0000, 0x0000, 0x0000, 0x0000)


Tell me what those numbers are, and I can tell you where your problem is.

That was the funniest thing I've read all day.

Never will a stop error like this (my experience now damn it!) tell you anything really about your specific problem. MS usually points at the ram first. That's what I usually point at first too. BUT, it could be ram, video, power supply, f*ed drivers, bad sectors on your hdd, anything really. I've even had a screwy prob with a floppy drive that caused stop errors when it was plugged in. Try the basic stuff first. Replace your ram, try a diff power source/supply, run an XP repair, remove devices from safe mode and try to boot... Ya know man. Maybe even try a different hard drive with a new install of XP on it.

Take no offense Giuliano, I do not mean to degrade you or anything. MS just doesn't program the troubleshooting side of things to tell you anything about your STOP errors...

Originally Posted by Tidder

That was the funniest thing I've read all day.

I'm happy you were amused, but I was serious.

Originally Posted by Tidder

Never will a stop error (my experience now damn it!) tell you anything really about your specific problem.

I disagree - I work on high-end Windows server platforms for a living, and have had to occasionally debug a STOP error.


In any case, I was saying that I could usually tell from the STOP code where the problem was, not what the specific problem was.

Such as a bad driver, a corrupt filesystem, or a hardware error.

The five numbers from a STOP code can mean a lot.. to those who know how to interpret it.

Originally Posted by Giuliano

The five numbers from a STOP code can mean a lot.. to those who know how to interpret it.

HAHA!!

I just it man. C'mon now, I'm not gonna sit here and try to interpret ANYTHING! I just hope that someone else out there isn't as lazy as I, and has the answer.

Well, I appreciate all the input thus far folks. Below is what it says after Technical info:

STOP: 0x0000008E (0xc0000005,0x8059231E,..........., 0x000000000)

I didn't copy the last 2 sections but I recall the last one being all 0's...

Giuliano or anyone...any help would be greatly appreciated.

When I was young, I found a beauty of Google tool:

http://www.google.com/search?hl=cs&q=0x0000008E&lr=

first hit:
http://support.microsoft.com/default...;EN-US;Q315335

man....