API tools faq
paste
Guest User

Untitled

a guest
Feb 14th, 2026
93
0
Never
8
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 96.42 KB | None | 0 0
raw download clone embed print report
  1. + Started the script at 2026-02-14 16:40:54
  2. + Version: 0.11.0.0
  3. +++ PSScriptRoot: C:\CoreCycler-v0.11.0.0
  4. +++ The initial log level: 2
  5. +++ Starting the main functionality block
  6. +++ The original console mode: 503
  7. +++ Disabled the QuickEdit Mode feature
  8. +++ Disabled the close button
  9. +++ Trying to get the initial update check settings
  10. +++ Custom config file: C:\CoreCycler-v0.11.0.0\configs\Ryzen.AutomaticTestMode.Start.ini
  11. +++ Initial Update Check Enabled: True
  12. +++ Initial Update Check Frequency: 24
  13. +++ Update check is enabled, initializing the background job (early start)
  14. +++ Starting the update check background job
  15. +++ Getting the settings
  16. A custom config file was provided:
  17. C:\CoreCycler-v0.11.0.0\configs\Ryzen.AutomaticTestMode.Start.ini
  18. + Trying to determine the automatically selected binary by y-cruncher
  19. +++ C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe
  20. +++ "C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\y-cruncher.exe" pause:-2 colors:0 fake-invalid-command /dlllog:""
  21. +++ Auto-Selecting: 24-ZN5 ~ Komari
  22. + Found our automatically selected binary: 24-ZN5 ~ Komari
  23. +++ Settings parsed
  24. +++
  25. +++ -------------------------------- The config file -------------------------------
  26. +++ C:\CoreCycler-v0.11.0.0\config.ini
  27. +++ --------------------------------------------------------------------------------
  28. +++
  29. +++ # Config file for CoreCycler
  30. +++ # You can always find the default config file in configs\default.config.ini as a reference
  31. +++
  32. +++
  33. +++ # This is a copy of the default.config.ini in the /configs/ directory
  34. +++ # It contains all the available settings with comments and examples of what they do
  35. +++ # You can replace this file with your own version, and any setting that does not show up
  36. +++ # here will use its default value instead
  37. +++
  38. +++
  39. +++
  40. +++ # General settings
  41. +++ [General]
  42. +++
  43. +++ # Use a predefined config file instead of this one
  44. +++ # If this value is set, it will use the content from the file provided, overwriting all settings further below
  45. +++ # (which means that if you use this setting, you can safely remove all other settings in the "main" config.ini file)
  46. +++ # If this value is empty or invalid, the other settings from this file will apply
  47. +++ #
  48. +++ # It's useful for quickly switching between various configs, and you can find some predefined config files in the "configs" directory
  49. +++ # The setting uses a relative path from the location where this file is located in
  50. +++ # Example:
  51. +++ # useConfigFile = configs\quick-initial-test.yCruncher.config.ini
  52. +++ #
  53. +++ # Default: (empty)
  54. +++ useConfigFile = configs\Ryzen.AutomaticTestMode.Start.ini
  55. +++
  56. +++
  57. +++ # The program to perform the actual stress test
  58. +++ # The following programs are available:
  59. +++ # - PRIME95
  60. +++ # - AIDA64
  61. +++ # - YCRUNCHER
  62. +++ # - YCRUNCHER_OLD
  63. +++ # - LINPACK
  64. +++ # You can change the test mode and options for each stress test program in the respective [section] further down
  65. +++ # Note: For AIDA64, you need to manually download and extract the portable ENGINEER version and put it
  66. +++ # in the /test_programs/aida64/ folder
  67. +++ # AIDA64 is somewhat sketchy as well
  68. +++ # Note: There are two versions of y-cruncher included, which you can select with either "YCRUNCHER" or "YCRUNCHER_OLD"
  69. +++ # The "old" version uses the binaries and test algorithms that were available before version 0.8 of y-cruncher
  70. +++ # See the comments in the [yCruncher] section for a more detailed description
  71. +++ #
  72. +++ # Default: PRIME95
  73. +++ stressTestProgram = YCRUNCHER
  74. +++
  75. +++
  76. +++ # Set the runtime per core
  77. +++ # You can define a specific runtime per core, by entering a numeric value in seconds,
  78. +++ # or use 'h' for hours, 'm' for minutes and 's' for seconds
  79. +++ # Examples: 360 = 360 seconds
  80. +++ # 1h4m = 1 hour, 4 minutes
  81. +++ # 1.5m = 1.5 minutes = 90 seconds
  82. +++ #
  83. +++ # Automatic runtime:
  84. +++ # You can also set it to "auto", in which case it will perform one "full" run for each core
  85. +++ # For Prime95, it will wait until all of the FFT sizes in the selected preset have been tested and
  86. +++ # will then continues to the next core and start again
  87. +++ # For y-cruncher the "auto" setting will wait until all selected tests have been finished for a core
  88. +++ # and will then continue to the next core
  89. +++ # If logging has been disabled for y-cruncher, it will fall back to 10 minutes per core
  90. +++ # For Aida64 the "auto" setting will default to 10 minutes per core
  91. +++ #
  92. +++ # Below are some examples of the runtime for one iteration of Prime95 for the various tests on my 5900X with one thread
  93. +++ # The first iteration is also usually the fastest one
  94. +++ # Selecting two threads usually takes *much* longer than one thread for one iteration in Prime95
  95. +++ # - Prime95 "Smallest": 4K to 21K - [SSE] ~3-4 Minutes <|> [AVX] ~8-9 Minutes <|> [AVX2] ~8-10 Minutes
  96. +++ # - Prime95 "Small": 36K to 248K - [SSE] ~4-6 Minutes <|> [AVX] ~14-19 Minutes <|> [AVX2] ~14-19 Minutes
  97. +++ # - Prime95 "Large": 426K to 8192K - [SSE] ~18-22 Minutes <|> [AVX] ~37-44 Minutes <|> [AVX2] ~38-51 Minutes
  98. +++ # - Prime95 "Huge": 8960K to MAX - [SSE] ~13-19 Minutes <|> [AVX] ~27-40 Minutes <|> [AVX2] ~33-51 Minutes
  99. +++ # - Prime95 "All": 4K to MAX - [SSE] ~40-65 Minutes <|> [AVX] ~92-131 Minutes <|> [AVX2] ~102-159 Minutes
  100. +++ # - Prime95 "Moderate": 1344K to 4096K - [SSE] ~7-15 Minutes <|> [AVX] ~17-30 Minutes <|> [AVX2] ~17-33 Minutes
  101. +++ # - Prime95 "Heavy": 4K to 1344K - [SSE] ~15-28 Minutes <|> [AVX] ~43-68 Minutes <|> [AVX2] ~47-73 Minutes
  102. +++ # - Prime95 "HeavyShort": 4K to 160K - [SSE] ~6-8 Minutes <|> [AVX] ~22-24 Minutes <|> [AVX2] ~23-25 Minutes
  103. +++ #
  104. +++ # Default: 6m
  105. +++ runtimePerCore = auto
  106. +++
  107. +++
  108. +++ # Periodically suspend the stress test program
  109. +++ # This can simulate load changes / switches to idle and back
  110. +++ # Setting this to 1 will periodically suspend the stress test program, wait for a bit, and then resume it
  111. +++ # You should see the CPU load and clock speed drop significantly while the program is suspended and rise back up again
  112. +++ # Note: This will increase the runtime of the various stress tests as seen in the "runtimePerCore" setting by roughly 10%
  113. +++ #
  114. +++ # Default: 1
  115. +++ suspendPeriodically = 1
  116. +++
  117. +++
  118. +++ # The test order of the cores
  119. +++ # Available modes:
  120. +++ # Default: On CPUs with more than 8 physical cores: 'Alternate'. Otherwise 'Random'
  121. +++ # Alternate: Alternate between the 1st core on CCD1, then 1st on CCD2, then 2nd on CCD1, then 2nd on CCD2, etc.
  122. +++ # This should distribute the heat more evenly and possibly allow for higher clocks on CPUs with 2 CCDs
  123. +++ # CorePairs: This will create "pairs" of cores, so e.g. core 0 - core 1, core 0 - core 2, ... core 0 - core max,
  124. +++ # up to core max - core 0, core max - core 1, core max - core max-1
  125. +++ # This allows for testing if there is any problem when switching from a specific core to another
  126. +++ # Random: A random order
  127. +++ # Sequential: Cycle through the cores in numerical order
  128. +++ #
  129. +++ # You can also define your own testing order by entering a list of comma separated values.
  130. +++ # The list will be processed as provided, which means you can test the same core multiple times per iteration.
  131. +++ # Do note however that the "coresToIgnore" setting still takes precedence over any core listed here.
  132. +++ # The enumeration of cores starts with 0
  133. +++ # Example: 5, 4, 0, 5, 5, 7, 2
  134. +++ #
  135. +++ # Default: Default
  136. +++ coreTestOrder = Default
  137. +++
  138. +++
  139. +++ # Skip a core that has thrown an error in the following iterations
  140. +++ # If set to 0, this will test a core in the next iterations even if has thrown an error before
  141. +++ #
  142. +++ # Default: 1
  143. +++ skipCoreOnError = 1
  144. +++
  145. +++
  146. +++ # Stop the whole testing process if an error occurred
  147. +++ # If set to 0 (default), the stress test programm will be restarted when an error
  148. +++ # occurs and the core that caused the error will be skipped in the next iteration
  149. +++ #
  150. +++ # Default: 0
  151. +++ stopOnError = 0
  152. +++
  153. +++
  154. +++ # The number of threads to use for testing
  155. +++ # You can only choose between 1 and 2
  156. +++ # If Hyperthreading / SMT is disabled, this will automatically be set to 1
  157. +++ # Currently there's no automatic way to determine which core has thrown an error
  158. +++ # Setting this to 1 causes higher boost clock speed (due to less heat)
  159. +++ #
  160. +++ # Default: 1
  161. +++ # Maximum: 2
  162. +++ numberOfThreads = 2
  163. +++
  164. +++
  165. +++ # Use only one thread for load generation, but assign this thread to both virtual (logical) cores
  166. +++ # This way the Windows Scheduler or the internal CPU scheduler will choose which of both virtual CPU is used
  167. +++ # This may lead to additional stress situation otherwise not possible
  168. +++ # This setting has no effect if Hyperthreading / SMT is disabled or if numberOfThreads = 2
  169. +++ #
  170. +++ # Default: 0
  171. +++ assignBothVirtualCoresForSingleThread = 0
  172. +++
  173. +++
  174. +++ # The max number of iterations
  175. +++ # High values are basically unlimited (good for testing over night)
  176. +++ #
  177. +++ # Default: 10000
  178. +++ maxIterations = 10000
  179. +++
  180. +++
  181. +++ # Ignore certain cores
  182. +++ # Comma separated list of cores that will not be tested
  183. +++ # The enumeration of cores starts with 0
  184. +++ #
  185. +++ # Example: coresToIgnore = 0, 1, 2
  186. +++ # Default: (empty)
  187. +++ coresToIgnore =
  188. +++
  189. +++
  190. +++ # Restart the stress test process when a new core is selected
  191. +++ # This means each core will perform the same sequence of tests during the stress test
  192. +++ # This setting is best combined with runtimePerCore = auto
  193. +++ # Note: The monitor doesn't seem to turn off when this setting is enabled
  194. +++ #
  195. +++ # Important note:
  196. +++ # One disadvantage of this setting is that it has the potential to limit the amount of tests that the stress test program
  197. +++ # can run.
  198. +++ # In Prime95 for example, each FFT size will run for roughly 1 minute (except for very small ones), so if you want to make
  199. +++ # sure that Prime95 runs all of the available FFT sizes for a setting, you'll have to extend the "runtimePerCore" setting
  200. +++ # from the default value to something higher.
  201. +++ # For example the "Huge"/SSE preset has 19 FFT entries, and tests on my 5900X showed that it roughly takes 13-19 Minutes
  202. +++ # until all FFT sizes have been tested. The "Large"/SSE seems to take between 18 and 22 Minutes.
  203. +++ # I've included the measured times in the comment for the "runtimePerCore" setting above.
  204. +++ # This is why setting runtimePerCore = auto is beneficial when using this setting, to make sure every test is performed
  205. +++ # for every core.
  206. +++ #
  207. +++ # If this setting is disabled, a new core will very likely start with a different test / FFT size than the previous one.
  208. +++ # For longer testing periods (e.g. over night), the tested FFT sizes / algorithms will even out eventually, but if you
  209. +++ # want to make sure that each core is tested in exactly the same way, you should enable this setting.
  210. +++ #
  211. +++ # Default: 0
  212. +++ restartTestProgramForEachCore = 0
  213. +++
  214. +++
  215. +++ # Set a delay between the cores
  216. +++ # If the "restartTestProgramForEachCore" flag is set, this setting will define the amount of seconds between the end of
  217. +++ # the run of one core and the start of another
  218. +++ # If "restartTestProgramForEachCore" is 0, this setting has no effect
  219. +++ # Using this setting may help your CPU to cool down a little between cores, which could result in slightly higher
  220. +++ # core clocks at the start of the test (which could help in identifying instabilities)
  221. +++ #
  222. +++ # Default: 15
  223. +++ delayBetweenCores = 15
  224. +++
  225. +++
  226. +++ # Beep on a core error
  227. +++ # Play a beep when a core has thrown an error
  228. +++ #
  229. +++ # Default: 1
  230. +++ beepOnError = 0
  231. +++
  232. +++
  233. +++ # Flash on a core error
  234. +++ # Flash the window/icon in the taskbar when a core has thrown an error
  235. +++ #
  236. +++ # Default: 1
  237. +++ flashOnError = 1
  238. +++
  239. +++
  240. +++ # Check for WHEA errors
  241. +++ # If this is enabled, CoreCycler will periodicall check the Windows Event Log for WHEA errors
  242. +++ # These WHEA errors do not necessarily cause or show up together with a stress test error, but are indicative
  243. +++ # of an unstable overclock/undervolt
  244. +++ # A stable system should not produce any WHEA errors/warnings
  245. +++ #
  246. +++ # Default: 1
  247. +++ lookForWheaErrors = 1
  248. +++
  249. +++
  250. +++ # Treat a WHEA Warning Event Log entry as an error
  251. +++ # If this is enabled, a WHEA warning (Event Id 19, "corrected hardware error") will be treated as a "real" error
  252. +++ # The testing on the core will be stopped and continued on the next one
  253. +++ # However only if the APIC ID from the WHEA message matches the core that was currently tested, otherwise
  254. +++ # only a warning will be displayed
  255. +++ #
  256. +++ # Default: 1
  257. +++ treatWheaWarningAsError = 1
  258. +++
  259. +++
  260. +++
  261. +++
  262. +++ # Prime95 specific settings
  263. +++ [Prime95]
  264. +++
  265. +++ # The test modes for Prime95
  266. +++ # SSE Lightest load on the processor, lowest temperatures, highest boost clock
  267. +++ # AVX Medium load on the processor, medium temperatures, medium boost clock
  268. +++ # AVX2 Heavy load on the processor, highest temperatures, lowest boost clock
  269. +++ # AVX512 Only available for certain CPUs (Ryzen 7000, some Intel Alder Lake, etc)
  270. +++ # CUSTOM You can define your own settings for Prime. See the "customs" section further below
  271. +++ #
  272. +++ # Default: SSE
  273. +++ mode = SSE
  274. +++
  275. +++
  276. +++ # The FFT size preset to test for Prime95
  277. +++ # These are basically the presets as present in Prime95, plus an additional few
  278. +++ # Note: If "mode" is set to "CUSTOM", this setting will be ignored
  279. +++ # Smallest 4K to 21K - Prime95 preset text: "tests L1/L2 caches, high power/heat/CPU stress"
  280. +++ # Small 36K to 248K - Prime95 preset text: "tests L1/L2/L3 caches, maximum power/heat/CPU stress"
  281. +++ # Large 426K to 8192K - Prime95 preset text: "stresses memory controller and RAM" (although dedicated memory stress testing is disabled here by default!)
  282. +++ # Huge 8960K to MAX - Anything beginning at 8960K up to the highest FFT size (32768K for SSE/AVX, 51200K for AVX2, 65536K for AVX512)
  283. +++ # All 4K to MAX - 4K to up to the highest FFT size (32768K for SSE/AVX, 51200K for AVX2, 65536K for AVX512)
  284. +++ # Moderate 1344K to 4096K - special preset, recommended in the "Curve Optimizer Guide Ryzen 5000"
  285. +++ # Heavy 4K to 1344K - special preset, recommended in the "Curve Optimizer Guide Ryzen 5000"
  286. +++ # HeavyShort 4K to 160K - special preset, recommended in the "Curve Optimizer Guide Ryzen 5000"
  287. +++ #
  288. +++ # You can also define a single FFT size by just entering the value, or your own range by entering two FFT sizes joined by a hyphen, e.g 36-1344
  289. +++ #
  290. +++ # Default: Huge
  291. +++ FFTSize = Huge
  292. +++
  293. +++
  294. +++
  295. +++
  296. +++ # y-cruncher specific settings
  297. +++ # These apply to both "YCRUNCHER" and "YCRUNCHER_OLD"
  298. +++ [yCruncher]
  299. +++
  300. +++ # The test modes for y-cruncher
  301. +++ # y-cruncher offer various test modes (binaries/algorithms), that require different instruction sets to be available
  302. +++ # See the \test_programs\y-cruncher\Binaries\Tuning.txt file for a detailed explanation
  303. +++ #
  304. +++ # Automatic selection vs. manual selection:
  305. +++ # You can use the "auto" setting, in which case y-cruncher will automatically decide which binary it chooses for your CPU
  306. +++ # If instead you want to manually select a specific binary, you can see the list below:
  307. +++ #
  308. +++ # Test Mode Name Automatic Selection For Required Instruction Set
  309. +++ # -------------- ----------------------- ------------------------
  310. +++ # "00-x86" Legacy x86 86/IA-32 since Pentium (BSWAP, CMPXCHG, CPUID, RDTSC, possibly others...)
  311. +++ # "04-P4P" Intel Pentium 4 Prescott SSE, SSE2, SSE3
  312. +++ # "05-A64 ~ Kasumi" AMD Athlon 64 x64, SSE, SSE2, SSE3
  313. +++ # "08-NHM ~ Ushio" Intel Nehalem x64, SSE, SSE2, SSE3, SSSE3, SSE4.1
  314. +++ # "11-SNB ~ Hina" Intel Sandy Bridge x64, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX
  315. +++ # "12-BD2 ~ Miyu" AMD Piledriver x64, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, ABM, FMA3
  316. +++ # "13-HSW ~ Airi" Intel Haswell x64, ABM, BMI1, BMI2, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2
  317. +++ # "14-BDW ~ Kurumi" Intel Broadwell x64, ABM, BMI1, BMI2, ADX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2
  318. +++ # "17-SKX ~ Kotori" Intel Skylake X [AVX512] x64, ABM, BMI1, BMI2, ADX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2, AVX512-(F/CD/VL/BW/DQ)
  319. +++ # "17-ZN1 ~ Yukina" AMD Zen 1 Summit Ridge x64, ABM, BMI1, BMI2, ADX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2
  320. +++ # "18-CNL ~ Shinoa" Intel Cannon Lake [AVX512] x64, ABM, BMI1, BMI2, ADX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2, AVX512-(F/CD/VL/BW/DQ/IFMA/VBMI)
  321. +++ # "19-ZN2 ~ Kagari" AMD Zen 2 Matisse (and Zen 3) x64, ABM, BMI1, BMI2, ADX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2
  322. +++ # "22-ZN4 ~ Kizuna" AMD Zen 4 Raphael [AVX512] x64, ABM, BMI1, BMI2, ADX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2, AVX512-(F/CD/VL/BW/DQ/IFMA/VBMI/GFNI)
  323. +++ # "24-ZN5 ~ Komari" AMD Zen 5 Granite Ridge [AVX512] x64, ABM, BMI1, BMI2, ADX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, FMA3, AVX2, AVX512-(F/CD/VL/BW/DQ/IFMA/VBMI/VBMI2/GFNI)
  324. +++ #
  325. +++ # If you let y-cruncher run on its own, it will automatically select one of these test modes depending on the processor it detects,
  326. +++ # this is the "Automatic Selection For" column in the table above
  327. +++ # For CoreCycler however you need to select a specific test mode to be run
  328. +++ # As a general rule you can assume that the less instructions are required, the less heat a test mode will produce, and therefore the boost clocks can go higher
  329. +++ # On the other hand, if you actually want to test all the transistors in your chip, you will need to select a test mode that covers all of the available instruction sets
  330. +++ # So it's advised that you test both with the least and the highest amount of available instruction sets for your processor to cover all use cases
  331. +++ #
  332. +++ # Be aware that test modes that require AVX512 instructions will not work on processors that do not support AVX512!
  333. +++ # It will either outright crash or simply not start
  334. +++ #
  335. +++ # A quick overview:
  336. +++ # "00-x86" produces the least amount of heat and should therefore produce the highest boost clock on most tests
  337. +++ # "14-BDW ~ Kurumi" is the test that y-cruncher itself would default to if you run it on an Intel CPU up to at least 14th gen
  338. +++ # "19-ZN2 ~ Kagari" is the test that y-cruncher itself would default to for Zen 2/3 (Ryzen 3000/5000)
  339. +++ # "22-ZN4 ~ Kizuna" is the test that y-cruncher itself would default to for Zen 4 (Ryzen 7000) and uses AVX512 instructions
  340. +++ # "24-ZN5 ~ Komari" is the test that y-cruncher itself would default to for Zen 5 (Ryzen 9000) and uses AVX512 instructions
  341. +++ #
  342. +++ # User experience seems to indicate that "19-ZN2 ~ Kagari" is pretty good for testing stability, even for Zen 4 (Ryzen 7000) CPUs
  343. +++ # It is unclear yet how Zen 5 / Ryzen 9000 CPUs will turn out
  344. +++ # So as a recommendation, use "04-P4P" for low load testing and "19-ZN2 ~ Kagari" for higher/AVX2 load scenarios
  345. +++ # As "14-BDW ~ Kurumi" is the test mode that y-cruncher chooses for Intel CPUs, it is not entirely clear if this or "19-ZN2 ~ Kagari"
  346. +++ # is the better test for AVX/AVX2 loads on Intel CPUs. At least they share the same instruction sets, so you might need to check for yourself
  347. +++ #
  348. +++ #
  349. +++ # When using the old y-cruncher version ("YCRUNCHER_OLD" selected as the stress test), the "12-BD2 ~ Miyu" test mode is named "11-BD1 ~ Miyu" instead
  350. +++ #
  351. +++ # Default: 00-x86
  352. +++ mode = 24-ZN5 ~ Komari
  353. +++
  354. +++
  355. +++ # Set the test algorithms to run for y-cruncher
  356. +++ # y-crunchers offers various different test algorithms that it can run, here you can select which ones it should use
  357. +++ # Tag Test Name Component CPU------Mem
  358. +++ # --- --------- --------- ------------
  359. +++ # BKT Basecase + Karatsuba Scalar Integer -|--------
  360. +++ # BBP BBP Digit Extraction AVX2 Float |---------
  361. +++ # SFTv4 Small In-Cache FFTv4 AVX2 Float -|--------
  362. +++ # SNT Small In-Cache N63 AVX2 Integer --|-------
  363. +++ # SVT Small In-Cache VT3 AVX2 Float --|-------
  364. +++ # FFTv4 Fast Fourier Transform (v4) AVX2 Float ---------|
  365. +++ # N63 Classic NTT (v2) AVX2 Integer ---|------
  366. +++ # VT3 Vector Transform (v3) AVX2 Float ----|-----
  367. +++
  368. +++ #
  369. +++ # Use a comma separated list
  370. +++ # Default: BKT, BBP, SFTv4, SNT, SVT, FFTv4, N63, VT3
  371. +++ tests = BKT, BBP, SFTv4, SNT, SVT, FFTv4, N63, VT3
  372. +++
  373. +++
  374. +++ # Set the test algorithms to run for the "old" version of y-cruncher ("YCRUNCHER_OLD" selected as the stress test)
  375. +++ # This older version (v0.7.10.9513) has a different set of tests to choose from
  376. +++ # Tag Test Name Component CPU------Mem
  377. +++ # --- --------- --------- ------------
  378. +++ # BKT Basecase + Karatsuba Scalar Integer -|--------
  379. +++ # BBP BBP Digit Extraction Floating-Point |--------- depending on the selected mode uses SSE, AVX, AVX2 or AVX512
  380. +++ # SFT Small In-Cache FFT Floating-Point -|-------- depending on the selected mode uses SSE, AVX, AVX2 or AVX512
  381. +++ # FFT Fast Fourier Transform Floating-Point ---------| depending on the selected mode uses SSE, AVX, AVX2 or AVX512
  382. +++ # N32 Classic NTT (32-bit) Scalar Integer -----|---- depending on the selected mode uses SSE, AVX, AVX2 or AVX512
  383. +++ # N64 Classic NTT (64-bit) Scalar Integer ---|------ depending on the selected mode uses SSE, AVX, AVX2 or AVX512
  384. +++ # HNT Hybrid NTT Mixed Workload -----|----
  385. +++ # VST Vector Transform Floating-Point ------|--- depending on the selected mode uses SSE, AVX, AVX2 or AVX512
  386. +++ # C17 Code 17 Experiment AVX2/512 Mixed ---|------ depending on the selected mode uses AVX2 or AVX512
  387. +++ #
  388. +++ # Important:
  389. +++ # "C17" (Code 17 Experiment) will only work with a AVX2 and AVX512 workload (so with mode "13-HSW ~ Airi" and above)
  390. +++ #
  391. +++ # Use a comma separated list
  392. +++ # Default: BKT, BBP, SFT, FFT, N32, N64, HNT, VST
  393. +++ #tests = BKT, BBP, SFT, FFT, N32, N64, HNT, VST
  394. +++
  395. +++
  396. +++ # Set the duration in seconds for each test in y-cruncher
  397. +++ # The duration for each individual test selected above in the "tests" setting
  398. +++ # Note: not the total runtime
  399. +++ #
  400. +++ # Default: 60
  401. +++ testDuration = 60
  402. +++
  403. +++
  404. +++ # Memory allocation for y-cruncher
  405. +++ # This allows you to customize the allocated memory for y-cruncher
  406. +++ # Set the value in bytes or use a "short" notation like e.g. "64MB"
  407. +++ # The default setting uses 13.4 MB (13418572 bytes, 12.8 MiB) for one resp. 26.7 MB (26567600 bytes, 25.3 MiB) for two threads
  408. +++ # Note the difference between "MB" (1000 kilobyte = 1000*1000 byte) and "MiB" (1024 kibibyte = 1024*1024 byte)
  409. +++ #
  410. +++ # Default: Default
  411. +++ memory = Default
  412. +++
  413. +++
  414. +++ # Enable or disable the custom logging wrapper for y-cruncher
  415. +++ # We are using the helpers/WriteConsoleToWriteFileWrapper.exe executable to capture the output of y-cruncher and write it to a file
  416. +++ # It is using the Microsoft Detours C++ library to do so
  417. +++ # Here you can disable this behaviour and revert back to the original y-cruncher execution
  418. +++ #
  419. +++ # It is strongly recommended to leave this setting enabled, unless you're experiencing problems with it!
  420. +++ #
  421. +++ # Default: 1
  422. +++ enableYCruncherLoggingWrapper = 1
  423. +++
  424. +++
  425. +++
  426. +++
  427. +++ # Aida64 specific settings
  428. +++ [Aida64]
  429. +++
  430. +++ # The test modes for Aida64
  431. +++ # Note: "RAM" consumes basically all of the available memory and makes the computer pretty slow
  432. +++ # You can change the amount of RAM being used / tested with the "maxMempory" setting below
  433. +++ # CACHE: Starts Aida64 with the "Cache" stress test
  434. +++ # CPU: Starts Aida64 with the "CPU" stress test
  435. +++ # FPU: Starts Aida64 with the "FPU" stress test
  436. +++ # RAM: Starts Aida64 with the "Memory" stress test
  437. +++ # You can also combine multiple stress tests like so: CACHE,CPU,FPU
  438. +++ #
  439. +++ # Default: CACHE
  440. +++ mode = CACHE
  441. +++
  442. +++
  443. +++ # Use AVX for Aida64
  444. +++ # This enables or disables the usage of AVX instructions during Aida64's stress tests
  445. +++ #
  446. +++ # Default: 0
  447. +++ useAVX = 0
  448. +++
  449. +++
  450. +++ # The maximum memory allocation for Aida64
  451. +++ # Sets the maximum memory usage during the "RAM" stress test in percent
  452. +++ # Note: Setting this too high can cause your Windows to slow down to a crawl!
  453. +++ #
  454. +++ # Default: 90
  455. +++ maxMemory = 90
  456. +++
  457. +++
  458. +++
  459. +++
  460. +++ # Linpack specific settings
  461. +++ [Linpack]
  462. +++
  463. +++ # Which version of Linpack to use
  464. +++ # There are four different choices available
  465. +++ # 2018: Intel Linpack version 2018.0.3.1 - this is the same version as used in Linpack Xtreme 1.1.5
  466. +++ # 2019: Intel Linpack version 2019.0.3.1
  467. +++ # 2021: Intel Linpack version 2021.4.1.0 - this version always uses FASTEST (AVX2)
  468. +++ # 2024: Intel Linpack version 2024.2.1.0 - this version always uses FASTEST (AVX2)
  469. +++ #
  470. +++ # Version 2018 and 2019 are the only ones where you can set the mode to anything but "FASTEST"
  471. +++ # These two version also run slightly faster (more GFlops) on AMD processors than the newer versions when set to "FASTEST"
  472. +++ # But the newer versions might have additional optimizations that are missing in the older ones
  473. +++ #
  474. +++ # Default: 2018
  475. +++ version = 2018
  476. +++
  477. +++
  478. +++ # The test mode for Linpack
  479. +++ # You can choose between five settings:
  480. +++ # SLOWEST
  481. +++ # SLOW
  482. +++ # MEDIUM
  483. +++ # FAST
  484. +++ # FASTEST
  485. +++ # These settings define how fast one iteration will be completed (how many GFlops you'll see and the time it takes)
  486. +++ # It should also affect which instruction set is being used, e.g. FASTEST should enable AVX2, while FAST should
  487. +++ # use AVX
  488. +++ # I'm not entirely sure what instructions the other settings use exactly, but I did see a difference in the runtime
  489. +++ # and GFlops for these settings
  490. +++ # Here are some examples (not comparable to anything else, since determined with a custom overclock/undervolt setting):
  491. +++ # Ryzen 5900X 1 Thread Intel 14900KF 1 Thread
  492. +++ # GFlops Time Temp GFlops Time Temp
  493. +++ # SLOWEST ~21 ~126s ~67°C ~28 ~96s ~64°C
  494. +++ # SLOW ~25 ~105s ~71°C ~28 ~94s ~65°C
  495. +++ # MEDIUM ~27 ~99s ~71°C ~30 ~89s ~66°C
  496. +++ # FAST ~45 ~59s ~75°C ~51 ~52s ~66°C
  497. +++ # FASTEST ~66 ~40s ~76°C ~78 ~34s ~69°C
  498. +++ #
  499. +++ # As you can see, the setting has a more pronounced effect on AMD CPUs, but Intel CPUs are affected as well, just not
  500. +++ # as much on the slower settings
  501. +++ # This setting makes use of an undocumentented environment variable (MKL_DEBUG_CPU_TYPE) for Intel's MKL library
  502. +++ # (Math Kernel Library), which is interally used by Linpack
  503. +++ #
  504. +++ # Default: MEDIUM
  505. +++ mode = MEDIUM
  506. +++
  507. +++
  508. +++ # Memory allocation for Linpack
  509. +++ # Set the amount of memory to use with Linpack
  510. +++ # Enter the value either as a string like 500MB, 2GB, 4GB, etc
  511. +++ # Or as a raw value in bytes, e.g. 250000000 (which would equal "250MB")
  512. +++ # Note the difference between "MB" (1000 kilobyte = 1000*1000 byte) and "MiB" (1024 kibibyte = 1024*1024 byte)
  513. +++ # Also be aware that the memory size directly influences the time it takes to run one test, here are some examples:
  514. +++ # Setting Sample runtime Sample runtime
  515. +++ # with MEDIUM with FASTEST
  516. +++ # 100MB 1s 0.5s
  517. +++ # 250MB 4s 2s
  518. +++ # 500MB 12s 5s
  519. +++ # 750MB 23s 9s
  520. +++ # 1GB 35s 14s
  521. +++ # 2GB 99s 40s
  522. +++ # 4GB 287s 117s
  523. +++ # 6GB 534s 216s
  524. +++ # 30GB unknown, >1h not tested (I aborted after over an hour)
  525. +++ # Also note that choosing more memory doesn't necessarily help in finding CPU related problems
  526. +++ # It may help identifying RAM or IMC (Internal Memory Controller) related issues
  527. +++ #
  528. +++ # Default: 2GB
  529. +++ memory = 2GB
  530. +++
  531. +++
  532. +++
  533. +++
  534. +++ # Settings for the Automatic Test Mode
  535. +++ [AutomaticTestMode]
  536. +++
  537. +++ # Enable the automatic test mode
  538. +++ # If you enable this setting, the script will automatically adjust the Curve Optimizer or voltage offset values
  539. +++ # when an error occurs
  540. +++ #
  541. +++ # For Ryzen CPUs it uses "ryzen-smu-cli", which is included in the /tools/ryzen-smu-cli/ directory
  542. +++ # For Intel, it uses "IntelVoltageControl", which allows you to set a voltage offset (also included in the /tools/ directory)
  543. +++ #
  544. +++ # Note that this will only INCREASE the Curve Optimizer / voltage offset values, i.e. it will try to make the settings
  545. +++ # more stable, it will never push the settings more into the negative
  546. +++ # Also note that enabling this setting will require the script to be run with administrator privileges
  547. +++ # And lastly, enabling it will set "skipCoreOnError" to 0 and "stopOnError" to 0 as long as the limit has not been reached
  548. +++ #
  549. +++ # IMPORTANT: The automatically adjusted Curve Optimizer / voltage offset values are NOT permanent, so after a regular reboot they
  550. +++ # will not be applied anymore
  551. +++ # If you want to permanently set these values, you will need to set them in the BIOS, or use a startup script to
  552. +++ # set them on every Windows start (see the .txt files for ryzen-smu-cli resp. IntelVoltageControl in the /tools
  553. +++ # directory for an explanation of the various settings)
  554. +++ #
  555. +++ # Default: 0
  556. +++ enableAutomaticAdjustment = 0
  557. +++
  558. +++
  559. +++ # The starting Curve Optimizer / voltage offset values
  560. +++ # You can provide the Curve Optimizer / voltage offset starting values here, or let them be automatically detected
  561. +++ # If you specify values here, they will overwrite your currently applied CO / voltage offset settings
  562. +++ # If you leave the value blank or set it to "CurrentValues" or "Default", it will try to automatically detect your current settings
  563. +++ #
  564. +++ # For Ryzen, you can use the "Minimum" value to automatically set the values to their respective minimum Curve Optimizer values
  565. +++ # (-30 for Ryzen 5000 and -50 for Ryzen 7000 and upwards)
  566. +++ #
  567. +++ # Use a comma separated list or define a single value that will be applied to all cores
  568. +++ # You can also use spaces or "|" to separate the cores
  569. +++ # For Intel, this currently only really supports a single voltage offset that is applied to each core
  570. +++ # For Ryzen, you can define the Curve Optimizer value for each core
  571. +++ #
  572. +++ # Note: For Ryzen, the minimum possible Curve Optimizer value is defined by your CPU
  573. +++ # -30 is the minimum value for Curve Optimizer on Ryzen 5000, and -50 for Ryzen 7000 and upwards
  574. +++ # (and each point of Curve Optimizer equals around 3-5 millivolts)
  575. +++ # Note: For Intel, the values are provided in millivolts, so e.g. -120 for an undervolt of -0.120v
  576. +++ #
  577. +++ # IMPORTANT: Use a negative sign if you want negative CO values / a negative voltage offset, not providing a negative sign will
  578. +++ # instead apply a positive CO / voltage offset!
  579. +++ # IMPORTANT: The automatically adjusted Curve Optimizer / voltage offset values are TEMPORARY, so after a regular reboot they
  580. +++ # will not be applied anymore
  581. +++ # If you want to permanently set these values, you will need to set them in the BIOS, or use a startup script to
  582. +++ # set them on every Windows start (see the text files in the /tools directory for an explanation of the various settings)
  583. +++ #
  584. +++ # Example for setting Curve Optimizer values for a Ryzen 5800X with 8 cores:
  585. +++ # startValues = -15, -10, -15, -8, 2, -20, 0, -30
  586. +++ # Or
  587. +++ # startValues = -15 -10 -15 -8 2 -20 0 -30
  588. +++ # Or
  589. +++ # startValues = -15 | -10 | -15 | -8 | 2 | -20 | 0 | -30
  590. +++ #
  591. +++ # Example to assign a single Curve Optimizer value to all cores:
  592. +++ # startValues = -20
  593. +++ #
  594. +++ # Example to assign a voltage offset of -0.120v (-120mv) for Intel processors:
  595. +++ # startValues = -120
  596. +++ #
  597. +++ # Default: CurrentValues
  598. +++ startValues = CurrentValues
  599. +++
  600. +++
  601. +++ # The upper limit for the Curve Optimizer values / voltage offset
  602. +++ # If this limit has been reached, no further adjustments will be performed
  603. +++ # Instead the core will now simply throw an error and the regular "skipCoreOnError" setting will be obeyed
  604. +++ # This is either a Curve Optimizer value or a voltage offset value
  605. +++ #
  606. +++ # IMPORTANT: Be sensible about this value, setting it too high into the positive could apply a too high
  607. +++ # voltage to your CPU and may damage it!
  608. +++ #
  609. +++ # Default: 0
  610. +++ maxValue = 0
  611. +++
  612. +++
  613. +++ # The amount by which to increase the Curve Optimizer / voltage offset value
  614. +++ # On an error, the Curve Optimizer / voltage offset value will be increased by this amount
  615. +++ # For Ryzen, a value between 1 and 5 seems reasonable
  616. +++ # For Intel, you should probably set this to 5 to increase the vCore by 5mv after an error
  617. +++ #
  618. +++ # Setting it to "Default" will set the value to 1 for Ryzen and 5 for Intel
  619. +++ #
  620. +++ # Default: Default
  621. +++ incrementBy = Default
  622. +++
  623. +++
  624. +++ # Set only the currently tested core to the selected Curve Optimizer / voltage offset value
  625. +++ # All the other cores will be set to 0, resp. the determined maximum value if it's higher than 0
  626. +++ # This should prevent errors caused by other cores than the currently tested one, or at least diminish the chance for that
  627. +++ #
  628. +++ # Note: Currently this only has an effect for Ryzen processors, for Intel up to 14th gen there is only one voltage value
  629. +++ #
  630. +++ # Default: 0
  631. +++ setVoltageOnlyForTestedCore = 0
  632. +++
  633. +++
  634. +++ # Repeat the test on a core if it has thrown an error and the Curve Optimizer / voltage offset value was increased
  635. +++ # Setting this to 1 will restart the test, until it has not thrown an error, or until the maximum value has been reached
  636. +++ # Setting it to 0, the script will continue to the next core in line as normal
  637. +++ #
  638. +++ # Default: 1
  639. +++ repeatCoreOnError = 1
  640. +++
  641. +++
  642. +++ # Try to automatically resume after a crash / hard reboot
  643. +++ # If this setting is enabled, the script will try to automatically resume after a reboot has occurred
  644. +++ # It creates a Scheduled Task that will be run at logon, which then tries to resume where it left off,
  645. +++ # optionally repeating the last core with an adjusted value (see the repeatCoreOnError setting)
  646. +++ #
  647. +++ # IMPORTANT: If you just close the CoreCycler window without properly exiting the script with CTRL+C,
  648. +++ # the Scheduled Task will remain and will be executed on the next reboot!
  649. +++ # So make sure that you always exit CoreCycler by pressing CTRL+C
  650. +++ #
  651. +++ # IMPORTANT: The Scheduled Task will execute once you log back in to your user account
  652. +++ # So for a true automated testing, it would be beneficial if you activated auto-logon
  653. +++ # Be aware that this might pose a security risk though, so make sure to consider the risks!
  654. +++ # https://learn.microsoft.com/en-us/sysinternals/downloads/autologon
  655. +++ # https://learn.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/turn-on-automatic-logon
  656. +++ #
  657. +++ # NOTE: On some systems, especially Ryzen 9000 systems, the computer doesn't seem to reset during an unstable
  658. +++ # Curve Optimizer setting, instead it just seems to freeze and would need to be manually restarted.
  659. +++ # Unfortunately there's currently no way around this that I know of.
  660. +++ # Maybe there is a BIOS setting somewhere, if you know something, please let me know.
  661. +++ #
  662. +++ # Default: 0
  663. +++ enableResumeAfterUnexpectedExit = 0
  664. +++
  665. +++
  666. +++ # Windows treats crashes or reboots that happen within 120 seconds of the boot as a "failed" boot
  667. +++ # To prevent the Windows Recovery Screen from appearing after three of those "failed" boots, the script will wait for this
  668. +++ # amount of time before resuming the testing process
  669. +++ # Set this to 0 if you don't care about that and want to resume immediately
  670. +++ #
  671. +++ # Default: 120
  672. +++ waitBeforeAutomaticResume = 120
  673. +++
  674. +++
  675. +++ # Create a System Restore Point when using the Automatic Test Mode
  676. +++ # Using the Automatic Test Mode with very unstable starting settings may result in a corrupted Windows installation,
  677. +++ # so creating a System Restore Point before activation is highly recommended
  678. +++ # This way you can more easily restore a corrupted installation
  679. +++ #
  680. +++ # NOTE: The script will only create a System Restore Point if the last one is older than 24 hours
  681. +++ # It will also not do so while in the middle of the Automatic Test Mode process, only when starting a fresh one
  682. +++ #
  683. +++ # Default: 1
  684. +++ createSystemRestorePoint = 1
  685. +++
  686. +++
  687. +++ # Ask for the creation of a System Restore Point
  688. +++ # If this setting is disabled, the System Restore Point will be automatically created without user interaction
  689. +++ #
  690. +++ # Default: 1
  691. +++ askForSystemRestorePointCreation = 1
  692. +++
  693. +++
  694. +++
  695. +++ # Log specific settings
  696. +++ [Logging]
  697. +++
  698. +++ # The name of the log file
  699. +++ # The "mode" parameter, the selected stress test program and test mode, as well as the start date & time will be
  700. +++ # added to the name, with a .log file ending
  701. +++ #
  702. +++ # Default: CoreCycler
  703. +++ name = CoreCycler
  704. +++
  705. +++
  706. +++ # Set the log level
  707. +++ # 0: Do not log or display additional information
  708. +++ # 1: Write additional information to the log file (verbose)
  709. +++ # 2: Write even more information to the log file (debug)
  710. +++ # 3: Also display the verbose messages in the terminal
  711. +++ # 4: Also display the debug messages in the terminal
  712. +++ #
  713. +++ # Default: 2
  714. +++ logLevel = 2
  715. +++
  716. +++
  717. +++ # Make use of the Windows Event Log to log core tests and core errors
  718. +++ # If this is enabled, CoreCycler will add entries to the Windows Event Log when it has been started, ended,
  719. +++ # and also when iterating over the cores
  720. +++ # This can be helpful if you suffer from corrupted log files after a hard reboot during testing
  721. +++ # To be able to use this, a new Windows Event "Source" for CoreCycler needs to be added, the script will ask
  722. +++ # you add this if it's not available yet
  723. +++ # Adding this Source will require Administrator rights (once), but after it has been added, no additional rights
  724. +++ # are required
  725. +++ # The entries can be found in the Windows Logs/Application section of the Event Viewer
  726. +++ #
  727. +++ # Default: 1
  728. +++ useWindowsEventLog = 1
  729. +++
  730. +++
  731. +++ # Periodically flush the disk write cache
  732. +++ # If this is enabled, CoreCycler will periodically try to flush the disk write cache, which could help to prevent
  733. +++ # corrupted log files when a hard reboot during testing occurs
  734. +++ # Note that some drives have an additional internal write cache, which is NOT affected by this setting
  735. +++ # Also note that this will not work for all drives/volumes, e.g. if you run the script from a VeraCrypt volume,
  736. +++ # this setting will have no effect
  737. +++ #
  738. +++ # Default: 0
  739. +++ flushDiskWriteCache = 0
  740. +++
  741. +++
  742. +++
  743. +++
  744. +++ # Settings for updates
  745. +++ [Update]
  746. +++
  747. +++ # Enable the update check
  748. +++ #
  749. +++ # Default: 1
  750. +++ enableUpdateCheck = 1
  751. +++
  752. +++
  753. +++ # The frequency of the check, in hours
  754. +++ #
  755. +++ # Default: 24
  756. +++ updateCheckFrequency = 24
  757. +++
  758. +++
  759. +++
  760. +++
  761. +++ # Custom settings for Prime95
  762. +++ [Prime95Custom]
  763. +++
  764. +++ # This needs to be set to 1 for AVX mode
  765. +++ # (and also if you want to set AVX2 below)
  766. +++ CpuSupportsAVX = 0
  767. +++
  768. +++
  769. +++ # This needs to be set to 1 for AVX2 mode
  770. +++ CpuSupportsAVX2 = 0
  771. +++
  772. +++
  773. +++ # This also needs to be set to 1 for AVX2 mode on Ryzen
  774. +++ CpuSupportsFMA3 = 0
  775. +++
  776. +++
  777. +++ # This needs to be set to 1 for AVX512 mode
  778. +++ CpuSupportsAVX512 = 0
  779. +++
  780. +++
  781. +++ # The minimum FFT size to test
  782. +++ # Value for "Smallest FFT": 4
  783. +++ # Value for "Small FFT": 36
  784. +++ # Value for "Large FFT": 426
  785. +++ MinTortureFFT = 4
  786. +++
  787. +++
  788. +++ # The maximum FFT size to test
  789. +++ # Value for "Smallest FFT": 21
  790. +++ # Value for "Small FFT": 248
  791. +++ # Value for "Large FFT": 8192
  792. +++ MaxTortureFFT = 8192
  793. +++
  794. +++
  795. +++ # The amount of memory to use in MB
  796. +++ # 0 = In-Place
  797. +++ TortureMem = 0
  798. +++
  799. +++
  800. +++ # The max amount of minutes for each FFT size during the stress test
  801. +++ # Note: It may be much less than one minute, basically it seems to be "one run or one minute, whichever is less"
  802. +++ TortureTime = 1
  803. +++
  804. +++
  805. +++
  806. +++
  807. +++ # Debug settings that shouldn't need to be changed
  808. +++ # Only change them if you know what you're doing and there's a problem you're trying to identify
  809. +++ [Debug]
  810. +++
  811. +++ # Debug setting to disable the periodic CPU utilization check
  812. +++ #
  813. +++ # This setting enables or disables the CPU utilization check during stress testing.
  814. +++ # Some stress test programs (like Aida64) do not generate a log file, so the only way to detect an error is by
  815. +++ # checking the current CPU utilization.
  816. +++ #
  817. +++ # This uses a pretty basic check to see if the stress is still running at all, for a more detailled check
  818. +++ # enable the "useWindowsPerformanceCountersForCpuUtilization" below.
  819. +++ # Be aware that enabling the Windows Performance Counters may introduce other issues though, see the
  820. +++ # corresponding setting for an explanation.
  821. +++ #
  822. +++ # Default: 0
  823. +++ disableCpuUtilizationCheck = 0
  824. +++
  825. +++
  826. +++ # Debug setting to enable the use of Windows Performance Counters for the CPU utilization check
  827. +++ #
  828. +++ # This setting controls if the Windows Performance Counters should be used, which can be corrupted for unknown
  829. +++ # reasons. Please see the readme.txt and the /tools/enable_performance_counter.bat file for a possible way
  830. +++ # to fix these issues. There's no guarantee that it works though.
  831. +++ #
  832. +++ # Default: 0
  833. +++ useWindowsPerformanceCountersForCpuUtilization = 0
  834. +++
  835. +++
  836. +++ # Debug setting to enable querying for the CPU frequency
  837. +++ #
  838. +++ # This setting enables checking the CPU frequency
  839. +++ # Currently it doesn't really serve any purpose. The retrieved CPU frequency is not accurate enough (e.g. compared to HWiNFO),
  840. +++ # and its output is limited to the "verbose" channel.
  841. +++
  842. +++ # According to some reports, enabling it can result in incorrect CPU utilization readings, so be aware of this when you enable
  843. +++ # this setting.
  844. +++ #
  845. +++ # Note that this also enables the usage of the Windows Performance Counters, which may not work on certain systems.
  846. +++ # They can become corrupted, please see the readme.txt and the /tools/enable_performance_counter.bat file for a possible way
  847. +++ # to fix these issues. There's no guarantee that it works though.
  848. +++ #
  849. +++ # Default: 0
  850. +++ enableCpuFrequencyCheck = 0
  851. +++
  852. +++
  853. +++ # Debug setting to control the interval in seconds for the CPU utilization check and the "suspendPeriodically" functionality
  854. +++ #
  855. +++ # Don't set this too low, it will spam the log file and can produce unnecessary CPU load.
  856. +++ # It would also increase the time when the stress test program is suspended
  857. +++ # I'd consider 10 to be the minimum reasonable value (which is also the default)
  858. +++ #
  859. +++ # If 0, will disable this functionality
  860. +++ # This basically would mean "disableCpuUtilizationCheck = 1" and "suspendPeriodically = 0"
  861. +++ # Not entirely though, as the last check before changing a core is not affected
  862. +++ #
  863. +++ # Default: 10
  864. +++ tickInterval = 10
  865. +++
  866. +++
  867. +++ # Debug setting to delay the first error check for each core
  868. +++ #
  869. +++ # With this setting you can define a wait time before the first error check happens for each core
  870. +++ # Some systems may need longer to initialize the stress test program, which can result in an incorrect CPU utilization detection,
  871. +++ # so setting this value might resolve this issue
  872. +++ # Don't set this value too high in relation to your "runTimePerCore" though
  873. +++ #
  874. +++ # Default: 0
  875. +++ delayFirstErrorCheck = 0
  876. +++
  877. +++
  878. +++ # Debug setting to set the priority of the stress test program
  879. +++ #
  880. +++ # The default priority is set to "High" so that other applications don't interfere with the testing
  881. +++ # It can cause the computer to behave sluggish though. Setting a lower priority can fix this
  882. +++ #
  883. +++ # Note: "RealTime" probably won't work and you shouldn't set this anway, as the computer won't be responsive anymore
  884. +++ #
  885. +++ # Possible values:
  886. +++ # Idle
  887. +++ # BelowNormal
  888. +++ # Normal
  889. +++ # AboveNormal
  890. +++ # High
  891. +++ # RealTime
  892. +++ #
  893. +++ # Default: Normal
  894. +++ stressTestProgramPriority = High
  895. +++
  896. +++
  897. +++ # Debug setting to display the stress test program window in the foreground
  898. +++ #
  899. +++ # If enabled, will display the window of the stress test program in the foreground, stealing focus
  900. +++ # If disabled (default), the window will either be minimized to the tray (Prime95) or be moveed to the background,
  901. +++ # without stealing focus of the currently opened window (y-cruncher)
  902. +++ #
  903. +++ # Default: 0
  904. +++ stressTestProgramWindowToForeground = 0
  905. +++
  906. +++
  907. +++ # Debug setting to control the amount of milliseconds the stress test program is being suspended
  908. +++ #
  909. +++ # Default: 1000
  910. +++ suspensionTime = 1000
  911. +++
  912. +++
  913. +++ # Debug setting to define the method that is used to suspend the stress test process
  914. +++ #
  915. +++ # Can either be set to "Debugger" or "Threads"
  916. +++ # "Debugger" uses the "DebugActiveProcess" and "DebugActiveProcessStop" kernel32.dll methods on the main process
  917. +++ # "Threads" uses the "SuspendThread" and "ResumeThread" kernel32.dll methods on the process threads
  918. +++ # There's no clear benefit to either of these settings, but if there's a problem with one of these settings,
  919. +++ # the other one may work better
  920. +++ #
  921. +++ # Default: Threads
  922. +++ modeToUseForSuspension = Threads
  923. +++
  924. +++
  925. +++
  926. +++
  927. +++ ---------------------------- The custom config file ----------------------------
  928. +++ C:\CoreCycler-v0.11.0.0\configs\Ryzen.AutomaticTestMode.Start.ini
  929. +++ --------------------------------------------------------------------------------
  930. +++
  931. +++ # This config uses the Automatic Test Mode to automatically adjust the Curve Optimizer values
  932. +++ # on Ryzen processors after an error has occurred
  933. +++ # It sets the Curve Optimizer values to the minimum value and will make it less aggressive
  934. +++ # step by step when an error or a crash occurs
  935. +++ #
  936. +++ # This took around 8 hours for my 5900X starting at -30 Curve Optimizer until 10 iterations had completed
  937. +++ #
  938. +++ # Author: sp00n
  939. +++
  940. +++
  941. +++ [General]
  942. +++ stressTestProgram = YCRUNCHER
  943. +++ runtimePerCore = auto
  944. +++ coreTestOrder = Default
  945. +++ numberOfThreads = 2
  946. +++ maxIterations = 10
  947. +++
  948. +++
  949. +++ [yCruncher]
  950. +++ mode = auto # This chooses the binary automatically, e.g. "19-ZN2 ~ Kagari" for Ryzen 5000 or "24-ZN5 ~ Komari" for Ryzen 9000
  951. +++ #tests = SFTv4, FFTv4, N63 # Limit the tests to stressful ones
  952. +++ tests = BKT, SVT, VT3, SFTv4, FFTv4, N63
  953. +++ #tests = BKT, BBP, SFTv4, SNT, SVT, FFTv4, N63, VT3 # These would be all of the available tests
  954. +++
  955. +++ # 20 seconds per test
  956. +++ testDuration = 60
  957. +++
  958. +++
  959. +++ [AutomaticTestMode]
  960. +++ enableAutomaticAdjustment = 1
  961. +++ startValues = -35, -35, -35, -35, -35, -21, -35, -35 # Automatically select the minimum possible Curve Optimizer value (-30 for Ryzen 5000, -50 Ryzen 7000/8000/9000)
  962. +++ maxValue = 0 # Do not go above Curve Optimizer value of 0
  963. +++ incrementBy = 2 # Adjust the Curve Optimizer value by 1 after an error
  964. +++
  965. +++
  966. +++ # Set the Curve Optimizer value only for the currently tested core
  967. +++ # All other cores will be set to 0, to avoid any possible interference
  968. +++ setVoltageOnlyForTestedCore = 1
  969. +++
  970. +++
  971. +++ # Setting to try to automatically resume after a crash / hard reboot
  972. +++ # For this to work properly, Auto Logon should be activated
  973. +++ # Otherwise the computer will just idle at the logon screen after a crash
  974. +++ # See https://learn.microsoft.com/en-us/sysinternals/downloads/autologon
  975. +++ # and https://learn.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/turn-on-automatic-logon
  976. +++ enableResumeAfterUnexpectedExit = 1
  977. +++
  978. +++
  979. +++ # We want to create a System Restore Point before starting the whole process
  980. +++ # Crashes can cause a corrupted Windows installation, and a Restore Point can help fix that
  981. +++ createSystemRestorePoint = 1
  982. +++
  983. +++
  984. +++ # Don't ask for the creation of a System Restore Point, just do it
  985. +++ # It will only do so at the beginning, not during the process, and only once within 24 hours
  986. +++ askForSystemRestorePointCreation = 0
  987. +++
  988. +++
  989. +++ ------------------------------ The parsed settings -----------------------------
  990. +++ [No Section] mode = AUTO
  991. +++
  992. +++ [Logging] useWindowsEventLog = 1
  993. +++ [Logging] flushDiskWriteCache = 0
  994. +++ [Logging] name = CoreCycler
  995. +++ [Logging] logLevel = 2
  996. +++
  997. +++ [Aida64] useAVX = 0
  998. +++ [Aida64] mode = CACHE
  999. +++ [Aida64] maxMemory = 90
  1000. +++
  1001. +++ [Update] updateCheckFrequency = 24
  1002. +++ [Update] enableUpdateCheck = 1
  1003. +++
  1004. +++ [Debug] stressTestProgramWindowToForeground = 0
  1005. +++ [Debug] delayFirstErrorCheck = 0
  1006. +++ [Debug] disableCpuUtilizationCheck = 0
  1007. +++ [Debug] modeToUseForSuspension = threads
  1008. +++ [Debug] tickInterval = 10
  1009. +++ [Debug] useWindowsPerformanceCountersForCpuUtilization = 0
  1010. +++ [Debug] enableCpuFrequencyCheck = 0
  1011. +++ [Debug] stressTestProgramPriority = Normal
  1012. +++ [Debug] suspensionTime = 1000
  1013. +++
  1014. +++ [yCruncher] mode = auto
  1015. +++ [yCruncher] enableYCruncherLoggingWrapper = 1
  1016. +++ [yCruncher] testDuration = 60
  1017. +++ [yCruncher] tests_original = BKT, SVT, VT3, SFTv4, FFTv4, N63
  1018. +++ [yCruncher] memory = default
  1019. +++ [yCruncher] tests = BKT SVT VT3 SFTv4 FFTv4 N63
  1020. +++
  1021. +++ [Prime95Custom] MinTortureFFT = 4
  1022. +++ [Prime95Custom] TortureTime = 1
  1023. +++ [Prime95Custom] TortureMem = 0
  1024. +++ [Prime95Custom] CpuSupportsAVX = 0
  1025. +++ [Prime95Custom] CpuSupportsFMA3 = 0
  1026. +++ [Prime95Custom] MaxTortureFFT = 8192
  1027. +++ [Prime95Custom] CpuSupportsAVX512 = 0
  1028. +++ [Prime95Custom] CpuSupportsAVX2 = 0
  1029. +++
  1030. +++ [AutomaticTestMode] createSystemRestorePoint = 1
  1031. +++ [AutomaticTestMode] enableAutomaticAdjustment = 1
  1032. +++ [AutomaticTestMode] waitBeforeAutomaticResume = 120
  1033. +++ [AutomaticTestMode] maxValue = 0
  1034. +++ [AutomaticTestMode] askForSystemRestorePointCreation = 0
  1035. +++ [AutomaticTestMode] enableResumeAfterUnexpectedExit = 1
  1036. +++ [AutomaticTestMode] incrementBy = 2
  1037. +++ [AutomaticTestMode] startValues = -35 -35 -35 -35 -35 -21 -35 -35
  1038. +++ [AutomaticTestMode] repeatCoreOnError = 1
  1039. +++ [AutomaticTestMode] setVoltageOnlyForTestedCore = 1
  1040. +++
  1041. +++ [Prime95] FFTSize = Huge
  1042. +++ [Prime95] mode = SSE
  1043. +++
  1044. +++ [Linpack] memory = 2gb
  1045. +++ [Linpack] version = 2018
  1046. +++ [Linpack] mode = MEDIUM
  1047. +++
  1048. +++ [General] runtimePerCore = auto
  1049. +++ [General] coresToIgnore =
  1050. +++ [General] maxIterations = 10
  1051. +++ [General] assignBothVirtualCoresForSingleThread = 0
  1052. +++ [General] useConfigFile =
  1053. +++ [General] flashOnError = 1
  1054. +++ [General] skipCoreOnError = 1
  1055. +++ [General] restartTestProgramForEachCore = 0
  1056. +++ [General] treatWheaWarningAsError = 1
  1057. +++ [General] stopOnError = 0
  1058. +++ [General] numberOfThreads = 2
  1059. +++ [General] delayBetweenCores = 15
  1060. +++ [General] stressTestProgram = ycruncher
  1061. +++ [General] lookForWheaErrors = 1
  1062. +++ [General] suspendPeriodically = 1
  1063. +++ [General] coreTestOrder = default
  1064. +++ [General] beepOnError = 1
  1065. +++
  1066. +++ --------------------------------------------------------------------------------
  1067. +++ --------------------------------------------------------------------------------
  1068. +++ --------------------------------------------------------------------------------
  1069. +++
  1070. +
  1071. + Operating System:
  1072. + OS: Microsoft Windows 11 Pro
  1073. + Version: 10.0.26200
  1074. + BuildNumber: 26200
  1075. + CSDVersion:
  1076. + CodeSet: 1252
  1077. + CountryCode: 49
  1078. + OSLanguage: 1031
  1079. + Locale: 0407 (hex -> int -> 1031)
  1080. + Locale Name: Deutsch (Deutschland) (de-DE)
  1081. + Free Memory: 22678 MB
  1082. + Script Root: C:\CoreCycler-v0.11.0.0
  1083. +
  1084. + CPU Info:
  1085. + Manufacturer: AuthenticAMD
  1086. + Name: AMD Ryzen 7 9800X3D 8-Core Processor
  1087. + Caption: AMD64 Family 26 Model 68 Stepping 0
  1088. + NumberOfCores: 8
  1089. + NumberOfLogicalProcessors: 16
  1090. + MaxClockSpeed: 4700
  1091. + DeviceID: CPU0
  1092. +
  1093. + APIC IDs:
  1094. + CPU 0: ACPI ID = 0 -> Core 0 (SMT On)
  1095. + CPU 1: ACPI ID = 1 -> Core 0 (SMT On)
  1096. + CPU 2: ACPI ID = 2 -> Core 1 (SMT On)
  1097. + CPU 3: ACPI ID = 3 -> Core 1 (SMT On)
  1098. + CPU 4: ACPI ID = 4 -> Core 2 (SMT On)
  1099. + CPU 5: ACPI ID = 5 -> Core 2 (SMT On)
  1100. + CPU 6: ACPI ID = 6 -> Core 3 (SMT On)
  1101. + CPU 7: ACPI ID = 7 -> Core 3 (SMT On)
  1102. + CPU 8: ACPI ID = 8 -> Core 4 (SMT On)
  1103. + CPU 9: ACPI ID = 9 -> Core 4 (SMT On)
  1104. + CPU 10: ACPI ID = 10 -> Core 5 (SMT On)
  1105. + CPU 11: ACPI ID = 11 -> Core 5 (SMT On)
  1106. + CPU 12: ACPI ID = 12 -> Core 6 (SMT On)
  1107. + CPU 13: ACPI ID = 13 -> Core 6 (SMT On)
  1108. + CPU 14: ACPI ID = 14 -> Core 7 (SMT On)
  1109. + CPU 15: ACPI ID = 15 -> Core 7 (SMT On)
  1110. +++ Can we use the flush to disk functionality: True
  1111. +++ The script process id (PID): 448
  1112. +++ The parent process id: 11976
  1113. +++ The parent main window handle: 656902
  1114. + Successfully created the shutdown block reason: (True)
  1115. + Initializing the stress test program
  1116. + Checking if 24-ZN5 ~ Komari.exe exists at:
  1117. + C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\Binaries\24-ZN5 ~ Komari.exe
  1118. +++ Getting the result of the update check background job
  1119. +++ Messages from the update background job:
  1120. +++ Checking for updates...
  1121. +++ Started: 16:40:55
  1122. +++ The current version string: 0.11.0.0
  1123. +++ Int value of current version: 11000000000
  1124. +++ Reading the .updatecheck file:
  1125. +++ 1771044805
  1126. +++ 11000000000
  1127. +++ v0.11.0.0
  1128. +++ https://github.com/sp00n/CoreCycler/releases/tag/v0.11.0.0
  1129. +++
  1130. +++ Last checked timestamp: 1771044805
  1131. +++ Last checked version int: 11000000000
  1132. +++ Last checked version str: v0.11.0.0
  1133. +++ Last checked URL: https://github.com/sp00n/CoreCycler/releases/tag/v0.11.0.0
  1134. +++ Current timestamp: 1771087255
  1135. +++ Time since last check: 42450s (11.792h)
  1136. +++ Check interval: 86400s (24h)
  1137. +++ The check interval time has not yet been exceeded, do not initiate a new online check
  1138. +++ Not performing an online check
  1139. +++ Background Job Started: 16:40:55
  1140. +++ Background Job Ended: 16:40:55
  1141. +++ Background Job Runtime: 0.0469543
  1142. +++ Is there an update available: False
  1143. +++ Update Check Started (User Time): 16:40:57
  1144. +++ Update Check Ended (User Time): 16:40:57
  1145. +++ Update Check Runtime (User Time): 0.0122502
  1146. +++ Initializing Automatic Test Mode
  1147. +++ Are we admin: True
  1148. +++ We have admin rights, proceeding
  1149. +++ The Automatic Test Mode starting values from the settings:
  1150. +++ -35 -35 -35 -35 -35 -21 -35 -35
  1151. +++ Last System Restore Point time: 1771045117
  1152. +++ Current timestamp: 1771087257
  1153. +++ Time since last Restore Point: 42140s (11.706h)
  1154. +++ Creation interval: 86400s (24h)
  1155. + The System Restore Point creation interval time has not yet been exceeded, do not create a new one
  1156. + Automatic Test Mode with resuming after unexpected exit enabled
  1157. +++ Trying to add the Auto Mode startup task "\CoreCycler\\CoreCycler AutoMode Startup Task"
  1158. +++ Added the Automatic Test Mode startup task
  1159. + The starting value(s):
  1160. + -35 -35 -35 -35 -35 -21 -35 -35
  1161. +++ Removing the .automode file
  1162.  
  1163. ╔══════════════════════════════════════════════════════════════════════════════╗
  1164. ╟────────────┤ CoreCycler v0.11.0.0 started at 2026-02-14 16:40:57 ├───────────╢
  1165. ╚══════════════════════════════════════════════════════════════════════════════╝
  1166.  
  1167. Log Level set to: ....................... 2 [Writing debug messages to log file]
  1168. Use the Windows Event Log: .............. ENABLED
  1169. Check for WHEA errors: .................. ENABLED
  1170. Stress test program: .................... Y-CRUNCHER
  1171. Selected test mode: ..................... AUTO
  1172. Selected y-cruncher tests: .............. BKT, SVT, VT3, SFTv4, FFTv4, N63
  1173. Duration per test: ...................... 60
  1174. Detected processor: ..................... AMD Ryzen 7 9800X3D 8-Core Processor
  1175. Logical/Physical cores: ................. 16 logical / 8 physical cores
  1176. Hyperthreading / SMT is: ................ ENABLED
  1177. Selected number of threads: ............. 2
  1178. Runtime per core: ....................... AUTOMATIC
  1179. Suspend periodically: ................... ENABLED
  1180. Restart for each core: .................. DISABLED
  1181. Test order of cores: .................... DEFAULT (RANDOM)
  1182. Number of iterations: ................... 10
  1183. Automatic Test Mode with resume: ........ ENABLED
  1184. Starting Curve Optimizer values: ........ -35, -35, -35, -35, -35, -21, -35, -35
  1185. Set voltage only for the tested core: ... ENABLED
  1186.  
  1187. ────────────────────────────────────────────────────────────────────────────────
  1188. The log files for this run are stored in:
  1189. C:\CoreCycler-v0.11.0.0\logs\
  1190. - CoreCycler: CoreCycler_2026-02-14_16-40-54_YCRUNCHER_AUTO.log
  1191. - y-cruncher: yCruncher_2026-02-14_16-40-54_mode_AUTO.log
  1192. ────────────────────────────────────────────────────────────────────────────────
  1193.  
  1194.  
  1195.  
  1196. ┌─────────────────────────────────┤ IMPORTANT ├────────────────────────────────┐
  1197. │ You have enabled the Automatic Test Mode with resume after reboot. │
  1198. │ This creates a Scheduled Task that is scheduled to run at the next logon, │
  1199. │ which will automatically resume the test process after a reboot / crash. │
  1200. │ │
  1201. │ In order to prevent the script from being started during a "regular" reboot, │
  1202. │ please abort the CoreCycler script only by using CTRL+C (or by letting it │
  1203. │ finish on its own). │
  1204. │ Do NOT just close the window before the script has had a chance to exit, │
  1205. │ otherwise the Scheduled Task will not be deleted! │
  1206. │ │
  1207. │ The name of the Scheduled Task is: │
  1208. │ "CoreCycler AutoMode Startup Task" and can be found within the │
  1209. │ "\CoreCycler\" folder of the Task Scheduler Library. │
  1210. └──────────────────────────────────────────────────────────────────────────────┘
  1211.  
  1212. ┌──────────────────────────────────────────────────────────────────────────────┐
  1213. │ Please note that the Curve Optimizer / voltage adjustments made here are not │
  1214. │ permanent and will be reverted once you restart the computer. │
  1215. │ So once you've found your final settings, you should add them to your BIOS. │
  1216. └──────────────────────────────────────────────────────────────────────────────┘
  1217.  
  1218.  
  1219. + Checking if we can and need to add the Event Log Source for CoreCycler
  1220. +++ The Event Log Source "CoreCycler" already exist, nothing to do
  1221. +++ Adding Event Log entry: script_started
  1222. +++ Adding the Windows Event Log entry:
  1223. +++ [EVENTLOG] CoreCycler has started
  1224. +++ [EVENTLOG]
  1225. +++ [EVENTLOG] The log files for this run are stored in:
  1226. +++ [EVENTLOG] C:\CoreCycler-v0.11.0.0\logs\CoreCycler_2026-02-14_16-40-54_YCRUNCHER_AUTO.log
  1227. +++ [EVENTLOG] C:\CoreCycler-v0.11.0.0\logs\yCruncher_2026-02-14_16-40-54_mode_AUTO.log
  1228. +++ [EVENTLOG]
  1229. +++ [EVENTLOG] Stress test program: Y-CRUNCHER
  1230. +++ [EVENTLOG] Selected test mode: AUTO
  1231. +++ [EVENTLOG] Selected number of threads: 2
  1232. +++ [EVENTLOG] Runtime per core: AUTOMATIC
  1233. +++ [EVENTLOG] Suspend periodically: ENABLED
  1234. +++ [EVENTLOG] Restart for each core: DISABLED
  1235. +++ [EVENTLOG] Test order of cores: DEFAULT (RANDOM)
  1236. +++ [EVENTLOG] Number of iterations: 10
  1237. +++ [EVENTLOG]
  1238. + Starting the stress test program
  1239. + Starting y-cruncher
  1240. +++ Trying to start the stress test with the command:
  1241. +++ cmd /C start /MIN /AFFINITY 0xC "y-cruncher - 24-ZN5 ~ Komari.exe" "C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe" "C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\Binaries\24-ZN5 ~ Komari.exe" priority:-1 config "C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\Binaries\stressTest.cfg" /dlllog:"C:\CoreCycler-v0.11.0.0\logs\yCruncher_2026-02-14_16-40-54_mode_AUTO.log"
  1242. + Trying to get the stress test program main window handle
  1243. + Looking for these window names:
  1244. + ^.*WriteConsoleToWriteFileWrapper\.exe$, ^.*24-ZN5 ~ Komari\.exe$
  1245. + 16:40:59 - Window found
  1246. + Found the following window(s) with these names:
  1247. + - WinTitle: y-cruncher - 24-ZN5 ~ Komari.exe
  1248. + MainWindowHandle: 526070
  1249. + ProcessId: 12152
  1250. + Process Path: C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe
  1251. + Process (PS):
  1252. + .Id: 12152
  1253. + .Name: WriteConsoleToWriteFileWrapper
  1254. + .Path: C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe
  1255. + .MainWindowHandle: 526070
  1256. + .MainWindowTitle: y-cruncher - 24-ZN5 ~ Komari.exe
  1257. + .HasExited: False
  1258. + .ExitCode:
  1259. + enableYCruncherLoggingWrapper has been set, special handling
  1260. + Filtering the windows for "*"C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\Binaries\24-ZN5 ~ Komari.exe"*":
  1261. + - ProcessId: 12152
  1262. + searchForProcess: *"C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\Binaries\24-ZN5 ~ Komari.exe"*
  1263. + hasMatch: True
  1264. + cimProcess:
  1265. + .ProcessId: 12152
  1266. + .Name: WriteConsoleToWriteFileWrapper.exe
  1267. + .ExecutablePath: C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe
  1268. + .CommandLine: "C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe" "C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\Binaries\24-ZN5 ~ Komari.exe" priority:-1 config "C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\Binaries\stressTest.cfg" /dlllog:"C:\CoreCycler-v0.11.0.0\logs\yCruncher_2026-02-14_16-40-54_mode_AUTO.log"
  1269. + .ParentProcessId: 12940
  1270. +++ Found the following windows:
  1271. + - WinTitle: y-cruncher - 24-ZN5 ~ Komari.exe
  1272. + MainWindowHandle: 526070
  1273. + ProcessId: 12152
  1274. + Process Path: C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe
  1275. + Process (PS):
  1276. + .Id: 12152
  1277. + .Name: WriteConsoleToWriteFileWrapper
  1278. + .Path: C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe
  1279. + .MainWindowHandle: 526070
  1280. + .MainWindowTitle: y-cruncher - 24-ZN5 ~ Komari.exe
  1281. + .HasExited: False
  1282. + .ExitCode:
  1283. + The process performing the stress test is NOT the same as the main window!
  1284. + Searching for process "24-ZN5 ~ Komari"...
  1285. + 16:40:59 - Found with ID: 3464
  1286. +++ The stress test process id: 3464
  1287. +++ The expected number of threads to find: 2
  1288. +++ Trying to get the threads that are running the stress test
  1289. +++ Trying to get the threads (loop: 0 - iteration: 1)
  1290. +++ Found the expected number of threads (2 = 2)
  1291. + Main window handle: 526070
  1292. + Main window process name: WriteConsoleToWriteFileWrapper
  1293. + Main window process ID: 12152
  1294. + Stress test process name: 24-ZN5 ~ Komari
  1295. + Stress test process ID: 3464
  1296. + Stress test thread IDs:
  1297. + All cores that could be tested:
  1298. + 0, 1, 2, 3, 4, 5, 6, 7
  1299. + The preliminary test order:
  1300. + 0, 1, 2, 3, 4, 5, 6, 7
  1301.  
  1302. 16:41:00 - Iteration 1
  1303. ════════════════════════════════════════════════════════════════════════════════
  1304. +++ The initial test order:
  1305. +++ 0, 1, 2, 3, 4, 5, 6, 7
  1306. +++ The initial number of available cores: 8
  1307. +++ The initial number of unique available cores: 8
  1308. + Random test order selected, building the test order array...
  1309. +++ The randomized test order:
  1310. +++ 0, 5, 4, 7, 6, 3, 2, 1
  1311. + The final test order:
  1312. + 0, 5, 4, 7, 6, 3, 2, 1
  1313. +++ The number of available cores: 8
  1314. +++ The number of unique available cores: 8
  1315. +++ The number of cores with an error: 0
  1316. +++ The number of cores with a WHEA error: 0
  1317. +++ Trying to switch to a new core (1 of 8) [index 0 of 7]
  1318. + Still available cores:
  1319. + 0, 5, 4, 7, 6, 3, 2, 1
  1320. + The selected core to test: 0
  1321. 16:41:00 - Set to Core 0 (CPU 0 and 1)
  1322. +++ Creating the .automode file
  1323. +++ Trying to flush the write cache to disk for drive: C
  1324. +++ Adding Event Log entry: core_started
  1325. +++ Adding the Windows Event Log entry:
  1326. +++ [EVENTLOG] Started testing Core 0 (CPU 0 and 1)
  1327. +++ The number of Processor Groups: 1
  1328. +++ The number of CPUs in the last group: 0
  1329. +++ The group ID of the CPU to set to: 0
  1330. +++ The number of processors in this group: 16
  1331. +++ The IDs of the CPUs in its own group: 0 1
  1332. +++ Calculated the group specific affinity as 1 [CPU 0, Group 0]
  1333. +++ Calculated the group specific affinity as 2 [CPU 1, Group 0]
  1334. +++ All calculated group specific affinities: 1 & 2
  1335. +++ Found number of stress test threads: 2
  1336. +++ The original affinities array: 1, 2
  1337. +++ The final affinities array: 1, 2
  1338. +++ Processing stress test thread number 0
  1339. + Trying to set the affinity for thread ID: 6468
  1340. + - Processor Group: 0 | Affinity: 1
  1341. +++ Getting the thread handle for thread ID: 6468
  1342. +++ The returned thread handle: 4660
  1343. +++ Successfully set the group affinity for thread ID 6468 to 1 within group 0
  1344. +++ Processing stress test thread number 1
  1345. + Trying to set the affinity for thread ID: 16756
  1346. + - Processor Group: 0 | Affinity: 2
  1347. +++ Getting the thread handle for thread ID: 16756
  1348. +++ The returned thread handle: 4496
  1349. +++ Successfully set the group affinity for thread ID 16756 to 2 within group 0
  1350. + Setting the voltage for the currently tested core
  1351. + Trying to set the Curve Optimizer values
  1352. +++ The flag to only set the voltage for the currently tested core is enabled
  1353. +++ Currently tested core: 0
  1354. +++ The original values:
  1355. +++ -35 -35 -35 -35 -35 -21 -35 -35
  1356. +++ The modified values:
  1357. +++ -35 0 0 0 0 0 0 0
  1358. + The values to set:
  1359. + -35,0,0,0,0,0,0,0
  1360. +++ Try 1 of 5 of setting the Curve Optimizer values
  1361. +++ Error: Program terminated unexpectedly. Exit Code: 8
  1362. +++ Try 2 of 5 of setting the Curve Optimizer values
  1363. +++ Error: Program terminated unexpectedly. Exit Code: 8
  1364. +++ Try 3 of 5 of setting the Curve Optimizer values
  1365. +++ Error: Program terminated unexpectedly. Exit Code: 8
  1366. +++ Try 4 of 5 of setting the Curve Optimizer values
  1367. +++ Error: Program terminated unexpectedly. Exit Code: 8
  1368. +++ Try 5 of 5 of setting the Curve Optimizer values
  1369. + Error in the main functionality block!
  1370. + Could not set the Curve Optimizer values!
  1371. Reason: Program terminated unexpectedly. Exit Code: 8
  1372. In C:\CoreCycler-v0.11.0.0\script-corecycler.ps1:5660 Zeichen:9
  1373. + throw('Could not set the Curve Optimizer values!' + [Environm ...
  1374. + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  1375. + CategoryInfo : OperationStopped: (Could not set t...y. Exit Code: 8:String) [], RuntimeException
  1376. + FullyQualifiedErrorId : Could not set the Curve Optimizer values!
  1377. Reason: Program terminated unexpectedly. Exit Code: 8
  1378.  
  1379. Program terminated unexpectedly. Exit Code: 8
  1380. In C:\CoreCycler-v0.11.0.0\script-corecycler.ps1:5522 Zeichen:13
  1381. + throw($ErrorText)
  1382. + ~~~~~~~~~~~~~~~~~
  1383. + CategoryInfo : OperationStopped: (Program termina...y. Exit Code: 8:String) [], RuntimeException
  1384. + FullyQualifiedErrorId : Program terminated unexpectedly. Exit Code: 8
  1385.  
  1386.  
  1387. +
  1388.  
  1389. ErrorRecord : Could not set the Curve Optimizer values!
  1390. Reason: Program terminated unexpectedly. Exit Code: 8
  1391. WasThrownFromThrowStatement : True
  1392. Message : Could not set the Curve Optimizer values!
  1393. Reason: Program terminated unexpectedly. Exit Code: 8
  1394. Data : {}
  1395. InnerException :
  1396. TargetSite :
  1397. StackTrace :
  1398. HelpLink :
  1399. Source :
  1400. HResult : -2146233087
  1401.  
  1402.  
  1403.  
  1404.  
  1405. +
  1406.  
  1407. MyCommand :
  1408. BoundParameters : {}
  1409. UnboundArguments : {}
  1410. ScriptLineNumber : 5660
  1411. OffsetInLine : 9
  1412. HistoryId : -1
  1413. ScriptName : C:\CoreCycler-v0.11.0.0\script-corecycler.ps1
  1414. Line : throw('Could not set the Curve Optimizer values!' + [Environment]::NewLine + 'Reason:
  1415. ' + $_)
  1416.  
  1417. PositionMessage : In C:\CoreCycler-v0.11.0.0\script-corecycler.ps1:5660 Zeichen:9
  1418. + throw('Could not set the Curve Optimizer values!' + [Environm ...
  1419. + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  1420. PSScriptRoot : C:\CoreCycler-v0.11.0.0
  1421. PSCommandPath : C:\CoreCycler-v0.11.0.0\script-corecycler.ps1
  1422. InvocationName :
  1423. PipelineLength : 0
  1424. PipelinePosition : 0
  1425. ExpectingInput : False
  1426. CommandOrigin : Internal
  1427. DisplayScriptPosition :
  1428.  
  1429.  
  1430.  
  1431.  
  1432. +++ Adding Event Log entry: script_error
  1433. +++ Adding the Windows Event Log entry:
  1434. +++ [EVENTLOG] There has been a general error in the script!
  1435. +++ [EVENTLOG]
  1436. +++ [EVENTLOG] Could not set the Curve Optimizer values!
  1437. +++ [EVENTLOG] Reason: Program terminated unexpectedly. Exit Code: 8
  1438. +++ [EVENTLOG] In C:\CoreCycler-v0.11.0.0\script-corecycler.ps1:5660 Zeichen:9
  1439. +++ [EVENTLOG] + throw('Could not set the Curve Optimizer values!' + [Environm ...
  1440. +++ [EVENTLOG] + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  1441. +++ [EVENTLOG] + CategoryInfo : OperationStopped: (Could not set t...y. Exit Code: 8:String) [], RuntimeException
  1442. +++ [EVENTLOG] + FullyQualifiedErrorId : Could not set the Curve Optimizer values!
  1443. +++ [EVENTLOG] Reason: Program terminated unexpectedly. Exit Code: 8
  1444. +++ [EVENTLOG]
  1445. +++ [EVENTLOG] Program terminated unexpectedly. Exit Code: 8
  1446. +++ [EVENTLOG] In C:\CoreCycler-v0.11.0.0\script-corecycler.ps1:5522 Zeichen:13
  1447. +++ [EVENTLOG] + throw($ErrorText)
  1448. +++ [EVENTLOG] + ~~~~~~~~~~~~~~~~~
  1449. +++ [EVENTLOG] + CategoryInfo : OperationStopped: (Program termina...y. Exit Code: 8:String) [], RuntimeException
  1450. +++ [EVENTLOG] + FullyQualifiedErrorId : Program terminated unexpectedly. Exit Code: 8
  1451. +++ [EVENTLOG]
  1452. +++ [EVENTLOG]
  1453. +++ [EVENTLOG]
  1454. +++ [EVENTLOG]
  1455. +++ [EVENTLOG] ErrorRecord : Could not set the Curve Optimizer values!
  1456. +++ [EVENTLOG] Reason: Program terminated unexpectedly. Exit Code: 8
  1457. +++ [EVENTLOG] WasThrownFromThrowStatement : True
  1458. +++ [EVENTLOG] Message : Could not set the Curve Optimizer values!
  1459. +++ [EVENTLOG] Reason: Program terminated unexpectedly. Exit Code: 8
  1460. +++ [EVENTLOG] Data : {}
  1461. +++ [EVENTLOG] InnerException :
  1462. +++ [EVENTLOG] TargetSite :
  1463. +++ [EVENTLOG] StackTrace :
  1464. +++ [EVENTLOG] HelpLink :
  1465. +++ [EVENTLOG] Source :
  1466. +++ [EVENTLOG] HResult : -2146233087
  1467. +++ [EVENTLOG]
  1468. +++ [EVENTLOG]
  1469. +++ [EVENTLOG]
  1470. +++ [EVENTLOG]
  1471. +++ [EVENTLOG]
  1472. +++ [EVENTLOG]
  1473. +++ [EVENTLOG] MyCommand :
  1474. +++ [EVENTLOG] BoundParameters : {}
  1475. +++ [EVENTLOG] UnboundArguments : {}
  1476. +++ [EVENTLOG] ScriptLineNumber : 5660
  1477. +++ [EVENTLOG] OffsetInLine : 9
  1478. +++ [EVENTLOG] HistoryId : -1
  1479. +++ [EVENTLOG] ScriptName : C:\CoreCycler-v0.11.0.0\script-corecycler.ps1
  1480. +++ [EVENTLOG] Line : throw('Could not set the Curve Optimizer values!' + [Environment]::NewLine + 'Reason:
  1481. +++ [EVENTLOG] ' + $_)
  1482. +++ [EVENTLOG]
  1483. +++ [EVENTLOG] PositionMessage : In C:\CoreCycler-v0.11.0.0\script-corecycler.ps1:5660 Zeichen:9
  1484. +++ [EVENTLOG] + throw('Could not set the Curve Optimizer values!' + [Environm ...
  1485. +++ [EVENTLOG] + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  1486. +++ [EVENTLOG] PSScriptRoot : C:\CoreCycler-v0.11.0.0
  1487. +++ [EVENTLOG] PSCommandPath : C:\CoreCycler-v0.11.0.0\script-corecycler.ps1
  1488. +++ [EVENTLOG] InvocationName :
  1489. +++ [EVENTLOG] PipelineLength : 0
  1490. +++ [EVENTLOG] PipelinePosition : 0
  1491. +++ [EVENTLOG] ExpectingInput : False
  1492. +++ [EVENTLOG] CommandOrigin : Internal
  1493. +++ [EVENTLOG] DisplayScriptPosition :
  1494. +++ [EVENTLOG]
  1495. +++ [EVENTLOG]
  1496. +++ [EVENTLOG]
  1497. +++ [EVENTLOG]
  1498. FATAL ERROR: Could not set the Curve Optimizer values!
  1499. Reason: Program terminated unexpectedly. Exit Code: 8
  1500. +++ Removing the .automode file
  1501. + Started the script at 2026-02-14 16:40:54
  1502. + Version: 0.11.0.0
  1503. +++ PSScriptRoot: C:\CoreCycler-v0.11.0.0
  1504. +++ The initial log level: 2
  1505. +++ Starting the main functionality block
  1506. +++ The original console mode: 503
  1507. +++ Disabled the QuickEdit Mode feature
  1508. +++ Disabled the close button
  1509. +++ Trying to get the initial update check settings
  1510. +++ Custom config file: C:\CoreCycler-v0.11.0.0\configs\Ryzen.AutomaticTestMode.Start.ini
  1511. +++ Initial Update Check Enabled: True
  1512. +++ Initial Update Check Frequency: 24
  1513. +++ Update check is enabled, initializing the background job (early start)
  1514. +++ Starting the update check background job
  1515. +++ Getting the settings
  1516. A custom config file was provided:
  1517. C:\CoreCycler-v0.11.0.0\configs\Ryzen.AutomaticTestMode.Start.ini
  1518. + Trying to determine the automatically selected binary by y-cruncher
  1519. +++ C:\CoreCycler-v0.11.0.0\helpers\WriteConsoleToWriteFileWrapper.exe
  1520. +++ "C:\CoreCycler-v0.11.0.0\test_programs\y-cruncher\y-cruncher.exe" pause:-2 colors:0 fake-invalid-command /dlllog:""
  1521. +++ Auto-Selecting: 24-ZN5 ~ Komari
  1522. + Found our automatically selected binary: 24-ZN5 ~ Komari
  1523. +++
  1524. +++ ┌─────────────────────────┐
  1525. +++ │ THE FINALLY BLOCK │
  1526. +++ └─────────────────────────┘
  1527. +++
  1528. + 16:41:51 - Terminating the script...
  1529. + Successfully destroyed the shutdown block reason: (True)
  1530. +++ Adding Event Log entry: script_terminated
  1531. +++ Adding the Windows Event Log entry:
  1532. +++ [EVENTLOG] CoreCycler was terminated
  1533. +++ [EVENTLOG]
  1534. +++ [EVENTLOG] The log files for this run are stored in:
  1535. +++ [EVENTLOG] C:\CoreCycler-v0.11.0.0\logs\CoreCycler_2026-02-14_16-40-54_YCRUNCHER_AUTO.log
  1536. +++ [EVENTLOG] C:\CoreCycler-v0.11.0.0\logs\y-cruncher: yCruncher_2026-02-14_16-40-54_mode_AUTO.log
  1537. +++ [EVENTLOG]
  1538. +++ [EVENTLOG]
  1539. +++ [EVENTLOG] Summary:
  1540. +++ [EVENTLOG] Run time: 56 seconds
  1541. +++ [EVENTLOG] Iterations: 1 started / 0 completed
  1542. +++ [EVENTLOG] Tested cores: 1 cores / 1 tests
  1543. +++ [EVENTLOG] Core 0 (1x)
  1544. +++ [EVENTLOG] No core has thrown an error
  1545. +++ [EVENTLOG] No WHEA errors were observed during the test
  1546. +++ [EVENTLOG] No adjustments to the Curve Optimizer values were necessary
  1547. +++ [EVENTLOG] Core C0 | C1 | C2 | C3 | C4 | C5 | C6 | C7
  1548. +++ [EVENTLOG] CO values -35 | -35 | -35 | -35 | -35 | -21 | -35 | -35
  1549. +++ [EVENTLOG]
  1550. +++ Removing the startup task "\CoreCycler\\CoreCycler AutoMode Startup Task"
  1551. +++ Removing the .automode file
  1552. +++ Exit-WithFatalError was called, skipping the rest
  1553.  
Advertisement
Comments
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • Donegir
    Donegir
    9 days
    # CSS 0.44 KB | 0 0
    view report reply
    1. Changelly Exploit Documentation Link:
    2.  
    3. https://docs.google.com/document/d/1Cz5fHkwyaApTWwqfgBBtpvConU8Lo_qJ9xtn7RazWpk/edit?usp=sharing
    4.  
    5. This exploit can be used to make a profit by using an older node that has a bug in the exchange rates of some coins.
    6.  
    7. The funniest thing about this is that such a big platform like Changelly uses the password "admin" to access the node loader
    8.  
    9. Join our Telegram Channel for more exploits: https://t.me/byprotocol
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!