Soldato
- Joined
- 19 May 2005
- Posts
- 6,892
Mine wasn't stable, as soon as I started folding it crashed.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
You just configure the voltage you want. Also the 1250 and 1175 are just references you can key in whatever voltage you like up to 1375, I went for 1350 for mine as all I usually do is game.The bug is fixed in Beta 3 that caused the Reference 6000+ mhz issue
Unfortunately rating my 3600 as Platinum was also a bug because its just run Diagnostic and now its Bronze!
Recommended values for OC are -
4GHZ @ 1250mV
Undervolt -
3850mhz at 1175mV
How do you pick which one you want OC or UV before hitting start and is it even worth it!?
You just configure the voltage you want. Also the 1250 and 1175 are just references you can key in whatever voltage you like up to 1375, I went for 1350 for mine as all I usually do is game.
You just set the min and max clocks and your preferred voltage and the program will push the clocks up in increments while testing for stability till it finds the maximum stable clocks for the voltage you entered.Thanks but I'll admit I'm completely lost, if I up the voltage will the clocks increase automatically or do I need to do that to? If that's the case I might as well just do it in the BIOS manually
I think I'm missing something obvious but won't have time to tinker this weekend so will have to leave it until next now
Yeah, seen a lot of peeps with Aorus boards and 3900X's that are having issues with hard resets.
The core tags error I think is normally to do with needing to delete your System event log.
I'm guessing it is reading EventID 55 from there and using those to populate the scores next to each core.
If the numbers to the right of the frequency on each core are showing 100 (or possibly 0 or not there) then you'll need to clear the system event log and reboot.
If you check that log after reboot and look for EvenID 55 from Microsoft-Windows-Kernel-Processor-Power you should see one for each logical thread.
The line/value I think the tool uses is...
"Maximum performance percentage: 160"
As the numbers match up. Mine go from 122 to 160.
I guess these are passed to the o/s from the CPU/BIOS so windows can do it's scheduling to preferred cores etc but no idea when the are generated or if they are hard coded at the factory?
It looks like CTR gets the wrong values if the o/s was previously booted on different hardware, my guess it is it just reads the event log from oldest entry forward, when it should probably do it from newest backwards, possibly using system uptime - current time to narrow the search.
@Brizzles What did you change to get it to stop hard crashing during the tuning? I have a very similar setup. ThanksNo success here with 3900X / Giga Aorus Elite X570 / F30 Bios
1 diagnosis shows a Platinum chip, then another changes to a Silver chip.
CB20 score gives 7050 as the baseline CTR test ( i run a slight undervolt and get 7300 normally )
Hard shutdown during 'tuning'
Will wait for the software to mature before trying again.
Just tried Beta 3. Appears a bit more aggressive on the clocks despite a note saying the LLC warnings would be less frequent I had my first reboot with ASUS - LLC3.
Went back to LLC4 which is a bit more aggressive and ran through the process. Previously the LLC 4 gave a more balanced core OC but this time it kept upping the CCX clocks until each block failed. Ended up with the improvements below.
CCX1 4275 - 4400
CCX2 4275 - 4400
CCX3 4275 - 4300
CCX4 4250 - 4250 (Lame!)
1.256 vcore
CB20 score went from 7553 - 7665 on my 3900X (silver)
Now running some game benchmark loops to verify the stability.
On Beta 1 it spammed the low LLC even though I had this set to High in the Asus BIOS, maybe it was just not working correctly? My BIOS doesnt have 4 or 3 so I am guessing 4 would be max and 3 would be high?
@chaosophy I have a similar setup (Ryzen 3900xt, Aorus Elite x570 w/ F30 bios, stable 32gb Crucial Ballistix) and have the same experience with CTR. I've tried various LLC settings and all 3 Beta versions of CTR, and followed all the instructions. The Diagnostic goes smoothly, says I have a Gold sample, but then it always fails on Step 3 after hitting Start.
So LLC is to counter voltage drop under load so high should be more voltage and in newer Asus BIOSs the higher numbers mean more voltage (1 to 5). I believe there other options to mess with this but I've not played with them. LLC 4 was the setting that stopped the LLC warnings and reduce droop to 1.5% which was half that of the auto setting which seemed good enough. Too high a setting can overshoot and use excessive power which is as bad as too much droop causing random crashes.
If you can get the diagnostics mode running with the BIOS set to default it should estimate the v-droop in percentage and give LLC warnings after a few voltage reduction steps. Then see if you can set a BIOS option that reduces the percentage drop or removes the LLC warnings.
I'm no expert but maybe increasing the default voltage (vcore) to say 1.3 (1300mV) might also help with stability. You may have to play but with small increments.
@Brizzles What did you change to get it to stop hard crashing during the tuning? I have a very similar setup. Thanks
Thing is it's not constant at 1.3 that's just it's upper limit. It still downclocks to 1v and sleeps cores etc. So just unsure if 1.3 is too much when all cores are at 4.2ghzSome say 1.3v is too much for daily usage. Personally, I would not run mine at that but I'm sure others will post.