Help test 2995125705 - Find a new top 5000 prime!

[lsoule]

710-711 complete, no primes.
Taking 712-713.

[Dougy]

706-707 complete, no primes.

[segmtfault]

709-710 complete, no primes.
Taking 713-714

[Kosmaj]

574-576 and 707-708 complete, no primes.
Taking 714-715.

Dougy
Thanks for your contribution. Checking these numbers takes a while but please condsider testing one more range later. If you prefer finding a (smaller) prime quickly, have a look at 15k thread or k*2^n-1, k<300 thread. And good luck with your studies!

[lsoule]

712-713 complete, no primes.
Taking 715-716

[segmtfault]

713-714 complete, no primes.
Taking 716-717

[em99010pepe]

Taking 717-718.

Carlos

[segmtfault]

I am also reserving 718-719

[BifMeister]

I'm reserving 719-720.

Thanks,
Bif

[em99010pepe]

Just checked the results.txt file and I have this line:

2995125705*2^717323-1 is not prime.
Iter: 138279/717344, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 5919653647646.242 != -9.444732988344107e+020
Possible hardware failure, consult the readme file.
Continuing from last save file.
2995125705*2^717345-1 is not prime.

The error is related to which number?

2995125705 717318
2995125705 717319
2995125705 717323
2995125705 717345
2995125705 717349

I will finish the current range then test again that number (717323 or 717345).

Cheers,

Carlos

[Kosmaj]

Carlos
It's related to n=717345. This can be a serious problem meaning that the program can miss primes. It's most often due to overheating of cpu[s], so if you are overclocking then slow down, if it's too hot in your room switch on the air-conditioner if you are running several applications at once then stop some of them or run LLR during the computer idle time. If nothing helps then you need a stronger heat-sink/fan for your cpu/case or a new case with better air flow. It can also be a faulty RAM module but in that case the whole system will be unstable. Finally here is the relevant part of the readme file (from prime95) mentioned in you output.

The other two errors messages, SUMINP != SUMOUT and ROUND OFF > 0.40
are caused by one of two things:
1) For reasons too complicated to go into here, the program's error
checking is not perfect. Some errors can be missed and some correct
results flagged as an error. If you get the message "Disregard last
error..." upon continuing from the last save file, then you may have
found the rare case where a good result was flagged as an error.
2) A true hardware error.

If you do not get the "Disregard last error..." message or this happens
more than once, then your machine is a good candidate for a torture test.
See the stress.txt file for more information.

Running the program on a computer with hardware problems may produce
incorrect results. [...] you could be wasting your CPU time.