GPU keeps getting stuck at different clockspeeds

[EvilWiffles]

Ello,

 

I'm running a GTX 970 G1 with custom bios and sometimes when I exit a game, my GPU would get stuck at 540MHz when I try playing another game.

I've decided it might be from Kboost so I installed EVGA PX and tried disabling or enabling it (it doesn't exactly tell me if it was enabled or disabled, it's crap) and now my GPU is stuck at 1290MHz and won't even boost to 1500MHz. I've tried messing with Kboost again but it's still stuck. I tried using DDU and removing all the drivers, removing EVGA application, installing the latest drivers in safemode and nothing has resolved the issue. I even reflashed my GPU and nothing helped.

 

What the literal fuck is wrong with my GPU now?

 

If you want, take a look at my custom BIOS and see if anything is wrong here.

https://drive.google.com/file/d/0BzebaMY6dr-beWtwdU43cXgzRk0/view?usp=sharing

[Leonius]

Ello,

 

I'm running a GTX 970 G1 with custom bios and sometimes when I exit a game, my GPU would get stuck at 540MHz when I try playing another game.

I've decided it might be from Kboost so I installed EVGA PX and tried disabling or enabling it (it doesn't exactly tell me if it was enabled or disabled, it's crap) and now my GPU is stuck at 1290MHz and won't even boost to 1500MHz. I've tried messing with Kboost again but it's still stuck. I tried using DDU and removing all the drivers, removing EVGA application, installing the latest drivers in safemode and nothing has resolved the issue. I even reflashed my GPU and nothing helped.

 

What the literal fuck is wrong with my GPU now?

 

If you want, take a look at my custom BIOS and see if anything is wrong here.

https://drive.google.com/file/d/0BzebaMY6dr-beWtwdU43cXgzRk0/view?usp=sharing

what happenes if you use the stock bios? does the problem still occur? also stupid question, but are the fan and the temps okay?

[EvilWiffles]

what happenes if you use the stock bios? does the problem still occur? also stupid question, but are the fan and the temps okay?

 

I asked for help on overclock.net and only gotten one reply which was useful information.

 

"Just had this issue myself the other day right after the 359.06 driver dropped and Windows 10 updated to the latest November build, I was also using MSI Afterburner to apply oc settings on boot.

I found that if I turn apply settings on boot in afterburner off, then clocks works/boosts as expected, but stuck on stock speeds. As soon as I apply the oc settings manually (instead of auto apply), then the first 3d program (R6:S/Arma3/GTA5 in my case) used will keep the settings, but as soon as I quit the program, the clocks will get stuck on idle profile (540mhz) and subsequent programs will not trigger to card to clock higher. Only a reboot will reset it.

I've not yet tried to revert back the driver to 359.00 yet as I got a good bump in performance in R6:S with 359.06 driver. My current solution is using modded bios so I don't have to use afterburner to oc (just OSD/monitoring only)"

 

So, I guess I cannot overclock at all till this shit gets fixed or go back to old drivers.

[Leonius]

 

I asked for help on overclock.net and only gotten one reply which was useful information.

 

"Just had this issue myself the other day right after the 359.06 driver dropped and Windows 10 updated to the latest November build, I was also using MSI Afterburner to apply oc settings on boot.

I found that if I turn apply settings on boot in afterburner off, then clocks works/boosts as expected, but stuck on stock speeds. As soon as I apply the oc settings manually (instead of auto apply), then the first 3d program (R6:S/Arma3/GTA5 in my case) used will keep the settings, but as soon as I quit the program, the clocks will get stuck on idle profile (540mhz) and subsequent programs will not trigger to card to clock higher. Only a reboot will reset it.

I've not yet tried to revert back the driver to 359.00 yet as I got a good bump in performance in R6:S with 359.06 driver. My current solution is using modded bios so I don't have to use afterburner to oc (just OSD/monitoring only)"

 

So, I guess I cannot overclock at all till this shit gets fixed or go back to old drivers.

 

that sucks, lets hope the issue gets resolved soon...