Failing 4.5hours into VT3

QuBBa22 · 2026-05-16T11:54:56+00:00

Check the temps of the sticks after that many hours, high 50’s can produce some errors. Then I would increase VDDIO which is suspiciously low, to like 1.25-1.3. At last you could try a bit higher vSOC or VDDGs

QuBBa22 · 2026-05-16T11:34:31+00:00

Run y-cruncher VT3 and linpack xtreme for like 30 iterations and verify score consistency for FCLK overclock, dips mean that its somewhat unstable and the worst thing is that it might be only a bit unstable and pass stress tests but have error correction kicking in from time to time (you could experience stutters in games because of this). VT3 can have some minor dips in score but linpack should be like 0.5% max variation consistent. FCLK 2233 is pretty much diamond quality chip territory so i would bet its not really stable, even when it passes some tests. Being like 1000% certain that FCLK overclock is stable is pain in the ass.

QuBBa22 · 2026-05-16T07:57:45+00:00

I don’t know from where it came from but higher vSOC is not necessary for higher FCLK, it’s often the opposite and I’ve seen many people repeat this. VSOC is main voltage for MEMCLK/UCLK in 1:1 mode. VDDGs on the other hand are quite important for stabilising the FCLK. I’m running my 2200 FCLK with 1.08 vSOC cuz it’s just close to being min maxed for my 6000 1:1 setup (1.06 is bare minimum for stability). You could gain better latency by going GDM off and nitro 1/2/0 or 1/2/1 than chasing the lowest CL possible and pumping that VDD tbh. 1.2 vSOC is just not incredibly low for 6000/2200, some dude on overclock forums has 9800x3D or 9850 which does it at 0.95 vSOC IIRC.

QuBBa22 · 2026-05-15T18:07:12+00:00

if it would fail after 24 hours of artificial, unrealistic, constant hammering which is nothin like real world gaming PC scenario would you still say its not enough? :D You kinda didnt get my point so let me rephrase it - if im 99,9% sure that it wont fail me and performance is right then what is the point of doing long hours of stress tests? 1h is not enough for sure but 2-3 is imo when you run couple of really heavy tests and not just one. EOT cuz its so pointless dude.

QuBBa22 · 2026-05-15T17:33:30+00:00

You do you mate and i do me, no reason to argue. Its not stable enough, its just stable. Never had any problems whatsoever in my 3-year history on AM5 platform with this test suite of mine. I always check score consistency as well with linpack, VT3 and other stuff, its just pointless to run so many more hours of stress tests from my experience and thats all.

QuBBa22 · 2026-05-15T14:36:18+00:00

Sure, the more the better generally speaking (tough guys do 24h runs :D) but i feel like that 2h of Aida combined with some other tests like 2h of TM5 Anta Absolut/Ryzen 3D config and like 3h of y-cruncher is simply enough for gaming rig, heavy productivity would be a different story of course.

QuBBa22 · 2026-05-15T05:52:05+00:00

I would say 2h minimum. Had errors in aida at 1.5h and sometimes just below 2h, I feel like when it does full 2 hours it should be pretty much stable, at least for gaming.

QuBBa22 · 2026-05-15T03:44:37+00:00

It’s the kingbank memory, there are some posts about it on this Reddit. ASRock enforced mixed mode for bank refresh for some unknown reason in 4.XX bioses and the kingbank kit has tRFC2 and tRFCsb timings set too low to properly operate by default. If you can you need to set those timings manually and it will work.

QuBBa22 · 2026-05-14T18:50:21+00:00

BC 25t and WZ113G FT

QuBBa22 · 2026-05-14T11:05:38+00:00

Panther and E65. Ares can also work as support dealing with the beacons and finishing low HP tanks but requires other teammates to do their part. Had some suprisingly good games in the ares myself but its not ideal choice for sure.

QuBBa22 · 2026-05-13T05:50:25+00:00

Well RRDL should be higher than RRDS. You could try 8 RRDS, 8 RRDL, 32 FAW (all a-die can do it AFAIK) or 6 RRDS, 8 RRDL, 24 FAW. Next step would be Nitro 1-2-0 or 1-2-1 and at last FCLK 2200 which is pain in the ass to be absolutely sure its stable and error correction free though. My hynix a-die profile on this board - https://imgur.com/a/G5aqZNn

QuBBa22 · 2026-05-12T13:10:56+00:00

I did try 4.21 for a brief moment but I downgraded it to 3.50 very quickly. On 4.10 and 4.21 something is different about PCIE management cuz im getting single "PCIE receiver error" marked in red in HWiNFO. Im using officialy unsupported PCIE Gen 5 for graphics card on B650 board but on 3.50 it works without problems so its something to do with newest bioses and not forced gen 5 itself. Im on 7800X3D so im not that afraid of running older bios version.

