• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Prime95 errors - please advise

Ch3w33

Member
I am running Prime95 for the first time, and I am getting fatal errors early on (less than 5 minutes) into the testing.

One error I get is:
Best time for 1792K FFT length: 185.978 ms. (this line provided for context)
FATAL ERROR: Resulting sum was 1018852900385555, expected: 1025534127961064

the other is:
Best time for 1792K FFT length: 198.146 ms. (this line provided for context)
FATAL ERROR: Rounding was 0.5, expected less than 0.4

I am running a new Athlon XP 1800+ thoroughbred on an Epox 8RDA+; I have two older Corsair 256M PC2100 DIMMS; Brand new Enermax EG301P-VE(FMA).

I was doing some light overclocking (which is why the first test result is faster) to 2000+, but when I received an error I reset everything back to default. I have not changed any voltages or the FSB.

Accroding to SpeedFan and MBMonitor, the CPU temperature has never exceeded 40C. The voltages right now are 2.61/4.92/12.16 and they have not fluctuated much during the tests or otherwise.

So, according to Prime95 there is definitely something wrong with my hardware. Can anyone help me figure this one out?😕
 
hi,
try using memtest or docmemory and check your ram extensively. if that is not it, it is possible but extremely unlikely that your cpu is giving errors. quite a while ago, the intel pentiums had problems with their fpu and actually couldnt do math correctly. anyway, good luck
 
OK, it's official - after 20 minutes of memtest and 250+ errors thereof, I've concluded that it just MAY be my memory that's the problem.

Seriously though - I ran the default memtest boot image as I was having some issues compiling a custom version. Could that be the problem, or is my memory indeed hosed? If so, how does this happen? It's Corsair, less than a year old, and has never been overclocked.

Thanks for the help.
 
hi,
sounds like it's really the memory.
i've seen this happen quite a few times before. memory does indeed go bad, even though it's not that frequent.
even new memory can be bad. i'd say just to rma it if possible, or replace it if not.
good luck.
 
Are you getting these errors while overclocked or back to normal settings?

Also are you bumping up the speed of the memory in the BIOS? Might want to set it back down to "By Speed" to be safe.

Last thing, with your overclocking, did you bump up the voltages? I got errors in Prime95 when I OCed my P4 2.66Ghz to 3.00Ghz at default voltage, but I just bumped the voltage a tiny amount and now running great.
 
Back
Top