mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Hardware

Reply
 
Thread Tools
Old 2020-10-20, 16:25   #1
Chelle
 
Jul 2020
S. Wales Uk

210 Posts
Default Hardware errors help

Hi
Anybody have any ideas?
Getting following hardware errors prime95.
As shown in the window:

LL value corrupt could not run jacobi error check
Errno 34 result too large
DOSerror :2
1 ILLEGAL SUMOUT/bad FFT data

Is likely the cause bad ram it’s ecc though?
Have swapped some ram but don't have enough to change all.

I’ve restarted it for the 3rd time from the beginning happened at 80% 40% and 70% complete aprox. Just gets stuck and repeats the last 1% or 2%.
Chelle is offline   Reply With Quote
Old 2020-10-20, 17:04   #2
moebius
 
moebius's Avatar
 
Jul 2009
Germany

461 Posts
Default

Which prime95 version do you use?
Could it be due to the RAM-settings in the BIOS (timings, wrong profile,OC,.....)?
Why don't you use PRP + proofs [prime95 v30.3 build 6] (which leads to correct results at many hardware errors, and you should also use this because it is preffered nowadays)?

Last fiddled with by moebius on 2020-10-20 at 17:10
moebius is offline   Reply With Quote
Old 2020-10-20, 17:26   #3
paulunderwood
 
paulunderwood's Avatar
 
Sep 2002
Database er0rr

1101101100012 Posts
Default

Try running memtest86+. You might have one or more bad sticks of RAM.

Also install a temperature monitoring software.
paulunderwood is offline   Reply With Quote
Old 2020-10-20, 17:30   #4
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

112448 Posts
Default

Welcome to the GIMPS Mersenne forum.

Current version of prime95 is v30.3b6. https://www.mersenne.org/download/
Switch from LL to PRP with Gerbicz Error Check and proof, with power 8 or so enabled by setting Options, resource limits, Temporary disk space limit to 6GB or more of on-disk storage allowed per worker, if you have the space. With the same effort as your past 3 failed attempts at one LL, you could have 2 PRP's completed or close to it, with proof generated, despite recurrent errors, and someone would run brief Cert assignments eliminating the work of conventional double checking or triple checking. So PRP is effectively, from a project-wide view, twice as fast as LL when both are working reliably, and PRP is even better relatively, when not entirely reliable.
In an extreme case, such as on my old unreliable Athlon system that since went to recycling, PRP/GEC may make no progress because of high error rate, while LL with Jacobi may miss errors and make iteration progress incorrectly producing eventual wrong results.

If determined to persist with LL anyway, make use of prime95's backup files.

Much more background/reference info available at https://www.mersenneforum.org/showthread.php?t=24607

Last fiddled with by kriesel on 2020-10-20 at 17:38
kriesel is online now   Reply With Quote
Old 2020-10-20, 19:41   #5
Chelle
 
Jul 2020
S. Wales Uk

2 Posts
Default

Have just now updated to the latest version, Was trying to see if I could continue the work without starting again. Tried using bu4 file (deleting others) but soon got ‘error writing intermediate file’ ‘result too large’

Yes I could start from beginning and change to PRP, maybe the only way, pity as nearly 70% done.
The main cause is the hardware but it takes like a month to show up each time.
Chelle is offline   Reply With Quote
Old 2020-10-20, 21:27   #6
Runtime Error
 
Sep 2017
USA

3·61 Posts
Default

Quote:
Originally Posted by Chelle View Post
Yes I could start from beginning and change to PRP, maybe the only way, pity as nearly 70% done.
Definitely a shame, but PRP will give the right answer even with an occasional error. Also, the new PRP in 30.3 generates a proof file that eliminates the need for a double check! So although restarting will cost 100% of the test, continuing will either cost 130% total (including double check) or 230% total (including triple check) if your residual was wrong.

Last fiddled with by Runtime Error on 2020-10-20 at 21:28
Runtime Error is offline   Reply With Quote
Old 2020-10-20, 21:49   #7
Uncwilly
6809 > 6502
 
Uncwilly's Avatar
 
"""""""""""""""""""
Aug 2003
101×103 Posts

100010111110102 Posts
Default

What is the size of your exponent? Just give us the millions range.

And what is the CPU type that you are using? How much RAM do you have? And are you trying to write your files to a USB drive?
Uncwilly is online now   Reply With Quote
Old 2020-10-21, 02:24   #8
phillipsjk
 
Nov 2019

1018 Posts
Default

Quote:
Originally Posted by Uncwilly View Post
... And are you trying to write your files to a USB drive?

tangent: my "white elephant" machine is using an 8GB USB drive, but I use BTRFS, which includes a check-sum. It is VERY slow, so am planing to buy a 64GB drive this week to replace it. More space puts off re-writes for a longer period of time (plus it can accommodate the new muti-gigabyte PRP proof files).


Plus I hope the new drive fits vertically in the 1U case (so I can use the drive bays for my backups when not factoring).
phillipsjk is offline   Reply With Quote
Old 2020-10-21, 13:18   #9
Xyzzy
 
Xyzzy's Avatar
 
"Mike"
Aug 2002

1EBF16 Posts
Default

Are you using "dup" or "single" for your data?
Xyzzy is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Hardware errors have occurred during the test! rgirard1 Software 16 2020-09-10 22:16
Possible hardware errors... SverreMunthe Hardware 16 2013-08-19 14:39
Hardware, FFT limits and round off errors ewergela Hardware 9 2005-09-01 14:51
more about hardware errors graeme Hardware 4 2003-07-08 09:14
Reproducable hardware errors? cmokruhl Software 2 2002-09-17 19:04

All times are UTC. The time now is 01:53.

Sun Dec 6 01:53:23 UTC 2020 up 2 days, 22:04, 0 users, load averages: 3.06, 2.97, 2.79

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, 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.