Gaming has been Samarveer’s greatest passion, and the Literature graduate in him takes immense joy in dissecting games for their themes, messages, and impact. Samarveer holds a deep appreciation of gaming, and considers the platform to be the most immersive and impactful across all media. He can be found engaging with gaming communities online, always ready to debate the finer points of ray tracing or itching to write an 8-page collegiate thesis on any game that impacts him emotionally.

I've spent months wondering why my RTX 4070 Ti seemed to have forgotten how to idle. With nothing running, it would sit at around 38–40W power draw, with the memory clock pinned at a whopping 1337MHz. This doesn't sound catastrophic — in fact, even my GPU fans weren't turning at idle — but when a GPU is doing nothing, watching it pull that sort of power 24/7 is hard to ignore.

At first, I assumed this was simply the price of running a high-refresh-rate dual-monitor setup. After all, I had a 240Hz OLED sitting alongside a 144Hz display, and everything worked perfectly otherwise. But the more I dug into those numbers, the less satisfied I became. There had to be a reason the GPU was working this hard while doing absolutely nothing, and soon enough, I found a fix buried several menus deep inside my PC.

My dual-monitor setup was keeping the GPU awake GPU-Z showed me exactly where the power was going

The first thing I had to look at was my display setup. I was running two monitors: my Alienware OLED at 240Hz and a second IPS display at 144Hz, both at 1440p. Everything worked perfectly, but that combination had apparently convinced my RTX 4070 Ti that idling was beneath it.

I installed GPU-Z and opened its Sensors tab to see what the GPU was actually doing at the desktop. The numbers immediately explained why I had been staring at surprisingly high idle power for months. My memory clock was sitting at 1337MHz, while GPU power draw hovered between 38W and 40W. This was not exactly what I expect from a GPU with nothing more demanding to do than display a desktop.

The most likely culprit was the display bandwidth. With two monitors running at different refresh rates, the pixel-clock requirements can apparently prevent the VRAM from dropping into its low-power idle state. Instead, the memory stays at its full P0 data rate, dragging power consumption along with it.

That gave me a proper lead rather than another Windows tweak to blindly throw at the problem. The question was whether the most common "solution" would convince the VRAM to calm down or not.

I tried the fixes everyone recommends Matching refresh rates helped, but not enough

My first test was the obvious one, and it was implementing a "solution" that almost everyone on the internet recommends. I dropped the Alienware from 240Hz to 144Hz, matching it to my second monitor. If the mismatched refresh rates were responsible for keeping the VRAM awake, this should have been the easy fix. To be fair, it did do something, but not enough.

The memory clock dropped from 1337MHz to 635MHz, while idling power consumption fell from roughly 38–40W to around 33W. So, the theory was clearly pointing in the right direction. The problem was that the GPU still wasn't properly idling.

There was another problem, too. I had just bought a 240Hz OLED. Even if this trick had worked, I would have been deliberately running it at 144Hz, simply to save a few watts at the desktop, which would have felt like an absurd compromise every day of the week. I wanted the refresh rate I had paid for, instead of a permanent reminder that my GPU had apparently developed an aversion to low-power states.

So, I tried something more drastic and switched off the second monitor entirely, just to be able to pinpoint the problem beyond any doubt. After a quick reboot, GPU-Z showed the memory clock dropping all the way to 100MHz, while power consumption settled around 20W. That was the confirmation I needed.

The monitors weren't merely correlated with the problem; the dual-display configuration was clearly keeping the memory from reaching its proper idle state. Now I knew what was causing the excessive power draw. The harder part was finding a way to keep both monitors running at their full refresh rates without making my GPU burn 40W doing absolutely nothing.

The fix was hiding in NVIDIA Control Panel Reduced Blanking let me keep both monitors at full speed

The solution was to lower the pixel clock without actually sacrificing meaningful refresh rate. As such, I went into the Nvidia Control Panel and clicked on Change Resolution. I first selected the primary 240Hz display, and created a custom resolution. Here, I kept the resolution and color-depth intact, while setting the refresh rate to 239Hz. The important part was changing the timing standard to CVT Reduced Blanking (CVT-RB), which reduces the blanking intervals and therefore the pixel-clock requirement.

I followed a similar process for the 144Hz display, setting it to CVT-RB and a 143Hz refresh rate. A Windows reboot followed, and once I saw the desktop again, I immediately opened up GPU-Z to check if things had worked.

After the reboot, GPU-Z finally gave me the numbers I had been chasing. Both displays were still running at essentially their full refresh rates, but the memory clock that had dropped from 1337MHz to 635MHz finally dropped to around 101MHz. At the same time, idle power consumption fell from the high 30–40W range straight down to just 21.5W. I had sacrificed one frame per second, and gained nearly half the idle power draw — that's a trade I can happily live with.

The fix was hiding in plain sight

There's something incredibly satisfying in fixing a problem that has been annoying you for months, especially when the solution turns out to be buried inside a menu you have probably opened a hundred times. PC hardware does have a strange habit of making perfectly normal behavior look like an unavoidable limitation, right up until you find the one setting that changes everything.

I also suspect this is why I enjoy troubleshooting my own hardware more than simply accepting an answer from a forum. The internet is full of perfectly reasonable fixes that work for most people, but "works" and "works without compromising the setup you actually paid for" are two very different things. Sometimes, getting the latter means digging one menu deeper and refusing to settle for the obvious answer.