[QUOTE=brucix;516842]When I run the new Mac OS X version 29.8b3 windows come up with black text on black backgrounds. If I select the text the background changes to blue and the text becomes visible. Im running the latest macOS Mojave version 10.14.4[/QUOTE]

Re-linking with the latest xcode magically fixed this. Hopefully, it will work for pre-Mojave users too.

Another example of why I hate Apple. They change the OS and don't care one whit that they break existing apps. At least they broke existing apps for a [B]hugely[/B] important feature.

I've got a few more suggestions:

1. If the user stops all workers, any already-stopped workers will display a message saying it's starting on the user's request followed by a second message saying it's stopped. This seems a bit redundant in my opinion. I've attached a screenshot for reference.

2. The default exponent for ECM and P-1 should be changed to something other than 1061 because M1061 was factored several years ago. Or even better: allow Prime95 to get the default exponent from the server.

3. On a related note: perhaps Prime95 could check for updates and notify the user. This would be especially useful if there is ever a reason to abandon an old version. The version 17 shift bug comes to mind here.

Another random low-priority suggestion:

PauseWhileRunning / LowMemWhileRunning show an appropriate message when <program> is running, but if there are multiple programs listed, and the first one detected (shown in the console message) is no longer running but another one is, the message is not changed. So you see
[i]Pausing because <ProgramA> is running[/i]
but it no longer is. Presumably this check happens every 10s or so - perhaps iff the previously-noted program is no longer running it could put out an additional console line saying the [i]current[/i] reason it's paused (or low-mem).

[QUOTE=James Heinrich;517118]Another random low-priority suggestion:

PauseWhileRunning / LowMemWhileRunning show an appropriate message when <program> is running, but if there are multiple programs listed, and the first one detected (shown in the console message) is no longer running but another one is, the message is not changed. So you see
[I]Pausing because <ProgramA> is running[/I]
but it no longer is. Presumably this check happens every 10s or so - perhaps iff the previously-noted program is no longer running it could put out an additional console line saying the [I]current[/I] reason it's paused (or low-mem).[/QUOTE]
PauseWhileRunning is a nice feature. It does not handle though, a situation I see leading to thermal shutdown of one of my systems. Antivirus/security software is always running, so it can't be in PauseWhileRunning if prime95 is to get anything done. Its cpu usage is very variable; mostly it's trivial, but it will saturate a core during a full system scan. Similarly backups and miscellaneous activity like multiple web browsers (especially a video stream) can push the system to cpu utilization that's more than it can handle thermally along with a throttled prime95 instance. It would be good if prime95 had an option PauseAboveLoad, where the load limit is the % cpu utilization by processes other than prime95 combined. Without it, I must manually pause prime95, and sometimes it gets forgotten for hours or days, or the thermal shutdown still gets initiated, despite prime95's throttle setting down to 20% now. If prime95 yielded entirely above a certain system load, I could probably raise the throttle value and get more throughput and fewer shutdowns.

After updating to 29.8b3 I see prime95 crushing often.

I do not get to see the error message, prime95 just stops running at some point, is anyone else having this issue?

I used backup files from previous version to continue (LL) tests using the new version.

[QUOTE=patgie;517257]After updating to 29.8b3 I see prime95 crushing often.

I do not get to see the error message, prime95 just stops running at some point, is anyone else having this issue?

I used backup files from previous version to continue (LL) tests using the new version.[/QUOTE]

What CPU? Are you overclocked? If you read threads like this one, you'll see that AVX-512 is not properly implemented on many motherboards, in terms of voltage control or turbo clock stepping. If you're overclocking, AVX-512 is the toughest load on the CPU and thus the best test of stability for your overclock.

If none of these apply, still provide some info about your hardware setup for those in the know to guess at your potential problem.

Version 29.8 runs AVX512 if your cpu supports it, while 29.4 and earlier uses AVX2/FMA. AVX512 is faster but more demanding for your CPU, check the temperature while running 29.8.

You can try disable AVX512 with this line in local.txt:
CpuSupportsAVX512F=0

If this helps then you know it is AVX512 causing it and you can maybe improve your cooling or check the BIOS for AVX512 settings that might be off.

[QUOTE=patgie;517257]After updating to 29.8b3 I see prime95 crushing often.

I do not get to see the error message, prime95 just stops running at some point, is anyone else having this issue?

I used backup files from previous version to continue (LL) tests using the new version.[/QUOTE]

Possibly related to this issue: [url]https://mersenneforum.org/showthread.php?t=24445[/url]

[QUOTE=ixfd64;517283]Possibly related to this issue: [url]https://mersenneforum.org/showthread.php?t=24445[/url][/QUOTE]

That's about right it is causing cudalucas to shut down too on the same machines.

Any way around it different than going back to the previous version?

I will try:

CpuSupportsAVX512F=0

it crushes while running simultaneously on my cpu i9 (prime95) + cudalucas on gpu

I have few laptops i5-i7 some with gpus running cudalucas that it would crush on too, no exceptions really sometimes it would be fine for days sometimes it would crush few hours after restarting

[QUOTE=patgie;517319]cudalucas[/QUOTE]
??

Did you try ATH's solution above?
Of course, on long term, you should fix your thermal issues, or bios (upgrade?), but right now, disabling the big AVX is the only way.

Cudalucas has nothing to do with it. Your CPU just crashes or goes into thermal lock. As long as you do not provide any info about the hardware (cpu/mobo/bios?) we can't help more...

[QUOTE=LaurV;517320]??

Did you try ATH's solution above?
Of course, on long term, you should fix your thermal issues, or bios (upgrade?), but right now, disabling the big AVX is the only way.

Cudalucas has nothing to do with it. Your CPU just crashes or goes into thermal lock. As long as you do not provide any info about the hardware (cpu/mobo/bios?) we can't help more...[/QUOTE]

i9 7940x 14x2 core 3.1ghz/
x299 ud4 pro/
f3

I am trying ATH solution, ms/iter went down from 1.5 to 1.8 I will be able to say if it is working after checking on other cpus later