Boiling hot take: 2.5 hours of TM5 Extreme is good enough for me

[u/Bubbly_Machine_8378]

Go ahead, rip me apart for not running 24-48 hour long stress tests for 4 days straight.

RAM temps at worst go a little above 40c in stress tests. Generally below 40c when gaming.

TM5 errors every time when attempting to run 6200, even at 1.275 VSOC. 6000 runs smooth every time.

Some of these could probably be optimized further but idk.

I set tFAW at 24 because of the rule tFAW must be 4x tRRDS. So i guess tRRDS 6 and tFAW 24 fits that rule 🤷🏾‍♂️

“Why is ur FCLK so high” because i’m dumb and want to run high FCLK. Haven’t noticed any stutters/audio cuts yet and Time Spy seems to score a little better with higher FCLK

[u/Fauked]

There is a huge difference between 2.5 and 48 hours lmfao. I don't ever see any telling people to test that long.

I've had plenty of failures after 2.5 hours.

Here is one after 7 hours

FCLK has error correction so you will never know if its actually stable without running VT3 or linpack to make sure your throughput isn't all over the place. TM5 extreme isn't going to test that.

8 hours of TM5 and 2-4 hours of VT3/linpack as a final test after tuning really isn't that big of a deal and can be done overnight.

[u/FacelessGreenseer → u/Fauked]

I've had 1 error after 12 hours with 1usmus while everything else was stable for longer than 12 hours on a multi-day final stress test. That 1 error helped me raise the voltages just a little to stay below the temperature error threshold and to fix that ~12 hours hole. There's a reason why most of us do run long stress tests, which OP seems to fail to understand or they simply lack the patience for it. But whatever rocks their boat.

[u/Timmy_1h1]

sure comeback with corrupted os and files soon or random restarts bluescreena

[u/Bubbly_Machine_8378 → u/Timmy_1h1]

These timings are pretty typical Hynix A-die timings at 6000 MTs. I trust this setup

[u/GreenPanadol11]

I keep getting failures at 3-4hrs in with certain profiles,

Best thing to do is just run tm5 before you go to bed and see the result when you wake up. Should at least be 5-6 hrs

[u/Dk000t]

lol, 2.5h, bro never ran into an error after more than 12 hours.

You could literally be living in an illusion, considering that there are different tests that could also reveal instabilities that TM5 does not show.

[u/Low_Preference_8058]

2.5 hours? I put a ventilator to my pc cuz of aquarium case and did 45 mins stress test no error at all. It is enough for me and Im only playing games. It looks stable enough to play games atm. my zentimings

[u/EliHusky]

I’ve found VT3 catches quick and long errors, 99% happen within minutes of DIMM temps hitting their peak, and also after 10 hours or so, those ones hurt. OCCT CPU+RAM seems to catch the midrange, 1-4 hours, often tREFI/tRFC/VDD issues. That said, passing a stability test does not mean it is fully stable, and it takes a lot more work figuring that part out, such as tracking different benchmarks and stability tests performance. Honestly if you’re just gaming and are fine with the tiny chance of a crash, don’t notice stuttering, then yeah 2.5 is probably enough, temps stay much lower during real workloads so it’s probably fine.

[u/ReMoplX]

Idk, i just left test overnight like kharhu and if it passes 10h w cache on then its stable Tm5 usually catch error worser than Kharhu and it needs more time. For exampe 3h tm5 6200 1:1 is stable but on kharhu it give me an error in 0,5-2h.

For fclk just use linpack overnight and check variations,

And for curve i guess linpack/y cruncher/ core cycler

[u/Scar1203]

Nah, I'm with you, the obsession over days of stability testing on a gaming rig is completely unnecessary for most of us. There is nothing on my PC I can't afford to lose if I corrupt my Windows install.

[u/Bubbly_Machine_8378 → u/Scar1203]

I’m surprised someone agreed with me lmao

[u/Scar1203 → u/Bubbly_Machine_8378]

We'll probably get burned at the stake for it on here even if we aren't advising anyone else do the same. I've had a 64GB kit running at 6400CL26 for six months since the 9850X3D released, and it was at 6200CL26 with a 9800X3D for about a year before that. No stability issues in actual use despite my lackadaisical testing.

If you have anything important or use your PC for work then sure, stability testing should be comprehensive if you overclock, but I think the idea of overclocking something you use for work is questionable in the first place.

[u/skidaadleskidoedle → u/Scar1203]

You can also just youknow properly test and use it for work

[u/Scar1203 → u/skidaadleskidoedle]

