MSI Afterburner 3.0.0 Beta 17(2013-11-14)

dack · Dec 30, 2013

hi unwinder, cant find the answer to this but i use AB b17 to undervolt my 290x VDDC and VDDCI, it works great! but after i restart my pc, voltages returns to AMD default although the other overclock/fan settings were restored. I had to hit the profile buttons to restore undervolt settings.

Any idea how to restore undervolt settings on boot automatically? I using the latest AMD CCC drivers. :banana:

Haldi · Dec 31, 2013

Unwinder said: ↑

Happy New Year, guys! Beta 18 will be submitted to MSI today. Changes list includes:

• Added low-level I2C access driver for AMD Bonaire, Curacao and Hawaii graphics processors. Low-level I2C access driver provides much faster access to I2C bus than ineffective native AMD ADL I2C access interface and addresses issues with GPU clock throttling when enabling voltage monitoring on AMD RADEON R9 290 series graphics cards
• Improved AMD ADL access layer with Overdrive 6 support to provide compatibility with future AMD GPUs
• Regular and SE versions of MSI Afterburner are now merged into single installer. Added voltage control mode selection option to the “Compatibility properties” section in “General” tab. Now you can toggle between reference design, standard MSI and extended MSI voltage control modes
• Added “boost edition” / ”GHz edition” GPU type selection option for reference design AMD RADEON 7970 and AMD RADEON 7950 based graphics cards to “AMD compatibility properties” section in “General” tab
• Added GPU usage averaging algorithm for Overdrive 6 capable AMD GPUs. Now displayed GPU usage is being averaged by sliding window to smooth GPU usage artifacts occurring due to bug in AMD ADL API on AMD Sea Islands GPU family
• Added optional unified GPU usage monitoring path via D3DKMT performance counters. Power users may enable it via configuration file as a workaround to replace native vendor’s GPU usage monitoring if it is working improperly (e.g. broken GPU usage monitoring in AMD ADL API for AMD Sea Islands GPU family)
• Added “Use dedicated encoder server” option to “Videocapture” tab
• RivaTuner Statistics Server has been upgraded to version 6.0.0

I guess it will be launched publicly on 30-31 Dec or in the first days of 2014 if MSI are already on Holidays.
Click to expand...

Unwinder said: ↑

We celebrate christmas in January in Russia, so it is still an usual work week here.
Click to expand...

Ahhh that's it ^^
MSI should change software development department to russia xD It always takes ages for new betas to arrive.

Unwinder said: ↑

Just to prevent possible misinterpretations I'll clarify once again: beta 18 WON'T fix jumping monitored GPU usage on 290 series, it is bad AMD driver's coding issue and it can be fixed by AMD driver team only. In beta 18 GPU usage artifacts (spikes/gaps) will be smoothed a bit due to adding special math filtering algorithm aimed special to correct erroneous AMD driver's readings on Hawaii. But the artifacts still will be visible and usage will go up and down, just not that rapidly as before due to post-processing data.
Some users with no expect knowledge in this area tend to insist that it is still broken in AB simply because they don't see that pattern in GPU-Z. Which is not true at all and I'll repeat once again that GPU-Z is simply displaying different performance counter under "GPU Load" name for Hawaii, what you see there is D3DKMT performace counter and not a hardware GPU load sensor reading coming from AMD ADL API. It doesn't (and not supposed to) match with values which you see in AB, CCC or any other vendor's tool working with AMD driver. Those who understand that and still wish to see D3D GPU usage perf counter instead of AMD GPU usage perf counter will be able to edit CFG and force AB to display DX perf counter instead of AMD's one.
Click to expand...

Hei! Look at that! Beta 18 fixxes the buggy GPU load. :stewpid:

But i'm looking forward to the new D3DKMT GPU load methode. I've had the feeling that the 2nd GPU was stuck on 100% in Crossfire even when it was not performing as supposed. wonder what this one will show.

Happy Holidays and all good things for next Year.

