B-Die DRAM OC issues

[dmt_taran]

I've never payed much attention to DRAM OC (XMP or simple clock raise aat 1-2 steps), but now I was itching to hike the system to the max.
But I've bumped into concrete wall.

So, the specs are 8700K, x hero, gskill trident 2x16GB B-die dual rank 14-14-14-34 1.35V 3000 mhz ram.

I've started from available on the market maximum - that is 4000 CL19 2x16 ram. I've checked primary timings, raised vSA/vIO to 1.30V (thus, 1.35 aftre boot), RAM was at 1.45V, that is more than factory 4000 mhz requires. Boot failed.
Then I've took moderate approach, decreased target frequency to 3600MHz, 17-19-39, vSA/vIO left the same, vRAM - 1.4V. I wasn't able to boot.
I've checked all things couple more times, raised vRAM to 1.45, kicked CL20 timings, raised vSA/vIO to 1.38V - nothing helped.

In both situations, boot stucked at RAM initialization with Qcode 6A.

Tried to push RAM at 3200 MHz withing factory settings - system does boot, but for veeeeery long time + it is not stable at all - numerous errors, application crashes, etc.

What am I doing wrong?

[NemesisChild]

Not sure what you're trying to achieve by pushing your memory that high.

Essentially the sweet spot is 3200 CL14. Call it a day if you can do 3400 CL14. Higher than that will require looser timings and basically slower speeds.

[dmt_taran]

NemesisChild wrote:
Not sure what you're trying to achieve by pushing your memory that high.

Essentially the sweet spot is 3200 CL14. Call it a day if you can do 3400 CL14. Higher than that will require looser timings and basically slower speeds.

Actually that's my goal. But! I couldn't run my kit stable at those settings - earlier I've tried just pushing ram from xmp 3000 to 3200mhz. System booted up, but I had numerous crashes and errors.

Now, with all-manual stuff, I can't make it run 3200 CL14, though kit is factory binned to 3000 CL14 - so it should easy ramp up additional 200 mhz without significant vRAM increase or CAS loose. Maybe I need exact example of secondary timings for 3200 mhz :confused:

P.S. BTW, isn't 3600CL16 ~= 3200CL14? Considering the table here - https://en.wikipedia.org/wiki/CAS_latency
+/- same latency, cycle time is on 3600 mhz ram side.
And both configurations are far away from 3000MHz CL14 - so, ATM, after I achieved some stability within 3600 16-16-16-36-2N, dunno if I really need that 3200CL14.
As for 4000 CL18 - you know, it's all about numbers 😄

[bass_junkie_xl]

dmt.taran wrote:
I've never payed much attention to DRAM OC (XMP or simple clock raise aat 1-2 steps), but now I was itching to hike the system to the max.
But I've bumped into concrete wall.

So, the specs are 8700K, x hero, gskill trident 2x16GB B-die dual rank 14-14-14-34 1.35V 3000 mhz ram.

I've started from available on the market maximum - that is 4000 CL19 2x16 ram. I've checked primary timings, raised vSA/vIO to 1.30V (thus, 1.35 aftre boot), RAM was at 1.45V, that is more than factory 4000 mhz requires. Boot failed.
Then I've took moderate approach, decreased target frequency to 3600MHz, 17-19-39, vSA/vIO left the same, vRAM - 1.4V. I wasn't able to boot.
I've checked all things couple more times, raised vRAM to 1.45, kicked CL20 timings, raised vSA/vIO to 1.38V - nothing helped.

In both situations, boot stucked at RAM initialization with Qcode 6A.

Tried to push RAM at 3200 MHz withing factory settings - system does boot, but for veeeeery long time + it is not stable at all - numerous errors, application crashes, etc.

What am I doing wrong?

hello here is my specs

8700k @ 5.1 ghz @ 1.296 v -manual
Asus x hero z-370 wifi - bios 1602-latest
16gb ( 2 x 8 gb ) g.skill (Trident-z RGB ) 3000 mhz cl-14-14-14-34 1.35v

i have my ram over clocked to 4000 cl-17-17-17-37 1.4v vccio @ 1.2v / vcssa @1.2v

100 % stable in asus real bench , prime 95 , mem test 86 , gaming

i can run 4133 18-19-19-39 , 4133 cl-19-19-19-39 , 4200 cl-19-19-19-39 it starts to **** on me around 4200

pretty good for a g,skill rgb 3000 cl-14 samsung bdie kit 🙂 im running 16gb though . yes there samsung bdies typhoon reader says so .

if u need some help i can help yas ! i wouldnt go past 1.2 ish" vccio / vcssa though over time .

[dmt_taran]

bass junkie xl wrote:
hello here is my specs

8700k @ 5.1 ghz @ 1.296 v -manual
Asus x hero z-370 wifi - bios 1602-latest
16gb ( 2 x 8 gb ) g.skill (Trident-z RGB ) 3000 mhz cl-14-14-14-34 1.35v

