I've been fighting to get my G.skill Ripjaws V F4-4266C17D-32GVKB to DDR4-4000 on my Asrock z390 Taichi (an infamously bad motherboard for memory overclocking) and managed to get it to 4006Mhz @ 1.45V V-DIMM. I then tried tightening the secondary/tertiary timings down and ran memtest86 for 12.5 hrs. (6 runs), then an orthos 6 core test with maxed dataset size for 4 hrs., prime95 with large FFT's for 2 hrs. and then the built-in windows 10 memory test and all tests passed then Metro: Exodus began crashing every time (and corrupting the auto-saves). After increasing the V-DIMM to 1.65V the crashes completely stopped. It's bizarre to me that a game would be more sensitive to unstable memory than all the memory and CPU test programs I used.
-
Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
Asrock z390 Taichi+DDR4-4000: Metro Exodus as system RAM tester
- Thread starter 80251
- Start date
- Joined
- Dec 25, 2020
- Messages
- 8,078 (5.19/day)
- Location
- São Paulo, Brazil
| System Name | "Icy Resurrection" |
|---|---|
| Processor | 13th Gen Intel Core i9-13900KS |
| Motherboard | ASUS ROG Maximus Z790 Apex Encore |
| Cooling | Noctua NH-D15S upgraded with 2x NF-F12 iPPC-3000 fans and Honeywell PTM7950 TIM |
| Memory | 32 GB G.SKILL Trident Z5 RGB F5-6800J3445G16GX2-TZ5RK @ 7600 MT/s 36-44-44-52-96 1.4V |
| Video Card(s) | NVIDIA RTX A2000 (5090 shipping to me soon™) |
| Storage | 500 GB WD Black SN750 SE NVMe SSD + 4 TB WD Red Plus WD40EFPX HDD |
| Display(s) | 55-inch LG G3 OLED |
| Case | Pichau Mancer CV500 White Edition |
| Audio Device(s) | Sony MDR-V7 connected through Apple USB-C |
| Power Supply | EVGA 1300 G2 1.3kW 80+ Gold |
| Mouse | Microsoft Classic IntelliMouse (2017) |
| Keyboard | IBM Model M type 1391405 |
| Software | Windows 10 Pro 22H2 |
| Benchmark Scores | I pulled a Qiqi~ |
Running very heavy workloads for stress testing only tend to mask stability problems in lighter or bursty workloads where the voltage transients tend to overshoot or overdrop 
That's why I insist on running Prime95 in blend mode instead of just large FFT, and keep ASUS's RealBench around (basically a script that loops lots of relatively heavy production programs)
That's why I insist on running Prime95 in blend mode instead of just large FFT, and keep ASUS's RealBench around (basically a script that loops lots of relatively heavy production programs)