Unwinder · Jan 1, 2014

Haldi said: ↑

But i'm looking forward to the new D3DKMT GPU load methode. I've had the feeling that the 2nd GPU was stuck on 100% in Crossfire even when it was not performing as supposed. wonder what this one will show.
Click to expand...

D3DKMT is unfied software performance counter coming from Direct3D runtimes. It doesn't come from GPU registers directly, so it can be easily visible just for the first GPU in multi-GPU config. So I won't be that optimistic to see something useful for CF there as well as I won't use it as permanent monitoring solution. Seeing Sea Islands hardware performance counters fixed in ADL from AMD side is much more preferable way.

BenYeeHua · Jan 1, 2014

Just asking a question about the NVIFR.

1. After deeper testing I've noticed that currently NVIFR works properly in D3D9 applications only. So frame capture performance boost between RTSS 5.4.0 and 5.5.0 can be measured in D3D9 applciations only, D3D1x still fall back to old traditional DirectX based capture implementation. Not sure if it is my implementation or NVIDIA driver issue.
Click to expand...

So, did you find the solution to support D3D1x?
Or it is fixed in newer driver?

Unwinder · Jan 1, 2014

Nope. I asked my contacts in NV to comnent that and haven't had any reply on this topic since that. Probably they try to keep it exclusive for SP only.

kcuestag · Jan 2, 2014

Unwinder, for some reason ULPS does not Disable properly even if I set it to Disable on MSI AB and then reboot the computer.

When I go to regedit, one of the cards (Usually 0000) has EnableUlps set to 1.

Any idea why this is happening? It seems like it also happened to THIS user.

Maybe this is one of the reasons why it also gets crazy GPU Usage?

Please excuse my ignorance, I tried searching but couldn't find others asking about this ULPS issue.

Unwinder · Jan 2, 2014

kcuestag said: ↑

Unwinder, for some reason ULPS does not Disable properly even if I set it to Disable on MSI AB and then reboot the computer.

When I go to regedit, one of the cards (Usually 0000) has EnableUlps set to 1.

Any idea why this is happening? It seems like it also happened to THIS user.

Maybe this is one of the reasons why it also gets crazy GPU Usage?

Please excuse my ignorance, I tried searching but couldn't find others asking about this ULPS issue.
Click to expand...

First, broken ADL GPU usage monitoring issue with Sea Islands has zero relation to ULPS. It applies to single GPU systems as well. Second, it is not necessary to change EnableUlps everywhere, it is enough to change it in active GPU registry keys.

BenYeeHua · Jan 2, 2014

Unwinder said: ↑

Nope. I asked my contacts in NV to comnent that and haven't had any reply on this topic since that. Probably they try to keep it exclusive for SP only.
Click to expand...

Thank for that info, I will wait until ShadowPlay start supporting Optimus, which likely will be using NVIFR to capture the frame.

kcuestag · Jan 2, 2014

Unwinder said: ↑

First, broken ADL GPU usage monitoring issue with Sea Islands has zero relation to ULPS. It applies to single GPU systems as well. Second, it is not necessary to change EnableUlps everywhere, it is enough to change it in active GPU registry keys.
Click to expand...

Thanks.

However, I was having the same issues as that guy from OCN, and after disabling "EnableUlps" (Was set to 1, now 0 and rebooted) I got rid of those crazy framerate drops in Battlefield 4 (Any other game was fine by the way).

Any chance you could consider disabling both for a future version? I know it may not affect most, but it seems like it helps for those having this issue.

Thanks, and happy new year.

Log in or Sign up

MSI Afterburner 3.0.0 Beta 17(2013-11-14)

dack Member

Haldi Master Guru

Unwinder Ancient Guru Staff Member

BenYeeHua Guest

Unwinder Ancient Guru Staff Member

kcuestag Master Guru

Unwinder Ancient Guru Staff Member

BenYeeHua Guest

kcuestag Master Guru

Share This Page