Download MSI AfterBurner 4.3.0 Beta 4

by Hilbert Hagedoorn on: 06/01/2016 09:22 AM | source: | 80 comment(s)

We've just released MSI AfterBurner 4.3.0 Beta 4. This new update once again is intended for more Pascal GeForce GTX 1070/1080 tweaking controls and improvements. Compared to version Beta 3 a new feature was added, you can now fix the Boost MHz and Voltage values by selecting a V/F point in the Curve (CTRL+F) window and then press L.

Here's the complete change-list:

Version 4.3.0 Beta 4

Added GPU Boost 3.0 technology support for NVIDIA Pascal graphics cards:

Added percent based overvoltage support
Added voltage/frequency curve customization support. You may use traditional core clock slider on NVIDIA GeForce GTX 1070 and 1080 graphics cards to apply fixed offset to all voltage/frequency curve points as well as use brand new flexible voltage/frequency curve editor window for more precise per-point curve adjustment. The editor window can be activated with <Ctrl> + <F> keyboard shortcut and it provides you the following features:

You may independently adjust clock frequency offset for each point with mouse cursor or <Up> / <Down> keys
You may hold <Ctrl> key to set anchor and fix clock frequency offset in minimum/maximum voltage point and adjust the offset of any other point with mouse to linearly interpolate the offsets between the anchor and adjustment points
You may hold <Shift> key while adjusting the offset of any point with mouse to apply the same fixed offset to all points. That’s equal to adjusting the offset with the slider in main application window
You may press <Ctrl> + <D> to reset offsets for all points
You may switch between traditional core clock control slider in the main window and voltage/frequency curve editor window to see how they affect each other in realtime
You may press <L> after selecting any point on the curve with mouse cursor to disable GPU dynamic voltage/frequency adjustment and lock the voltage and core clock frequency to a state defined by the target point. This feature allows you to test graphics card stability independently for each voltage/frequency point of the curve using real 3D applications or any stress test of your choice. In addition to stability testing usage scenario, MSI Afterburner allows you to save a curve with locked point setting to a profile, so you may easily switch between dynamic voltage/frequency management and fixed voltage/frequency settings in realtime (e.g. to achieve the maximum performance during benchmarking). Please take a note that fixed voltage and frequency settings do not allow you to disable power and thermal throttling.
Increased default maximum limits for <Core clock>, <Memory clock> and <Memory usage> graphs to improve graphs readability on NVIDIA Pascal series graphics cards

Improved representation of performance limits graphs for NVIDIA graphics cards per NVIDIA recommendations:

<Voltage limit> and <OV max limit> graphs have been merged into single <Voltage limit> graph
<Utilization limit> graph has been renamed to <No load limit> graph
<SLI sync> graph is now hidden on the systems with single NVIDIA GPU

Added uP1816 voltage regulators support to provide compatibility with future custom design MSI graphics cards
Improved validation and handling of erroneous data reported after TDR on NVIDIA graphics cards
Startup profile is now also affected by <Lock profiles> button, which means that you cannot modify or delete your startup overclocking settings while this button is pressed. This feature can be useful to protect startup overclocking settings from modification while temporarily testing various overclocking scenarios on overclocked system
Added support for unofficial overclocking mode with disabled PowerPlay on PowerPlay7 capable hardware (AMD Tonga and newer graphics processors family)
Added ability to use low-level hardware access interface on the systems with AMD graphics cards when legacy VGA BIOS image is not mapped to memory
Fixed bug causing the maximum value to be invisible on some hardware monitoring graphs under certain conditions (e.g. <Framerate> or <Frametime> graphs after closing 3D application)

Download MSI AfterBurner right here.

Related Stories

Download MSI AfterBurner 4.3.0 Beta 3 - 05/27/2016 02:00 PM
In this new build of MSI AfterBurner we have added support for the new GeForce GTX 1070 and 1080. Included is GPU Boost 3.0 technology, meaning all new V/F curve based overclocking with Pascal GPU bas...

Download GeForce 368.25 WHQL for GeForce GTX 1080 - 05/26/2016 05:25 PM
This new driver supports the new flagship GeForce GTX 1080; the most advanced gaming graphics card ever created. Discover unprecedented performance, power efficiency, and gaming experiences&mdash;...

