I have an 850W PSU en route and I will also check Aida64 for AVX512 stability

[QUOTE=GP2;507309]This exponent ([M]51794089[/M]) is currently assigned to someone else (probably an anonymous churner), but [M]47526449[/M] and [M]49834937[/M] are also mismatching results from your machines.[/QUOTE]

Hmm, your result for [M]47526449[/M] turned out to be good.

In about 15 hours [M]49834937[/M] will complete. I'll also triple-check [M]47148053[/M] and [M]47185343[/M] and [M]49353571[/M] and [M]50998279[/M] and then maybe poach [M]51794089[/M] if it doesn't make progress.

Other than [M]51794089[/M], your results also had error codes for [M]83210321[/M] and [M]83275091[/M], which appear to have double-checks well underway.

Thanks for all your help

Additional failed double checks (PRP):

[url]https://www.mersenne.org/report_exponent/?exp_lo=79075979&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79062083&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79078529&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79087627&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79109357&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79143199&full=1[/url]

Prime95 V29.5b9 benchmark stall
 

Tomorrow is Groundhog Day. Does this mean 6 more weeks of benchmark stall issues?

The system had been updated for Window Ten patches and restarted minutes before this benchmark attempt was started. It had run a couple of days trouble-free in v29.5b8 since the last self-scheduled benchmark resulted in a stall, before that restart.

Uhoh, it was very quickly reproducible.

Do you use the newest BIOS version for your system?

I can see the i7-8750H processor is from Q2 2018, long after the Skylake flaw that was found in January 2016 with M49, but just in case it is some similar issue?

[QUOTE=ATH;507404]Do you use the newest BIOS version for your system?

I can see the i7-8750H processor is from Q2 2018, long after the Skylake flaw that was found in January 2016 with M49, but just in case it is some similar issue?[/QUOTE]
On Jan 9 2019, BIOS update applied: [url]https://www.mersenneforum.org/showpost.php?p=505412&postcount=142[/url]
There's another set of BIOS updates out very recently, which I can try.
Windows Ten just updated today after the benchmark stall.

[QUOTE=simon389;507369]Thanks for all your help

Additional failed double checks (PRP):

[url]https://www.mersenne.org/report_exponent/?exp_lo=79075979&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79062083&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79078529&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79087627&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79109357&full=1[/url]
[url]https://www.mersenne.org/report_exponent/?exp_lo=79143199&full=1[/url][/QUOTE]

Interesting, and have you used the error checking at PRP tests? At the non-triple checked exponents we can see that "Unverified (Reliable)", thought that you get this only when you have used the error checking.

ps. Ofcourse at least at the first exponent the third run, that used type=4 was useless, that can't verify a type=1 result. Not to mention that you can't use type=2,4 for a fast PRPC test.

Another stall, after the Win Ten update, from the self scheduled benchmarking in prime95 29.5b9. System BIOS of the i7-8750H laptop at this point was 1.4.0. It's been updated to 1.5.1 since. Don't know if it matters, but I usually access this system (and others not showing a problem) via TightVNC 2.8.8. And another benchmark stall, after the 8 Dell updates including BIOS 1.5.1 and a restart.

[QUOTE=R. Gerbicz;507449]

ps. Not to mention that you can't use type=2,4 for a fast PRPC test.[/QUOTE]

Does this mean that gpuowl shouldn't do any first-time PRP tests;
or only avoid using it to check previous PRP tests done with PRIME95 ?

[QUOTE=R. Gerbicz;507449]Interesting, and have you used the error checking at PRP tests? At the non-triple checked exponents we can see that "Unverified (Reliable)", thought that you get this only when you have used the error checking.[/QUOTE]

As of today the exponent [M]79075979[/M] is confirmed bad, so we have a type-1 PRP test with a bad residue!

Simon, do you have the log file?

[QUOTE=GP2;507466]As of today the exponent [M]79075979[/M] is confirmed bad, so we have a type-1 PRP test with a bad residue!

Simon, do you have the log file?[/QUOTE]
Since the bad one's shift is nonzero, that's presumably prime95/mprime, not gpuowl. And it's the first of four primality tests recorded on that exponent. The two matching are not both shift zero runs, so ok there.