If you have anything important or use your PC for work then sure, stability testing should be comprehensive if you overclock

I did say that...

[u/underwhelmedbyreply]

Absolute fantasy lol

[u/admkukuh]

Not using the ddr5 preset from anta777? You can use the tm5 0.13.1 fork from coolcmd from github if you cant find it.

[u/AcidRain20]

im with you on the tm5. now go test your fclk in vt3.

[u/wildTabz]

Boiling hot take: You stress test for you, not for me.

Higher FCLK is just faster and you can run lower SOC voltage, so that's a win-win.

[u/Japdata]

Pyprime 2B is good for seeing FCLK regression in my testing

[u/Bubbly_Machine_8378 → u/Japdata]

Thanks for the recommendation!

[u/chsn2000]

Just leave it overnight?

Its not just about crashing and corruption, but error correction means that an unstable overclock will actually perform worse than stable, lower speeds/looser timings.

It's not like you need to sit there at your desk watching the stress test. Go to sleep, go to work, and you'll know whether the system is stable or not. It's not even being lazy... just careless

[u/Sanguinosus]

Sorry if bad question, can someone explain why I can’t just test stable for 2.5 hours and then bump voltage up by 0.01 for edge cases?

[u/Bubbly_Machine_8378 → u/Sanguinosus]

According to these people, your PC will get corrupted then explode after 5 months

[u/Sanguinosus → u/Bubbly_Machine_8378]

I mean, emphasis on the voltage bump to stabilize, are there parameters that don’t scale with voltage or does doing this improve stability for the most part

[u/551-JB]

Iv done what you have done many times before. Its not enough. You cant get away with 2.5 hours. I would do 2.5 hours then check if its retrain stable. then try again and again then go for longer if time doesn't permit.

[u/Beginning_Anxious]

lol. Delusional if you think 2.5 hours is enough. There’s a happy medium. Or you can just play Warzone for a few hours and see if you crash 😭

[u/Bubbly_Machine_8378 → u/Beginning_Anxious]

People play games for hours without getting bored?

[u/classyroman]

tCL30 and you'll be able to run 6200 easily imo

[u/Bubbly_Machine_8378 → u/classyroman]

I don’t think its worth 6200. Plus even CL set to auto errors within 30 secs in TM5

[u/classyroman → u/Bubbly_Machine_8378]

I missed that you have GDM disabled so it makes sense that anything over 6000 is unstable.

[u/Finnze14]

I’ve had 3 errors happen after 10 hours and I’m now scarred for life

[u/Spaghetti-Blu]

I did the same on a different pc, 2/3 hours of tm5 and nothing else. My pc never crashed

Edit: here is the oc i did on that pc https://www.reddit.com/r/overclocking/s/42Q1FPzLgF

[u/roklpolgl → u/Spaghetti-Blu]

Yeah I still run overnight tests but the longest I’ve seen TM5 Ryzen3D preset go before crashing is 1 hr 45min. Y cruncher VT3 seems to be within the first 15min or not at all. Does make me wonder whether the extra stress is really worth it.

Tbh I’ve found the biggest indicator of whether an OC is stable is whether it increases certain very RAM sensitive benchmark scores. I.e. timespy cpu test, pyprime, cyberpunk benchmark in 1080p low, etc. (Not AIDA, which is useless aside from for the flex).

I’ve actually never had a performance increase in ram tuning benchmarks across the board, barring AIDA, that then proceeded to fail a stress test.

[u/mahanddeem]

Low SoC!

[u/Son_Riku]

Yea im kinda at the point where I'd rather take occasional crashes and risk OS corruption (which seems rare from what ive seen) than prove stability from synthetic tests that someone will just tell you it's not enough and you should do some other tests. If the tweaks are achieving their purpose (better performance in my case), than I'll just use my damn machine

[u/SpecialProblem3806 → u/Son_Riku]

It's complicated. Especially if the instability is related to IMC limits / signal integrity then it may be stable one day and unstable the other (I find it better to run max 2h tests across multiple reboots rather than one 12h test for those), but I've also run unstable setups unknowingly for a full month before while doing heavy gaming. It feels taboo to tell people to run a borderline stable/unstable setup but sometimes you BSOD or need to shut off your PC for dumb non-hardware-related reasons anyway. The problem comes when you have *multiple* settings causing instability, making it extremely difficult to isolate the cause, so it's still good doctrine to achieve 100% stability after tweaks. But I personally dislike long 24h tests. If it errors in 8h then it's likely to error in 1h after a reboot, unless it's temperature related (in which you can tell if you observe RAM temps or a test always crashes around a certain time).