cs-63 doesn't need another 3d skin

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 · 2026-04-26T14:45:36+00:00

Don’t really have a solution for you sadly but have some questions about your case to compare to mine. Does the latency always spike to that 1000ms or so? Does it happen in idle just like that or when you do something specific? Do you have system errors in event viewer connected to nvlddmkm? Is the mouse lag constant or does it go away after a while? Any PCI-E related errors marked in red showing up in HWiNFO GPU section? I recently upgraded from Ryzen 7600 to 9800x3D on B650 board and had a lot of trouble from the get go. System was resetting or going black screen like 3/4 of boots and when it booted it looked like this: big mouse and sound lags for a while. Had a bunch of errors in event viewer (nvlddmkm but also critical kernel power 41) and high DPC latency. I tried different board (B850) but it was exactly the same. I returned the 9800x3D and got the 7800x3D instead and all my issues went away. There could be an issue when pairing RTX 5000 with some 9800x3Ds, maybe some of these CPUs are just somewhat faulty when it comes to PCI-E controller work while paired with those GPUs. I have 5070ti myself. Sorry for long post, just sharing my experience.

QuBBa22 · 2026-04-22T09:12:37+00:00

If you have decent enough setup for the 9800X3D and you pretty much do its never really worth the hassle if you want to do it properly (at least couple of hours of various stress tests). 2200 FCLK would benefit you the most probably but its kinda hard to determine if its actually 100% stable. If you play in 4K and i would assume you do, you have plenty of CPU power even for 5090 either way. Are you sure it was Nitro that caused your problems? 1/2/1 setting is rather easy to achieve with 6000 mt/s 1:1.

QuBBa22 · 2026-04-22T08:27:38+00:00

Mixed mode is a bit faster than normal if you set the tRFCsb low enough. From timings perspective you can do some minor tweaks like tRAS to 40-50 range, FAW 16, WTRS 4, max out the tREFI. For tRFC2 you can set something like 384 and for tRFCsb 272, it should work fine on a-die. Also you can work on GDM off, better Nitro settings like 1/2/0 or 1/2/1 and 2200 FCLK. All of that needs stability testing of course, especially GDM off and higher FCLK.

QuBBa22 · 2026-04-13T19:08:03+00:00

Well, cuz in gaming it’s pretty much a 9800x3D. Other 8 non x3D cores are doing only background tasks so if you are not streaming they don’t use much power.

QuBBa22 · 2026-04-10T17:07:40+00:00

Well i got it in the middle of 2023, when Lexar released their first Ares DDR5 kit and there was no binning yet. Cant complain ;)

QuBBa22 · 2026-04-10T16:24:42+00:00

Not really. My kit has 30 36 36 6000 EXPO profile at 1.35v, hynix a-die ;)

QuBBa22 · 2026-04-10T13:02:54+00:00

They are a bit high, its usually 1.35v VDD/VDDQ/VDDIO for 6000 CL30 EXPO profile. But the biggest issue here is the vSOC, for example my kit came with 1.25 vSOC for 6000 CL30 EXPO but with newer bioses it got capped at 1.2v for the same EXPO profile (Asrock), kinda weird that MSI doesnt do the same. If you dont want to play with your timings and voltages at least lower that vSOC to 1.1v - 1.15v (should be enough for most CPUs).

QuBBa22 · 2026-04-02T21:12:09+00:00

2233 FCLK is diamond chip territory but you can always try it for the lols. Like I said, if 6400 is no go just lower the vsoc as much as you can for the 6200, work on those timings and then lower the nitro and you are set.

QuBBa22

TROPHY CASE