- Jun 30, 2004
- 16,539
- 1,973
- 126
OK. I have a dual-boot Win7/Win10 configuration, cloned perfectly to an NVMe M.2 from what had been SATA SSD. I don't think the problem is related to that.
On another system with SLI GTX 970, I had some problems with "stuck" power states for the graphics cards. They wouldn't return to the low-power state, instead choosing to remain at one level below full bore with the OC settings. I would uninstall AFterburner and uninstall the NVidia drivers and the problem would disappear. Then I discovered this is often caused by running software -- like the web-browser, system-tray items, etc.
In Windows 7, the system and graphics card behave perfectly, but I did a lot of trial-and-error tweaking to iron out some glitches and gaming anomalies.
In Windows 10, I'm trying to get the configuration to behave perfectly before adding more software. The other day, while attempting to clock the GTX 1070 parallel to the Win 7 installation, the system froze with the usual graphics symptoms. I don't think that caused my "power-state" problem, though. I think my attention was called to it because of attention to the clock settings, the NVidia drivers and SW, and Afterburner.
In Windows 10, the card runs idle at around 40C, and the power-state stays at the clocks of 1536 and 4000 Mhz -- at stock settings. there must be a power configuration option in either Windows or NVidia Control Panel that will fix this, I just don't know what it is. And obviously, I want good gaming performance -- assured before I install my games.
I'm still reviewing my sys-tray items, but haven't found a culprit. Maybe it's an Aero-mode feature of Win 10.
Any thoughts about this? At idle, the card should clock down to ~145Mhz and 405Mhz. But -- no cigar.
Just went through the hoops resolving a PerfMon problem in the Win 7 part of the configuration -- solved easier than I thought through CMD->lodctr /r. I was hoping somebody could save me some time and trouble on this other problem.
Then -- I can plant the flag and say that I've conquered this monster!
On another system with SLI GTX 970, I had some problems with "stuck" power states for the graphics cards. They wouldn't return to the low-power state, instead choosing to remain at one level below full bore with the OC settings. I would uninstall AFterburner and uninstall the NVidia drivers and the problem would disappear. Then I discovered this is often caused by running software -- like the web-browser, system-tray items, etc.
In Windows 7, the system and graphics card behave perfectly, but I did a lot of trial-and-error tweaking to iron out some glitches and gaming anomalies.
In Windows 10, I'm trying to get the configuration to behave perfectly before adding more software. The other day, while attempting to clock the GTX 1070 parallel to the Win 7 installation, the system froze with the usual graphics symptoms. I don't think that caused my "power-state" problem, though. I think my attention was called to it because of attention to the clock settings, the NVidia drivers and SW, and Afterburner.
In Windows 10, the card runs idle at around 40C, and the power-state stays at the clocks of 1536 and 4000 Mhz -- at stock settings. there must be a power configuration option in either Windows or NVidia Control Panel that will fix this, I just don't know what it is. And obviously, I want good gaming performance -- assured before I install my games.
I'm still reviewing my sys-tray items, but haven't found a culprit. Maybe it's an Aero-mode feature of Win 10.
Any thoughts about this? At idle, the card should clock down to ~145Mhz and 405Mhz. But -- no cigar.
Just went through the hoops resolving a PerfMon problem in the Win 7 part of the configuration -- solved easier than I thought through CMD->lodctr /r. I was hoping somebody could save me some time and trouble on this other problem.
Then -- I can plant the flag and say that I've conquered this monster!
Facebook
Twitter