I've tried to keep everyone promptly informed of Mersenne news - good or bad. So, here we go...
My verification run of M#40 just completed....not prime. Now we wait for Guillermo Ballester Valor's run to complete in the next few days. Our runs matched at 13 million iterations.
Possibilities are:
1) The original run was flawed or there is a bug in the version of prime95 used.
It is hard to imagine a bug or hardware glitch that generates an all zero LL result.
If memory is zeroed at some point, the next LL iterations are -2, 2, 2, 2, ...
2) My overclocked machine generated an undetected error or the prime95 version
I'm using has a bug that is affecting my result.
3) I was debugging an out-of-memory bug report last night. It is theoretically
possible there is an OS bug that affects other processes in these severe
circumstances.
I have save files every million iterations. If this really is a new Mersenne prime,
then I'll rerun the last iterations again to make sure the latest prime95 does not have
a bug.
_________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