i have my ram over clocked to 4000 cl-17-17-17-37 1.4v vccio @ 1.2v / vcssa @1.2v

100 % stable in asus real bench , prime 95 , mem test 86 , gaming

i can run 4133 18-19-19-39 , 4133 cl-19-19-19-39 , 4200 cl-19-19-19-39 it starts to **** on me around 4200

pretty good for a g,skill rgb 3000 cl-14 samsung bdie kit 🙂 im running 16gb though . yes there samsung bdies typhoon reader says so .

if u need some help i can help yas ! i wouldnt go past 1.2 ish" vccio / vcssa though over time .

Lucky You, 8700K 5.1@1.296 is not bad. Mine is a dud - 5GHz only at 1.38V stable (within my system at least) - so I don't deny the possibility of CPU limits - that it simple can't run most of RAM can do..

BTW, could You please look out for secondary timings?*

[bass_junkie_xl]

dmt.taran wrote:
Lucky You, 8700K 5.1@1.296 is not bad. Mine is a dud - 5GHz only at 1.38V stable (within my system at least) - so I don't deny the possibility of CPU limits - that it simple can't run most of RAM can do..

BTW, could You please look out for secondary timings?*

prime 95 wanted 1.328 v for 5.1 ghz and ram @ 4000 cl 17 to pass with no wheas still pretty good i think i can do 5.2 ghz under 1.4v maybee 1.38 ish .

here is my mem and cpu z info screen shots i adjusted 2nd timmings a bit not to much just the first 4

here is with prime blend running for 1.5 hrs dual monitor capture might have to zoom it

[dmt_taran]

bass junkie xl wrote:
prime 95 wanted 1.328 v for 5.1 ghz and ram @ 4000 cl 17 to pass with no wheas still pretty good i think i can do 5.2 ghz under 1.4v maybee 1.38 ish .

here is my mem and cpu z info screen shots i adjusted 2nd timmings a bit not to much just the first 4

here is with prime blend running for 1.5 hrs dual monitor capture might have to zoom it

What about SA/IO, vRAM?

[bass_junkie_xl]

dmt.taran wrote:
What about SA/IO, vRAM?

3000 cl 14 1.35 @ 4000 cl 17-18-19-38 2nd timmings a little tweaked dram @ 1.398 v vccio @ 1.2 / vcssa @ 1.2 v

[mrvortep]

bass junkie xl wrote:
hello here is my specs

8700k @ 5.1 ghz @ 1.296 v -manual
Asus x hero z-370 wifi - bios 1602-latest
16gb ( 2 x 8 gb ) g.skill (Trident-z RGB ) 3000 mhz cl-14-14-14-34 1.35v

i have my ram over clocked to 4000 cl-17-17-17-37 1.4v vccio @ 1.2v / vcssa @1.2v

100 % stable in asus real bench , prime 95 , mem test 86 , gaming

i can run 4133 18-19-19-39 , 4133 cl-19-19-19-39 , 4200 cl-19-19-19-39 it starts to **** on me around 4200

pretty good for a g,skill rgb 3000 cl-14 samsung bdie kit 🙂 im running 16gb though . yes there samsung bdies typhoon reader says so .

if u need some help i can help yas ! i wouldnt go past 1.2 ish" vccio / vcssa though over time .

For that P95 stability - is that an AVX build or non-AVX (26.6) - and if the former, what is your AVX offset, if any?

[NemesisChild]

I easily OC'ed my 2x16GB 3200 CL14 set to 3400 CL14 simply by just increasing the DRAM voltage to 1.375v.
You have a good board and memory chip, so basically the CPU IMC would be your major limitation.
Do manual settings, do not use XMP and don't mess with the secondary timings.

Did you try Maximus Tweak mode 1 or even mode 2?

[dmt_taran]

NemesisChild wrote:
I easily OC'ed my 2x16GB 3200 CL14 set to 3400 CL14 simply by just increasing the DRAM voltage to 1.375v.
You have a good board and memory chip, so basically the CPU IMC would be your major limitation.
Do manual settings, do not use XMP and don't mess with the secondary timings.

Did you try Maximus Tweak mode 1 or even mode 2?

Yup, thought mine could do aswell.
For now, all previous bootable set-ups, unfortunately, were unstable, so I didn't achieved any stable result, exept one I'm testing right now.
maximus tweak is on 1

So, I'll mark it up: 3200MHz, CL14, Command rate 2T, 1.4V, vSA+IO 1.20V

Though, I was unable to force the thing boot with 1T command rate, only in stock 3000MHz. In any other OC case, it just stucks at RAM initialization with bF (6F) code.


P.S. What's the better option for ram oc test? For such purpose I've always used AIDA, but I can see people utilizing this "testmem" thing....though I don't really like it, looks glitchy. But if it is more effective, why not.