See UPDATE below.
Does anyone know if the memory test in OCCT 6.2.2 is actually reliable?
I noticed in their changelog that they recently changed how it works in 6.2.0.
After hours of running it will sometimes show that it found 2, 4 or 6 errors, and sometimes I've restarted and used the same settings that previously gave errors with no errors for 22h+. I also previously tested the memory with the same settings with memtest86 pro 8.3 for > 34h with no errors.
I'm testing using an AMD Ryzen 9 3900x, Asus ROG Strix B550-I Gaming, GSkill Ripjaws V 64GB DDR4 3600 C18.
UPDATE: Under Linux running Linpack I saw an correctable MCE, which appears to be related to Infinity Fabric. But since it was correctable it didn't cause an error in Linpack. So the rare error the sometimes shows up under OCCT might be uncorrectable IF errors. That would potentially explain why it seems so random. I'll to see if I can make the errors go away entirely by increasing the voltage for IF. According to the developer OCCT 6.x doesn't report MCEs but version 7.x will.
Hi,
I am new to adjusting RAM Timings etc., have watched a few videos and read a lot. What you see below is what I ended up with so far. My setup:
Asus ROG Strix B650E-E Gaming Wifi
G.Skill Trident Z5 DDR5-6400 CL32-39-39-102 2x32GB (F5-6400J3239G32GX2-TZ5RK)
Ryzen 7 9700x
In normal use this config was stable, however when running the OCCT memory stability test, it failed after about 90 s due to an error occurring. I tried going down with the FCLK back to 2000 or with the TRAS back to 102. Both had seemingly no effect. Sadly it is still very difficult to get an idea of how tight or lose a timing is or what causes the errors. Maybe someone here has the same kit or someone more experienced can find an obvious error in my configuration. I'd appreciate any help or advice
Videos
Hi, in the latest version of OCCT, there is a CPU+RAM test. In the description, it says it's testing the CPU but the name says RAM.
Is this test enough for memory testing or should I also perform the test that clearly says "memory test"?
If yes, one question: the test lets you choose the amount of memory you want to test. Default is 80%, is there a reason not to test 100%?
What settings should I use on OCCT to stress test ram/fclk/uclk?
I.e instruction set, ram percentage (what percentage should I set?), threads etc???
Thanks
I just got a new pc, with a 5700x3d, 32gb 3200mhz skill ram. I stress tested it in stock config, I got errors detected within a minute of stress testing the default settings in OCCT. I looked online and saw that it might be a ram issue, so I turned off DOCP (so it was running at 2133mhz) and encountered no issues. I tried it again with DOCP on and got errors again. Also with prime 95 errors were encountered on many cores (with DOCP on).
I think it's a RAM issue, but I don't know what my next step should be. Should I just return my ram and get different sticks? Or is there something else I can do?
in OCCT personal (i paid for the license) , for like a 8-12 hour test overight for typical cpu + ram stability, should i do:
medium dataset or large?
variable or steady load type?
auto, fixed, or core cycling mode?
Whats recommended and why? (Mainly looking for memory stability overnight because ive been testing timings and voltages. So far im stable with a 2 hour memory test at 80% memory and no errors.. but i wanted to try the cpu+ram test next because i hear thats the one to do for long durations. Is this true?
Is occt memtest accurate? It show no error after 30 mins of CPU + linpack + mem + GPU but windows resource monitor show a lot of mem hard faults some times even 300/s I'm running a cheap ahh whitelabel b550m, 5700g with pbo enabled and soc tension on 1125mv, 2 sticks of patriot viper 3200mhz cl18 overclocked to 3800 cl20 also overclocking my igpu to 2200mhz with 1200mv
edit: also sorry if I said something dumb it's my first time getting this deep into overclocking
For CPU is it pretty much large data set / extreme mod / variable load / and avx2 instruction set? How about thread settings, leave on auto?
For memory its just 100% / avx2 / and leave threads on auto right? Or there is no need for this as the test for CPU with large extreme avx2 should also work for memory errors too?
I'm afraid my VRAM could be damaged due to some weird artifacts in some games, but I never used OCCT for VRAM damage
Only used it for CPU before, but ended up being very slight degradation which OCCT couldn't detect.
Any tips?
Hi,
Not sure if this is the correct subreddit to post because I’m not tuning RAM or anything. I ordered a new RAM kit that is 64GB 6000 CL26 and it is coming today. I only plan on enabling expo, but I am not gonna tune it or change timings or anything like that. Just gonna hit EXPO and use it like that.
I’ve seen some people question stability of 6000 CL26 RAM. I have a 9950X3D and a ASUS ROG Strix X870E-E mobo. To test for stability, should I run OCCT for an hour or y cruncher for an hour? Or are those tests not good? Just trying to test to ensure the RAM is stable before its return window. Obviously want to avoid data corruption issues that could be caused and damaged components, ya know?
I primarily game and browse the internet and sometimes do film editing in Davinci Resolve. I don’t want to burn up my CPU and am uncomfortable with crazy high CPU temps that I know tests can cause. Any way around this? During gaming, my temps only go to like 65 Celsius.
Thank you!
If my PC passes successfully the CPU+RAM test, is a memory test alone worth it? Also if yes, what amount of ram should I select? Default is 80%, is there a reason for that or should I go 100%?
Follow up to "OCCT ruined my ram OC!". The IMC wasn't happy, that's all it was. I raised IOD from 1000 to 1025mv and that's all it took. Thanks again for the help mates.
VDDG_IOD is for the infinity fabric data links on the IO Die side
Mem controller runs on SOC directly (a bit too low SOC can present with errors on memory tests or mem OC failure)
Part of the memory stuff (the phy) runs on CLDO_VDDP.
Still interesting to present in this way and good fix!
Put your SD's on 2. SD stands for same dimm, but there is no other side of the dimm since your mem is single rank, that timing does nothing and could even be flat out 1. But I've heard from someone that setting it to 2 instead of 1 gives better performance, and after doing some testing I can confirm that. Also try to see if you can run SCL's on 2/2. Try if 4/6 works for DDs. tWR barely errors so I'd leave that value out for last to test bcs it could be mistaken for another timing that gives the error. Rfc could also get some work done. RDWR and RTP look good. You could try to lower cwl to 16 and increase rcdwr to sacrifice some turnaround latency for better overall latency. YMMV, requires some testing. Also for RDWR i use cwl - cl + rdwr = X. X = 8 is great, 10 is ok. You now have a value of 8, so if you lower cwl to 16, that would be 16 - 18 = -2. You could set it to 10 to get to the value of 8.
Hi everyone,
I'm meeting a local seller tomorrow to pick up a 32GB (2x16) G.Skill Trident Z RGB 3200MHz kit. The price is a steal, so I want to make sure I'm not getting scammed.
I know MemTest86 is the gold standard for stability, but running 4 passes at the seller's house is out of the question as it takes too long.
My plan is to bring a USB drive with OCCT and run the Memory Test (Instruction set: AVX2, 80% of RAM) for about 15 minutes.
-
Is 15 minutes of OCCT enough to catch 90% of "broken" modules?
-
Should I change any specific settings in OCCT to make the test more aggressive for a short duration?
-
Is there any other "quick" tool (under 20 mins) that you'd recommend over OCCT for on-the-spot testing?
I managed to bring my memory rated 3000/C15 to 3600/C18 (FCLK 1800), paired with an R7 5700X (stock, no OC, no PBO), by following the DDR4 bible, managing to tighten almost every timing as suggested. I have Gear Down Mode enabled, CR1T. I've ran TM5 extreme by Anta for 2 hours (3 cycles completed), Prime95 Large FFTs + OCCT VRAM, OCCT AVX2 without any trouble, but OCCT SSE starts showing constant errors after a dozen or so cycles. I've tried to tinker with voltages and aimlessly loosen some timings, no improvements. Should I lower frequency? What could make the SSE fail and what exactly do I need to tune?
I had my cheap crappy 4S8D tuned as tight as possible and had passed many cycles of tm5 extreme and absolut but when I decided to tweak my curve optimization with OCCT it became clear that OCCT was finding memory errors, not CPU errors.
I can run 4/4/16 & 4/8 until my ram heats up and OCCT heats it up more than TM5 or Ycruncher. It took a while to figure out what was causing so many errors in OCCT CPU test but it turned out to be RRDS/L/FAW. Raising them to 5/7/20 works. No other timings changes alleviated the errors.
I have a 80mm fan blowing on the dimms but OCCT still causes memory errors. If my PC passes tm5 and Ycruncher, is that enough for a gaming rig? Is OCCT known to overheat ram or am I stuck with 5/7/20? Thanks.
Edit: 4/4/16 relaxed to 5/7/20 and CO adjusted a few pts. Killed my memory performance :(
Alternate 2T profile
Which one is better for Ryzen?