Prime95 v30.4/30.5/30.6

[Prime95]

factor64.o is built from factor64.asm

[petrw1]

Originally Posted by Prime95

Is it continuing from a savefile? If so, try renaming it.

If that fixes it, send me the savefile and worktodo.txt

I've tried deleting all save files too with no difference.
I've tried lower bounds, more or less workers ... .every attempt crashes the PC.

I tend to believe it is a conflict between my specific Windows 10 state and something in the pminus1 code.
I wish I could be more specific.

[S485122]

Originally Posted by petrw1

I've tried deleting all save files too with no difference.
I've tried lower bounds, more or less workers ... .every attempt crashes the PC.

I tend to believe it is a conflict between my specific Windows 10 state and something in the pminus1 code.
I wish I could be more specific.

The fact that running an unprivileged program leads to "the PC immediately shutdown (no blue screen...just boom)" is interesting ;-) But it probably means there are no crash dump files :-(

But you should still check the dedicated folder : %UserProfile%\AppData\Local\CrashDumps (C:\Users\User\AppData\Local\CrashDumps for the user "User") for .dmp files. One way to do that is to open an elevated command prompt, "cd" to the root of your disk, and enter the "dir *.dmp /s /a" command, it will search the whole disk, including hidden and system folders and files. If there are files that seem relevant by their date, you can use the free program "WinDbg" that you can download from the MicrosoftStore, to show the content of dump files in a user "friendly" way. The files or the WinDbg output might interest George :-)

Since the initial crash lead to loss or corruption of several files (prime.txt, local.txt ...) you could look for disk errors in the event viewer, do a CHKDSK /F from an elevated command prompt but most probably the storage is OK.

One thing you could do, is to install the latest version of prime95 in a NEW folder, NOT using ANY your old prime95 files (prime.txt, local.txt, worktodo.txt, ...) Enter computer and user name, set the maximum memory, stop prime95 and inject the P-1 assignment in your worktodo.txt file after checking its syntax or better get a P-1 assignment from PrimeNet.

If that leads to the same results a thorough check of Windows might be useful (dism and scansfc...)

Jacob

[drkirkby]

Originally Posted by Prime95

factor64.o is built from factor64.asm

Thank you. The linux64/makefile only contains

FACTOROBJ = factor64.o

so does not have enough information to build factor64.o from factor64.asm, which is in prime95/factor64.asm. I thought that file was for Windows only, since it was in the prime95 directory.

I could work out how to do it, but it's not necessary for me, as it was ecm.c that I wanted to recompile. I did manage to build the program, and achieved what I wanted to, but I believe the makefile is lacking the required information.

[chalsall]

Originally Posted by drkirkby

Thank you. The linux64/makefile only contains ... so does not have enough information to build factor64.o from factor64.asm, which is in prime95/factor64.asm

That raises an interesting point... The "make" system allows implicit build paths. Perhaps this particular target should be more explicitly and clearly defined.

Given a million idiots, occasionally a very small number of them will guess (and radiate) something worth thinking about...

[drkirkby]

Originally Posted by chalsall

Given a million idiots, occasionally a very small number of them will guess (and radiate) something worth thinking about...

Was that comment really necessary?

I've been on a large number of forums in my years on the internet, including two maths related

1. I did a huge amount of work in porting the SageMath software to Solaris. I had few disagreements with anyone over the years.
2. Mathematica forums.
3. Keysight forum for professional test equipment.
4. Amateur radio forums.
5. Web design forums
6. Computer server forum.
7. Some on groups.io that I jointly own - i always share ownership, in case I die.
8. Many others.

I've never come across any with such a toxic atmosphere as here. I had some PMs with someone who was getting abuse for asking too many questions. In a PM he wrote:

"I have been around here for a long time, and the tone rarely gets as bad as it has been lately. It will get better, and more relaxed, like it always does."

I point out an issue with a makefile, and get comments about a million idiots.

[chalsall]

Originally Posted by drkirkby

I point out an issue with a makefile, and get comments about a million idiots.

To be perfectly honest... You talk too much. You ask way too many questions which have already been answered. You are lazy, and like to see your words "in print".

The very patient amongst us say things like "don't scare off people".

The more serious say things along the lines of don't waste our very valuable time.

Read the prior art.

Please!!!

[Prime95]

Originally Posted by drkirkby

Thank you. The linux64/makefile only contains

FACTOROBJ = factor64.o

so does not have enough information to build factor64.o from factor64.asm, which is in prime95/factor64.asm.

The make process is a bit of a mess as you've discovered.

None of the make files deal with assembly code. Originally, only Microsoft MASM could assemble the source and MASM only ran under Windows. An object file converter by Agner Fog was used to create the Linux .o files. Recently, I switched to UASM, an open source MASM knockoff. In theory, UASM runs under Linux, but I've never tried it.

[kriesel]

Running prime95 v30.6b4 on a laptop with Windows 10 Home version 21H1 build 19043.1110, stage 2 of a large exponent, 12GB allowed of 16GB system ram, power settings to never sleep or hibernate while plugged in, and observed drastic variation in time between updates of the same exponent's stage 2 progress of over 33:1.
It had earlier been running solidly at ~1200 seconds (20 minutes) between updates.

Any ideas on what caused it or how to stop the slowdowns from occurring?
I've tried dropping the allowed ram from 12GB to 11 but also see occasional high disk activity there.

While prime95 showed ~11GB being used, Task Manager showed ~4GB ram use for the prime95 process and sometimes ~350MB/sec of disk activity. Stop and restart of the app made no difference. Memory was ~97% in use, but no conspicuous memory hog in the process listing in Task Manager. Prime95 is the only app running.

A system restart seems to have cleared up the situation for now, with Task Manager showing prime95 using ~11GB ram now.

[petrw1]

Originally Posted by petrw1

I've tried deleting all save files too with no difference.
I've tried lower bounds, more or less workers ... .every attempt crashes the PC.

I tend to believe it is a conflict between my specific Windows 10 state and something in the pminus1 code.
I wish I could be more specific.

So now it also crashes doing PFactor.
A little more digging leads me to believe it may be the power supply.
I can run 3 (of 4) cores just fine but when I start the 4th.....bada BOOOM!!!

HOWEVER....it does NOT BOOM if I run the Benchmarks or Stress test using all 4 cores .... ummmm

[S485122]

I am doing double checking on Mersennes in the trailing edge.
All those work units use the same FFT path :
AVX-512 FFT length 3M, Pass1=192, Pass2=16K, clm=2, 12 threads

What I don't understand is that sometimes the iteration times are about 10% higher for some exponents. It isn't linked to the exponent size, the workload on the computer, memory usage or the external and thus the internal temperature.
56606299 0,933
56713403 1,036
56713903 0,930
58008077 0,932
58011197 0,941
58157783 1,021
58203581 0,924
58238839 0,932
58238963 0,924
The slower runs are preceded and followed by "normal" runs.