![]() I took a quick look at the Inspector arguments but drew the same conclusion, voltage seemed quite bothersome to adjust by CLI.Īctually realized that if I check the "Apply settings at Windows startup" in Afterburner i can remove it from autostart, the settings will still be applied, not sure how/why this works. You can also set voltage/frequency points via this API, but it's really tedious and I found that Max-Q GPUs don't offer a lot of undervolting potential.Īh alright, yeah I'm primarily interested in undervolting for now. When I'm loading the CPU a lot, both fans spin without the dGPU being active. The GPU fan turns on when either the CPU or the GPU temperature are reaching a certain level. It is controlled in part by the BIOS and in part by the GPU, so the truth should lie in the golden middle, the EC firmware, which has access to CPU, as well as GPU temperature. The GPU fan is also temperature dependent. My guess is that as soon as the dGPU is turned on, the GPU fan turns on By the way, don't forget that the fan profile is different when the charger is plugged in than when the machine runs on battery. That's really complicated to answer without being one of the engineers who worked on the Blade 15 motherboard and/or firmware.įor me the CPU load resulting from this was making the CPU hover at around 50-55☌ the entire time, which is right around the default trip point. As I wrote, MSI Afterburner polls sensors in a way that Nvidia's driver doesn't seem to like given Razer's implementation. If i set the polling rate to 60 seconds in Afterburner I can hear the fans spin once every minute ![]() I did the same for ThrottleStop by the way. Nvidia Inspector closes itself automatically when called with arguments, so it doesn't hang around after it did its work. You should now have the offsets being applied on logon or shortly thereafter. You can also set voltage/frequency points via this API, but it's really tedious and I found that Max-Q GPUs don't offer a lot of undervolting potential.Īnyway, then you disable all checkboxes in the conditions tab for the task, so that it always runs on logon. You tell it the number of the GPU (0 for the first one), then the P-State for which to set the offset (0 for the high-load P-State, where it matters) and lastly the offset in MHz. This is the content of the arguments textbox: "-setBaseClockOffset:0,0,232" "-setMemor圜lockOffset:0,0,550" Then you create a new action, that is to start an application, with the path to the Nvidia Inspector executable. Then in the scheduled tasks (taskschd.msc) you'd create a new task to run with the highest privileges (so that UAC doesn't ask every time whether to run it) with the trigger of any user logging in. ![]() :) I put Nvidia Inspector into %appdata%\Roaming\Nvidia Inspector. Not as simple as sharing the exported task XML if you want to set it up differently than I have. Mind sharing your Nvidia Inspector start-command/.bat-file? You can do so by simply clicking flair under your link!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |