I have a Ryzen 7 5800x and a Aorus Gigabyte B450m pro wifi motherboard, Windows 11. I recently upgraded to the new CPU and have been using it for a couple weeks. I decided to use Ryzen Master to use to auto optimize for the CPU. It took about an hour and I think it blue screened at one point. But when it was complete I hit apply and it went to rest the PC. When it did, the Aorus screen comes up like it it's booting and the blue screens and says it has to restart. When it restarts, it says its going to repair but then crashes again. It just starts doing this over and over. I tried putting the bios into safe mode but that didn't do anything. Please someone help. I'm fairly new to this stuff.

Hi all,

I purchased a 5950x for my MSI x570 Gaming Plus and it's been working excellently. I wanted to try my luck at overclocking and saw that there was an application to do this, the Ryzen Master. I spent the day yesterday attempting to get this to work and when doing the Optimizer Curve for the CPU Windows would boot up but at the login screen at about 3 seconds in it would hard reboot.

Edit: Please note that I have tried both Default and Auto OC Control Mode and both result in hard reboots at login.

I am interested in any suggestions on how to address this. Thank you for any assistance.

Anybody else having issues with the auto curve optimizer?

I've gotten to 97% on the last core twice and then it'll BSOD and I have to start again.

Since this happened twice I've updated my bios to v18 which is stable from the MSI MAG X570 TOMAHAWK page.

Currently using an 5900x, x570 mag TOMAHAWK mobo, Corsair 3600 dominator platinum ram.

Had pbo and xmp enabled during the previous tests. Will try now with a fresh bios.

Anybody else having similar issues?

Title basically describes most of my problem.

System:

• Ryzen 9 5900X

