Corecycler

Skip to content. You signed in with another tab or window, corecycler. Reload to refresh your session.

Once overclocked, your system stability is at risk. It's not necessarily that something bad will happen to the components themselves, but more that you'll have to suffer through crashes, restarts, and all manner of errant behavior if the component doesn't jibe with its new clocks and voltages. Though the PBO algorithms in AMD Ryzen processors do well to optimize performance, modifying voltage and clock values to take things further is possible. CoreCycler is a stability test script that you can use to ascertain the stability of your AMD Ryzen processor. Once undevolted and overclocked, AMD Ryzen processors oftentimes exhibit some very curious behavior. In short, it's not uncommon for users to enjoy stability under load and stress-testing, but have their system falter during idle and generally lower load work.

Corecycler

Alpha version. Added a wrapper. The y-Cruncher output is now saved as a log file and checked for errors. Added a new assignBothVirtualCoresForSingleThread setting that allows you assign both virtual logical cores to a single stress thread. This way the Windows Scheduler should bounce back and forth the load between the both virtual cores, which may open a new possibility to test for load change instabilities. Added support for Prime95 versions Also updated the included Prime95 version to For more recent Prime95 versions the FFT size where an error happened is provided in the log file it wasn't before , so this information is now used if available. No more guesstimating. Skip to content. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. You switched accounts on another tab or window.

Otherwise you cannot really be sure if an error happened due to an unstable CPU or corecycler unstable memory overclock, corecycler.

Log in. Sign up. JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. CineBench single threaded almost always worked fine, and getting Prime95 stable with load on all cores was also relatively quick. Waiting for crashes while idling or while playing a game wasn't so appealing either, and on Reddit someone even suggested using the Windows Repair as some kind of stability test So this sparked the idea for this tool.

Log in. Sign up. JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. CineBench single threaded almost always worked fine, and getting Prime95 stable with load on all cores was also relatively quick. Waiting for crashes while idling or while playing a game wasn't so appealing either, and on Reddit someone even suggested using the Windows Repair as some kind of stability test

Corecycler

Alpha version. Added a wrapper. The y-Cruncher output is now saved as a log file and checked for errors. Added a new assignBothVirtualCoresForSingleThread setting that allows you assign both virtual logical cores to a single stress thread. This way the Windows Scheduler should bounce back and forth the load between the both virtual cores, which may open a new possibility to test for load change instabilities.

Sphere maker minecraft

Thank you! Maybe you should add a reclaimer "for high risk users only" on your statments Register a new account. You signed out in another tab or window. Sign in here. Weder Mr. Audioboxer Replies. A: Short answer: all of them. If the default settings are not doing anything for you, then you may perhaps want to modify the config. It seems like we'd really need AMD to provide us a way to "lock" a core at an arbitrary point on it's boost curve so we could test the whole range. Previous Next. Share More sharing options After you're sure that both overclocks are stable on their own, you can combine them and check for instabilities again. Sign In Sign Up.

Once overclocked, your system stability is at risk. It's not necessarily that something bad will happen to the components themselves, but more that you'll have to suffer through crashes, restarts, and all manner of errant behavior if the component doesn't jibe with its new clocks and voltages.

Latest commit History Commits. A: The config. Two idiots with the same idea. It does not worth it. Although for Aida64 you'll need to manually download and extract the Portable Engineer version due to its license I don't think I can include it. I was thinking my CPU was stable but it seems it's actually not! And it's even a PowerShell script as well. I can't squeeze any more MHz with the PBO Boost Offset not even 25Mhz without having to drop all curve values that leads to multi core performance loss. A: Very likely your Curve Optimizer setting is unstable. Again: I understand your approach and it's absolutely ok to play around these limits to find whatever you like, but you cannot claim this as a general rule. Thank you! With that I hope to squeeze out some more MHz because the hot spots are distributed more evenly, which could lead to slightly higher boost clock as well. Apparently Aida64 doesn't like running the stress test on the first thread of Core 0.