stop 0x0000008e on A8V

Kels0

Distinguished
Aug 24, 2004
1
0
18,510
I'm having the strangest problem with a newly built system. I get that stop error about 10 seconds after logging into a fresh WindowsXP install. No file is referenced on the bluescreen, only additional memory addresses (0xC0000005,0x8060AB13,0xB21F79A0,0x00000000)

Hardware:
-Asus A8v Deluxe
-Athlon 3500+
-ATI x800 pro video
-Promise S150 SX4 RAID controller, with 3 new 200gb Maxtor SATA drives setup as RAID-5 (latest firmware and driver)
-2x512 Corsair TwinXL 3200 sticks.
-Antec trupower 480 PS

Tried the following, with no luck:

-Latest Hyperion drivers are loaded
-4.7 and 4.9 Catalyst drivers tried
-Memtest86 run for 6 hours, no errors
-nothing in event viewer sheds any light
-all startup files stripped from startup folder and registry.
-Changed BIOS settings from "Auto" to manual, and bumped memory voltage to 2.7v.
-dropped CPU voltage to 1.5v
-Changed BIOS from AGP 8x to 4x
-Temp on Asusprobe is in the low 30's C.
-disabled Cool n Quiet and Qfan
It does boot to safe mode, but it has frozen in safe mode a couple of times.

What gets me is *when* it happens...I can literally count to 10 before it blows up after logging in. That's gotta be a clue, but I don't know what it's telling me.

I'm about to strip another system for parts to swap out, but I thought I'd ask here first, since I'm not looking forward to hours of part swapping and OS reinstalling 🙁

TIA for any thoughts...
 
Try starting up with your hard drives connected through IDE.

<font color=blue>AthlonXP-M 2500+(12x211)</font color=blue><font color=green>Abit NF7-S</font color=green><font color=red>Kingston DDR400 2x256Mb</font color=red>
<b>Old Expierienced Hands, Finally</b>
 
I will asume that you have your memory running LL or lower. Now that I've made an ass of u and me, I will tell you that the ondie mem controller needs a good burn-in (sometimes) before it can handle low latencies. Relax your mem timings a bit, and you should be ok.