You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR: [Time]
ERROR: There has been an error while running Prime95!
ERROR: At Core 0 (CPU 0)
ERROR MESSAGE: FATAL ERROR: Rounding was 0.5, expected less than 0.4
+ There was an FFT size provided in the error message, use it.
ERROR: The error happened at FFT size 1600K
+ There has been some error in Test-StressTestProgrammIsRunning, checking (#2)
+ Trying to close the stress test program to re-start it
+ Trying to close the stress test program
+ Trying to close Prime95
+ Resuming threads for process: 18828 - prime95
+++ ID: - 7500 ok - 11708 ok - 18092 ok
+ Trying to gracefully close Prime95
+++ The window process main window handle: 591692
+++ Try 1
And this also occurred for another core-
ERROR: [Time]
ERROR: There has been an error while running Prime95!
ERROR: At Core 9 (CPU 18)
ERROR MESSAGE: FATAL ERROR: Rounding was 0.5, expected less than 0.4
+ There was an FFT size provided in the error message, use it.
ERROR: The error happened at FFT size 16000K
+ There has been some error in Test-StressTestProgrammIsRunning, checking (#2)
+ Trying to close the stress test program to re-start it
+ Trying to close the stress test program
+ Trying to close Prime95
+ Resuming threads for process: 19728 - prime95
+++ ID: - 19740 ok - 17792 ok - 19928 ok
+ Trying to gracefully close Prime95
+++ The window process main window handle: 1312348
+++ Try 1
I only had it restart Prime95 correctly once all the other times the script just stops working.
The text was updated successfully, but these errors were encountered:
I've turned on the debugging option to bring Prime95 to the foreground, and it seems to just freeze when there's an error, not sure why
Fresh install of Windows 11 24h2
I thought this only occurred with preferred cores, but it seems any core that errors causes Prime95 to just crash? The program can't be interacted with at all. I'm using Huge+SSE and turned runtimePerCore = auto and restartTestProgramForEachCore = 1
Hm, that's not a very common behavior. Maybe another angle would be to play around with the priority of the stress test program in the config.ini.
In earlier versions of CoreCycler this was set to High, but in more recent ones I've changed it back to Normal (which should actually prevent freezing issues). The default priority of Prime95 if you start it on its own is Below Normal as far as I can remember.
Here's the log for when this happens -
And this also occurred for another core-
I only had it restart Prime95 correctly once all the other times the script just stops working.
The text was updated successfully, but these errors were encountered: