Version 0.11.0.0 offers support for Ryzen 9000 for the Automatic Test Mode, and has replaced the outdated WinRing0 system driver with a version from PawnIO.
To be able to use it, you will need to install PawnIO from
https://pawnio.eu/.
At the same time, PBO2Tuner and pbocli have been removed, as they also still contain WinRing0. They have been replaced with
SMUDebugTool as an alternative if you look for a GUI interface to set the Curve Optimizer values.
Unfortunately the Intel component (
IntelVoltageControl) still uses WinRing0, so you may need to add an exclusion for it if you want to run it on an Intel CPU.
y-cruncher has also been updated to version 0.8.7 Build 9547, which brought back the `00-x86` test binary mode!
### Changelog:
**Automatic Test Mode:**
- The Automatic Test Mode should now support Ryzen 9000 (and 8000)!
- Added a new `setVoltageOnlyForTestedCore` config option, which when active will only set the currently tested core to a negative Curve Optimizer value. All the other cores will be set to 0, which avoids any possible crashes due to other cores being too low
- Added the creation of a System Restore Point when the Automatic Test Mode is being started. This helps recovering from a corrupted Windows installation (ask me how I know)
This can be turned off in the config if you don't care about that
- Added a new `Minimum` option for the voltage starting values. These will set the Curve Optimizer values to -30 for Ryzen 5000 and -50 for Ryzen 7000 and above (and will throw an error for Intel)
- The default value for the starting values is now `CurrentValues` - and it does it says, it uses the currently set values as the starting point, which is actually the same behavior as the previous `Default` value, just more clear
- You can now provide the Curve Optimizer starting values separated with a `|` as well, which makes it easier to use the values provided at the end of a test
- There is now a 120 second waiting time after a crash before the testing is resumed, to avoid Windows registering this as a "failed" boot if the computer crashes immediately after starting the test again.
Otherwise you might run into a situation where the Recovery Screen is being brought up during the reboot, and no testing can proceed.
The waiting can be changed in the config file, and it can also be skipped by pressing a key
- The scheduled task for the auto-resume of the testing should now be more protected against simply vanishing during a crash (although it sometimes still seems to happen)
- The .automode file should not corrupt as often anymore during a crash
**Misc changes:**
- Migrated from WinRing0 to PawnIO to account for Windows Defender now recognizing it as a possible threat
- Updated y-cruncher to version 0.8.7 Build 9547
- Switched to using
ryzen-smu-cli for setting the Curve Optimizer values
- Added a new `Ryzen.AutomaticTestMode.Start.ini` config preset, which makes use of `setVoltageOnlyForTestedCore = 1` and the `Minimum` starting values
- Added checks for Visual C++ libraries and for .NET 8
- The .automode file is now in JSON format
- Updated the included
BoostTester tool to support a `--core-repeat <n>` argument, which allows for longer durations per core
- You can now use `auto` for the mode in y-cruncher, which will use the automatically selected binary that y-cruncher selects
- Added a new `CorePairs` option for the core testing order. This will form "pairs" for cores, so e.g. 0-1, 0-2, 0-n, up to n-0, n-1, n-(n-1)
- Added a `Run Multiconfig CoreCycler.bat` batch file that allows you to chain multiple config files, it will look for `multiconfig-x.ini` files (see the file comments for caveats)
- You can now define a single FFT size to Prime95 (so e.g. `720` instead of `720-720`)
**Multiple bug fixes:**
- Fixed a problem with the update check and the 2025-12-09 Windows Security Update (KB5072033 resp. KB5074596)
- The Ryzen 9950X3D seemed to have a different AVX512 order, tried to fix this
- Fixed a bug with directories that contain square brackets
- Fixed a bug where the core that crashed could be added multiple times to the testing sequence, making the last in the sequence to be skipped
- Fixed a bug where `stopOnError` caused problems in combination with the automatic test mode
- Added a check if one of the CCDs for Ryzen is disabled to prevent a bug
- Fixed a bug where a new log file would be started if the core that crashed the computer was core 0
- Fixed a bug with resuming the threads, which sometimes caused the script to abort
- Fixed an issue where setting the CO values would take longer than expected if y-cruncher was used
- Sometimes Aida64 didn't exit correctly when terminating the script. This should now work better
- Fixed a bug when registering the scheduled task
- Made the error checks for Visual C++ and .NET more precise
- Added functionality that checks if the System Restore is enabled, and if not, asks to enable it
- Added additional error check when creating the Event Log source
- Added multiple tries to get and set the Curve Optimizer values, because ZenStates-Core can seem to fail from time to time
- Waiting for one second before restarting the stress test program now, which hopefully should avoid errors if the allocated memory could not be freed fast enough
- Added some explanation for the CPULOAD error message
- Tried to avoid some errors when trying to get the stress test process
