r/overclocking • u/tzawad • 2h ago
Looking for Guide RTX 5070 Ti UV – 3000 MHz @ 935 mV while keeping stock idle clocks (~180 MHz)
Hey everyone,
About a year ago, I was experimenting with undervolting my MSI RTX 5070 Ti Gaming Trio OC Plus.
My main goal wasn't just to reduce voltage or get higher clocks. I was trying to answer one question:
Is there a way to undervolt the GPU while keeping the lower part of the V/F curve close to stock, so the card can still drop to its normal idle clocks (~180 MHz)?
Some of my earlier UV curves resulted in much higher minimum clocks at idle.
I found a curve editing technique online and started experimenting with it in MSI Afterburner. It uses Ctrl + left-click to tilt the V/F curve, Alt + left-click to move it down, and then flattens the curve above the target voltage.
I didn't invent this method, just adapted it for my own testing.
Here's my short demonstration: https://youtu.be/09i5ctr1EDI
Back then, I was aiming for around 3100 MHz @ 935 mV.
After almost a year away from gaming, Call of Duty got me back into GPU tuning. This time I went for a slightly more conservative profile: ~3000 MHz @ 935 mV, which has been stable for me so far (COD MV4)
Some results from 20 loops of 3DMark Speed Way, logged with HWiNFO64
- Target GPU clock: ~3000 MHz @ 935 m
- Average effective clock: 2968 MH
- Reported core voltage under load: 930 mV\
- Average GPU power: 275 W
- Average core temperature: 63.6°C
- Average hotspot temperature: 73.3°C
- Average fan speed: 1426 RPM
- Memory offset: +1000 MHz
- Idle GPU clock: ~180 MHz
Combined_UV_Analysis_RTX5070Ti.pdf
While trying to understand how and why this method works, I used ChatGPT Deep Research and Gemini Deep Research to explore the technical side of it. I then combined the results into a single PDF using Google's NotebookLM.
So the document is basically a mix of AI-generated research and explanations, together with my own test data. I'm not really sure how accurate all the technical conclusions are, or whether they fully explain what I'm seeing.
Full PDF report (Google Drive):
https://drive.google.com/file/d/1KNWMGUgBsxoiEfU1K-WjsZcoxD2DUoM6/view?usp=sharing
What do you guys think? Does the explanation make sense, or am I missing something?
The interesting part for me is not the 3000 MHz target itself, but getting this behavior under load without losing the low idle clocks.
I'm also curious if anyone else has tried this approach or found a simpler way to achieve similar results.



