Hello All,
My system:
- Athlon X2 5000+ Black Edition (Brisbane 65nm) overclocked to 3.0GHz
- MSI K9A2 Platinum motherboard (790FX chipset)
- Crucial Ballistix DDR2 1066, 1GB x 2 (running at DDR2800)
- PC Power & Cooling Silencer 750 Quad PSU
- GeCube HD3870 video card
- Seagate Barracuda 750GB HDD
- Samsung SH-S203N Sata DVD burner
- Kingwin RVT-9225 92mm CPU cooler, installed with Arctic Silver 5
- Sony 1.44MB floppy
- Windows XP Pro (32-bit) w/SP2
System was built mid-February. I began by running Memtest86 v3.4 for 24+ hours with no errors. I then installed the OS, and ran stability tests using Prime95 on both cores, and encountered no errors for 10+ hours. I then set the CPU clock from the initial 2.6GHz to 3.0GHz, and repeated the tests - again, finding no troubles. Although I can't read the core temperatures due to the Brisbane problem, the motherboard reports the CPU temperature in the mid-20s for idle, and low 30s for high loading. The CPU HSF is cool to the touch. The system has been 100% rock stable ever since - until now.
I finished a game of Oblivion last night, and left the system to go into power-saving standby mode. This morning, the screen was blank (as it should have been), but the system wouldn't "wake-up" on keyboard or mouse activity. I reset the system, but the screen remained utterly blank. I repeated this several times, and finally got the BIOS message saying that my overclock had failed. I went into BIOS setup, verified the settings (but didn't change anything) and started Windows. Everything seemed fine.
I started Prime95 in the mixed mode and it failed almost immediately. I then tried the small FFT test, which runs primarily from CPU cache and uses little external memory. The system ran a little longer, but it still failed the test after a minute or so. I then restarted the system and dropped the CPU clock to 2.8GHz, and tried Prime95 again. Still had failures.
I put the Memtest86 floppy into the drive and restarted the system. After running for one minute and 45 seconds, Memtest86 halted with an "unexpected interrupt" error. This is not what I would expect to see for a memory error. I have run this program on other systems with bad RAM, and have seen what those kind of error messages look like. I restarted Memtest86, and shortly afterwards, the program crashed!
This is where I am now. I don't believe it's a RAM problem, but it might be. It could also be a motherboard or CPU problem. My question to all of you is this: How can I figure out what is bad? I don't have any other AMD2+ motherboards or suitable CPUs to swap out, and I don't want to buy more just for the purpose of testing.
I would like (helpful) suggestions as to what I should do next?
Thanks in advance for your help!
Altazi
My system:
- Athlon X2 5000+ Black Edition (Brisbane 65nm) overclocked to 3.0GHz
- MSI K9A2 Platinum motherboard (790FX chipset)
- Crucial Ballistix DDR2 1066, 1GB x 2 (running at DDR2800)
- PC Power & Cooling Silencer 750 Quad PSU
- GeCube HD3870 video card
- Seagate Barracuda 750GB HDD
- Samsung SH-S203N Sata DVD burner
- Kingwin RVT-9225 92mm CPU cooler, installed with Arctic Silver 5
- Sony 1.44MB floppy
- Windows XP Pro (32-bit) w/SP2
System was built mid-February. I began by running Memtest86 v3.4 for 24+ hours with no errors. I then installed the OS, and ran stability tests using Prime95 on both cores, and encountered no errors for 10+ hours. I then set the CPU clock from the initial 2.6GHz to 3.0GHz, and repeated the tests - again, finding no troubles. Although I can't read the core temperatures due to the Brisbane problem, the motherboard reports the CPU temperature in the mid-20s for idle, and low 30s for high loading. The CPU HSF is cool to the touch. The system has been 100% rock stable ever since - until now.
I finished a game of Oblivion last night, and left the system to go into power-saving standby mode. This morning, the screen was blank (as it should have been), but the system wouldn't "wake-up" on keyboard or mouse activity. I reset the system, but the screen remained utterly blank. I repeated this several times, and finally got the BIOS message saying that my overclock had failed. I went into BIOS setup, verified the settings (but didn't change anything) and started Windows. Everything seemed fine.
I started Prime95 in the mixed mode and it failed almost immediately. I then tried the small FFT test, which runs primarily from CPU cache and uses little external memory. The system ran a little longer, but it still failed the test after a minute or so. I then restarted the system and dropped the CPU clock to 2.8GHz, and tried Prime95 again. Still had failures.
I put the Memtest86 floppy into the drive and restarted the system. After running for one minute and 45 seconds, Memtest86 halted with an "unexpected interrupt" error. This is not what I would expect to see for a memory error. I have run this program on other systems with bad RAM, and have seen what those kind of error messages look like. I restarted Memtest86, and shortly afterwards, the program crashed!
This is where I am now. I don't believe it's a RAM problem, but it might be. It could also be a motherboard or CPU problem. My question to all of you is this: How can I figure out what is bad? I don't have any other AMD2+ motherboards or suitable CPUs to swap out, and I don't want to buy more just for the purpose of testing.
I would like (helpful) suggestions as to what I should do next?
Thanks in advance for your help!
Altazi