Overclock.net banner
1 - 20 of 24 Posts

MusTriesOCing

· Registered
Joined
·
77 Posts
Discussion starter · #1 ·
I've got a kit of Crucial Ballistix (BL16G32C16U4W.M8FB1) on a Gigabyte Z690 UD DDR4 that I've been messing around with. This is my first experience overclocking memory but I have done a bit of research by reading the GitHub DDR4 OC guide and watching Buildzoid's (Actual Hardware Overclocking) videos on YT of him overclocking various Ballistix kits

I've got this kit to 3900MHz (all timings in Asrock Timing Config screenshot) and it has ran 2.5 hours (44 cycles) of TestMem5 with the PCBDestroyer config and 11 passes of Linpack Xtreme. I haven't fully minimised all the timings yet. I tried running Extreme1 Anta777 but it will randomly stop testing like 30 to 40 mins into the test

It passed the tests with 0 errors but when I put the PC to sleep shortly after ending the TestMem5 run the PC did not wake properly from sleep afterwards. It was in sleep for probably around 30 minutes. The PC turned on, ie lights and fans came on like normal, the DRAM debug LED stayed on a few seconds but then went away but my monitors stayed black and my mouse and keyboard weren't lit up.

is this normal or a sign of instability?

I am running 1.25V VCCSA and 1.45V VDIMM, neither of which I have touched since I started. I literally just inputted them in manually and went about overclocking without considering more or less voltage for either. Is this sleep state problem caused by too low System Agent voltage? What's a safe voltage for that? I know Alderlake is relatively new but if anyone knows what the official 24/7 voltage is for SA please let me know


Also if any of you have any tips, on overclocking Micron Rev.B or what timings I can lower for 3900MHz or 4000MHz from the screenshot attached, I'd appreciate any input

Thank you

Photograph Light Black Font Screenshot
 
Is your CPU under-volted at all?
 
Does it do it at stock?

I've had a half dozen boards where sleep was buggy as hell on early BIOS revisions.
 
Discussion starter · #6 · (Edited)
Does it do it at stock?

I've had a half dozen boards where sleep was buggy as hell on early BIOS revisions.
Nope when I use only XMP the sleep mode works as normal
Maybe Gigabytes current BIOS version bugs out with faster memory for the sleep states?
 
Nope when I use only XMP the sleep mode works as normal
Maybe Gigabytes current BIOS version bugs out with faster memory for the sleep states?
Hm. Sorry, I threw the idea out because it's caught me a cropper before now more than once. It's one reason I tend to just disable/ignore sleep mode entirely - more trouble than it's worth for me.

I suppose sleep bugging out at faster memory speeds might be an issue, but in my experience on newer chips (post 3000 series) if sleep is bugged it'll do it at stock as well.
 
most likely going to require a bios fix. sleep mode was bugged on msi unifyx z690 once entered manual settings, fixed since a22 bios, main bioses on website (not beta) are still sleep bugged. My prior gigabyte boards on z390 had similar sleep bug on early bios triggered by manual settings.

But you can try high performance mode in power options and see if sleep works, or using balanced mode, change pcie express>>link power management.. change to off.
 
after waking from S3 on my Z690 Aorus Elite AX DDR4 it's 50/50 if it will hard lock up just after waking

Running 2 x 32GB Crucial Ballistix 3600 @ 3733 15-17-17-34-540-CR1

Seems to be Voltage related trying to narrow it down its fine apart from that 12000% karhu
prime 95 avx etc
 
Discussion starter · #10 ·
after waking from S3 on my Z690 Aorus Elite AX DDR4 it's 50/50 if it will hard lock up just after waking

Running 2 x 32GB Crucial Ballistix 3600 @ 3733 15-17-17-34-540-CR1

Seems to be Voltage related trying to narrow it down its fine apart from that 12000% karhu
prime 95 avx etc
Must be a Gigabyte BIOS problem then
If you figure out how to fix it on current BIOS versions then please do let me know
I've messages Gigabyte Esupport about it and will update the post of their response
 
Discussion starter · #12 ·
Im suspecting VCCSA

It was on 1.20v have set it to auto (1.34v) and it hasnt done it yet

Will get back if it does it
also if it does turn out to be that i will lower VCCSA as low as i can and get back
Any update?
 
Oh and since you have the same ram as me but single rank and 3200 instead of 3600

i have spent hundreds of hours dialing in the ram

CL 15 is to low at 3900

here's what i run at 3900 and its karhu 30033% stable

You may need a bit more voltage though as mine is a better bin

1.38V maybe?

anything not listed leave on auto

VDDQ CPU = 1.20V (Dont leave on auto thats 1.35V)(Crucial Ballistix Micron B die really doesnt like 1.35V and will cause fails in karhu fast)
Make sure you Set Gear 1 it wont post at Gear 2 with these timings

Code:
Final 3900 Timings
Ram 2 x 32 GB Crucial Ballistix 3600
Micron B Die Dual Rank BL2K32G36C16U4B
CPU Base Clock = 100.33
Gear Mode = Gear 1
VCCSA = 1.35V (Auto)
Realtime Memory Timing = Auto
Memory Timing Mode = Dynamic (Fixed = Random Hard Lockups after S3)
DRAM Voltage 1.350V
VDDQ CPU = 1.20V (Dont leave on auto thats 1.35V)(Crucial Ballistix Micron B die really doesnt like 1.35V and will cause fails in karhu fast)

Detailed Timings @ 3900
CAS Latency                     16
tRCD                            18
tRP                             18
tRAS                            36

