Closed SoumyadebBasu closed 5 months ago
This is working as expected, core numbering starts with 0, as it is the case in the BIOS.
That is what I thought initially, but corecycler keeps restarting the process with error "the CPU usage was too low" Here is the log CoreCycler_2024-02-03_22-27-27_PRIME95_SSE.log
This is then a different issue, unfortunately not too uncommon especially with Windows 11 it seems.
You can try to use the 0.9.5.0alpha2: https://github.com/sp00n/corecycler/releases/tag/v0.9.5.0alpha2
It also includes a debug switch in the config.ini to disable this CPU utilization check and solely rely on the log file output, you can set this with disableCpuUtilizationCheck = 1
in the [Debug]
section if the alpha still throws the same error.
Thank you. Unfortunately the alpha also had the same issue. Probably something to do with my system. I have set disableCpuUtilizationCheck = 1
and restartTestProgramForEachCore = 1
. Thank you for the help and the script as well.
Everytime I try to run the script. The affinity is always being set on the wrong core. The script says it's setting on core 4 but it sets on 5. If the script say the affinity is on core 1 it sets to core 2. Only in case of Core 0 it sets the affinity correctly.