Advice on Max safe voltage on Mem

[EL_JOCK]

Update after posting this i restarted my PC and a F9 error, its making no sense it can pass any stress test for hours, thinking either the bios needs work to knock out some bugs or i might just have the worst IMC going,

Have made a few tweaks to the above settings and started a stress test see how it gets on, but going off previous its likely to pass all that then start F9'ing at random times.

Will be putting in a new PSU later as mine is getting on a bit and i have some coil whine in my GPU that might chill out a bit with a better PSU, also need a new GPU the 290 is way over due for replacement.

enough rambling back to testing....

Ste hope your 3466 works out

 

[8 Pack]

I am kinda lost in this thread what needs testing if anything? And using which sticks?? I can try tomorrow.

 

[EL_JOCK]

Hi 8Pack,

Think its just been a bit of knowledge sharing between me an Ste, I'm having random F9 post errors even after hours of testing (all passes) but it will for some reason on a restart just F9 at some random time but then boot ok with settings still selected. (i.e it does not revert to 2133) so not sure whats going on, have gone back to 2933 which seems fine, and will look at 3200+ speeds after the next round of Bios updates. Think all the info is good just something not clicking with my system at the mo.

I have the following ram on the gigabyte gaming 5 x370

https://www.overclockers.co.uk/g.sk...channel-kit-f4-3600c16d-16gtzr-my-10l-gs.html

 

[Ste]

I am kinda lost in this thread what needs testing if anything? And using which sticks?? I can try tomorrow.

Hi mate, we are just messing about trying to get 3466 on the gigabyte gaming 5 which is a bit harder than on the taichi or crosshair. Nothing needs testing although if you have any experience or advice on the timings to play with to try and avoid memory training failure (F9 codes on gigabyte) that would be useful! If you have any of these boards in your testing rig it'd be useful to see what your thoughts are!

I tried the stilts 3466 timings this morning and although it booted it crashed at 150% HCI with blue screen and F9 code and wouldn't come back up. I think his 35 TRAS is too aggressive for my kit at 3466. I slackened it but then got F9 trying to boot so gave up. So temperamental and difficult to diagnose.

My own 14-14-14-14-38-54 is 1000% stable at 3466 1.45v, but again F9 codes everywhere.

Have signed up at OCN to see if anyone can weigh in and for now back to 3333.

AGESA 1.0.0.7 could be good but I suspect it'll be focussed on stability on the lesser kits that still can't even do 3200.

Edit - if your 3200 is now playing up again that's weird. There must be something in there not clicking. Could do a full upload of every BIOS setting if helpful...

 

[8 Pack]

I can try this yeah. I have promised I will try MSI gaming Carbon first then I will have a go. I tried Gaming 7 and that was fine but only to qualify and not 3466mhz. Ryzen CPU very strange when tuning so I think each boot can be different training on lower timings which is a pain ass. Intel also can train diifferently but I think the balance of timings is geared to stability and more consistency on Intel.

 

[Ste]

Cool, thanks.

If you put every single setting in manually would it have anything to train?

 

[8 Pack]

In practice always because some settings are only available to the bios engineers.

 

[Scougar]

Is there a way to stop it from training once a stable setting is found?

 

[smogsy]

Hi Ste, 8Pack or anyone having issues with getting 3200 on a Gigabyte X370 Gaming 5 F6 bios. This might work on other system "Hell I'm not sure why it works at all" I did say it was more magic!

Now, please read some of the posts above for more context and good info from 8Pack and Ste, but in short i have a 1600, with 3600 C16 Samsung b die memory, could do 2944 no issues super tight speeds, 3200 was a no go with any volts from 1.35v up to 1.5v, soc 1v upto 1.2v. There just seemed to be a block did not matter how loose the timings went or how much voltage i applied to it.

So today i just went all out turned off my pc pulled the power cord, then the 24 pin, popped out the cmos battery then put a screw driver between the cmos pins held for 5 sec to totally clear the cmos, also pushed the power button a few times to make sure all the charge was out the system. (i think there is a name for this type of reset but not sure)

Any roads following that, plugged it all back together, booted into bios, (says it has been reset), set mem clock to 3200 (by typing it in, not using page up or down). typed in cas 16-16-16-16-36 (just wanted a basic easy timings to start with) all other settings on auto.

Go into voltage type'd in 1.45 volts for Dram & SOC 1.1

Save and exit, No F9 errors "Great", back into bios 1.4v Dram Save and exit, No F9 errors "super", back into bios 1.35v Dram save exit no F9 errors "What its working"

Boot into windows load up Aida64 run stability test as i type this its just passed the 30 minute mark no crashes no issues, this is the best place i have gotten to ever when going for 3200, will update as i do more testing but for what ever reason a full cmos reset seems to have cleared what ever issue the system was having.

take it easy

Gigabyte bios is so untested its silly.

i was testing 3600/3466/3333 just yesterday. was working ok but was trying to find a stable frequency. 3600 failed so tested 3466. reboot the pc. now i cant even input anything apart from 3200/2133
Also it reset all my fan profiles. & my cpu tweaks.

second time this happened on this board where on a reboot it lost all my data.

 

[Ste]

Yeah similar issues here. Really difficult to pinpoint some of the crap it throws out sometimes. Will be going ASUS a next time although to be fair that won’t be for a good few years!

 

[smogsy]

Yeah similar issues here. Really difficult to pinpoint some of the crap it throws out sometimes. Will be going ASUS a next time although to be fair that won’t be for a good few years!

full cmos clear fixed it for now..

running hci @ 3333

 

[Ste]

Yeah until it throws another wobbly one

I’m solid at 3333 14-14-14-14-60-256 which is reasonable although latency a bit high. Same settings also fine at 3466 when it boots but F9 codes regularly screw that up.

 

[8 Pack]

F9 is training code which is pain in the ass. I had consistent stuff with gaming 7. I have to say did not try for too long.

 

[Silent_Scone]

Is the Gaming 5 even validated for those speeds?

 

[EL_JOCK]

Is the Gaming 5 even validated for those speeds?

Think the top speed on the box is 3200, but after loads of messing around and testing, I have 3333 cracked I think! The last few days PC has been fine, no odd behaviour think i have had 1 F9 in a large amount of restarts and boots but on the second attempt it was fine so have not lost any sleep over it.

Current settings, passed 500% on memtest and an hour on Aida64 with no issues and only 1 F9 in 2 days

 

[Ste]

Great timings!

 

[EL_JOCK]

New bios out for gigabyte boards, maybe help out...its a revision of the aegis 1.0.06

WARNING

The F7 bios on the gaming 5 has an issue with CPU offset voltage, it does not work correctly i.e it puts way way way more on than you planned.

Good News manual cpu voltage seems to work again without the 15.5x CPU multi lock.

 

[Ste]

Oh very interesting. Are you going to give it a try? I suspect it has only improved for some of the QVL kits to work with XMP on but you never know if they’ve tweaked the training process the dreaded F9 GFYS codes may reduce at higher frequencies...

 

[EL_JOCK]

not had the time yet, just plugged in my previous settings and it work first time no issues, just info for others having issues....(making me want to start testing now)

 

[Ste]

Just read the gigabyte thread. Not risking that for a while.