tRC                             54
tWR                             10
tRRD_S                          4
tRRD_L                          4
tWTR_S                          Auto (3)
tWTR_L                          Auto (6)
tRFC                            585
tRTP                            5
tFAW                            16
Command Rate                    1

tREFI                           58320
tRDRD_sg                        7
tRDRD_dg                        Auto (4)
tRDRD_dr                        7
tRDRD_sg                        7
tRDWR_sg                        12
tRDWR_dg                        12
tRDWR_dr                        12
tRDWR_dd                        12
tWRWR_sg                        7
tWRWR_dg                        Auto (4)
tWRWR_dr                        7
tWRWR_dd                        7
tWRRD_sg                        26
tWRRD_dg                        23
tWRRD_dr                        7
tWRRD_dd                        7
 
Discussion starter · #15 ·
Oh and since you have the same ram as me but single rank and 3200 instead of 3600

i have spent hundreds of hours dialing in the ram

CL 15 is to low at 3900

here's what i run at 3900 and its karhu 30033% stable

You may need a bit more voltage though as mine is a better bin

1.38V maybe?

anything not listed leave on auto

VDDQ CPU = 1.20V (Dont leave on auto thats 1.35V)(Crucial Ballistix Micron B die really doesnt like 1.35V and will cause fails in karhu fast)
Make sure you Set Gear 1 it wont post at Gear 2 with these timings

Code:
Final 3900 Timings
Ram 2 x 32 GB Crucial Ballistix 3600
Micron B Die Dual Rank BL2K32G36C16U4B
CPU Base Clock = 100.33
Gear Mode = Gear 1
VCCSA = 1.35V (Auto)
Realtime Memory Timing = Auto
Memory Timing Mode = Dynamic (Fixed = Random Hard Lockups after S3)
DRAM Voltage 1.350V
VDDQ CPU = 1.20V (Dont leave on auto thats 1.35V)(Crucial Ballistix Micron B die really doesnt like 1.35V and will cause fails in karhu fast)

Detailed Timings @ 3900
CAS Latency                     16
tRCD                            18
tRP                             18
tRAS                            36

tRC                             54
tWR                             10
tRRD_S                          4
tRRD_L                          4
tWTR_S                          Auto (3)
tWTR_L                          Auto (6)
tRFC                            585
tRTP                            5
tFAW                            16
Command Rate                    1

tREFI                           58320
tRDRD_sg                        7
tRDRD_dg                        Auto (4)
tRDRD_dr                        7
tRDRD_sg                        7
tRDWR_sg                        12
tRDWR_dg                        12
tRDWR_dr                        12
tRDWR_dd                        12
tWRWR_sg                        7
tWRWR_dg                        Auto (4)
tWRWR_dr                        7
tWRWR_dd                        7
tWRRD_sg                        26
tWRRD_dg                        23
tWRRD_dr                        7
tWRRD_dd                        7
Thank you I really appreciate the full list of timings :)

Couple questions, did Dynamic mode change anything in terms of performance? I'm not exactly sure what it does and how it would affect the system

And does the VDDq voltage only affect Rev B or is it a well known thing for other dies? Because I've seen some people recommend up to 1.4v and buildzoid even used 1.5v but that was very early during alder lake's release and he even said he wasn't sure it was safe or necessary
 
VDDQ seems specifix to Gigabyte motherboards and Crucial PCB's is my take on it
Dynamic mode doesnt change anything with regards to performance

Most people pushing VDDQ are using Samsung B die
i have only seen one person on Micron B Die pushing VDDQ and he was using a msi motherboard and Corsair PCB's

If i push my VDDQ from 1.20V to 1.35V i fail karhu at like 50%
i have also seen a few other people say the same with Micron B die

Y-Cruncher is fine 2.5b is like 64s

Here's it at them timings on my old 12900K

Image
 
Gigabyte boards are the most difficult to overclock ram on, and up to 10th gen boards they were still using t toplogy which wouldn't even reach 3200 for a lot of users.

Maybe they actually listened to my angry feedback if you're managing to get 3900 on them now, but it still looks like theres issues.

My current asrock board is pretty bad, but still a better experience for ram OC then everything I keep reading about gigabyte boards mirroring the experience I had with them.

With Asrock you have to configure all the ram settings at once, they don't tune fine adjustments and refuse to boot after mild tinkering, so anytime I want to change something I have to reload stock settings first then reload a profile to adjust.
 
Gigabyte boards are the most difficult to overclock ram on, and up to 10th gen boards they were still using t toplogy which wouldn't even reach 3200 for a lot of users.

Maybe they actually listened to my angry feedback if you're managing to get 3900 on them now, but it still looks like theres issues.

My current asrock board is pretty bad, but still a better experience for ram OC then everything I keep reading about gigabyte boards mirroring the experience I had with them.

With Asrock you have to configure all the ram settings at once, they don't tune fine adjustments and refuse to boot after mild tinkering, so anytime I want to change something I have to reload stock settings first then reload a profile to adjust.
I wouldnt say they are that bad
people just whack voltage at it thinking that will solve the issue

I can boot 4300 on my 13900K the 12900K was just able to boot at 4000

12900K i can get 3900 Karhu 30033% Stable with tight timings
13900K i can get 4133 Karhu 30033% Stable with tight timings

T-Topology is great on the older boards if you run 4 sticks
My 9900K + Z390 Aorus Master runs 4 x 16GB Crucial Ballistix 3200 @ 3600 16-18-18-36 CR1 Tight subs 30033% Karhu Stable

And is also fine if you run 2 Sticks
My 8700K + Z390 M Gaming rung 2 x 16GB Crucial Ballistix 3600 @ 3600 16-18-18-36 CR1 Tight subs 30033% Karhu Stable
 
1 - 20 of 24 Posts