Over the last month, my watt-usage at ~idle (with apps running, but not very active) has gone from:
~120W->250W, CPU/GPU < ~5% (according to process explorer).
I can't seem to bring it back down to anything close to where it was, using the same set of apps, more or less.
I'm using a watt-meter at the plug to see watt usage.
Any suggestion to figure out why the seemingly large increase in power consumption without much if any increase in CPU/GPU usage?
I think it's possible that even legitimate apps I'm using now are using more power than before, but shouldn't such a remarkable change in wattage be reflected in CPU/GPU usage? I.e, what system resources are being used to use all those extra watts?
- Windows 7 Home Premium 64
- i7 920 @2.67MHz
- NVIDIA GeForce GTX 285
- RAM was 6B (3x2GB, speed unknown). Added 12GB (3x4GB 1600MHz). Working in tri-channel. 'My computer' reports 18GB total, 16GB usable.
The lower wattage is possibly when speedstep kicks in and lowers the clock speed and voltage of your cpu. If speedstep kicks off and the cpu ramps back up to full speed, that would cause an increase in wattage. Turn off speedstep in the bios then boot up and check if it fluctuates like that.
I updated/edited my post to reflect that my wattage has gone up, but I can't seem to bring it back down, even if I set max CPU to 1% in Windows Power Settings. Do I need to enable speedstep in BIOS to enable that CPU-max Windows Power Setting? I haven't checked yet in BIOS whether this is enabled or not. Any way to do so without rebooting?
I'm curious to understand why starting e.g. Chrome for the first time adds 30 Watts permanently, even after I close Chome.
I see 2 chrome.exe procs using 3.5% GPU each.
When I close chrome, that GPU usage goes away and no other procs except for csrss.exe (uses 0.7%), but the watts go down by only ~3 if anything.
I'd suspect chrome initialization starts up some e.g. system tasks that eat up CPU or GPU even after it is finished, however, I don't see any GPU usage (according to list of procs in ProcessExplorer) and CPU doesn't go up to make up for anything the GPU was previously doing.
I'll have to double check what CPU is before ever starting Chrome after a reboot to see how much CPU overall, goes up, but doesn't come down, after starting and ending Chrome.
If you know how I might avoid a reboot and clean up any mess starting Chrome might have left, I'd be happy to learn it! : )
Again, turned out it was actually not using as many watts as I thought. The router watt-use went up, and I hadn't expected that. I suppose other users were hitting it hard. I should have separated the router in my test but neglected to. Sorry for all the commotion. However, all the info presented here was helpful. Thanks everybody!