Download Radeon Software Crimson Edition 16.5.3 Driver - 05/24/2016 07:13 AM
A new day a new driver, AMD just released their Radeon Software Crimson Edition 16.5.3 Driver. This update offers optimization for three games - "Overwatch," "Total War: Warhammer,...

Download Nvidia GeForce 368.22 WHQL driver - 05/23/2016 03:34 PM
Download the new Nvidia GeForce 368.22 WHQL driver. It is optimized for Overwatch, World of Tanks, and War Thunder, the Nvidia driver team was working up until the last minute to ensure every perfo...

Download AMD Crimson Catalyst 16.5.2.1 Driver - 05/17/2016 07:07 AM
AMD released yet another driver update, a hotfix that offers up-to 35% more performance on the AMD Radeon R9 390 series products in Doom versus the previous edition released last week. Download...

6 pages 1 2 3 4 5 6

Unwinder
Moderator

Posts: 14519
Joined: 2000-09-05

#5284947 Posted on: 06/06/2016 02:55 PM

So are you thinking it is either a bad graphics driver install or a bug in the driver that is the main cause (I know Nvidia has already acknowledged at least one bug in the current driver affecting fan functionality)? Or could there be something causing a conflict with the driver?

That's not what I'd be worried about, that's driver bug for sure. There was similar issue with total power reporting stuck at 10% in early branch 361 drivers for Maxwell cards as well and it was eventually fixed by NV. Give Pascal drivers some times to be polished.

LocoDiceGR
Senior Member

Posts: 2010
Joined: 2011-10-22

#5284958 Posted on: 06/06/2016 03:17 PM

Can you stop posting nonsense in AB threads please?

VirtualMirage
Junior Member

Posts: 14
Joined: 2016-06-04

#5284960 Posted on: 06/06/2016 03:21 PM

That's not what I'd be worried about, that's driver bug for sure. There was similar issue with total power reporting stuck at 10% in early branch 361 drivers for Maxwell cards as well and it was eventually fixed by NV. Give Pascal drivers some times to be polished.

Thanks for the speedy reply. I guess I will be patient. This is the first time in a long time that I have been a first adopter of a new video card. I've usually waited a bit before buying a new video card. If it wasn't for me upgrading to a 4K monitor, I would have waited. I think the last time I jumped on the early band wagon was back in the 2001-2002 with the Geforce 3/4 and All-In-Wonder 9700 Pro.

At the very least the problems are not catastrophic and are fairly easy to fix (thankful for my Samsung 950 Pro M2 and quick reboots). It's just annoying at this point.

Unwinder
Moderator

Posts: 14519
Joined: 2000-09-05

#5284968 Posted on: 06/06/2016 03:41 PM

Its not nonsense,

Dont try to convince people that your software dont have BUGS.

Don't you assume that probably I can see a "bit" deeper than you which task are performed inside this software and which tasks are out of its control and performed inside display driver and hardware?
I'm starting getting tired of your strange posts in 4.3.0 beta threads, starting from requests to improve Tonga voltage control, debates about Tonga EOL (when in fact even Fiji is not a development priority now) and ending by statements declaring that releasing new beta just for Pascal has no sense. That is what I call nonsense and I'd really like to avoid wasting time on commenting it. Stop that please.

LocoDiceGR
Senior Member

Posts: 2010
Joined: 2011-10-22

#5285007 Posted on: 06/06/2016 05:03 PM

Don't you assume that probably I can see a "bit" deeper than you which task are performed inside this software and which tasks are out of its control and performed inside display driver and hardware?
I'm starting getting tired of your strange posts in 4.3.0 beta threads, starting from requests to improve Tonga voltage control, debates about Tonga EOL (when in fact even Fiji is not a development priority now) and ending by statements declaring that releasing new beta just for Pascal has no sense. That is what I call nonsense and I'd really like to avoid wasting time on commenting it. Stop that please.

Unreal. Im out. :puke2:

VirtualMirage
Junior Member

Posts: 14
Joined: 2016-06-04

#5288800 Posted on: 06/13/2016 05:09 PM

