• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question Intel 285k + RAM help.

lawshadow

Junior Member
Hi all

System
CPU Intel 285K SP 101
Board ASRock Z890i Nova ITX
RAM G Skill DDR5 8800 2x24GB F5 8800C4255H24GX2 TZ5CK
GPU XFX RX 9070 XT
Storage 2x Samsung 990 Pro dual boot Windows 11 and Linux Bazzite
PSU Corsair SF1000
Cooling custom CPU loop
BIOS 3.12 latest as of yesterday did a BIOS update.
Currently running: Intel default profile and XMP1 = 6400mhz NGU and D2D = auto this time. Have not tested yet. Since the issues where on BIOS version 2.26 on Asrock mb.

I initially ran XMP 8800 and later reduced frequency to 8400 then 7800 then 7600 with help from G Skill support. All synthetic tests passed including MemTest86, Karhu, OCCT, Prime95 and TM5 full 24 cycles except on 8800mhz which was deceptive stable on Testmem5 (custom profile) error in 2 min. I then moved to 8400mhz now all tests redone and ALL passed incl Testmem5 full 24 cycles.

Real world gaming is not really stable. I get random clean CTDs straight to desktop in Elden Ring, Helldivers 2 and Cyberpunk 2077. This happens on both Windows 11 and Linux Bazzite. Event Viewer usually shows 0x0000005 Access Violation. No WHEA errors no GPU driver resets no BSOD.

The common thread across all frequencies and both OSes is that NGU and D2D were always manually set to 30 for latency reasons without further tweaks. Switching from ASRock Extreme profile to Intel Default did not change behavior.

I have seen mixed reports that some CPUs handle NGU and D2D at 30 without voltage changes while others do not.

Questions
Can NGU and D2D at 30 without fabric or SA related voltage tuning cause 0x0000005 access violation type CTDs under gaming load.
Does this look more like uncore or fabric instability rather than DRAM itself given that all memory tests pass and the issue is OS independent?
Is backing NGU and D2D down to AUTO the correct first step before touching any voltages and if set at auto do i really feel the latency penalty with latest BIOS?


Not interested in CPU core overclocking only stable low latency gaming if it doesnt involve to much fiddling or rather not to.
Many thanks in advance
 
i take it that everything is stock?
try lowering the timings on the RAM. XMP is not the champion it used to be.
 
What's the point of "low latency gaming" if it crashes?
I don't understand gamer "stable" memory. 285K supports DDR5-6400. Run at that.
 
i take it that everything is stock?
try lowering the timings on the RAM. XMP is not the champion it used to be.
Correct partially:

First i enabled "Asrock extreme profile" inside BIOS and then changed to "intel default profile".
Asrock extreme profile i did do a higher PL1 and PL2 out of memory it was i think 300w pl1 and 350 pl2 recommended by an user on some forum. And did manually set NGU and D2D at first at 32 and then 30....NO voltage tweaks at first. People did told me to change various voltage in VNNAON and system agent but eventually i refrained from it i did try the settings but due to in my eyes bit conflicting advise how to properly set up VNNAON os asrock mb and other voltage tweaks i stopped knowing very well i am NOT that versed with these more indepth settings. hence i switched to "intel default profile" and only changed NGU + D2D to 30 i realize NOW i didnt change the RING value to say 40 in all my RAM freq ie 8400 - 7800 - 7600...could it be that RING at default/auto is culprit?
 
What's the point of "low latency gaming" if it crashes?
I don't understand gamer "stable" memory. 285K supports DDR5-6400. Run at that.
You are 100% right

But i can tell you 6400 vs say 8400 has a difference 8400 way less 1% lows and far more smoother overall gameplay compared to 6400mhz maybe due to seeing it inside the BIOS already set at 6400mhz officially supported speed of Arrow Lake but this was JDEC. I then realized later on there is also an XMP1 profile also with 6400mhz but with far tighter CAS timings like 39 instead of that JDEC 52 CAS. Will try to really pay attention to XMP1 6400mhz profile during gaming and report.

Do you own a Arrow Lake if so how did you set it up ie stock + XMP?
If so how does gaming feel to you with which resolution and gpu you use?
 
could it be that RING at default/auto is culprit?
i have no clue. we're just testing. lowering ram timings is the easiest check you can do, and we do it because XMP just doesnt work anywhere near as good as they tell us, specially with high-end sticks. if the crashes continue with relaxed ram timings, then we know it's not the sticks, or the power delivery, and we can move on to the other thousand things that could be broken.
 
Back
Top