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...
-Tj-
Senior Member
Posts: 17803
Joined: 2012-05-18
Senior Member
Posts: 17803
Joined: 2012-05-18
#5284279 Posted on: 06/04/2016 05:34 PM
The only reason for a GPU to drop like that is very low GPU utilization / or it kick into a hardware SAFE mode, typically in combo with a driver crash and instability.
This,
Happened to me on Fermi, Kepler and now Maxwell when OC'ed too much
The only reason for a GPU to drop like that is very low GPU utilization / or it kick into a hardware SAFE mode, typically in combo with a driver crash and instability.
This,
Happened to me on Fermi, Kepler and now Maxwell when OC'ed too much
VirtualMirage
Junior Member
Posts: 16
Joined: 2016-06-04
Junior Member
Posts: 16
Joined: 2016-06-04
#5284300 Posted on: 06/04/2016 06:23 PM
Monitoring is nothing new to me, it's actually what I do professionally in a large data center. I've always done monitoring on my home PC, did so with my GTX 970 and my GTX 560 Ti before it using Afterburner and my Logitech G15 keyboard. I've been really happy with the software and your work, so it isn't a question in quality of workmanship. I am just trying to figure what is causing this anomaly, whether or not it is directly or indirectly related to Afterburner is what I am trying to determine or if it is just pure coincidence and I need to look elsewhere. I am just starting my path at where the most recent change occurred when the problem started, a process of elimination. And if it was a bug, I just wanted to bring it to someone's attention.
I know prior to installing the beta and playing "blindly", I wasn't having such issues because the performance difference and benchmark results are largely different. Also, the sound of the fan when running in "gimped" mode versus normal is quite noticeable too. In "gimped" mode the temps hardly go up enough for the fan to spin up whereas in normal mode you do hear the fan spin up after playing for a bit in games such as GTA V.
I was hoping to receive some guidance to find the cause and, ultimately, find a solution from maybe someone else that has experienced similar problems.
I'll continue to troubleshoot and will post any updates I come across.
If you install software to "view some monitoring", you absolutely cannot say how your system behave when you don't monitor it in background. You're misundersranding fundamental basic principle: GPU Boost 3.0 is NOT handled dynamically on MSI AB or any other software side, it is purely closed NVIDIA driver/hardware technology transparent for applications and you cannot directly alter clock management from software. Besides "safe" mode after TDR the factors that may limit the performance in realtime are reflected on appropriate graphs: power limit, thermal limit, voltage limit and no load limit. This way GPU Boost is giving you some feedback and allowing to see current performance limitation reasons vector. And if it confuses you then peobably the best choice for you would be playing blindly, i.e. without seeing realtime hardware state.
Monitoring is nothing new to me, it's actually what I do professionally in a large data center. I've always done monitoring on my home PC, did so with my GTX 970 and my GTX 560 Ti before it using Afterburner and my Logitech G15 keyboard. I've been really happy with the software and your work, so it isn't a question in quality of workmanship. I am just trying to figure what is causing this anomaly, whether or not it is directly or indirectly related to Afterburner is what I am trying to determine or if it is just pure coincidence and I need to look elsewhere. I am just starting my path at where the most recent change occurred when the problem started, a process of elimination. And if it was a bug, I just wanted to bring it to someone's attention.
I know prior to installing the beta and playing "blindly", I wasn't having such issues because the performance difference and benchmark results are largely different. Also, the sound of the fan when running in "gimped" mode versus normal is quite noticeable too. In "gimped" mode the temps hardly go up enough for the fan to spin up whereas in normal mode you do hear the fan spin up after playing for a bit in games such as GTA V.
I was hoping to receive some guidance to find the cause and, ultimately, find a solution from maybe someone else that has experienced similar problems.
I'll continue to troubleshoot and will post any updates I come across.
Unwinder
Moderator
Posts: 16274
Joined: 2000-09-05
Moderator
Posts: 16274
Joined: 2000-09-05
#5284387 Posted on: 06/04/2016 11:28 PM
I was hoping to receive some guidance to find the cause and, ultimately, find a solution from maybe someone else that has experienced similar problems.
If you don't see the guidance, it doesn't mean that it is not provided.
Reading the recent posts carefully, you could collect some useful info there and most important find out that your target (i.e. GPU Boost dynamic clock frequency control) lies outside of any software, then try to pay attention to GPU Boost feedback provided in form of performance capping reasons vector.
Looking at performance capping related set of graphs in HW monitoring module and seeing which GPU Boost performance limits exactly is holding the clocks you could answer your question.
I was hoping to receive some guidance to find the cause and, ultimately, find a solution from maybe someone else that has experienced similar problems.
If you don't see the guidance, it doesn't mean that it is not provided.
Reading the recent posts carefully, you could collect some useful info there and most important find out that your target (i.e. GPU Boost dynamic clock frequency control) lies outside of any software, then try to pay attention to GPU Boost feedback provided in form of performance capping reasons vector.
Looking at performance capping related set of graphs in HW monitoring module and seeing which GPU Boost performance limits exactly is holding the clocks you could answer your question.
VirtualMirage
Junior Member
Posts: 16
Joined: 2016-06-04
Junior Member
Posts: 16
Joined: 2016-06-04
#5284436 Posted on: 06/05/2016 02:36 AM
If you don't see the guidance, it doesn't mean that it is not provided. Reading the recent posts carefully, you could collect some useful info there and most important find out that your target (i.e. GPU Boost dynamic clock frequency control) lies outside of any software, then try to pay attention to GPU Boost feedback provided in form of performance capping reasons vector.
Looking at performance capping related set of graphs in HW monitoring module and seeing which GPU Boost performance limits exactly is holding the clocks you could answer your question.
While I hope it doesn't happen again, I'll take a closer look at the other parameters. But from what I recall, I didn't notice anything else deviating that would cause a cap (e.g., temp was well below threshold, power wasn't fluctuating or capped, fan speed wasn't capped, CPU wasn't heavily loaded, etc.). What is interesting, and maybe you know, is that when this did occur it did not affect the memory clock speed, just the GPU clock speed. Where as in normal desktop and idle scenarios both the GPU and memory clock run at a lower speed (typically GPU at 139 MHz and memory at 405 MHz) and both ramp up when a graphical load occurs, in these instances the memory clock speed would still ramp up to 5000 MHz but the GPU will gimp, only going up to around 865-1066 MHz.
Is that normal for when the video card goes into safety mode or when the drivers go unstable? Or is it expected for both GPU and memory clock speed to run lower?
Also, I did just stumble on a way to log the monitored data to a file. That will certainly be helpful.
Thanks again!
If you don't see the guidance, it doesn't mean that it is not provided.
Reading the recent posts carefully, you could collect some useful info there and most important find out that your target (i.e. GPU Boost dynamic clock frequency control) lies outside of any software, then try to pay attention to GPU Boost feedback provided in form of performance capping reasons vector.
Looking at performance capping related set of graphs in HW monitoring module and seeing which GPU Boost performance limits exactly is holding the clocks you could answer your question.
While I hope it doesn't happen again, I'll take a closer look at the other parameters. But from what I recall, I didn't notice anything else deviating that would cause a cap (e.g., temp was well below threshold, power wasn't fluctuating or capped, fan speed wasn't capped, CPU wasn't heavily loaded, etc.). What is interesting, and maybe you know, is that when this did occur it did not affect the memory clock speed, just the GPU clock speed. Where as in normal desktop and idle scenarios both the GPU and memory clock run at a lower speed (typically GPU at 139 MHz and memory at 405 MHz) and both ramp up when a graphical load occurs, in these instances the memory clock speed would still ramp up to 5000 MHz but the GPU will gimp, only going up to around 865-1066 MHz.
Is that normal for when the video card goes into safety mode or when the drivers go unstable? Or is it expected for both GPU and memory clock speed to run lower?
Also, I did just stumble on a way to log the monitored data to a file. That will certainly be helpful.
Thanks again!
Click here to post a comment for this news story on the message forum.
Moderator
Posts: 16274
Joined: 2000-09-05
If you install software to "view some monitoring", you absolutely cannot say how your system behave when you don't monitor it in background. You're misundersranding fundamental basic principle: GPU Boost 3.0 is NOT handled dynamically on MSI AB or any other software side, it is purely closed NVIDIA driver/hardware technology transparent for applications and you cannot directly alter clock management from software. Besides "safe" mode after TDR the factors that may limit the performance in realtime are reflected on appropriate graphs: power limit, thermal limit, voltage limit and no load limit. This way GPU Boost is giving you some feedback and allowing to see current performance limitation reasons vector. And if it confuses you then peobably the best choice for you would be playing blindly, i.e. without seeing realtime hardware state.