BSOD on XP Pro install...

Bleek · 26 Jul 2006 at 14:27

Hey guys, having some trouble with a machine.

It was working fine until one day it started to reboot after logging in to Windows. After numerous attempts and curing the problem I tried re-installing XP via the auto repair (console), it got the to point where the old files are removed and then it trys to re-install the O/S but gave me a generic error saying to contact my admin. :rolleyes:

So I then tried re-installing XP Pro over the top, I enter the serial and the hardware starts to install etc then it gets right to the end of the XP install say 5 minutes left and there it is again BSOD.

I get STOP: 0X0000008E (0XC0000005, 0X8062FBF.... the same BSOD as before after login.

Now I assumed at first a ram stick was faulty so I swapped out, same problem, tried 3 known good ram sticks and everything on default timings etc but still the problem persisted.

I'm now thinking it could well be the motherboard at fault here? Any ideas to throw into the mixing pot as I'm stuck without an O/S that wont even install.

Keylow · 26 Jul 2006 at 14:37

Well 0X08E and 0XC05 both point to RAM after a quick google. I take it youve tried different RAM slots?

Bleek · 26 Jul 2006 at 14:58

Keylow said:
Well 0X08E and 0XC05 both point to RAM after a quick google. I take it youve tried different RAM slots?

Yep, that's what makes me think its the mobo! Problem is its not very old at all.

Anyone know of a good ram tester to check my banks?

Chronictank · 26 Jul 2006 at 15:17

you could use memtest to see where the problem is,
http://www.memtest.org/
stick it on a floppy disc/cd and boot from it.

Take 1 DIMM out and run memtest on the one remaning one.
Check for errors
Replace the DIMM currently installed with the one you took out
Run memtest to check for errors.
If you get errors in both runs try both chips in the other slot,
this will tell you if it is definitely the mobo or the ram.

That way you will know which slot is broken, return the mobo under warranty or get a new one i guess if its the culprit

warren_1979 · 26 Jul 2006 at 17:55

What makes you think its not the RAM. I had the same problem on XP install and it was the RAM.

Bleek · 27 Jul 2006 at 11:12

warren_1979 said:
What makes you think its not the RAM. I had the same problem on XP install and it was the RAM.

3 seperate modules that working working fine then all of a sudden all 3 give a BSOD. Just seems unlikely.

Thanks for the link to memtest Chronictank, I'll give it a try.

Admiral Huddy · 27 Jul 2006 at 12:31

Edleake said:
3 seperate modules that working working fine then all of a sudden all 3 give a BSOD. Just seems unlikely.

Thanks for the link to memtest Chronictank, I'll give it a try.

it goes that way.. I had a twin pair of 1Mb OCZ PC4000 sticks. Been in since March.. I reinstalled windows a few weeks back and added a new drive. BSODs all over the place. Thought it was the drive but it turns out one of the stick was faulty after a memtest86+ test. The memory is now in the hands of an RMA.

Why did they go wrong? Who knows.. :confused:

I was sure it was the H/D.. Why wouldn't I.