Go Back > Great Internet Mersenne Prime Search > Software

Thread Tools
Old 2002-08-31, 17:24   #1
ebx's Avatar
Aug 2002

101 Posts


I have seen a few errors in my log files at 2 different hosts, one at home and one in a rack room.

Two error types:

ERROR: ROUND OFF (0.4999008179) > 0.40

ERROR: SUM(INPUTS) != SUM(OUTPUTS), 6.671785364156798e+16 != 6.671785364161534e+16

Most are SUM. Both cases followed by

Possible hardware failure, consult the readme file.
Continuing from last save file.

Torture for hours didnt produce any info. They all started in a very hot day. I dont know one in rack room but my home CPU was over 60c.

How bad are they?
ebx is offline   Reply With Quote
Old 2002-08-31, 17:44   #2
Digital Concepts
Digital Concepts's Avatar
Aug 2002

2×33 Posts

Overheating does cause errors in CPU and memory. George wrote here, that you have a 50% change of the exponent run being invalid.

Prime95 detected that something happened when numbers went out of spec. It kept reruning from the last known good checkpoint until numbers went back into spec. The problem is the overheat may have harmed work done before that checkpoint (but didn't know it yet) and this would then carry through the rest of the WU.
Digital Concepts is offline   Reply With Quote
Old 2002-08-31, 18:36   #3
ebx's Avatar
Aug 2002

11001012 Posts

RATS! 56% is much too high. Will errors be reported to primenet so it could set a flag for those exponents?

Or offer an option that when we see such an error, we start from the beginning.
ebx is offline   Reply With Quote
Old 2002-08-31, 19:47   #4
garo's Avatar
Aug 2002
Termonfeckin, IE

22·691 Posts

Yes the errors are reported to primenet. Anyway, doublechecking ensures that only matching results are accepted.

If your CPU temp is back to normal and you have less than 50% of the exponent complete I'd say start over.

Stop Prime95.
Go into the P95 directory and look for two files named pxxxxxxx and qxxxxxx where the x's are numbers representing your exponent. Remove the two files and restart P95 and you should start over.
garo is offline   Reply With Quote
Old 2004-01-02, 22:09   #5

2×3×7×127 Posts
Default lots of epsilon errors

Hi, I got all these errors (and no others) over a period of a few days.

The errors seem to all be very small; within a reasonable floating-point epsilon.

I ran the torture test for a few hours without failures. My AMD Athlon 2700+ isn't overclocked. It's not hot here.

I'm disappointed; I had hoped to be able to help with the Mersenne prime search. But, I am going to discontinue running this computation.

If in fact these are epsilon errors and the results from my computer have a chance of being useful, could someone let me know?

Oliver Jones

Iteration: 4592344/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 1.276158324226189e+83 != 1.27615832422619e+83
Iteration: 4691536/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 2.917352435159693e+82 != 2.917352435159695e+82
Iteration: 6706828/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 6.538809292854271e+66 != 6.538809292854284e+66
Iteration: 6791001/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 6.548121686333023e+66 != 6.548121686333019e+66
Iteration: 6841061/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 1.113625838140894e+67 != 1.113625838140895e+67
Iteration: 7264636/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 1.70034274692042e+76 != 1.700342746920419e+76
Iteration: 7499587/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 1.446904841557651e+67 != 1.44690484155765e+67
Iteration: 7622131/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 6.479168211454303e+67 != 6.479168211454303e+67
Iteration: 7635629/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 2.365930387327026e+67 != 2.365930387327026e+67
Iteration: 8828490/22024853, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 3.649538737865422e+83 != 3.649538737865421e+83
  Reply With Quote
Old 2004-01-02, 22:25   #6
nfortino's Avatar
Nov 2003

3×5×11 Posts
Default Re: lots of epsilon errors

Originally posted by OliverJones
If in fact these are epsilon errors and the results from my computer have a chance of being useful, could someone let me know?
Completed exponents with 10 sum(inputs)!=sum(outputs) historically have a 60% chance of being bad, and therefore you should not finish it. Try running Memtest86 to see if bad memory is the cause of your problem. If that comes clean, try running a few double checks, and when they complete check here (link at bottom of page) to check if they match the other result.
nfortino is offline   Reply With Quote

Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
ERROR: SUM(INPUTS) != SUM(OUTPUTS) AES PrimeNet 6 2007-10-05 18:48
LLR SUM(INPUTS) != SUM(OUTPUTS) error jbristow Software 4 2007-08-14 04:07
v. 2.13: SUM(INPUTS) != SUM(OUTPUTS) Kaiw Software 7 2005-10-26 14:49
SUM(INPUTS) != SUM(OUTPUTS) rudi_m Software 3 2005-08-22 15:42
ERROR: SUM(INPUTS) != SUM(OUTPUTS) flava Hardware 3 2004-01-19 17:52

All times are UTC. The time now is 16:00.

Fri May 7 16:00:33 UTC 2021 up 29 days, 10:41, 1 user, load averages: 3.77, 3.90, 4.05

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.