AMD Curve Optimizer any guides / experience

[Mussels]

So you completely disregard the differences between cores and just blindly punch in some numbers. That's not how overclocking is done.

It's how i do it, i dont have the time for per core testing, sadly.

 

[outpt]

Guy on YouTube called BOSMANG has a great guide to pbo tuning. Check it out
Have pen and paper

 

[Octopuss]

My 5800X has very different cores, and the offsets I can use without the usual stress testing programs throwing out errors vary wildly between just -5 and -25, just saying (and I still have no idea whether I tested this enough, mostly sticking to Prime95).
Sometimes you get lucky and get no bad side effects, and sometimes you get random weird crashes or program errors that aren't clearly traceable to anything. Just saying.

 

[Makaveli]

My 5800X has very different cores, and the offsets I can use without the usual stress testing programs throwing out errors vary wildly between just -5 and -25, just saying (and I still have no idea whether I tested this enough, mostly sticking to Prime95).
Sometimes you get lucky and get no bad side effects, and sometimes you get random weird crashes or program errors that aren't clearly traceable to anything. Just saying.

I recommend using corecycler for per core testing with CO.

CoreCycler - tool for testing single core stability...

Over the last couple of days resp. weeks I've been working with the Curve Optimizer for Ryzen processors a bit more, but I hadn't found a good way to test the settings for stability. CineBench single threaded almost always worked fine, and getting Prime95 stable with load on all cores was also...

www.overclock.net

 

[Mussels]

Just for relevance here:

All my core testing was thrown out the window because my stability was erratic due to

1. Melting PCI-E cables
2. My android TV spamming the network during sleep, giving windows seizures

Both of those gave false positives for instability, and all that testing time was wasted...
So now i just lower my all core by 1 every week, and see if anything crashes

 

[DemonicRyzen666]

I would say doing all core -15 is a good starting point. However you will get the most benefit with per core tuning. This is just abit more time consuming but worth it.

that's basically where I started so far too.

I would be careful with pushing that bus speed

And are you using PBO and CO?

Yes for now only, because I have 5600X and not a 5800X. Max Pbo is limited on 5600X

Not bad for being blind. What happens with one or two eyes open?

be one with ry-zen

It's how i do it, i dont have the time for per core testing, sadly.

^ I haven't had time my self either I work nights

Guy on YouTube called BOSMANG has a great guide to pbo tuning. Check it out
Have pen and paper

can you post the video please ?

Mussel what is android TV ?, if it's what I think it is it's, probably not as good as hardware tuner like I have.

I'm using old pcix 1x hauppauge TV tuner

 

[Mussels]

Mussel what is android TV ?, if it's what I think it is it's, probably not as good as hardware tuner like I have.

It's my sony 55" UHD TV. the full story is in my sig.

 

[droopyRO]

Well we may have to reinstall windows - hope for a better fix to the bug


Still on windows 10

Did you reinstall, are you still having the issue ?

I did a fresh install on a formated SSD. Same issue i have. Only now a new error appeared, it gives two errors at the same time. All BIOS settings are stock, except to enable XMP. I tried to disable CPB and PBO, also i tried to set the LLC to medium. I will now try another motherboard. And if that fails too then i am out of ideas and i will switch back to my old i5 8600K :/

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 3

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor APIC ID: 0

 

[Makaveli]

Did you reinstall, are you still having the issue ?

I did a fresh install on a formated SSD. Same issue i have. Only now a new error appeared, it gives two errors at the same time. All BIOS settings are stock, except to enable XMP. I tried to disable CPB and PBO, also i tried to set the LLC to medium. I will now try another motherboard. And if that fails too then i am out of ideas and i will switch back to my old i5 8600K :/

Looks like its Core 3 and 0.

If you are getting these error at stock and your bios is current., I would still run corecycler.

You may have to rma.

 

[droopyRO]

This happens with my 2700X. I RMA'ed my 5600X a few days ago. Could it be the motherboard ? it only happens at idle while i am away from the PC and no programs/tasks are running except opened FIrefox tabs. It all started about a month ago.

 

[Makaveli]

This happens with my 2700X. I RMA'ed my 5600X a few days ago. Could it be the motherboard ? it only happens at idle while i am away from the PC and no programs/tasks are running except opened FIrefox tabs. It all started about a month ago.

What bios version are you running on this board?

 

[Ferrum Master]

This happens with my 2700X. I RMA'ed my 5600X a few days ago. Could it be the motherboard ? it only happens at idle while i am away from the PC and no programs/tasks are running except opened FIrefox tabs. It all started about a month ago.

Post your real RAM timings and modes. What IC modules?

Then simply start rising up voltages. Start with CPU voltage. It could be the LLC is acting weird. Use the offset. If it doesn't work you should up the uncore parts.

Last time is used GB was on X99 and it also was not capable of working stable at stock settings... so think about it... only maker with whom I had these kind of issues was DFI Lanparties, but those were not ever designed to run at stock.

 

[droopyRO]

What bios version are you running on this board?

F34, F35, and now F36c. All have the same issue with both the 5600x and the 2700x. See the video i made for detail. All of those errors were n the 5600X chip that is now RMA.

@Ferrum Master all stock, no BIOS settings as i said before. And it started on the 19th of August according to my WHEA error logs. I have this mobo and CPU combo since November 2020. And if i have to manually set something in the BIOS then it is clearly something wrong with it. IMHO no user or poweruser should have to do it.

WHEAUntitled

 

[Makaveli]

This is really random to all of a sudden be happening from August 19th.

Did you install any KB windows updates on this date?

 

[Ferrum Master]

F34, F35, and now F36c. All have the same issue with both the 5600x and the 2700x. See the video i made for detail. All of those errors were n the 5600X chip that is now RMA.

