I have my 3200 16-18-18-36 kit running at 3600 16-18-18-36 1.38vHow good is memory OC (Ballistix Sport LT) with the Aorus Elite?
I have my 3200 16-18-18-36 kit running at 3600 16-18-18-36 1.38vHow good is memory OC (Ballistix Sport LT) with the Aorus Elite?
2x16GB.2x16gb or 2x8?
Enviado desde mi Mi A1 mediante Tapatalk
Thanks for sharing. Your scores are very similar to what I used to get on my previous Intel based system. Any pointers on what I could be doing wrong? (I am using the slot above the GPU). Are you using any beta Samsung NVME drivers or the one posted on their website?Got the same drive on an X570 Pro, benchmark while in use (MHW).
Edit: The first Magician and CrystalDiskMark screenshots were taken with the last MS Surface NVMe driver while the drive was in use. The second Magician screenshot was taken with the Samsung NVMe driver active, in idle.
Yeah did a clean install of course of version 1903. Also as per Crystal DiskInfo it is in PCI-E 3.0 4x mode. I will check all BIOS options once more to make sure nothing is obviously wrong.Just a thought but did you do a clean install of win 10 or did you just take your old OS out of your old build?
Also maybe go in bios and force pcie to gen 3 instead of auto. There have been bugs if left on auto it will actually drop to gen 2 or lower which will cut your performance
The option is there, finally!New F4 bios for the Elite released today. Lets hope it has the Spread Spectrum option visible, so we can change it![]()
The F4 posted on Gigabyte website yesterday for the Elite (non-wifi) https://www.gigabyte.com/Motherboard/X570-AORUS-ELITE-rev-10/support#support-dl-biosWhich F4 does he mean... link? F4J beta bios or F2 which was released today on Gigabyte site? Is that a mistake btw, did they mean F4? F2 doesnt make sense ( https://i.imgur.com/YJNHHIO.png ). This should be F5.
Make sure you have BLCK set to Auto to be bale to see it.Can anyone with an Xtreme please verify there's still no Spread Spectrum option? I've updated to the latest F4 version but can't find it anywhere. People with other boards have said the option is now there for them.
I do, using the fast preset timings from DRAM calculator, rock stable at 1.4v!Has anyone OCd a ballistix sport LT from 3200 to 3600MHz C16 in an Aorus Elite? Is it stable?
Enviado desde mi Mi A1 mediante Tapatalk
YMMV, but running 2x16 here no problem, I am too lazy to reboot to give you the timing, but they are exactly like in DRAM calculator (but I remember I ignored their 1.43v and kept 1.4v)I forgot to ask: 2x8 or 2x16?. I'm aiming for 2x16,but will they reach the target oc of 3600? Also, what timings? (I didn't download the calculator yet xD )
Enviado desde mi Mi A1 mediante Tapatalk
Care to share your full RAM timings and voltage? Thanks!-Less DPC also with my Nvidia Card (still in IRQ Mode)
-still stable RAM OC with Micron Edie @3600 mhz CL 16
32 GB Ram Crucial Ballistik (3000 CL15 -> [email protected] MHZ / CL16 -> Micron E Die
With it I saw my boost go to 4,625 for first time in the life of this 3900x!!With that new power plan my little 3600 boosts up to 4192. All good.
This to me sounds like unstable RAM/CPU OC, if you have done any. I experienced the same when I was trying to max my RAM OC on many BIOS versions, rock stable once I figured it out and reached a stable RAM timing and voltage.With regards to the issue that users here are having with PCs not booting/BIOS resets, I replaced my OCZ ZX 1250w with a new Seasonic thinking that could be the problem and it still remains (the ZX 1250w had horrible coil whine so I don't mind the change one bit..)
My X570 Elite board now does one of three things.. (with my PSU left switched on 24/7)
* You press the power button, and get a Black screen.. the fans inside the case spin in a *certain way* the PC will go no further.. you can sit here for 5 mins and not boot or get a reset, so you power it off.
* You press the power button again and the monitor comes on and we boot up!
The 3rd scenario..
* You press the power button, and you get a black screen BUT you hear the fans inside the case ramp up, ramp down *quiet reset sound* , ramp up, ramp down *quiet reset sound* it does this once again then the screen comes on and the BIOS tells you that it has been reset.
Can we please have some acknowledgement from Gigabyte that this is a known issue that's being investigated for a fix?
Congrats on your new build! Did you update the bios to the latest one? and did you install the RAM in the correct slots? (A2 and B2) This is what it says in your board manual to insure maximum compatibility for 2-dimms configs.recently finished my build: x570 Aorus Master, 3900x, 5700 XT and this memory kit: https://www.newegg.com/team-16gb-288-pin-ddr4-sdram/p/N82E16820331244
sadly the kit is not on the board's QVL (i remember checking a different x570 aorus board that i was planning to get for the build that did in fact list the kit as supported so i assumed the much higher tiered board would also support it). needless to say i've been experiencing some issues and i wanted to make sure these are caused by lack of compatibility and nothing else
basically, the ram will only run at what the system defaults to (minimum timings downclocked to 2400mhz, fabric at 1200) and at w/e ryzen master automatically sets the timings to when raising fabric clock in coupled mode.
the system does not boot in XMP (although the correct clock and timings are displayed when choosing the option in the bios), tried manually setting the dram voltage and then manually setting all the timings to no avail. i also tried manually overclocking in multiple clocks with very loose timings (based off of dram calc, also tried various dram calc timings at different frequencies) - but the system doesn't post. only thing that works is resetting cmos at that point.
on top of all of that, i've experienced similar issues (system not booting, more of less the same error codes) when setting the fan curve to silent.. had to reset cmos because of that aswell.
anyone have any similar experiences? is it possible this is all caused by lack of compatibility with the memory or is there a different issue?
any help would be appreciated. ty!
You nailed it!! was going crazy over CB20 reboots until I set the SOC voltage to Auto!Here's my first feedback about F20a... TLDR; I'm probably going back to F12a soon
The good:
- Unlocked settings in AMD CBS
- PMU pattern bits can be now configured manually
- Better memory compatibility (can run CL16 with GDM Disabled now)
- ProcODT at 60 with XMP profile fixed
- Can now run VDDP/VDDG at 1000/1050
- Better UI graphics...
The bad:
- IMC is broken; memory bandwidth (Sandra) at 3800 MHz is much lower than F12a, almost same as when configured at IF 1800/3600 MHz.
- Memory latency is different (Sandra); about 75% worse (2-5 ns), rest better (2ns)
- Almost all voltages, LLC settings behave differently
- Worse scores in benchmark, from a tiny bit to quite considerably, probably related to memory issues
- Weird stalls under the main Windows install, feels much slower
- Fixed SOC Voltage now is a problem, up to reboots during CB20 MT, have to keep in Auto
- VDDP/VDDG at 900/950 is messy now, much lower scores
hmm, cannot seem to find that option in my Elite BIOS, do you mean a positive SOC voltage offset? I tried that but it has the same effect as setting it manually to the value I want.Try to change your "Over voltage" setting for SoC. I encountered a similar issue with reboots and I think that fixed it by upping it from AUTO, seems overly low in F20a @ stock.
I did try some other things as well but I think this one was what fixed the issue.
Thank you for elaboration, sadly that option is not available for the Elite.I mean "over voltage protection" basically your board shutdown limit if it reaches these limits.
You find them in your PWM/LLC settings page if you board allows you to set these things.
Indeed it is the case. Any way to be able to set that 400mv limit on the x570 Elite?Just want to mention "Over voltage protection" is set really low for F20a BIOS on the X570 AORUS XTREME.
AUTO = 300mv = ~1.100V SoC limit, you exceed this = reboot.
350mv = ~1.150v SoC limit, you exceed this = reboot.
So meaning, maximum 400mv over voltage protection only allows 1.200V maximum for SoC. They will have to fix this.
Unsure if Vcore is effected yet.