Blue screen Error when booting and not booting at times

Good day all,

I get this blue screen from my machine :

Error code 1000008e, parameter 1 c0000005, parameter 2 8056c0b5, parameter 3 F6F04C24, parameter 4 00000000 .

Now before i got this error.. my machine was giving me the beep codes for bad motherboard/ bad cmos. so i when and bought a new bought.

Windows XP started to install the machine just rebooted.

Now XP is installed and i either get the above error or the machine refuses to start.

The last time i got it to start i did a memtest using memtest and the ram sticks passed with flying colours.

Any pointers would be greatly appreciated.

Could it be a bad processor ? or faulty PSU ? or what else ?


AMD DURON 1200
512MB ram
ASrock K7vm motherboard
40GB hard drive
onboard video, sound, lan.

 

so u got a new MB and u just plunked the system back together w/ xp already installed? define what u did exactly or ... i'd say just clean install if u haven't yet.

 

Ok here is what i did.

When the old board died (as in the cmos beep codes told me.. 9 beeps to be exact.

So i changed the board with a new one.

did a windows clean install on the system. And it rebooted by itself during the install, and i had to do a check disk.

Windows finally installed, then i got the blue screen with that message when i double clicked on the MY computer Icon.

Rebooted and did a memory test with memtest (the latest version) and the memory (512DDR RAM STICK) passed all the test.

AFter memtest rebooted and got that same blue screen error.

Rebooted one more time and the machine refuse to boot up and gives no beep codes what so ever.

when i hit the power button.. the cpu fan starts up, the hard drive, the cd drom.. but no POST and no screen display.

Its been like that since.

 

Should that 1000008e have been 0x0000008e? That would be KERNEL_MODE_EXCEPTION_NOT_HANDLED (nice info to have).

In that case, I'd be pretty confident that the exception was
0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.

That would leave you looking at some sort of memory glitch. Possibly a bad stick even with the memtest returning clean since software testing apps for hardware aren't that reliable when they say all is well. Possibly memory and mobo that just don't like each other. I'm not enough of a hardware guy to know.

I am confident enough it's hardware related rather than OS to move this thread to the hardware section since some sharp folks look at that section who never look in the XP section.