• RTX 2070 Super (oc'd)

• x570 elite

• G.skill Trident Z RGB 4x8GB, DDR4, 3200Mhz, 14CL

• Seasonic Focus PX-750

• Kraken x62

I ran the Curve Optimizer tool in Ryzen Master per core. It took ~17hours aproximately and the following results came out:

After I did this, I started having microstutter issues in various games (CS2, Aimlabs) and I haven't been able to get rid of this issue ever since.

Naturally reverted the settings and didn't do anything. Tried a CMOS reset as well and also no effect.

So at this point I'm wondering if the Curve Optimizer tool in Ryzen Master can have caused permanent damage to my CPU or any of my other components that may be causing this microstutter? Last thing left to try is that I do a full clean windows install but after that I'm not sure what else I can do other than starting to replace parts.

So in the amd ryzen master app, i tried the optimization curve on all cores. After waitingnfor an hour for it to be fully optimized, i applied it. My pc restarted and then everytime i got into my home windows screen it will just restart again and then the blue screen came out in which to choose F1, F8 or Esc. Tried everything on that blue screen but nothing works. What should i do now? I cant even open up ryzen master to disable the optimization curve. CPU: Ryzen 7 5800 X RAM: 32 GB DDR4 3200MHZ GPU: RX 9060XT 8GB PSU: 600W MOTHERBOARD: AORUS X570I WIFI

I have a ryzen 5600 + rx 6600 + silverstone ET750 gold PSU + ID cooling se-242-xts cooler. I turned on PBO in the BIOS and auto OC in ryzen master, everything works fine and its stable in prime95. But if i set curve optimizer mode to "all cores", the system becomes unstable, fails prime95 tests and randomly restarts by itself.

This happens even if i spend 32 minutes letting the utility test the settings (which it then claims is fine, but results in an unstable system).

Does anyone know why this happens or how to fix it? Not sure what this curve optimizer mode is exactly. I assume it means how the CPU speed ramps up in relation to voltage?

Theres no overheating, even during prime95 stress tests the highest temp i saw so far was 67 degrees celsius, voltage with curve optimizer mode averaged 1.065v, without curve optimizer, it averages higher, about 1.085v.

I got sudden restart issues happening while gaming just like the one in the video and im trying to find the problem so i just need to know if this is normal or not while applying curve optimizer. Note that curve optimizer is not applied after this restart and kernel event 41 and whea 18 processor core erros shows in event viewer, which also exist when it suddenly crashes during gaming or any cpu intensive task. Also this is the only way for the reboot to happen on purpose as i can play for days or even a week without a single crash. This is a newly build pc and the problems started right away. Tried updating bios and chipset and already replaced Psu and mobo

CPU-AMD-RYZEN 5 5600 Tray With fan XFX SPEEDSTER SWFT 210 AMD RADEON™ RX 6650 XT GIGABYTE B450 DS3H V2 Team T-Force Delta RGB DDR4 8GB 3200MHz CL16 2 x 8 Klevv Cras C710 1TB M.2 Pcie 3x4 Nvme 3D NAND (SSD) XIGMATEK ANUBIS PRO MESH TOWER Case 4FANS Seasonic CORE-GM-650 Partial modular PC Power Supply 80PLUS Gold 650 Watt XIGMATEK Windpower WP964 RGB Black 90mm CPU AIR Cooler

unite violet governor act memory person north engine rainstorm wrench

This post was mass deleted and anonymized with Redact

I used Ryzen Master to figure out a per-core optimized curve. When I applied the suggested curve in the BIOS I noticed games would crash (CoD Cold War, FH5, Halo Infinite...) saying there was an issue with the GPU.

The CoD Cold War devs offered their time to take a deep dive into the issue... They told me my CPU OC was the issue! I turned off the curve in the BIOS and then BOOM, smooth sailing.

I've heard folks having similar issues. I'm interested to understand why this is the case. Does the scheduling of tasks start getting messy with an optimized curve?

P.S.: I would like to add that I'm very grateful for devs who take the time to help regular folks like me. I can understand how tricky that job may be, and those extra minutes make the world of difference. Thank you!

This is free performance that I hadn’t taken advantage of in the year I’ve owned my Ryzen 5600, so I’m writing to this to advocate that nobody else wait as long as I did.

This is my guide. There are many like it, but this one is mine😁.

Curve Optimization is very easy - the testing being automated - and poses no danger whatsoever to one’s hardware; the worst you can expect is a Windows bluescreen, and that is no more deleterious than stalling a car. The only drawback is that you will need to have your computer running tests that render it useless – if you are prepared to leave it running overnight and/or while at work, though, this is not a problem – and it can take a long time.

1. Software (all free)

You will need:

• AMD Ryzen Master (latest version)

• HWINFO (to get the preferred core order and, optionally, compare before and after temps/power)

• Core Cycler (which contains PBO2Tuner – set and test curve optimizer values)

• CPU and gaming benchmarks (compare before and after performance, test for real-world stability)

2. Preliminaries

• Open HWINFO and uncheck both boxes, then navigate to “Central Processor(s)”-> <your CPU>. Make a note of the sequence after “Core Performance Order” – this is the order in which we will be testing them with Core Cycler, but you must SUBTRACT 1 from each value; Core Cycler starts numbering cores at 0, not 1.

• Open AMD Ryzen Master, select Advanced View, click Curve Optimizer, Per Core, then click Start Optimizing. Ryzen Master will then enter an automated procedure to generate its best estimate of what your CPU is capable of. Plan to be away from your computer for at least an hour while this is going on; when you come back, make a note of the values it generates, but DO NOT APPLY them - just close the program. Note that the “subtract 1” rule applies to Ryzen Master, as with HWINFO.

• Open the Core Cycler config file and make the following changes:

“stressTestProgram = YCRUNCHER”

“coreTestOrder = <your order from earlier>” - remember to subtract one from each

“numberOfThreads = 2”

“mode = 20-ZN3 ~ Yuzuki” in the ycruncher section, halfway down the page.

Some rationale:

The preferred core order is from WORST to BEST under-volter, and thus MOST to LEAST likely to fail – this is because the more preferred a core is, the more efficiently it is already running, and so the lower the voltage floor is. This makes testing faster because the most unstable cores will fail first, and dropped cores are left out of subsequent intra-session iterations by Core Cycler. Also, the ycruncher Yuzuki test is considered to be the most difficult one to pass, so we might as well start with it; you can – and should – run others afterwards.

• Open Windows Event Viewer, right-click on Custom Views, and click Create Custom View. Check “Warning”, and “Error”, then “By source”, and check “WHEA Error” in event sources. Name the view something meaningful, then exit the Event Viewer. This is just in case Windows ever BSODs – not likely, but possible – and we will need to know which core failed.

3. Testing – Round One

Create a spreadsheet like the one below – we will be keeping track of passes and fails.

When you’re ready to leave the computer alone, close all programs, open PBO2Tuner and key in the values given by Ryzen Master earlier, then click Apply, and minimize the program. These values are applied as though they were typed into the BIOS, and persist until they are changed, or the computer is restarted.

Run “Run CoreCycler” - the testing will begin, and will run until you stop it, or until every core has thrown an error.

~TESTING HAPPENS – LEAVE FOR AS LONG AS POSSIBLE, PREFERABLY 6+ HOURS~

When you come back to the computer, if Core Cycler is still running, stop it with Ctrl-C, and see which core/s, if any, have failed; Ryzen Master’s supplied values are usually rather optimistic, so you should expect some errors, which show up in bright purple text. (If you accidentally close the window, the log file contains all the same information, but is more annoying to parse.)

Scroll around the window and see how long it took for the core/s in question to error out – a fast error is anything under 10 mins, IMO, and a slow error is anything over. Any core with a fast error will be having its CO value increased by 2, while slows will have theirs increased by 1; if any cores don’t error (in which case, Core Cycler will still be running on those cores when you come to check), add them to the

“coresToIgnore =”

– no point hitting these cores again until Round 2.

(If the machine has reset, go into Event Viewer and look in your custom view – under Error, there will be an entry called “Processor APIC ID”, with a number, the number corresponding to a thread. Core 0 will run threads 0 and 1, Core 1, threads 2 and 3, and so on; whichever core was running the failed thread, increase its CO by 3 or 4 – that core was not even close to stable!)

Update your spreadsheet as shown below, with the adjusted CO values, and save it – when you are ready for your next test session, put these new values into PBO2Tuner before you start.

Keep repeating the above until all cores pass a session of this “all cores at once” testing.

and so on; my last all-core session, after shedding cores as they passed, looked like this:

4. Testing – Round 2

The next step is to extend the testing for each core. You can jump right to hitting one core for 6+ hours (as I did), or divide the cores into two groups (“front half, back half”, from the order earlier, is best), and test them one half at a time, Ignoring the cores in the other half. This will double the amount of time each core is under stress, and might generate errors that didn’t appear before, but you will be much closer to the true stable value thanks to the previous testing.

Change the core testing order to match the results from Round One - they might not be the same as the HWINFO values; for example, HWINFO gave me 2 ,1 ,0, 4, 3, 5, but ordering by the results of my Round One, worst to best, would be 0, 1, 4, 5, 3, 2.

Do the “increment on error” procedure from before, until the front half all pass, and then do the same for the rear half.

5. Testing – Round 3-4-5

If you like, you can split the cores again, and repeat, getting all groups stable. Keep splitting until you get to the point where only one core is being tested at a time:

• Ryzen 3 – four, two twos, four ones.

• Ryzen 5 – six, two threes (or three twos), six ones.

• Ryzen 7 – eight, two fours, four twos, eight ones.

• Ryzen 9 – 5900 = twelve, two sixes, then each six as per Ryzen 5; 5950 = sixteen, two eights, then each eight as Ryzen 7.

Yes, this CAN be a lot of testing, but Curve Optimizer CPUs are most likely to crash at the highest boosts (= lowest loads), so sheer duration is the only way to generate any confidence in stability. Thankfully, Ryzen Master gets us most of the way there; the values it gives are usually stable enough at least for idle Windows tasks.

My last round of Yuzuki was a 40-iteration test on each core individually - 5-6 hours per core:

From Ryzen Master's -28, -30, -30, -30, -30, -30, I ended up at -20, -21, -29, -26, -22, -26.

6. Further Testing

It is advisable to use the PRIME95 HUGE on each core in turn, as this is another very low load situation that lets the CPU boost to its maximum; make these changes in the Core Cycler config file. Feel free to try to some other presets as well – no such thing as too much testing. Read what other users found to be their “magic bullet” test settings, and try those out.

The best test, though, is, as always, to use the thing - browse, game, edit, do whatever you normally do.

7. Finalizing

When you’re happy that everything tests stably, go into the BIOS and enter your final values in the Curve Optimizer menu – this will save you having to use PBOTuner2 every time you boot up.

If your computer ever crashes (not impossible) use the Event Viewer to identify the rogue core, and increase its CO value in the BIOS.