prime95 can only ECM number which like k*b^n+c,
but I want to use it to factor any integer！
how can I do this?

On another PC, Windows 10 Prime95 x64 PC, with build 3, neither Manual Communication nor Unreserve Exponent are selectable in the menu. They're both greyed out.

[QUOTE=Prime95;509652]Yes, x87 FFTs only support exponents up to about 79.3 million.[/QUOTE]

Can't run beta 3 on a 9900K
Same error as the above poster: "an unsupported operation was attempted" when clicking on the stress test. Can't even open the stress test window.
Clean folder installation.

[QUOTE=bbb120;509662]prime95 can only ECM number which like k*b^n+c,
but I want to use it to factor any integer！
how can I do this?[/QUOTE]

Pminus1=5,4534567,1,45000,450000

[QUOTE=bbb120;509662]prime95 can only ECM number which like k*b^n+c,
but I want to use it to factor any integer！
how can I do this?[/QUOTE]

Use GMP-ECM

[QUOTE=Falkentyne;509670]Can't run beta 3 on a 9900K
Same error as the above poster: "an unsupported operation was attempted" when clicking on the stress test. Can't even open the stress test window.
Clean folder installation.[/QUOTE]

Sorry. Testing on Windows 10 is not easy for me. I usually test on Windows Vista 32-bit and if that works, I assume the 64-bit Windows version will also work.

Anyway, I found the problem (the torture test dialog box is different in Windows 32 and Windows 64). Please try build 4.

[QUOTE=Flammo;509669]On another PC, Windows 10 Prime95 x64 PC, with build 3, neither Manual Communication nor Unreserve Exponent are selectable in the menu. They're both greyed out.[/QUOTE]

That will happen is UsePrimenet=0 is set in prime.txt.

Unrelated posts have been moved here: [url]https://mersenneforum.org/showthread.php?t=24122[/url]

[QUOTE=Prime95;509692]That will happen is UsePrimenet=0 is set in prime.txt.[/QUOTE]
Thanks, I had accidentally loaded it from a backup copy I made just prior to copying the new build over. You're right it's working:smile: fine.

I am unable to perform any stress test on i9 7900X using AVX-512. I am using latest build4 in Windows10 Pro x64. After disabling this instruction set ("run a weaker torture test") everything is fine.
I am running this CPU at fixed 3.5 GHz, RAM is running in quad channel configuration at 2666 with stock voltage. CPU cooler is Corsair H115i PRO.
The same applies to another CPU i7 7820X on a different platform.

After launching "Small FFTs" test, program freezes with "worker starting" messages (see attached). CPU utilization is at 100%, however nothing else happens in "worker window". Stopping a torture test produces an output "Stopping all worker threads." in comm window but utilization remains at 100% and again nothing else happens. Selecting "Exit" only minimizes the application to tray icon, and again nothing else changes (utilization is still at 100%). Afterwards I have to manually kill it from task manager.

Launching any other stress test, makes application minimize to tray icon (after 2-3 seconds) and after a moment (another 2-3 seconds) it disappears. This scenario generates in Windows logs two entries "Information" and "Error" - attached are txt files containing details.

As I've mentioned I am reproducing such behavior on another PC with different CPU / motherboard / RAM configuration.

Any ideas what might be wrong? :confused2:

Update: running everything on stock settings doesn't change anything.

[QUOTE=Cruelty;509873]I am unable to perform any stress test on i9 7900X using AVX-512. I am using latest build4 in Windows10 Pro x64.[/QUOTE]

I don't have an AVX-512 machine running Windows here. I use linux for my AVX-512 testing.

If you run just one torture thread instead of 16 or 20 does the torture test begin OK? If one works, does two? etc.

Have you checked the BIOS for AVX-512 offset (voltage)? Mystical has reported many early motherboards had this set improperly or not at all.