mersenneforum.org Prime95 v30.3
 Register FAQ Search Today's Posts Mark Forums Read

2020-11-03, 02:06   #474
Viliam Furik

"Viliam Furík"
Jul 2018
Martin, Slovakia

2·3·7·11 Posts

Quote:
 Originally Posted by storm5510 Windows 10 did not give me any problems. I just checked. It is set to 1. I have never tried any fractional values, like 1.5. In this case, I would have gone into local.txt and set the value to 1536. For some reason, I always use powers of 2 for things of this type, although I do not know why. Regardless, I am pleased a few here paid some attention to this.
If you try to set the value to half of the total installed RAM, I think you will get the error again.

 2020-11-03, 13:20 #475 Runtime Error   Sep 2017 USA 5·47 Posts I'm curious what happened with 100574899. It seems that Mihai Preda did PRP, and then curtisc & George Woltman both did CERTs, but then I still got it as a first-time check. Was there something suspicious with Preda's run? Thanks.
2020-11-03, 20:01   #476
Prime95
P90 years forever!

Aug 2002
Yeehaw, FL

165048 Posts

Quote:
 Originally Posted by Runtime Error I'm curious what happened with 100574899. It seems that Mihai Preda did PRP, and then curtisc & George Woltman both did CERTs, but then I still got it as a first-time check. Was there something suspicious with Preda's run? Thanks.
Gpuowl 7.1 had a bug in proof generation. The two Certs failed, the result was marked suspicious and the exponent was reassigned as a first time check.

2020-11-04, 02:59   #477
Runtime Error

Sep 2017
USA

EB16 Posts

Quote:
 Originally Posted by Prime95 Gpuowl 7.1 had a bug in proof generation. The two Certs failed, the result was marked suspicious and the exponent was reassigned as a first time check.
Interesting, & thanks for the reply - I appreciate it!

2020-11-27, 15:01   #478
James Heinrich

"James Heinrich"
May 2004
ex-Northern Ontario

2×412 Posts

Just a minor oddity I noticed:
Quote:
 Mersenne number primality test program version 30.3 Optimizing for CPU architecture: Core i3/i5/i7, L2 cache size: 6x1 MB, L3 cache size: 6x19712 KB
The 6x1MB L2 is correct, but there's only a single 19.25MB L3 cache. It is a VM though so perhaps that's confusing it (I don't have any other system running mprime to compare output).

 2020-11-27, 20:24 #479 kriesel     "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 140D16 Posts V30.3b6 crash instead of completing exponent Code: [Nov 27 14:15] Worker starting [Nov 27 14:15] Setting affinity to run worker on CPU core #1 [Nov 27 14:15] Setting affinity to run helper thread 1 on CPU core #2 [Nov 27 14:15] Resuming Gerbicz error-checking PRP test of M182000029 using FMA3 FFT length 10M, Pass1=1280, Pass2=8K, clm=2, 2 threads [Nov 27 14:15] PRP proof using power=7x2 and 64-bit hash size. [Nov 27 14:15] Proof requires 2.9GB of temporary disk space and uploading a 364MB proof file. [Nov 27 14:15] Iteration: 181998738 / 182000128 [99.99%]. [Nov 27 14:16] Iteration: 182000000 / 182000128 [99.99%], ms/iter: 29.771, ETA: 00:00:03 It will crash during producing the proof. I can't capture the worker window at the crash because the app disappears from the screen. This was repeatable, as results.txt excerpt shows. Code: [Sun Nov 22 03:24:00 2020] Error reading PRP proof interim residues file. Errno: 13, Permission denied DOSerrno: 23 [Fri Nov 27 14:06:22 2020] Error reading PRP proof interim residues file. Errno: 13, Permission denied DOSerrno: 23 [Fri Nov 27 14:14:56 2020] Error reading PRP proof interim residues file. Errno: 13, Permission denied DOSerrno: 23 So wouldn't you know it, I go to document it, and the fourth time it succeeds and reports a result. Yay. I didn't change anything, except to stop prime95 and continue, to avoid running the last 0:03:35 over and over. The drive had over 300GB of free space at the time. System sat idle for over 5 days as a result of the first crash in the series. Last fiddled with by kriesel on 2020-11-27 at 20:25
 2020-11-27, 22:03 #480 PhilF     Feb 2005 Colorado 617 Posts DOSerrno 23 is "Too many file open in system". I guess when you restarted Prime95 it closed some files. It's hard to speculate at this point whether your system ran out of file handles overall, or if Prime95 is possibly leaking open files over time.
2020-11-27, 22:18   #481
kriesel

"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

3×29×59 Posts

Quote:
 Originally Posted by PhilF DOSerrno 23 is "Too many file open in system". I guess when you restarted Prime95 it closed some files. It's hard to speculate at this point whether your system ran out of file handles overall, or if Prime95 is possibly leaking open files over time.
I restarted it multiple times after multiple crashes, and only the fourth try worked.
System has not yet been up for 16 days.
This says 23 is "FCB unavailable".
Others say CRC error.
04 is too many files open.

Last fiddled with by kriesel on 2020-11-27 at 22:21

 2020-11-27, 22:23 #482 PhilF     Feb 2005 Colorado 617 Posts In Visual Studio, which I think George builds with, it shows as Too many open files in system. Not to be confused with doserrno 24, which is "Too many open files", lol. Last fiddled with by PhilF on 2020-11-27 at 22:31
2020-11-28, 01:17   #483
kriesel

"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

3·29·59 Posts

Quote:
 Originally Posted by PhilF In Visual Studio, which I think George builds with, it shows as Too many open files in system. Not to be confused with doserrno 24, which is "Too many open files", lol.
Thanks.
Event viewer is showing a lot of these errors in system log.
The device, \Device\Harddisk0\DR0, has a bad block.
Kinda poor since it's only ~3-4 years old and has led a sheltered life.

Application log had this from a p95 crash
Faulting application name: prime95.exe, version: 30.3.1.0, time stamp: 0x5f5ae7c7
Faulting module name: prime95.exe, version: 30.3.1.0, time stamp: 0x5f5ae7c7
Exception code: 0xc0000409
Fault offset: 0x000000000245e79c
Faulting process id: 0x5d6c
Faulting application start time: 0x01d6c4f8cce1c42d
Faulting application path: C:\Users\ken\Documents\p95\prime95.exe
Faulting module path: C:\Users\ken\Documents\p95\prime95.exe
Faulting package full name:
Faulting package-relative application ID:

2020-11-28, 01:33   #484
PhilF

Feb 2005

617 Posts

Quote:
 Originally Posted by kriesel Thanks. Event viewer is showing a lot of these errors in system log. The device, \Device\Harddisk0\DR0, has a bad block.
Does the timestamp on the bad block event match one of the Prime95 crash times?

EDIT: Never mind, I just noticed you said your log is showing a lot of bad block entries. The good news is that I think you found your problem. The bad news is that I think you found your problem.

Last fiddled with by PhilF on 2020-11-28 at 01:37