Jump to content

Godryc

Member
  • Posts

    12
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Godryc's Achievements

  1. Because american corporations make more money by supplying only the cheapest materials.
  2. I should have done this first... The issue is on hold for now, but I will very likely revisit this thread in a few weeks. I need to use my 2nd monitor at work for a while. That's a good suggestion and I will give that a shot when I am able to. I see it as more of a sidestepping of the actual issue, but anything that resolves into a working solution is a good solution. What I'd really like to figure out is what exactly occurred, and why. The only thing I can come up with is the Asus GPU BIOS Updater. I ran it only for the installer to tell me that there was no need to update the BIOS as it was already running the most current version. It was right after that where things began messing up. Prior I was running two monitors just fine with the GPU idling along at 139. This is the best thread on this particular issue to date. I haven't found anything with better resources when I was searching for a fix. Thank you for your replies. I'm sure it will help out someone with the same issue as this is the best thread on this issue out there.
  3. Reporting back after having played around with the Multi Display Power Saver feature from within Inspector for a bit, it seems to be a bit of a bandaid fix as the clocks won't clock themselves UP properly. Typically the clocks will be set at 608MHz while gaming and then shoot up to ~1868MHz from time to time for ~ 2 sec at a time before dropping back down to 608MHz resulting a very laggy and stuttery game experience. I'll fiddle with the thresholds a bit to see if that helps.
  4. I feel a bit stupid now but I suppose I should not merely disabled the second monitor via settings but I should have physically unplugged the monitor. Because after reading the new replies I did just that and it worked. GPU will downclock if the second monitor is unplugged. It's just odd that it seemingly happened out of the blue, I had been running a dual monitor setup for several months now without any hiccups. That does seem to help. My GPU just downclocked for the first time in days simply by enabling this option. However, now my GPU won't clock up when running a game. I'll have to play around with those settings a bit and report back with my results. It is interesting to note that I ran with a dual monitor setup for several months without this issue occuring.
  5. I sure did try that as one my very first troubleshooting steps. I also tried uninstalling geforce altogether. Sorry I forgot to mention that in the OP.
  6. You have no idea how much I appreciate your continued help with this! Here's a screenshot (note the System monitor gadget in the lower right):
  7. Found the GPU setting in Process Explorer, thank you for that! It did not show anything out of the ordinary, ie, no app or program that should be causing the GPU to clock up.
  8. Update: After being able to see the GPU performance using the new W10 task manager, it is verified that there is not an app forcing the GPU to run at higher than what is considered normal at 'idle'. PS: I am rapidly running out of hair to pull out. The idea of reinstalling Windows has crossed my mind, but, UGH.
  9. Hmmm... I can't see where in Process Explorer the GPU monitor is, nor how to add it manually. I'll take another look. I just tried the PCI setting, it did not change the clocks. Something got "hardwritten" somewhere, there has to be some corresponding ini file or a registry entry I can tweak. EDIT: Yeah, I can't figure out how to see the GPU Performance nor how to add it: I might just wait for the forced Fall update to complete. Not a huge deal as my suspicion is it has nothing to do with a background app anyway. Then again I might have to come back and eat my words, lol!
  10. I intuit the issue is a setting, registry or something written directly to the issue. I've pretty much ruled out that there is a process keeping my GPU clocks locked by attempting to reset the Performance Level in NV Inspector. The fact that I am unable to change the Performance Level from a P0 to anything lower tells me there is something else going on and is keeping my GPU locked at a permanent CUDA P0 level. I'll check on the Fall update though so I can verify with certainty and rule that out as the culprit. That 3rd party tool you mentioned seem nifty but seems to have a steep learning curve. I'll look into that further this weekend if I haven't been able to resolve the issue by then.
  11. I should have added that as part of my troubleshooting process so far. The only thing I haven't done is kill the process you mentioned. In addition to the things you mentioned I have also tried disabling Geforce Overlay and Streaming. Some of the forums I have read suggested to set Adaptive in NV Control Panel instead of Optimal. I figured default Optimal would be better, so thank you for confirming that! I'm attaching a screenshot of NV Inspector. It is curious how it will not allow me to change the Performance level from P0 to P2 after applying the setting.
  12. I'm having an issue where my 1070 (Asus Strix will no longer idle below 911MHz (clock) and 4007MHz (Memory). I have attempted: - Googling the issue (most users reporting the issue were able to resolve the problem after uninstalling this program or that, none of which I have installed to begin with) - changed the Power Managment Mode in nvidia control panel from "Optimal" to "Adaptive" - Un/Re-installing Asus Gpu Tweak II - Installing/ Unistalling the newest version of Asus PGU Tweak II - Installing/ Uninstalling MSI Afterburner - Updated to the latest nvidia drivers - set both my monitors from 144Hz to 60Hz - disabled secondary monitor and ran only 1 monitor at 60Hz - Performed two clean installations of the nvidia drivers in safe mode using DDU from guru3d - attempted to change the Performance Level from P0 to P2, P5 and P8 using nvidia Inspector (setting P-State does not apply however, it remains at P0) I'm about to pull out my hair as I do not understand what is causing this or how to fix it. Any help would be appreciated!
×