[GosuPl]

What's your D2D/NGU on that OCF and 265K and what voltages are you using for them?
I am struggling with D2D over 3000 when the ram is over 8000...

For now NGU 32 and D2D 34. SA around 1.41, and VANON auto , around 0,850

Update :

Unfortunately, I got excited too soon — the motherboard started acting up again. It's throwing BSODs even on default settings. Looks like I got a faulty unit. I'll try a few more things, but if nothing helps, I'm swapping the mobo — not worth the stress.

 

[Ind.puneet]

What's your D2D/NGU on that OCF and 265K and what voltages are you using for them?
I am struggling with D2D over 3000 when the ram is over 8000...

For now NGU 32 and D2D 34. SA around 1.41, and VANON auto , around 0,850

Update :

Unfortunately, I got excited too soon — the motherboard started acting up again. It's throwing BSODs even on default settings. Looks like I got a faulty unit. I'll try a few more things, but if nothing helps, I'm swapping the mobo — not worth the stress.

I would suggest don’t overclock d2d ngu and cache yet.. first stablize memory then settle for 32 32

 

[chibi]

In my experience, leave d2d to absolute last. Make sure your core, memory and ring clocks are 110% stable first then work on ngu. Not just synthetic tests, but real world application usage for at least a week before moving to d2d last.

 

[zwer54]

For now NGU 32 and D2D 34. SA around 1.41, and VANON auto , around 0,850

Update :

Unfortunately, I got excited too soon — the motherboard started acting up again. It's throwing BSODs even on default settings. Looks like I got a faulty unit. I'll try a few more things, but if nothing helps, I'm swapping the mobo — not worth the stress.

That's exactly what D2D oc does. Returning to auto doesn't fix it, set it manually to 30 and BSODs will be gone.

 

[GosuPl]

So even if I did two BIOS updates in a row using Flashback, and didn't touch D2D / NGU afterwards, but in HWinfo64 D2D shows default (i.e. 21) and NGU 26, this board still goes crazy with D2D set to auto? I set D2D to 30 like you said and I'm starting the tests.

 

[zwer54]

So even if I did two BIOS updates in a row using Flashback, and didn't touch D2D / NGU afterwards, but in HWinfo64 D2D shows default (i.e. 21) and NGU 26, this board still goes crazy with D2D set to auto? I set D2D to 30 like you said and I'm starting the tests.

I'm not sure what's going on but I figured out as soon as I get BSOD while D2D being at x31 or over, by setting it manually to x30 it just works afterwards. To be funnier once it's stable I go back to bios, set it to 35 and still works fine afterwards. The issue comes back after the PC has been turned off for some time.

Just got home from work, tighten sub latencies a bit more and run TM5, passed with Ring 42, NGU/D2D 35, didn't throw any bsods from cold boot. VNNAON voltage I set to 0.99V, NGU 1.20, ring 1.21V.