MSI AfterBurner Overclock Application Discussion forum This forum is intended for MSI customers for questions on the AfterBurner Overclock Utility based off Rivatuner. In this section the users help each other out with answers as well as support staff from MSI.

Bad luck for NVIDIA owners then. Don't expect a quick fix. I'm currently busy with more priority tasks, have AlwaysTroublesInside GPUs in all my home PCs and won't be able to start even to investigate it within at least a week.

In meanwhile, can somebody with NVIDIA card and 196.21 run Afterburner/Precison with /BE (Build Emulator) command line switch? It will capture NVIDIA driver's API state into special emulator file called NVAPIEmulator.cfg. I'd like to see the contents of such emulator file, probably it will point out a quick solution.
After doing that, don't forget to remove the emulator file, otherwise Afterburner/Precision will function in hardware emulation mode.

In meanwhile, can somebody with NVIDIA card and 196.21 run Afterburner/Precison with /BE (Build Emulator) command line switch? It will capture NVIDIA driver's API state into special emulator file called NVAPIEmulator.cfg. I'd like to see the contents of such emulator file, probably it will point out a quick solution.
After doing that, don't forget to remove the emulator file, otherwise Afterburner/Precision will function in hardware emulation mode.

From this dump it looks looks like NV changed clock domain IDs due to some odd reason (most likely there are more different clock domains coming in GF100 chips?). So it should be rather easy to fix.
Under such conditions only shader clock control should be disabled in current Precision/Afterburner (I use domain ID checking for shader clock only and always treat the first two domains as core/memory clock domians). Is shader clock control slider the only clock slider disabled now?

From this dump it looks looks like NV changed clock domain IDs due to some odd reason (most likely there are more different clock domains coming in GF100 chips?). So it should be rather easy to fix.
Under such conditions only shader clock control should be disabled in current Precision/Afterburner (I use domain ID checking for shader clock only and always treat the first two domains as core/memory clock domians). Is shader clock control slider the only clock slider disabled now?

Yes the shader is the only one that is disabled and does not display frequency. If you try setting new clocks they return to their original values when you hit apply.

If you try setting new clocks they return to their original values when you hit apply.

Which clocks are you trying to set? Without bumping shader clock core clock is limited by shader_clock/2. Don't think that NVIDIA changed anything besides that, try to boost core clock just a bit to stay within shader_clock/2 range,or change just the memory clock leaving core clock at defaults. Most likely it will work,

Which clocks are you trying to set? Without bumping shader clock core clock is limited by shader_clock/2. Don't think that NVIDIA changed anything besides that, try to boost core clock just a bit to stay within shader_clock/2 range,or change just the memory clock leaving core clock at defaults. Most likely it will work,

Tried what you suggested and still can't get the Shader slider to work. Unless I am misunderstanding your suggestion.

Which clocks are you trying to set? Without bumping shader clock core clock is limited by shader_clock/2. Don't think that NVIDIA changed anything besides that, try to boost core clock just a bit to stay within shader_clock/2 range,or change just the memory clock leaving core clock at defaults. Most likely it will work,

It wont let you adjust memory clock even a little.As soon as you hit apply, it goes back to default.

I've just peeked into issue a bit deeper. The driver uses different domain IDs when reporting and when setting new clocks so it sounds like a bug in the driver and not an intentional overclocking interface evolution. Bugreport is filled and sent to NVIDIA.