- disableCpuUtilizationCheck is now defaulting to 1

- The script is now trying to detect if there's a mixed core setup, where some cores have 2 threads and others only 1 (i.e. Intel)

config.default.ini

@@ -24,7 +24,9 @@ stressTestProgram = PRIME95
 # Automatic runtime:
 # You can also set it to "auto", in which case it will perform one full run of all the FFT sizes in the selected
 # Prime95 preset for each core, and when that is finished, it continues to the next core and starts again
-# For Aida64 and y-Cruncher, the "auto" setting will default to 10 Minutes per core
+# For y-Cruncher the "auto" setting will wait until all selected tests have been finished for a core
+# and will then continue to the next core
+# For Aida64 the "auto" setting will default to 10 Minutes per core
 #
 # Below are some examples of the runtime for one iteration for the various tests on my 5900X with one thread
 # The first iteration is also usually the fastest one
@@ -37,7 +39,7 @@ stressTestProgram = PRIME95
 # - Prime95 "Moderate":  1344K to 4096K - [SSE] ~7-15 Minutes  <|> [AVX] ~17-30 Minutes  <|> [AVX2] ~17-33 Minutes
 # - Prime95 "Heavy":        4K to 1344K - [SSE] ~15-28 Minutes <|> [AVX] ~43-68 Minutes  <|> [AVX2] ~47-73 Minutes
 # - Prime95 "HeavyShort":   4K to  160K - [SSE] ~6-8 Minutes   <|> [AVX] ~22-24 Minutes  <|> [AVX2] ~23-25 Minutes
-# - y-Cruncher: Depends on the number of selected tests and the duration per test
+# - y-Cruncher: ~10 Minutes
 # Default: 6m
 runtimePerCore = 6m
 
@@ -357,24 +359,18 @@ TortureTime = 1
 
 # Debug setting to disable the periodic CPU utilization check
 #
-# Important:
-# Normally you should not need to set this, as it is the only way to determine for certain test programs (like y-Cruncher)
-# if the stress test is still running or if there has been an error.
-# However on some systems this seems to report incorrect values, which causes the script to throw an error despite
-# the stress test program still running fine, so here is a way to disable this behavior.
-#
-# Be aware that you will have no idea which core has thrown an error if "disableCpuUtilizationCheck" is set to 1
-# and "restartTestProgramForEachCore" is set to 0.
-# y-Cruncher is always initialized with logical core 2 (and 3 for two threads), and since CoreCycler has no way of knowing
-# that there has been an error with "disableCpuUtilizationCheck = 1", it will just keep on running, while y-Cruncher will
-# always display logical core 2 (and 3) as the one having thrown the error.
+# This setting enables or disables the CPU utilization check during stress testing.
+# Some stress test programs (like Aida64) do not generate a log file, so the only way to detect an error is by
+# checking the current CPU utilization.
+# There have been quite a few reports though that this doesn't work correctly on some systems, especially if
+# Windows 11 is being used, so this check is now disabled by default.
 #
 # Note: The check for the CPU utilization uses the Windows Performance Counters, which can be corrupted for unknown
 #       reasons. Please see the readme.txt and the /tools/enable_performance_counter.bat file for a possible way
 #       to fix these issues. There's no guarantee that it works though.
 #
-# Default: 0
-disableCpuUtilizationCheck = 0
+# Default: 1
+disableCpuUtilizationCheck = 1
 
 
 # Debug setting to enable querying for the CPU frequency