Ripjaws V 3000/15 — any owners?

[NewbieOneKenobi]

As per title, does anyone happen to have owned a pair of these?

I just wonder how much you've managed to squeeze out of them by overclocking, to have a better idea of where I might be headed if I start playing more seriously with them (to reduce the need for step-by-step testing, small increments followed by hours of running memory tests and being unable to use the computer, which is a no-go in my case). So far I've been able to run them at XMP but 3300 Mhz instead of 3000, without touching the timings. This gives better results than OC'ing the CPU, and I can't OC both to the max at the same time, have to choose one or the other (the highest CPU clocks are only stable with XMP off).

My next conundrum is whether I should replace them with faster DDR4 or keep them until DDR5 pricing becomes more reasonable.

 

[NewbieOneKenobi]

Performance board but not top tier — z390 Aorus Pro. No FSB change. The matter is simply that if I put an ambitious overclock on the CPU together with using the XMP profile, Prime95 will crash and sometimes GameSpy also will. A milder CPU overclock combined with XMP works (and produces better results by several hundred points in GameSpy compared to 2133 MHz memory and e.g. 5 GHz CPU), and I can even take the memory overclock a bit beyond XMP. A large CPU overclock without XMP also works (and produces worse results). However, they don't work together. I remember reading it somewhere that you can't always combine a high overclock with XMP, perhaps in the board's manual or settings description in BIOS. I certainly can't understand why enabling XMP reduces the CPU's OC headroom especially yeah, when FSB is not part of the equation. I may be old-fashioned, but I use Prime95 for testing and want it to run stable for 4–5 hours. However, I start from relatively high targets, and some of them crash already in benchmarks or during the first 30 minutes of Prime95 (such as a 5 GHz CPU overclock or even 4.8 on all cores combined with enabling the XMP profile to overclock the memory to 3000 MHz), sparing me the wait. I very rarely encounter situations in which the system can run for 30 minutes stable but can't run for several hours, like crashing after 1–2 hours. It almost always crashes (well, returns an error, not crashes literally) either during the first 30 minutes or not at all. At least with this board.