Corsair H170i Elite Capellix XT review
Forspoken: PC performance graphics benchmarks
ASRock Z790 Taichi review
The Callisto Protocol: PC graphics benchmarks
G.Skill TridentZ 5 RGB 6800 MHz CL34 DDR5 review
Be Quiet! Dark Power 13 - 1000W PSU Review
Palit GeForce RTX 4080 GamingPRO OC review
Core i9 13900K DDR5 7200 MHz (+memory scaling) review
Seasonic Prime Titanium TX-1300 (1300W PSU) review
F1 2022: PC graphics performance benchmark review
Download MSI AfterBurner 4.3.0 Beta 4
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.
Download MSI AfterBurner 4.3.0 Beta 3 - 05/27/2016 03: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 06: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 08: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 04: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 08: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...
JonasBeckman
Senior Member
Posts: 17563
Joined: 2009-02-25
Senior Member
Posts: 17563
Joined: 2009-02-25
#5316481 Posted on: 08/04/2016 05:20 PM
Hello,
I got my very first SSD last week and did a clean install of Windows 10 x64 Enterprise Edition. Twice. I just started thinking, that perhaps that can be related? Instead of a startup of over 3 minutes I am now booting up under 20 seconds. MSi Afterburner loads directly after the nVidia driver (Which is loaded first) when I have it installed; unlike EVGA's Precision which seems to take it's time. I have the issue with Afterburner, but not Precision. Perhaps that was what caused the TDR in the first place? I don't know. It's just my observations.
Ah the startup issue, yeah there's been some threads about that in the past for Afterburner from both AMD and Nvidia GPU owners so there's a property in Afterburners main config file for delaying start so it only starts after X amount of time thus giving the display driver (And possibly the OS too.) time to fully initialize first so that could indeed help.
(IE for compatibility with giving the GPU it's proper clock and voltage settings which can be unstable if this is done out of order.)
I'll see if I can't find it's name again.
(Think the value you input was either for seconds or milliseconds.)
EDIT: MSIAfterburner.cfg where you've installed MSI Afterburner too and then this setting:
StartupDelay = 0
And it's in milliseconds.
http://forums.guru3d.com/showthread.php?t=319977
Hello,
I got my very first SSD last week and did a clean install of Windows 10 x64 Enterprise Edition. Twice. I just started thinking, that perhaps that can be related? Instead of a startup of over 3 minutes I am now booting up under 20 seconds. MSi Afterburner loads directly after the nVidia driver (Which is loaded first) when I have it installed; unlike EVGA's Precision which seems to take it's time. I have the issue with Afterburner, but not Precision. Perhaps that was what caused the TDR in the first place? I don't know. It's just my observations.
Ah the startup issue, yeah there's been some threads about that in the past for Afterburner from both AMD and Nvidia GPU owners so there's a property in Afterburners main config file for delaying start so it only starts after X amount of time thus giving the display driver (And possibly the OS too.) time to fully initialize first so that could indeed help.
(IE for compatibility with giving the GPU it's proper clock and voltage settings which can be unstable if this is done out of order.)
I'll see if I can't find it's name again.
(Think the value you input was either for seconds or milliseconds.)
EDIT: MSIAfterburner.cfg where you've installed MSI Afterburner too and then this setting:
StartupDelay = 0
And it's in milliseconds.
http://forums.guru3d.com/showthread.php?t=319977
Legacy-ZA
Senior Member
Posts: 257
Joined: 2011-12-29
Senior Member
Posts: 257
Joined: 2011-12-29
#5316500 Posted on: 08/04/2016 05:53 PM
Ah the startup issue, yeah there's been some threads about that in the past for Afterburner from both AMD and Nvidia GPU owners so there's a property in Afterburners main config file for delaying start so it only starts after X amount of time thus giving the display driver (And possibly the OS too.) time to fully initialize first so that could indeed help.
(IE for compatibility with giving the GPU it's proper clock and voltage settings which can be unstable if this is done out of order.)
I'll see if I can't find it's name again.
(Think the value you input was either for seconds or milliseconds.)
EDIT: MSIAfterburner.cfg where you've installed MSI Afterburner too and then this setting:
StartupDelay = 0
And it's in milliseconds.
http://forums.guru3d.com/showthread.php?t=319977
Thank you for the advice!
I have made the modification to the said file and will definitely re-try using MSi Afterburner. I really got freaked out the other day, checkered black screen and then the BsoD... I still don't know if it could damage my hardware. It was like Aferburner and nVidia's driver was in the battle ring fighting things out, just the ring kept collapsing in the end. lol
But I think this is it; from a logical stand point, it just has to be. I will report back.
Ah the startup issue, yeah there's been some threads about that in the past for Afterburner from both AMD and Nvidia GPU owners so there's a property in Afterburners main config file for delaying start so it only starts after X amount of time thus giving the display driver (And possibly the OS too.) time to fully initialize first so that could indeed help.
(IE for compatibility with giving the GPU it's proper clock and voltage settings which can be unstable if this is done out of order.)
I'll see if I can't find it's name again.
(Think the value you input was either for seconds or milliseconds.)
EDIT: MSIAfterburner.cfg where you've installed MSI Afterburner too and then this setting:
StartupDelay = 0
And it's in milliseconds.
http://forums.guru3d.com/showthread.php?t=319977
Thank you for the advice!
I have made the modification to the said file and will definitely re-try using MSi Afterburner. I really got freaked out the other day, checkered black screen and then the BsoD... I still don't know if it could damage my hardware. It was like Aferburner and nVidia's driver was in the battle ring fighting things out, just the ring kept collapsing in the end. lol
But I think this is it; from a logical stand point, it just has to be. I will report back.
Legacy-ZA
Senior Member
Posts: 257
Joined: 2011-12-29
Senior Member
Posts: 257
Joined: 2011-12-29
#5316506 Posted on: 08/04/2016 06:12 PM
Well, what do you know, that fixed the issue JonasBeckman. I changed my Startup delay to 10,000 (10 seconds) The issue is now history. <3
I think EVGA was wise to put in this delay by default to give the drivers a chance. I am just glad there was a config file to change this for MSi Afterburner, because I really do prefer using it.
The only issue that now remains is this:
I usually setup 2x profiles and save them, one with the defaults and one with my Overclock so I can change between them if I must. It was a good thing I did or I would have had to fix the OC's BsoD in Safe Mode. In any case; If I swap from my default profile to my OC profile, the Power Limit % becomes un-linked from the Thermal limit and vice versa. For example:
OC Profile
Power Limit = 126%
Thermal Limit - 92C
When I swap to my default profile it will look like this:
Default Profile:
Power Limit = 126% (<--- This obviously not being the default)
Thermal Limit - 83C
nVidia's Control Panel also reverts some settings to default after a restart after the new Windows 10 update. Which is what the Reddit thread is about. Though, that just happens to my "V-sync" option.
I was merely curious earlier if this could also be why MSi afterburner did the same?
Well, what do you know, that fixed the issue JonasBeckman. I changed my Startup delay to 10,000 (10 seconds) The issue is now history. <3
I think EVGA was wise to put in this delay by default to give the drivers a chance. I am just glad there was a config file to change this for MSi Afterburner, because I really do prefer using it.
The only issue that now remains is this:
I usually setup 2x profiles and save them, one with the defaults and one with my Overclock so I can change between them if I must. It was a good thing I did or I would have had to fix the OC's BsoD in Safe Mode. In any case; If I swap from my default profile to my OC profile, the Power Limit % becomes un-linked from the Thermal limit and vice versa. For example:
OC Profile
Power Limit = 126%
Thermal Limit - 92C
When I swap to my default profile it will look like this:
Default Profile:
Power Limit = 126% (<--- This obviously not being the default)
Thermal Limit - 83C
nVidia's Control Panel also reverts some settings to default after a restart after the new Windows 10 update. Which is what the Reddit thread is about. Though, that just happens to my "V-sync" option.
I was merely curious earlier if this could also be why MSi afterburner did the same?
vase
Senior Member
Posts: 1652
Joined: 2015-03-20
Senior Member
Posts: 1652
Joined: 2015-03-20
#5316511 Posted on: 08/04/2016 06:21 PM
@legacy-za
just a question on the side.
do you use afterburner to force a custom fan profile?
if now, why not just remove it from autostartup once you have set it up with the correct clocks and powerlimit.
or are you the kind of person who changes the OC every day?
@legacy-za
just a question on the side.
do you use afterburner to force a custom fan profile?
if now, why not just remove it from autostartup once you have set it up with the correct clocks and powerlimit.
or are you the kind of person who changes the OC every day?
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 257
Joined: 2011-12-29
If you upgraded from 10586.x to 14393.x (Win10 anniversary / RS1) the way this works is that the process essentially is a full reinstall of the entire OS although it does keep settings and drivers but still reinstalls them so the current AMD and Nvidia GPU settings (The ones stored in the Windows registry at least.) are reset just as if you did a display driver update.
For Afterburner well I haven't had any problems here but it's a older GPU and version 4.2.0 whereas this is a early public version for supporting the 1080 GPU and probably by now also the 1070 and 1060 although I do not know if the 1060 is supported in this build as it was released fairly recently, same with the Titan X(2) albeit they're all "Pascal" GPU's but that probably doesn't matter much as I'd imagine it still needs specific software support in Afterburner as well.
Anyway reinstalling (uninstalling and then installing it again.) Afterburner or just deleting the config files manually should work to reset any settings to minimize any potential issues with a older / existing configuration.
Hello,
I got my very first SSD last week and did a clean install of Windows 10 x64 Enterprise Edition. Twice. I just started thinking, that perhaps that can be related? Instead of a startup of over 3 minutes I am now booting up under 20 seconds. MSi Afterburner loads directly after the nVidia driver (Which is loaded first) when I have it installed; unlike EVGA's Precision which seems to take it's time. I have the issue with Afterburner, but not Precision. Perhaps that was what caused the TDR in the first place? I don't know. It's just my observations.