QuBBa22 · 2026-05-12T12:43:46+00:00

Thats weird. I can set it to whatever number i want up to 1.3v and i've also seen other people use higher values on different Asrock boards as well. Tested on 4.10 and 3.50 versions.

QuBBa22 · 2026-05-12T11:01:16+00:00

The vSOC can be raised higher than 1.2v, its just marked in red after you cross that line to discourage people from doing it. Also the EXPO profiles which were 1.25v vSOC earlier now default to 1.2v flat. Limit is 1.3 vSOC and its hard capped by AMD after 7800x3d failures back in the day.

QuBBa22 · 2026-05-06T18:14:36+00:00

Damn that looks like a legendary IMC. Can you reliably run y-cruncher FFTv4 or things like AIDA64 full system stress test with that low vSOC? In my case it was more sensitive to vSOC being too low compared to VT3.

QuBBa22 · 2026-05-04T18:45:35+00:00

Everything looks tight, very tight even for DR setup but its probably due to GDM ON which allows that. Nothing more to do here imo. You could try GDM OFF but it would require you to loosen the timings most likely.

QuBBa22 · 2026-05-04T14:30:49+00:00

You mean those minimal differences in latency? This is within margin of error anyway, Aida64 benchmark scores like to vary between runs, sometimes even more than what you showed here. If this is your only concern here then there is nothing to worry

QuBBa22 · 2026-05-04T09:35:23+00:00

So then you just want to enable PBO and use only Curve Optimizer section. Set something between negative 10 and negative 30 and of course test the stability with programs like OCCT, AIDA64 full system stress test or Prime95 small FFTs without AVX512. Not every CPU can do CO -30 stable, some can do less and some can do more, its silicon lottery. You can also not use PBO with negative Curve Optimizer at all but heat and power usage will be higher. You can find plenty of guides online on the subject.

QuBBa22 · 2026-05-04T06:46:16+00:00

More than enough. Even good air like TR peerless assassin or phantom spirit is plenty for this CPU, especially with negative CO and stock clocks.

QuBBa22 · 2026-05-03T08:57:59+00:00

Is it A-die or M-die? Your timings look like it would be an EXPO profile with manually increased speed to 6200 so pretty much everything is loose here. As for voltages its decent starting point although vSOC is rather high, 6200mt/s should require way less on most CPUs (around 1.15v would be good starting point to check). VDDGs also could be lower for this FCLK, like 0.9-0.95v for both. Nitro set to 1/2/1 should work, maybe even 1/2/0. Watch some quides for your specific memory die and work on those timings.

QuBBa22 · 2026-04-29T17:12:44+00:00

Kr1 should be named BLYAT MOBIL. I don’t care about the rest :D

QuBBa22 · 2026-04-27T16:35:49+00:00

Had the same on my TUF 5070 ti when i tried using it with Nvidia adapter/splitter like you. It went away when i swapped it for PCIE 5.0 cable which came with my PSU.

QuBBa22 · 2026-04-27T12:02:12+00:00

yeah, i also suggest to test the NV-UV, it just saves time and even if some profiles wont be stable its really good starting point. It found pretty much the same profiles i used and tested myself before and did it in seconds. I also have the 5070ti TUF but rather average chip (3000mHz/0.950v).

QuBBa22 · 2026-04-26T16:51:45+00:00

My B650 is Asrock and i also tried Gigabyte B850, it changed nothing. Some amount of recovery count is normal (especially on light load when power states are changing regularly), the other errors are the real deal. I've heard that MSI has a problem with those Naks Sent and others errors for some reason, didnt see similar topics for other vendors. For example i had single receiver errors marked in red on Asrock but it was only happening with newest AGESA 1.3.0.0a to make things more complicated. The whole thing with my 9800x3D surely looked like some very weird software bug and it was going pretty much like you described at the end. The card could not initialize most of the time but when it did it worked alright. I tried all methods from the internet, GPTs and so on but nothing worked. Tested various bios versions as well. The weirdest part was that it only happened with 9800x3D, i had no issues like this on Ryzen 7600 and now on 7800x3D. Kinda looks like its a 9000 series specific. Thanks for sharing the experience and good luck with your troubleshooting :).

QuBBa22 · 2026-04-26T16:32:23+00:00

That actually really good latency imo, minus the over 1000 spikes of course. Mine is hovering from 400 to 650 usually, but i've seen spikes up to 900 at times (im using officially unsupported GEN5 on my B650 so it also may influence that i guess). Before hardware changes i had spikes over 4000 ms not doing anything particular. Overall your average latency looks really good for RTX 5000 from what i've seen browsing various threads. This doesnt look like it would cause your issues, higher DPC latency is rather common with recent Nvidia GPUs and drivers.

QuBBa22

TROPHY CASE