v0.10.0.0alpha4

[sp00n]

• Added an automated test mode with automatic Curve Optimizer / voltage offset adjustment on error
• Added the possibility to automatically resume the script after a reboot via a Scheduled Task
• A WHEA warning/error can now be treated as a "real" error if the APIC ID matches the tested core
• See the default.config.ini for the new settings
• Fixed a bug with the detection of the starting values (see FATAL ERROR on Line Number: 4645 (Release v0.10.0.0alpha1) #79)
• Added config presets for Automatic Test Mode
• Fixed a bug where Linpack wouldn't start from a directory including a space (fixes An bug related to path where there is a blank space in the path name. #84)
• Fixed a bug where resuming after a crash with a "default" coresToTest order would result in an index out of bounds error (fixes Fatal error: index out of range #85)
• Also it didn't resume on the crashed core
• The config file's content is now put into the log file for easier debugging
• Fixed a bug where the log file for y-cruncher was actually using the naming scheme for Linpack (under unclear circumstances, but it happened at least once)
• Fixed a bug when the update check doesn't return any output at all (fixes Update check fails #83)
• Fixed a bug with Linpack's path AGAIN
• The Automatic Test Mode unfortunately doesn't work with Ryzen 9000

---

This discussion was created from the release v0.10.0.0alpha4.

[Camadams1179]

CoreCycler_2024-10-17_20-40-55_PRIME95_SSE.log

Got this from my 5900X

[sp00n]

Hmm, the APICID.exe I'm using the get the amount of cores only seems to report back 8 cores instead of 12 on your machine.

Can you check manually what happens if you execute tools\APICID.exe inside the command line?
For my 5900X it outputs the following:

Logical CPU 0 - Physical Core 0 - APIC ID 0 - SMT On
Logical CPU 1 - Physical Core 0 - APIC ID 1 - SMT On
Logical CPU 2 - Physical Core 1 - APIC ID 2 - SMT On
Logical CPU 3 - Physical Core 1 - APIC ID 3 - SMT On
Logical CPU 4 - Physical Core 2 - APIC ID 4 - SMT On
Logical CPU 5 - Physical Core 2 - APIC ID 5 - SMT On
Logical CPU 6 - Physical Core 3 - APIC ID 6 - SMT On
Logical CPU 7 - Physical Core 3 - APIC ID 7 - SMT On
Logical CPU 8 - Physical Core 4 - APIC ID 8 - SMT On
Logical CPU 9 - Physical Core 4 - APIC ID 9 - SMT On
Logical CPU 10 - Physical Core 5 - APIC ID 10 - SMT On
Logical CPU 11 - Physical Core 5 - APIC ID 11 - SMT On
Logical CPU 12 - Physical Core 6 - APIC ID 16 - SMT On
Logical CPU 13 - Physical Core 6 - APIC ID 17 - SMT On
Logical CPU 14 - Physical Core 7 - APIC ID 18 - SMT On
Logical CPU 15 - Physical Core 7 - APIC ID 19 - SMT On
Logical CPU 16 - Physical Core 8 - APIC ID 20 - SMT On
Logical CPU 17 - Physical Core 8 - APIC ID 21 - SMT On
Logical CPU 18 - Physical Core 9 - APIC ID 22 - SMT On
Logical CPU 19 - Physical Core 9 - APIC ID 23 - SMT On
Logical CPU 20 - Physical Core 10 - APIC ID 24 - SMT On
Logical CPU 21 - Physical Core 10 - APIC ID 25 - SMT On
Logical CPU 22 - Physical Core 11 - APIC ID 26 - SMT On
Logical CPU 23 - Physical Core 11 - APIC ID 27 - SMT On

But for you it seems to have stopped after Logical CPU 15.

[Camadams1179]

I swapped from a 5800x, anything i could do to fix this? I reset bios and still no change...
APICID:
Logical CPU 0 - Physical Core 0 - APIC ID 0 - SMT On Logical CPU 1 - Physical Core 0 - APIC ID 1 - SMT On Logical CPU 2 - Physical Core 1 - APIC ID 2 - SMT On Logical CPU 3 - Physical Core 1 - APIC ID 3 - SMT On Logical CPU 4 - Physical Core 2 - APIC ID 4 - SMT On Logical CPU 5 - Physical Core 2 - APIC ID 5 - SMT On Logical CPU 6 - Physical Core 3 - APIC ID 6 - SMT On Logical CPU 7 - Physical Core 3 - APIC ID 7 - SMT On Logical CPU 8 - Physical Core 4 - APIC ID 8 - SMT On Logical CPU 9 - Physical Core 4 - APIC ID 9 - SMT On Logical CPU 10 - Physical Core 5 - APIC ID 10 - SMT On Logical CPU 11 - Physical Core 5 - APIC ID 11 - SMT On Logical CPU 12 - Physical Core 6 - APIC ID 16 - SMT On Logical CPU 13 - Physical Core 6 - APIC ID 17 - SMT On Logical CPU 14 - Physical Core 7 - APIC ID 18 - SMT On Logical CPU 15 - Physical Core 7 - APIC ID 19 - SMT On

[sp00n]

The 5800X is an 8 core processor, but it should've updated the cores. 🤔
There are a couple more things you could check that would help me debug.

1. Open a PowerShell terminal, run the following and post the output:
   (Get-CimInstance -ClassName Win32_Processor) | Select-Object -Property Name, ThreadCount, NumberOfCores, NumberOfLogicalProcessors
   and
   $Env:PROCESSOR_IDENTIFIER, $Env:NUMBER_OF_PROCESSORS

2. Attach a screenshot of the TaskManager, when it's switched to the "Performance" tab and after right-clicking on the graph and selecting "Change graph to" -> "Logical processors".

3. Download, extract and run the attached GetLogicalProcessorInformationEx file and post the output.

GetLogicalProcessorInformationEx.zip

[sp00n]

Did you get around testing something?

[ToWi89]

When running automated test mode, after a crash it restarts the test without changing the voltage offsets when using YCRUNCHER as stress test. So it just keep on crashing. Didn't have this issue when using prime95 as test option

[ToWi89]

Yeah, after the restart, it start up a new run. In that run it starts with the last saved start values, not adjusted due to the crash.

Attached are 2 logs, the first is the initial startup, crashed just after midnight, approx 15 mins in the 30 min run on core 0 with an offset of -14. The second one is after auto restarting this morning (I don't have auto login after reboot set up), starting again with a -14 offset on that core.
CoreCycler_2024-10-26_23-51-10_YCRUNCHER_19-ZN2 ~ KAGARI.log
CoreCycler_2024-10-27_09-46-47_YCRUNCHER_19-ZN2 ~ KAGARI.log

Edits made to the voltage settings due to reported errors are updated just fine.

[ToWi89]

Forget that last message. In the new run it started again on core 0 with -14, got a WHEA error, updated the voltage to -13. With -13 the system rebooted. The log shows the -13 being stored in the automode part, however corecycler applies -14 at the restart.
CoreCycler_2024-10-27_09-46-47_YCRUNCHER_19-ZN2 ~ KAGARI.log
CoreCycler_2024-10-27_10-18-51_YCRUNCHER_19-ZN2 ~ KAGARI.log

[sp00n]

Meh, classical noob mistake, I was checking if there was a core index value passed to script, but of course core 0 registered as "not set", and so the whole functionality never executed if the crash happened on core 0.

Fixing this now.

[sp00n]

Ok, you can try the alpha5 from here:
https://github.com/sp00n/corecycler/releases/tag/v0.10.0.0alpha5

Please let me know if this fixed your problem. I was already considering alpha4 to be the release candidate for the final 0.10 version, and if this bug is fixed, the alpha5 might be it then.

[ToWi89]

Hi, sorry for taking so long to get back. I've been running the latest update for a couple of days now, and it's quite stable! Occasionally the autostart file gets corrupted and just sais nul nul nul, but that's likely due to the system getting unstable without throwing any errors. Weirdly enough it will pass any stress test for days (16 cores takes a while), but the whole system just becomes very unresponsive after a while at large negative offsets on the non-performance cores. Anyhow, that's a me issue, not a corecycler issue.