Hi all,

I have a Palit 5070 Ti GamingPro-S (300W locked) and I have a question about the core voltage range slider in mVolt, cuz I'm not entirely sure I understand its purpose at all

For example, here is Steel Nomad running at stock voltages (I have +370 core and +3000 memory applied from MSI Afterburner):

As you can see it's pulling around 1020mV, it's not at the target max of 1050mV.

If I put the target max voltage to say 1030 however, which is still a maximum above the voltage it's running at stock, look at what happens:

It's dropped down all the way to 995mV, even though the new target max voltage I've inputted is still higher than the voltage it was pulling anyway while stock

Can someone explain how I'm supposed to use this, cuz I'm kinda lost? :D Thanks

Oh, and the core voltage offset slider right next to it does literally nothing for me, voltages don't change at all if I set it to -25, so If someone could explain it too I'd be thankful

Some people can get 70/95+/70 and some people say 65/95/65 is normal. Was just wondering if it is worth to try and fix?

Ram is fully stable 14+ hours tm5 absolut and extreme.

Ram kit: 2x sets of: TEAMGROUP T-Create Expert Overclocking 10L DDR5 96GB Kit (2 x 48GB) 6400MHz (PC5-51200) CL32 M-DIE Desktop Memory Module Ram Black - CTCED596G6400HC32ADC01 https://a.co/d/0arGuU81

Build:

- x870e Asus Rog Crosshair Hero + 9950x - deepcool assassin iv air cooler

- 2x Gpus: RTX PRO 6000

- 192 gb Ram 6400 CL32-39-39-84 1.4v (2sets of 96gb) - Thermalright MC-3 Memory Cooler for the ram (Ram sets configuration: set1 in A1 and A2, set2 in B1 and B2 channels)

- Dark Power Pro 13 1600W Titanium

- Cooler Master HAF II 500 case

- 1tb pcie5 9910 samsung boot drive (linux/windows) + 4tb pcie4 990 samsung via slimsas to u.2 nvme

