Does anybody else experience some problems when trying to overclock the 650m?
For more than 3 years I successfully overclocked my GPU by forcing P-state 1 in NvidiaInspector, but after playing some Fallout 4 this morning, forcing p states no longer seems to work.
Whenever I click on that .bat file, nothing happens, even though it used to work for years...
-I tried resetting the SMC and PRAM several times - no effect.
-I tried several different driver - no effect.
-Completely uninstalling and reinstalling drivers - no effect.
The only thing that still (kind of) works is the standard 135MHz Core overclock...
Here is the content of my .bat file:
nvidiaInspector.exe -setBaseClockOffset:0,0,250 -setMemoryClockOffset:0,0,550 -setpowertarget:0,0 -setVoltageOffset:0,0,0 -setGpuClock:0,2,1150 -setMemoryClock:0,2,3058 -forcepstate:0,1
The only strange thing I noticed is, that there were some visual anomalies in Fallout 4 - a small red or green flicker or some lod/texture flickering. I hadnt experienced it before this morning though. Is it possible that I have a GPU defect? Why would forcing p states suddenly not work anymore?
I hope somebody can help me out!
EDIT: Ok, didnt see this coming: Microsoft .net Framework 4.6 apparently disables forcing p-states - as soon as I removed it (installed it this morning for Fallout4Snip), it all works again. So if anyone experiences the same problem: Remove that framework and all is well again!
For more than 3 years I successfully overclocked my GPU by forcing P-state 1 in NvidiaInspector, but after playing some Fallout 4 this morning, forcing p states no longer seems to work.
Whenever I click on that .bat file, nothing happens, even though it used to work for years...
-I tried resetting the SMC and PRAM several times - no effect.
-I tried several different driver - no effect.
-Completely uninstalling and reinstalling drivers - no effect.
The only thing that still (kind of) works is the standard 135MHz Core overclock...
Here is the content of my .bat file:
nvidiaInspector.exe -setBaseClockOffset:0,0,250 -setMemoryClockOffset:0,0,550 -setpowertarget:0,0 -setVoltageOffset:0,0,0 -setGpuClock:0,2,1150 -setMemoryClock:0,2,3058 -forcepstate:0,1
The only strange thing I noticed is, that there were some visual anomalies in Fallout 4 - a small red or green flicker or some lod/texture flickering. I hadnt experienced it before this morning though. Is it possible that I have a GPU defect? Why would forcing p states suddenly not work anymore?
I hope somebody can help me out!
EDIT: Ok, didnt see this coming: Microsoft .net Framework 4.6 apparently disables forcing p-states - as soon as I removed it (installed it this morning for Fallout4Snip), it all works again. So if anyone experiences the same problem: Remove that framework and all is well again!
Last edited: