• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Patriot Viper Steel 3733 kit overclock results good?

Joined
Aug 4, 2021
Messages
182 (0.13/day)
System Name Jamesbondosaurus
Processor Ryzen 5 5600x @ 4.75ghz PBO
Motherboard MSI B550i MPG Gaming Edge MAX Wifi
Cooling Arctic Esport Duo White / Black
Memory Patriot Viper Steel @ 3733 C16
Video Card(s) Inno3D RTX 3070
Storage 120GB PNY CS900. 1TB Crucial BX500. 1TB WD Blue M.2. 8TB WD Red HDD.
Display(s) Gigabyte M27Q
Case Phanteks P200A PE
Audio Device(s) Onboard
Power Supply Super Flower Leadex III
Mouse G305
Keyboard Some cheap mechanical keeb
Software Windows
Benchmark Scores Like 5 FPS if I play Dying Light 2 at 8K.
So managed 3800mhz 16-19-19-27-58 1.45v

Originally 3733 17-21-21-41-69 1.35v

I have not used a Dram calculator.

Stock.

20210817011847_1-jpg.212942


Overclock.

20210817035450_1-jpg.212949
 

Attachments

  • ZenTimings_Screenshot_27152808.7153558.png
    ZenTimings_Screenshot_27152808.7153558.png
    32.1 KB · Views: 1,053
Last edited:
Try to get your tRFC down to between 450 and 550 but with a 2060 it really isn't worth pushing the ram unless you're doing it for fun.
 
Try to get your tRFC down to between 450 and 550 but with a 2060 it really isn't worth pushing the ram unless you're doing it for fun.
Fun, plus emulation needs as much throughput as you can throw at it.
Thanks for the heads up.

I have found my primary timing wall at c16 and frequency at 3800, which to me is completely fine this was an upgrade from Corsair Samsung B die 3000mhz that could not OC at all.
Also brought the voltage down to 1.4v on the Dram and SOC voltage does nothing to get passed those walls.

The FPS improvement in TR is remarkable from that kit.
 
That's a pretty sizeable gain.

It's not 16-19-19, that 19 is tRCDWR which is mostly irrelevant (you can set like 8 if you want to, it's tRCDRD that's "tRCD"). You're running 16-19-27-58.

There's a few things but you kinda need to know what IC this is/might be before you start tinkering. Matters a lot for how low specific timings can go, how much VDIMM can be pushed safely, quirks, etc.

1.2V VSOC seems like a lot for 3800, especially since the CLDOs are relatively relaxed.

If it's Hynix CJR there should be a fair bit of room:

5900x cjr.png
 
That's a pretty sizeable gain.

It's not 16-19-19, that 19 is tRCDWR which is mostly irrelevant (you can set like 8 if you want to, it's tRCDRD that's "tRCD"). You're running 16-19-27-58.

There's a few things but you kinda need to know what IC this is/might be before you start tinkering. Matters a lot for how low specific timings can go, how much VDIMM can be pushed safely, quirks, etc.

1.2V VSOC seems like a lot for 3800, especially since the CLDOs are relatively relaxed.

If it's Hynix CJR there should be a fair bit of room:

View attachment 212950
I have since found out what it is. Hynix C-die using Thaiphoon burner, I had to disbale Malwarebytes to download it.
 
CJR then. Personally wouldn't run anything over 1.4V on CJR, but then again the generic "not-Bdie" safe recommendation is <1.45V so your call. CJR does not really scale anything like B-die with voltage, maybe tCL and that's about it. Some redditors believe 1.4V+ degraded their CJR over time, I'd take it with a grain of salt but still be mindful.

I'd give the timings I sent a reasonable chance of being stable at <1.4V (tCL all the way down to tRFC, but tRFC you will have to consult the chart), but only up to 3733. I had a hard time stabilizing those mundane timings at 3800, tRCD and tRP might have to come up to 20. ymmv. Don't copy the rest of the timings

tCWL 16 and tRDWR 8 are fine if you don't want to push it that hard, but try and drop tRTP a few notches.

CJR is aight as a no-frills daily, if you're looking to have a lot of fun tinkering you'd probably want to look elsewhere.

Reous tRFC list v21 (1).png
 
So managed 3800mhz 16-19-19-27-58 1.45v

Originally 3733 17-21-21-41-69 1.35v

I have not used a Dram calculator.

Stock.

20210817011847_1-jpg.212942


Overclock.

20210817035450_1-jpg.212949

you haven't managed anything until you run prime 95 for 15 minutes and aida64 stability system test for 25 minutes.

I had plenty of ram OC's stable in games, only to crash in other rare games. only way to truly test is to get those two programs stable from my experience, but eh
 
Interestingly and kind of shockingly, my FPS result after drastically lowering other timings lowered the FPS to 188 FPS result, removing any OC and is below the XMP profile performance and still at 3800mhz.
 
I have since found out what it is. Hynix C-die using Thaiphoon burner, I had to disbale Malwarebytes to download it.
So same as my 3600 modules. They seem to sell the 3733 with higher timings, that's all.
These are the best numbers I've managed over time, but I run four modules.

ZenTimings_Screenshot_27153515.4185031.png
 
Last edited:
Interestingly and kind of shockingly, my FPS result after drastically lowering other timings lowered the FPS to 188 FPS result, removing any OC and is below the XMP profile performance and still at 3800mhz.
Could be your vddg iod is too low and you got latency penalty. Try soc 1.1, vddg 1.02, vddg ccd 0.94 and vddp 0.9. Post zentimings with the low timings? Procodt is also too high, try 34. Run all else on auto.
 
Could be your vddg iod is too low and you got latency penalty. Try soc 1.1, vddg 1.02, vddg ccd 0.94 and vddp 0.9. Post zentimings with the low timings? Procodt is also too high, try 34. Run all else on auto.
Unfortunately they can't go that low on the ProcODT at these speeds.
 
Could be your vddg iod is too low and you got latency penalty. Try soc 1.1, vddg 1.02, vddg ccd 0.94 and vddp 0.9. Post zentimings with the low timings? Procodt is also too high, try 34. Run all else on auto.

I'd hesitate to touch procODT unless unstable and exhausted every known troubleshooting avenue. Default procODT rules for CJR and B-die are very different on the Asus/Gigabyte boards I've used. I trust it's not done without a reason.

Interestingly and kind of shockingly, my FPS result after drastically lowering other timings lowered the FPS to 188 FPS result, removing any OC and is below the XMP profile performance and still at 3800mhz.

Have you actually tested if it's stable, or are you just going off whether it can boot and finish the benchmark? HCI Memtest, TM5, Karhu etc. If not this is all a waste of time, most ICs do wacky unexplainable shit in benchmarks if they're anything more than very slightly unstable.

Though honestly with those primaries it's not a surprise, I would much rather take the XMP at 17-21-21-41-69 (as long as it's actually CL17, Geardown off and 2T) and bump the speed up to 3800 with the volts to make it stable. Or even take the XMP primaries and just drop to CL16 and see how much volts it needs.

Rather than use 16-19-27-58-89 and the hodgepodge of timings. That tRP, tRAS and tRC are all way too high although admittedly tRAS doesn't do much aside from influence tRC.
 
Maybe try working the subtimings first and then doing the primaries.
 
Try tRRDS to 6, tRRDL to 8, tFAW to 16 or 20, lower tRP a little more, tCWL between 12 and 14, whatever is lowest, lower tRFC between 540 and 560, whichever works. try tRAS as 35 then lower it, tRC stays high
 
Back
Top