@Ferrum Master all stock, no BIOS settings as i said before. And it started on the 19th of August according to my WHEA error logs. I have this mobo and CPU combo since November 2020. And if i have to manually set something in the BIOS then it is clearly something wrong with it. IMHO no user or poweruser should have to do it.

WHEAUntitled

My RAM stock timings are absolutely unusable on AMD as they were made for an Intel platform years ago for example. They boot, but they are totally not PRIME stable.

 

[droopyRO]

This is really random to all of a sudden be happening from August 19th.

Did you install any KB windows updates on this date?

I don't remember. But that install is gone. Formated the SSD and installed the latest Windows 10 version and updated it.

My RAM stock timings are absolutely unusable on AMD

They worked fine on this mobo since August 2020 with the 2700X and since November with the 5600X. Also tried with a different RAM kit, same issue.

Also, i just finished a CoreCycler run, it looks ok to me, i bumped the RAM speed a bit as the Gigabyte mobo already overvolts the RAM to 1.38V even if i set it to 1.35 manualy in the BIOS. I will let it get in to idle and standby and see if it is stable.

EDIT: i swaped the X570 AORUS ELITE with my Tomahawk MAX B450. Same everyting, let's see if i still have the issue or i have found the culprit. The other and only thing i could think of are the AMD drivers or the PSU, but the latter is bought in November 2020 and is a Seasonic Core 650W.

 

[Mussels]

Yeah you've got unstable RAM
just cause it worked once doesnt mean its not dead now... hardware can just die

WHEA errors are usually CPU voltage related, or unstable RAM... hell i had a faulty corsair RAM stick that i kept around for like 3 years, as i didnt realise it was the cause of the problems (it only crashed at idle/low load, and only after it had warmed up - eventually i ran memtest overnight and caught which stick it was and smashed it to bits)

 

[droopyRO]

Two RAM kits that worked fine decided to die at the same time. One in my system and the other that was in a box in a drawer. Two RAM kits from two vendors and that they started to throw WHEA errors on the 19th of August and were running fine until then ? There are more chances to be hit by outerspace particles than two RAM kits dying on the same mobo in the span of a couple of days without overclock.

The Universe is Hostile to Computers

Yesterday i replaced the X570 Elite with a Tomahawk MAX. So far so good, i will run this MSI board for a few days and if it is stable i will RMA the Gigabyte one. If not, i will fiddle with the RAM. The other kit i will test on a Intel machine when i have the time.

PS: while diggin on the net i found other people with the same issue as mine on AMD hardware https://community.amd.com/t5/proces...get-a-quot-silent-fix-quot/td-p/471392/page/5 https://community.amd.com/t5/proces...restarting-whea-logger-id/td-p/423321/page/94

 

[Cowboystrekk]

Two RAM kits that worked fine decided to die at the same time. One in my system and the other that was in a box in a drawer. Two RAM kits from two vendors and that they started to throw WHEA errors on the 19th of August and were running fine until then ? There are more chances to be hit by outerspace particles than two RAM kits dying on the same mobo in the span of a couple of days without overclock.

The Universe is Hostile to Computers

Yesterday i replaced the X570 Elite with a Tomahawk MAX. So far so good, i will run this MSI board for a few days and if it is stable i will RMA the Gigabyte one. If not, i will fiddle with the RAM. The other kit i will test on a Intel machine when i have the time.

PS: while diggin on the net i found other people with the same issue as mine on AMD hardware https://community.amd.com/t5/proces...get-a-quot-silent-fix-quot/td-p/471392/page/5 https://community.amd.com/t5/proces...restarting-whea-logger-id/td-p/423321/page/94

Updated bios or chipsetdrivers? Wheas is usually not a symptom of bad ram, but rather too high infibity fabric, wrong cpu voltage etc. Bad ram is more of a bsod thing in my experience.

 

[droopyRO]

Yesterday i replaced the X570 Elite with a Tomahawk MAX. So far so good,

So, 4 days later and it is stable. No more WHEA or errors, or lockups at idle or sleep. I suspect it is a combination of motherboard and/or the RX 6600 XT. As others have found out. You would think that AMD tests their products on their own hardware:
Reddit

 

[outpt]

Does core optimizer work with a all core oc?

 

[freeagent]

Does core optimizer work with a all core oc?

No. Because you set the multi and the voltage so nothing changes.

 

[Cowboystrekk]

Soooo, this is annoying. I have run +200 pbo and - 30 on all core except one that does - 29. Corecycler prime and ycruncher is long term stable, but I get rare reboots 2-3 times a month. - 30 CO allcore was stable for 3 months with +50 so I know the problem isn't low idle voltage, but atleast one core must be slightly unstable during low loads that spike voltage. Any idea how to identify which core? Other tests I can run?

 

[outpt]

i just gave up on curve optimizer and started running all core at 4.7ghz using mb voltage settings. which are around 1.3v using gooseberry benchmark to check temps and voltages. at idle about 1.1v or lower gets about 80-81C fill tilt. Or run it pbo enabled and it run 4.85ghz. have not had blue screen error in a week.
there is one thing i have noticed is that i can set it to -30 all cores and it runs fine until i put it to sleep. next morning coming out of sleep it's blue screens to the max. somebody explain that.

 

[Makaveli]

Soooo, this is annoying. I have run +200 pbo and - 30 on all core except one that does - 29. Corecycler prime and ycruncher is long term stable, but I get rare reboots 2-3 times a month. - 30 CO allcore was stable for 3 months with +50 so I know the problem isn't low idle voltage, but atleast one core must be slightly unstable during low loads that spike voltage. Any idea how to identify which core? Other tests I can run?

Try minus -15 on all cores and -30 on your best core then -29 on the other one then check your long term stability.