MRC96

Hi, I've posted a day or two ago but still have this issue. My 1080ti isn't automatically amping up its voltage when under load and I'm lost as to what is going on, I've tried uninstalling driver changing bios rolling drivers back, reinstalling windows and reinstalling windows on a portable ssd (which funnily enough allows for the voltage to change) with that being the case I'm totally at a loss as to what's going on. I'm not sure if it's a windows 10 update or drivers that have caused it or if I've somehow bugged out the gpu's bios? The base clock reported without any overclock added in XOC is 1455, that's how bad things are... its performing worse than a card 1/4 the price right now and I'm losing my mind trying to fix it. Any additional ideas would be hugely appreciated.

Unfortunately I've tried that and accepted my fate of a full reinstall. Luckily I've got more than enough storage space to get everything essential backed up.

If anyone ever ends up here from google, the issue seems to be with windows itself so a reinstall should fix the issue. Pain in the butt I know but it seems to be the only way as even a system restore hasn't solved the problem.

this had been done prior and I've rechecked and the settings are still the same. Only thing that's happened to cause this issue is a crash. I think the main issue is that the voltage is fixed at 775mv. Manual overclocking is working but a crash occurs over 150mhz. GPU boost 3.0 was doing all the heavy lifting before.

So a week or so ago my my GPU crashed while loading into league of legends. The PC stayed on but all the screens crashed. After reboot and ever since the FPS in games has been awful. The gpu no longer seems to overvolt? aka it stay at 787v where as before it was reaching around 1047. likewise the clock speed sits now at 1481 instead of comfortably reaching 2067mhz before. I'm at a loss as to what to do more as I have: Reinstalled GPU drivers, rolled drivers back, rolled back bios. I will be trying a different install of windows 10 next but is that likely to fix it or has a hardware error occurred? Edit: http://www.userbenchmark.com/UserRun/4385044 <- Build