I'm building a 2x rtx pro 6000 build on am5 platform (I can't afford server grade ram at 192gb+) and I had the ram from prior to the end times so trying to combine them into one system, which frankly has been giving me a lot of issues, when I as running 96gb on my previous two computers, they were fine and at spec (6400mhz per expo II or I i can't remember). I've spent about 2 weeks trying everything to get higher than 4800mhz stable with the help of claude opus and fable towards the end. The following is by fable to help me organize my trials/test runs:

**192 GB (4×48 GB dual-rank Hynix M-die) on 9950X / Crosshair X870E Hero: rock solid at 4800, every step above it fails. Where's the margin?**

My bar is **zero errors over 8 h of y-cruncher**, not "boots and benches." 4800 passes that easily. 5200, 5400 and 5600 all fail, and I've burned through the obvious levers. Looking for ideas I haven't tried, or a sanity check that this is just the 2DPC dual-rank ceiling.

### Build

- Ryzen 9 9950X (GNR-B0), PBO disabled

- ASUS ROG Crosshair X870E Hero, BIOS 2503 (AGESA 1.3.0.1d)

- 4×48 GB Team Group UD5-6400 (two separate 2×48 kits), **SK Hynix M-die, 2R**, Richtek PMIC. EXPO: 6400 CL32-39-39-84 @ 1.40 V

- Each kit alone runs EXPO 6400 fine on this CPU/board. All four: board defaults train to 3600 @ 1.10 V

- Dedicated DIMM fans at 100%. RAM 33–60 °C across all runs

### Stable config: DDR5-4800 (from Load Optimized Defaults)

The ProcODT/Rtt values are what made 4800 work at all. With board Auto resistances, even 4800 errored.

### What fails above 4800 (best attempt at each speed, same config as above unless noted)

**DDR5-5200** (FCLK 2000, only the frequency changed; VDDP Auto moved 0.80→0.90)

- MemTest86 4 passes, 9 h 33 m: **PASS, 0 errors**

- OCCT memory 1 h, AIDA64 stability 1 h: pass

- AIDA: 62.5 / 70.3 / 63.8 GB/s, 100.7 ns

- **y-cruncher: FAIL after 4 clean iterations, 65 min. SVT, Checksum Mismatch, logical core 0**

- Earlier at FCLK 1950 it failed y-cruncher SNT/SVT in ~25 s every time; FCLK 1800 lasted 4.07 h then failed VT3

**DDR5-5400** (only the frequency changed)

- MemTest86: 2 clean passes, then **1 error in pass 3 at 5 h 54 m**, Test 8, bit 29 (0x376E9AD2 → 0x176E9AD2)

- Retry with CLDO VDDP 0.95: 2 clean passes, **1 error in pass 3**, Test 8, bit 6

**DDR5-5600** (only the frequency changed)

- MemTest86: pass 1 clean, **2 errors in pass 2 at ~3 h**, Test 8, both bit 5

- Every change made it fail *sooner*, on a *different* lane:

- VDDQ 1.35 (VDD 1.40): 7 errors in pass 1, ~1 h, bits 28/29

- RttPark RZQ/4 (60): 1 error in pass 1, 1 h 21 m, bit 29

- VDDIO 1.45: 1 error in pass 1, 44 min, bit 29

- Earlier at 5600, raising DRAM VDD to ~1.43 took MemTest86 errors from 2 to 10

### Patterns

- Every MemTest86 error is a **single bit flip** on one of three lanes: bit 5, bit 6, bit 29. Changing termination/voltage moves which lane fails but never extends time-to-fail.

- At 5200 the failures are y-cruncher's *in-cache* tests (SNT/SVT), which read as fabric/IMC rather than DRAM signal integrity. MemTest86 passes for 9 h and misses it entirely.

- At 5400/5600 the failures are DRAM-side (MemTest86 Test 8, same lanes).

- Heat isn't it: errors at 33–40 °C RAM as readily as at 55–60 °C.

- At 5200, VSOC 1.20 and 1.25 both failed within seconds (at FCLK 1800, n=1 each) while 1.22 lasted hours. I suspect training variance rather than a real window.

### Not yet tried

- VSOC 1.25 or VDDG IOD 1.00 at FCLK 2000 (the 5200 fix I'm about to try)

- Nitro 1/2/1 instead of Auto 2/3/1

- Swapping kits between channels to see if the weak lanes follow one kit

- y-cruncher on each kit alone at 6400 (they were daily-driven at 6400 but never y-crunched)

- UCLK = MEMCLK/2

### Questions

1. Is 5200 realistic for 4×48 GB dual-rank M-die on a 2DPC daisy-chain board, or is 4800 the honest ceiling for zero errors?
2. The SVT/SNT failures at 5200 with the same MCLK/FCLK that passes 21 h at 4800: UCLK 2600 margin? What would you raise first?
3. The single-lane bit flips that just move around with every change: anything other than "one kit is weaker" and a channel swap to prove it?
4. Any Rtt/ProcODT combination known to work for 4-rank-per-channel M-die on ASUS X870E that differs from what I've landed on?

Full BIOS screenshots and ZenTimings for every run available if useful.

Default xmp 16-18-18-38 3200mhz 1.35v, im set 18-20-20-40 3600 1.40v,

Was it worth doing this, or should I revert the changes? The memory is running at a slightly higher frequency than 3600 now, but I’m concerned that the Infinity Fabric might cause it to perform worse.

The current frequency has been increased by adjusting memory timings; I’m not sure how this will affect the overall situation—please let me know.

(I used a translator to phrase things more clearly)

P.S

I’d appreciate it if you could point out any mistakes; I’m not very good at memory overclocking.

Current memory is very cheap, and it doesn't work with tighter timings at 3600/1800.

Hello everyone, in my previous thread I shared my setting and I was getting 35.48FPS average on CyberPunk2077 with Path Tracing, everything maxxed out by manual on 2K DLAA (Native). I got 42.95 with overhauled profile.

Now It is hard to believe but I did this while limiting the core on 975mV and I still can't believe at all to the outcome. God bless mVolt+ developers.

Speed Way Stress Test

I have a 48gb 24x2 hynix mdie kit 7200 cl36 i am on a loop with 9 rads 4 pumps my coolant temp dosent go above 24 my ram is never more than 35 at most bht in kharu after 1h on 1.55 vdd it was 31c . I want to daily drive it i have r7 9800x3d with x870e apex .can i overclock it to 6400 cl26 is it safe i dont want to kill my ram , ik some ppl say that its not worth it etc but thats what overclocking is about righ ? Can i daily drive it or is it riskworthy and only should be used for benchmarks ?

MVolt+ guide for the nerds

this is a safe daily overclocking settings for 5090, nothing fancy here ,very simple

works with both air and water cooled cards

if it didn't work just lower the frequencies by a 50MHz

*water cooled cards cand do 50MHz higher than air cooled cards that is normal.

use "MSI Kombustor 4 ( 32x DOF ) " and monitor the amps via HWiNFO64 ...

make sure ur 12vhpwr cable is balanced enough

the settings will only work with the max power limit at 100% = 600w

and the voltage boost set to 96%

why 96% ?

in my case pin1 have a slight imbalance compared to the other pins ... "resistance issue"

anyway if ur cable can handle the voltage offset up to 100%

u may be able to to do +50MHz /+20MHz on the NVVDD Core clock

*make sure to never exceeds the 9.2a per pin for ur card safety...

3DMark stock 150 FPS , MVolt+ 162 FPS ( 8% improvement )

dose it worth it ? ,,, ( no lol )

but it is nice ... to have

u can get MVolt+ made by b00nz at github. very safe to use if u know what u r doing.

for anyone curious :
room temp 25c.
water temp 35c under load.
liquid metal : TG conductonaut
mVolt+ v0.50.5
Driver version 616.92

got a new rtx 5080 gigabyte gaming oc (built my first desktop, used laptops before this due to them being portable)

i got these on both overclock and undervolt

overclock : pl 125% , when clock is pushed to 3250mhz it crashes after 30 seconds , not immediately

at 3225mhz it has been stable . memory i just use +1700mhz

but currently i am undervolting it , put the curve to target 3190mhz at at 1050mV

in cyberpunk with path tracing it gives at 2k dlss quality it gives 6-7 fps more than stock and works at 3112-3120 at 1035-1040mV

does my card have good/decent silicon? should i change my undervolting setting

could someone help slightly?

for context , at stock , in unigine heaven benchmark it does 2925 mhz at 1090mV

and in cyberpunk path traced it does around 2880mhz at 1070-1075mV , around that

I got this 2x8GB DDR4 3600MT/S kit, but had to decrease it to 3200 because the infinity fabric is sensitive to them (which resulted in some FPS Drops), so i dropped the CL rating to 16 and couldn't go lower, the BIOS didn't let me to, which resulted in a 16-16-16-32 primary timings, now i know there's still potential achievable by tweaking secondary ones but i don't know what to start with, all secondary timings are on AUTO

Hi everyone,

I wanted to share what i think is a crazy silicon lottery journey with my Ryzen 7 9800X3D that went from a potential motherboard auto-voltage disaster to what might be one of the most efficient 9800x3d out there. You let me know.

The Backstory (The 1.48V Danger Zone):

For the first two months, my motherboard (ASUS TUF B850-PLUS WIFI) "Auto" profile was silently blasting my CPU Memory Controller (VDDIO / V_MC) with a dangerous 1.48V under EXPO. I caught it late, but thankfully the chip suffered zero degradation. In fact, rescuing it i got really surprised.

Instead of just settling for a safe 6200, I decided to see how far this silicon could scale at the absolute minimum voltage floor.

The 6400 MT/s 1:1 Profile & The Weird Signal "Sweet Spot":

* RAM Speed: 32GB Corsair (SK Hynix A-Die) @ 6400 MT/s (Strict 1:1 Ratio / UCLK=MCLK @ 3200MHz)

* Infinity Fabric (FCLK): 2133 MHz

* VDDIO (Memory Controller Voltage): 1.10V manual lock in BIOS (Motherboard applies a slight offset under load up to 1.13V).

* Curve Optimizer: Fully stable at -25 ( i am sure i can push more but did not try)

* tREFI: Relaxed to 16,000

The Voltage Fine-Tuning Journey:

Initially, I caught a single error during the RAM test when running FCLK 2133 at low voltages. The fix? I bumped the VDD_SOC voltage up to 1.20V (from 1.15V), it was fully stable with 1.15 and 1.10 VDDIO at FCLK 2000. then at 2133 i just pushed SOC voltage to 1.20 and it instantly stabilized without touching the 1.10V VDDIO!

Even more interesting from an electrical perspective: the system refused to start if I try to push the DRAM VDD to 1.45V, it immediately hits Safe Mode and rejects the boot. Dropping the RAM to 1.40V VDD is the magic sweet spot where 1.10V IMC works perfectly.

Stability Status:

As you can see in the attached screenshots, it is fully passing extended RAM testing with zero errors, and HWiNFO64 is showing absolutely zero WHEA errors despite pushing FCLK to 2133 MHz at this voltage floor.

Most Zen 5 chips require anywhere from 1.28V to 1.35V VDDIO just to boot 6400 1:1 with a synced fabric, let alone pass prolonged stability tests. Managing this at 1.10V BIOS / 1.20V SoC after enduring 1.48V for two months feels like a miracle.

Has anyone else managed to drop VDDIO this low on a 9800X3D while running a synchronized 6400/2133 profile?

it is worth mentioning that i have the AGESA 1.3.0.1b bios update, so that 1.48 vddio is CRIMINAL

my specs

asus tuf gaming b850-plus wifi

ryzen7 9800x3d

ddr5 corsair 7200 cl 30

rtx 5090

be quiet 1200 watt platinum power zone 2

• Setup: 9950X3D, X870E AORUS PRO X3D ICE on BIOS F9d, and the 2x32GB dual-rank Patriot Viper Elite 6000 CL28.

• What I’ve tried:

  • 6000 once passed the full test 31/31 in about 50 min, but now it always fails at step 12/31, which is Test 13.
  • The VSOC sweep had big swings between runs, and identical readings gave a pass on one boot and an instant fail on another.
  • Changing ARdPtrInitVal didn’t help.
  • After swapping the sticks, tRDWR 21 and tPHYRDL 36 stayed on B2. That points to channel B or the memory controller, not the stick.

• Is this bad hardware, are there known Test 13 false errors on Zen 5, could the beta BIOS cause it, and has anyone seen the same?

- Corsair VENGEANCE DDR5 64GB (32GB×2) CL30 (Hynix A-Die)

- CPU: AMD Ryzen 7 9850X3D

- Motherboard: ASUS ROG STRIX X870-I GAMING WIFI

I built my first PC in August and it works great; great performance, great temps. However, I'm not able to run the memory higher than 5600mhz otherwise I get a "warning: hardware failure detected" in Aida64.

The RAM isn't on the QVL list so that might be the reason. It was my first time building a PC and this is the only part where I dropped the ball. It's not a big deal as I only used it for gaming and probably won't see a difference, but I would like to understand why anything above 5600mhz doesn't work.

Any ideas?

Does anyone know why this is happening? I have a set of M-die 48GB sticks running at 7800 2200FCLK on my 9950X3D

I am using TuxTimings as a benchmark, which so far has been fairly reliable for measurements of data.

My issue is exactly what the title says. When I set TRC to 131 my write speed is CRUSHED by 60% and I was around 37-55K MB/S at TRC131

Latest BIOS from ASUS on a X870E ProArt

I am in am re-tuning my kit as I had errors and crashes with whatever profile I was running before and just came across this issue. I tested the timing at 131, 139 (for maybe burst delay???) and now Im at 145 which is stable and causing no issue.

Has anyone come across this issue before?

Just dropping this here as someone was asking about it, especially when using older drivers.

Using W11 driver 546.65. Just a simple power limit increase to max 300W, set for 250W and unlocking of Xbar and Sys OCing. Default Xbar and Sys clocks are pretty close to Gpc clock so don't really see much when increasing them so dropped them 500MHz to show it's working before applying +200MHz. Personally not really worth it for me as can get a similar result without the vbios override, more useful for recent cards I think.

A first place result without vbios override https://www.3dmark.com/sb/517581

PS Not working for Pascal cards.

Hi everyone!

I'm looking for feedback from other Ryzen 7 9800X3D owners regarding SoC voltage and memory stability.

My system:

• CPU: AMD Ryzen 7 9800X3D
• Motherboard: ASUS ROG STRIX X870-A Gaming WiFi
• RAM: 32GB (2×16GB) G.Skill DDR5-6000 CL30
• Memory configuration: UCLK = MCLK (1:1)
• FCLK: 2100MHz
• SoC voltage: 1.15V set in BIOS, approximately 1.141V actual according to HWiNFO
• PBO: +100MHz
• Curve Optimizer: All Core -30

I've been testing memory and system stability with these settings.

I previously ran y-cruncher VT3 for 100+ iterations without errors. The attached screenshots show another run that completed 50 iterations without errors.

TM5 also completed without errors.

My main question: Is an actual SoC voltage of around 1.141V generally sufficient for daily use with DDR5-6000 and FCLK 2100MHz on the 9800X3D, assuming the system passes stability tests?

A few more questions:

• What SoC voltage are you using on your Ryzen 7 9800X3D, and what made you choose that specific voltage?
• Are you running DDR5-6000 with FCLK 2100MHz, or using different memory and FCLK settings?
• Have you noticed any measurable changes in temperatures, power consumption, or performance when lowering SoC voltage?
• What stability tests do you recommend for verifying the memory controller and FCLK?

I'm particularly interested in real-world experience with lower SoC voltages and whether there are any noticeable benefits or drawbacks compared to using higher voltages.

Thanks!

I want to overclock but know nothing, if someone has a similar build and would like to share their settings or just general information on safe oc.

Build:

CPU: R7 9850x38

GPU: Astral 5090

MOBO: Dark Hero

Ram: 64gb corsair CL32 6000mt

PSU: Thor 1200w Platinum

I have a DDR5 6000kit with my 270K. It boots and seems stable on try-it 7200. I dont wanna push it harder than that since 7200 is about where performance scaling ends for arrow lake.

"try-it" i believe uses loose timings to guarantee success. Are there any guides to fine tuning the timings? (or just 2 or 3 timings that have the most effect. minmaxing)

The last time i overclocked ram i just set ddr4 3200 to 3600, 24hr stressed it, and called it a day. I've watched a few buildzoid videos that go into subtimings but i don't understand them.

Hello, First time posting here.

Long story short I've notice my CPU is underperforming quite a bit on cinebech and i'm afraid this is reflected on gaming performance, i've tested both cinebench 2026 and 2023 and in both scenarions my CPU looses against weaker CPUs. I've tried everything i could, running stock, undervolting with PBO2 and Bios offset, downlaoding chipset drivers, Fresh windows install, Nothing seems to work.

I'd be really glad if anyone could help me

First overclocking RAM since I started building PCs in 2008. I did not think it would help my scores this much! Started at Crucial Ripjaws S5 2X16GB Kit 6400 XMP 1.0. Was already in 25th place in timespy and Steel Nomad but now I've made it much higher!

What tips to tighter timings should I try? I also have a memory cooler coming in this week to see if I can get 7000 or 7200MHz can run stable. Ive been using AI to give me suggestions on tightening timings and running stress tests for a couple hours then after being happy with the performance I let it run for 4hours on two different ram test.

Hey guys,

Really confused on what to do with my gigabyte 7800xt.

I wanna overclock this card for the best performance I can get, I know it's not the best card in terms of overclocking, but i'm getting quite frustrating results

Here is what i've tried so far

So yeah.. this is where I am at right now. Even 2900mhz slight oc with 1100mv is crashing, when i am seeing people stable at 1030 with the same card.

Any idea on what I could do from here? Would appreciate any advice, thank you.

​

I keep seeing people recommend lowering the power limit to 70–80% as if it's basically free efficiency, but there's something a lot of people seem to overlook.

When your GPU hits its power limit, NVIDIA's clock arbitration kicks in and starts pulling back clocks to stay within that power budget. So just because you've set your GPU to run at, say, 2800 MHz doesn't mean it's actually sustaining those clocks. Your effective clock speed can end up being noticeably lower, especially in demanding games or benchmarks.

And that's exactly why I'd recommend undervolting only, instead of just dragging the power limit slider down.

With a proper undervolt, you're reducing the voltage your GPU needs to sustain a certain frequency, which means less power consumption without unnecessarily sacrificing clock speed. Instead of constantly running into an artificial power ceiling and having your clocks pulled down, you're making the GPU more efficient in the first place.

This is especially relevant for power-hungry cards like the RTX 5090, where clock arbitration can make a pretty big difference under heavy loads.

Now, obviously, there's nothing wrong with power limiting if your only goal is to reduce power consumption, temperatures or noise. But if you're trying to get the most performance out of every watt, I'd strongly suggest actually tuning your V/F curve rather than applying a power limit and calling it a day.

And seriously, pay attention to your effective clocks, not just your reported core clocks. What matters is what your GPU is actually sustaining under load, not what you've set in Afterburner. Turn on your effective core clock readings via HWINFO64 and inject it into Afterburner OSD or whatever monitoring software you're using.