Prime 95 Error

[pirred908]

I started Prime 95 on my computer last night, but ran into a problem. The test only runs for about 30 seconds and than comes up with an error. I don't know what the error is telling me, so thats why I'm here.

Heres the error:

Begining a continuous self-test to check your computer.
Please read stress.txt. Choose Test/Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
FATAL ERROR: Resultng sum was 6.590767582844902s+016, expected: 6.590767582848179e+016
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes - 1 errors, 0 warnings.
Execution halted.

Please help. My system specs are listed in my signature.

 

[MichaelD]

Grr. I typed a big, long reply to this...and my connection crapped out. :| Let's try again.

Basically, your overclock is not stable. P95 will show errors that don't show with other "stress" programs like 3DMark, etc.

Raise the CPU voltage one notch at a time until you get no errors for at least 12 hours. Yes, 12 hours.

If you top out the voltage and it's still not stable, your CPU is incapable of supporting the OC you're requesting from it. I see you've got watercooling...so cooling isn't an issue, IMO.

 

[pirred908]

I've bumped the CPU voltage up to approx. 1.7, and I'm still getting errors on Prime 95, within a minute of the test running? Do I just keep going? Could there be another BIOS setting I should check?

 

[viivo]

It could also be your ram. Have you tested it with Memtest86?

 

[viivo]

Edit: Double post.

 

[pirred908]

I tested my RAM with Memtest86 for 24 hours, with no errors. My RAM timings are set to "Optimal".

 

[pirred908]

^

 

[Navid]

Reduce your CPU frequency gradually and run prime95. Keep doing this until you get no errors.
You should also change the CPU voltage in small steps. Increasing the CPU voltage does not always increase speed. I have a P4 and I get the highest speed at 1.575. If I go one step higher or lower, my speed decreases.

Edit:
The prime95 error text is not really important. The fact that it has stopped means that the CPU has a problem. I say this based on the fact that you have passed memtest.
That is why it is better to run memtest first as you have.

 

[thorin]

CPUs are not designed to be overclocked. If you OC it and it errors then guess what? You went too far for your particular CPU. Put it to it's regular settings and try it. Also let us know what your temps are like.

Thorin

 

[Mullzy]

1) go back to stock everything (ram/cpu/voltage) and make sure Prime is stable
2) put your ram on a divider to completely remove it as a problem(if its already underclocked... sorry I don't know AMD bus/memory ratios)
3) increase your CPU until you top out
4) put your ram back to its fastest setting and see if you're still stable

 

[OMG1Penguin]

If a computer lasts 4ish hours, it will be acceptably stable (for games, not distributed computing), if you get errors that quickly (30 seconds), your apps will crash out of nowhere. It is more irksome than you would first think.

 

[ku]

Same thing happened to me on my old NF7 motherboard. I couldn't figure it out until one day, I decided to switch the the ram slots and it fixed it! Try rearranging the ram (ie. if you're currently running DIMM1+2, try 1+3, you'll still be running Dual Channel)
Also, when I was gettin errors in P95, Memtest86 ran perfectly with no errors.

 

[pirred908]

Okay heres the update:

1. I completly shut down my computer and turned the standby power off.
2. I switched the RAM from slots 1 and 3 to slots 2 and 3.
3. I cleared the CMOS by moveing the jumper over for about 30 seconds, than moved it back.
4. I booted up and went into the BIOS.
5. I tried to to load "Fail-Safe" settings, but my computer would just sit at the motherboard main screen (never got to windows loading screen)
6. I reset the BIOS to "Optimized" settings and the computer booted into windows fine.
7. I ran prime 95, I got the SAME ERROR AGAIN!

What do I do now?

Should I flash the BIOS? If so, how? Do I reinstall windows again?

 

[ectx]

strange your pc won't boot w/ fail safe.

but I'd check the temperature first.

 

[pirred908]

^

 

[pirred908]

^

 

[thorin]

Still waiting to hear what your temps are.

Thorin

 

[pirred908]

Originally posted by: thorin
Still waiting to hear what your temps are.

Thorin

My CPU Temp according to "Motherboard Monitor 5" is 55C

 

[ku]

Hmm... I still think it's your ram. Try taking out 1 stick and running P95 again. If you still get the error, try another slot. If you still get the error, try the other stick and switch slots again if that doesn't work.

 

[pirred908]

Can I put the one stick of RAM into any of the 3 slots?

 

[thejackal1]

you should be able to.

 

[pirred908]

Update:

Completly shut down my computer.

Reset the CMOS useing the proper jumper. I forgot to turn off the standby power, could I have messed something up?

Took both sticks of RAM out, and put one stick in slot 1.

I left the second stick of RAM completly out of the computer.

I had to reset to optimal defaults in the BIOS, so Windows XP Home would boot.

I'm running Prime95 right now, and I'm not getting any errors what so ever.

What do I do now? Try the second stick in slot one to see if its bad? If I ran Memtest86 with both sticks in, with no errors, is it possible the RAM could still be bad?

Please help. Thank you.

 

[pirred908]

Update:

Completly shut down computer.

I took the original stick of RAM out of slot 1 and tried the other stick of RAM in the same slot.

I started Prime 95

A Blue Screen of Death poped up saying "MEMORY_MANAGMENT"

I tried Prime 95 two more times after restarting and the test failed within a minute both times.

Is it safe to say the memory is DOA?

I think I'm going to be RMAing it back to Newegg. Am I making the right decision?

 

[pirred908]

^

 

[HappyCracker]

Run Memtest86 overnight. Why are you running optimal settings anyway? Set everything at default, RAM at SPD, processor non-overclocked to test true stability. Start Memtest with both modules in. If it starts throwing errors then run each stick separately, probably with that one that gave problems first to figure out what the deal is.