Jump to content

660m forcing p-state 0 not possible anymore


Recommended Posts

For nearly two years I was overclocking my 660m via Nvidia Inspector without any issues. I simply used a desktop shortcut with these paramters:

-forcepstate:0,0 -setGpuClock:0,2,1165 -setMemoryClock:0,2,2600

Everything worked fine the whole time. I'd always see the core clock change to 1165 mhz but today after I updated to 390.00 drivers the only thing that would go up is the memory clock to 2600, p-state as the core clock would not change. I immediately went back to the previous version 358.91 using clean install but the problem remained.

What could've happened?

Bios version is unmodified 80.07.27.00.05 and I'm running on Win7 Home.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.