KernelDrops is right, and it's worth being precise about why so you don't waste an evening on it.
Adrenalin's per-state tuning (Tuning → Custom → the voltage/frequency table) maps to the GPU's DPM states. Your top state is basically state 4/5, and that's what a game or a stress test loads. Idle is state 0, which on RDNA3 is governed by the display engine and the memory clock, not by the V/F curve you edited. So a 1030 mV top-state setting is genuinely useful — it's cutting your gaming power and heat — but it will show exactly zero change in idle draw. That part isn't broken, it's just out of scope.
The 35–45 W idle is almost certainly the memory clock refusing to drop. Verify before changing anything: leave the machine on the desktop for five minutes with nothing open, then look at the memory clock and "GPU only power draw" sensors in GPU-Z or HWiNFO. If the memory clock is pinned near its maximum instead of dropping to a couple hundred MHz, you've confirmed it. The cause is usually the display pipeline needing a fixed memory clock to drive two outputs whose timings don't share a common blanking interval — 165 Hz and 60 Hz don't.
Practical order of attack:
- Set both monitors to the same refresh in Windows. Even 120/120 usually drops you into double digits.
- If that's not acceptable, try the second panel at 60 Hz from a DP port rather than HDMI; mixed outputs are worse than two of the same.
- Check for HDR on one display and not the other, and any custom resolution you've created — both keep the memory clock up.
- Disable hardware acceleration in your browser and chat apps temporarily to rule them out.
- Measure again. On a properly configured dual-display setup you should land somewhere around 12–18 W at the wall for the card alone.
One caveat: some of this is driver-side and has improved and regressed across releases, so don't chase it with a VBIOS flash. If matching refresh rates gets you to ~15 W, take the win and stop there.