I'm curious, while I understand that Afterburner needs to be running in the background in order for the custom fan and OC profiles to work, does it need to keep in constant contact with the video card in order for it to retain the profiles?

As an update, I am still seeing the issue I described before. However, this time I decided to do a clean uninstall of the drivers and software. I uninstalled Afterburner, Riva Tuner, Geforce Experience, and used DDUD to completely remove the video card drivers. I then installed the latest Nvidia driver 368.39.

Everything seemed to be working fine with just the drivers (basing on benchmarks and actual gameplay, furmark showed me clock speeds). I then installed Afterburner. At first everything seemed to be working fine with no issues. I ran several tests and played through my games quite a bit with no problem. Then the problem started to come back. But this time I had profiles saved in Afterburner. So instead of rebooting the PC, I would just change the profile. Once I selected a different profile the issue would resolve itself and run fine until the next time it acted up.

I've even done this "profile reset" mid game where after loading up the game, I noticed the clock speed didn't ramp up and the game's frame rate was very low, choppy. I minimized the game window, opened Afterburner and refreshed the profile, and went right back into the game right where I left off. The game ran perfectly fine at full clock speeds (including boost) without issue for the next hour or so I was playing.

Again, nothing in the event logs indicating a failed driver. The chart data looks no different than before, memory speeds seem to be unaffected when this happens, the GPU clock speed that it caps at wouldn't always be the same (sometimes in the 800s, sometimes in the low 1,000s, etc.).

The only commonality that I see is that I notice whenever the problem does occur it is when I bring the monitor out of sleep. I have the machine's power profile set to high performance, the machine does not get powered off, hibernate, nor put to sleep. Only the monitor is set to go to sleep after 20-30 minutes. I don't recall it happening every time the monitor goes to sleep, but when it does occur it is after the monitor comes out of sleep (I've never seen it happen while actively using the machine or in the middle of gaming). The 4k monitor is connected via DisplayPort and is G-sync enabled. DisplayPort Deep Sleep has been disabled.

PhazeDelta1
Moderator

Posts: 15616
Joined: 2010-09-12

#5289802 Posted on: 06/15/2016 02:26 AM

Unwinder, can you please add the following to the rtss applications profile list and set application detection level to none for all 3?

PowerDVDMovie.exe

PowerDVD16Agent.exe

PowerDVD16ML.exe

Noisiv
Senior Member

Posts: 6664
Joined: 2010-11-16

#5289812 Posted on: 06/15/2016 03:16 AM

Did u remove AB to see if the 'problem' still exists?

If No its AB problem.

That's a common misconception.
Bear with me please.

You could have a perfectly healthy system, and AB could be 100% bug free and working as intended.
Yet your system + AB = kaboom!

And then you say, ah but all I've added is AB. So it must be AB's fault, right?
RIGHT? Wrong.
Your perfectly healthy system was deemed healthy by you doing CD, EF, GH etc kind of things.
Yet if it does a perfectly legal operation which AB asks it to do, it brakes. It does not mean its AB bug.

In fact in this little hypothetical, yet perfectly plausible example of mine - it's clearly your PC's fault.

VirtualMirage
Junior Member

Posts: 14
Joined: 2016-06-04

#5294407 Posted on: 06/24/2016 03:20 PM

Another update:

This past Sunday I decided to disable the option to have my monitor go to sleep after a set time period. Ever since I have disabled that I haven't run into gimped clock issue. Now it has only been just short of a week, so it isn't definitive, but this is the longest I have gone without issues (before the issue would occurred at least once or twice a day). Of course, now I have to remember to turn off my monitor manually every time I step away from the computer, but at least the clock speeds on the GPU are not acting up.

As mentioned before, I don't have any other power save features enabled on the PC. Windows is set to High Performance, C-State is disabled in the BIOS, and sleep and hibernate options are disabled. I only had the monitor go to sleep after 20-30 minutes.

Now the question is why does the monitor power save option randomly gimp the GPU clock speed? Secondly, is it just the video driver itself that is at fault or is it a combination of Afterburner's interaction that is causing the problem (this is where earlier I was questioning what Afterburner needs and does to communicate with the video card)? Something else? I've never had this happen before.

On another note, I know the app is still in beta, but I did notice something weird occur once or twice with it when tinkering with overclocks. I decided to use the curve chart to set my overclocks, which worked great (I did the shift click drag method to adjust the whole curve at the same time). But once or twice the app acted like it "forgot" the curve setting and reverted my settings to a lower, previously set overclock (which was set using just the slider method). It was either after a reboot or closing and reopening the app when this occurred. My overclock was saved as a profile, yet it changed/reverted the profile. Something random.

Unwinder
Moderator

Posts: 14519
Joined: 2000-09-05

#5294938 Posted on: 06/25/2016 01:22 PM

I'm curious, while I understand that Afterburner needs to be running in the background in order for the custom fan and OC profiles to work, does it need to keep in constant contact with the video card in order for it to retain the profiles?

You're misunderstanding fundamental thing. AB doesn't need to be running in background for custom OC profiles to work. Overclocking is not a dynamc process for any OC software and I repeated a few times in this thread that GPU Boost clock controller is doing all the dynamic clock/voltage control job independently of any applications. The only thing thah is done by AB or any other similar overclocking applications is passing desired clock/voltage offsets to NVIDIA driver, it is being done just ONCE when you specify new clock settings and click "Apply" or load previously defined OC settings via profile. All the subsequent dynamic clock freqency changes are NOT HANDLED BY SOFTWARE.

LocoDiceGR
Senior Member

Posts: 2010
Joined: 2011-10-22

#5294974 Posted on: 06/25/2016 03:06 PM

Are you working on RX 480 support and stuff like that?

Any new Beta coming?

Unwinder
Moderator

Posts: 14519
Joined: 2000-09-05

#5294990 Posted on: 06/25/2016 03:56 PM

480X had to be sent from Taiwan to me this Thursday. It didn't arrive yet.

VirtualMirage
Junior Member

Posts: 14
Joined: 2016-06-04

#5295205 Posted on: 06/26/2016 03:40 AM

You're misunderstanding fundamental thing. AB doesn't need to be running in background for custom OC profiles to work. Overclocking is not a dynamc process for any OC software and I repeated a few times in this thread that GPU Boost clock controller is doing all the dynamic clock/voltage control job independently of any applications. The only thing thah is done by AB or any other similar overclocking applications is passing desired clock/voltage offsets to NVIDIA driver, it is being done just ONCE when you specify new clock settings and click "Apply" or load previously defined OC settings via profile. All the subsequent dynamic clock freqency changes are NOT HANDLED BY SOFTWARE.

Sorry, I did understood it as that when the GPU and drivers are sent the OC profile the GPU does all the dynamic work. What I didn't understand earlier until now was if the OC software had to remain open in the background to enforce the change since I was under the assumption that the OC profile was not editing the BIOS of the GPU to keep the changes (I was thinking of it more as a LUT, if anything). I wasn't trying to assume that the OC software was doing all the work of choosing what clock speed and when. That's why I kept referencing the software, thinking of it as acting as more of a LUT and wondering if the connection between the software and the drivers had to be constant, which lead me to wonder about the monitor sleep mode and it (so far as I can see) as being the culprit between it breaking or resetting this link.

But if that is not the case then, then I still wonder why the monitor sleep mode randomly gimps the clock speed when the monitor wakes up.

cutepuppy671
Member

Posts: 73
Joined: 2008-12-16

#5296029 Posted on: 06/27/2016 11:18 PM

Is there a way to fix the error message that keeps popping up, stating

RivaTuner Statistics Server "Cannot establish connection with the update server!"

VirtualMirage
Junior Member

Posts: 14
Joined: 2016-06-04

#5296074 Posted on: 06/28/2016 12:38 AM

Is there a way to fix the error message that keeps popping up, stating

RivaTuner Statistics Server "Cannot establish connection with the update server!"

You can disable it from trying to contact the server if you want, that is one way to stop the error message.

Open up the RivaTuner Statistics Server (you might find it in your notification area), Click the crescent wrench, and change the "Check for available product updates" to "never".

6 pages 1 2 3 4 5 6

Post New Comment

Click here to post a comment for this news story on the message forum.