MSI afterburner bug report & suggestion

So I have this odd bug I have experienced before..

I bumped my new gtx 960 up by about 120mhz on the core, so +120 on the slider. Next time I started my computer and start AB, the slider had returned to +0. So I put it back to +120 and my game crashed! I checked the monitoring graphs and my core clock was pushing 1600mhz! So, it's as if the +120mhz I set yesterday had become the new +0 base value...I tried uninstalling and reinstalling AB and the base core value at +0 is still 120mhz higher than it should be....

 

I recommend to add hardware cursor capture in 3D games because when u are recording games like League of Legends or The Sims and so such games it looks a bit odd when u are doing "things" without a mouse

 

What I normally do is setup profiles, were first slot is stock clocks for core and memory.
Then I setup the other slots for varying OC levels, once set i lock them .
Make sure you got both options "appy OC at system startup" and "start with windows" are enabled .
Never ran into that issue with any card I have had, but maybe driver is resetting w/o you knowing it.
Try slightly lower OC if profiles setting doesn't help.

 

Ive requested this over a year ago and yet nothing has happened and it is pissing me off. Get mad.

I just took an hour adding 40 cfg files to have 3D profiles not turn on. Mostly adobe products and small software that don't need gpu overclocks. That is absolutely ridiculous. There NEEDS to be a WHITELIST to be able to add the process names of the applications you want an overclock on instead of creating a billion cfg files.

There also needs to be profile settings for the following things:

-laptop closed
-things that do need overclocking on



Laptop closed profile
Whitelist profile


The program needs to read from ONLY these 2 cfg files to find all the processes that you want to use. And you type whatever you want as far as processes go) in these 2 files with the laptop closed profile just being a checkbox option to allow a separate clock for when your laptop lid is closed.

2D/3D profiles are just not efficient enough to not waste ppl's time. I thought about creating autohotkey programs to achieve this but then you have the UAC problem.....

Please stop being aholes and make this happen. I give no craps about how mad you get because of how I said it. Shouldn't have ignored the first time.

 

Whoa there sparky. Take a deep breath and read the document that comes with the distributive. LAPTOP's are NOT officially supported nor will they ever be.

 

That is only a half percent of what my main post was about......................
Even if laptops arent supported, A. it works fine on my laptop, B. There's another 99% of what I posted that ain't tied to laptops at all......

Not only that, detecting whether a laptop lip is closed , if laptops were supported, or not is less than 5 short lines of code.

 

Well with that kind of strong talk I'm sure Alex will jump through hoops to make it happen. LOL

I think you might want to steer clear of this forum area.

 

It's called reverse psychology. Ppl like you like to draw attention to the negative while ignoring everything positive.

If that's the case, then have fun making 75 txt files just for a feature to work correctly.............

btw, feel free to keep going back and forth to fill up 8 pages with nonsense butthurtness. it only helps draw attention to what I want

And as you can see, I don't post here much at all anyway. But yeah, go ahead.

 

No, I don't squabble with youngsters, consider yourself warned. I'm out.

 

Well, if you do it more than one time, you are doing it wrong.
You could have saved those cfg files and after a reinstall of Windows or MSIAB you could just restore them.
You could have shared your list of false 3D apps with unwinder to include them on the default ignore list.

MSIAB supports suspending and or hybernating. Set your Laptop accordingly when closing and you are done.

 

It's the first time I had to do it.
I'm doing it wrong anyway, hence the request. No way is something supposed to be so tedious. When intel xtu does it, you type in the exe name and press okay and you're done and you get a nice easy list you can reuse. Only for what you want. Here, you gotta make a new text file, copy the name from the list, add .cfg behind it along with the .exe, and then copy and paste 2 lines in every file you make. Let alone, make a file for almost every program on your pc instead of adding what you actually want to use it on. It's just simply bad implementation. Even Gedosato has a whitelist for you to easily add what you want and be done with it. Here, I gotta worry about what else I missed because if I activate a new program I overlooked, then my card will be hyper acting for no reason.

Sure Msi supports suspending and hibernation. But not a lot of programs do and are half coded and once you go into that state, you may come back and half the programs start malfunctioning. Which is why I disable sleep and hibernation and coded my own program to reduce resolution and cpu clocks when the lid is closed and to keep that value separate from the other normal and overclock clocks. I wouldn't even have to do that if msi ab didn't ask for uac everytime I summon a cmdline for it to switch a profile. Which is why I asked for that lid close feature for msi, so I can 'underclock' while my lid is closed without having to toggle a uac prompt. So I basically made my own low power state. Not to mention hibernation mode is bad for ssds.

 

MSI AB does not support per process OC , the list in RTSS is mainly for OSD and if it triggers 3d clocks .
Only way AFAIK to change clocks is through profiles/hotkeys/2D/3D.

 

shame on me for quoting an old(er) post but it solved some confusion i had.

thanks unwinder.

 

Asus R9 Fury detection issues with 4.2.0

Hi all,

I've just built a brand new gaming PC and having installed windows and the latest Crimson (16.1) hotfix drivers. I was excited to install afterburner and try to OC my card in line with what digital foundry suggested in their review of the Asus Strix R9 Fury.

I was rather surprised to find that my GPU isn't detected at all by v4.2.0. Quite how this is possible I don't know when plenty of people have the same card and a quick search didn't show a lot of posts mentioning the issue.

I rolled back to Afterburner 4.1.0 and low and behold, AB detects the card fine and even adds a natty dragon to the afterburner skin! I then went to version 4.1.1 and that also works perfectly (although it is reporting the driver version as 15.8 not 16.1 but I'm assuming thats to do with it being a major release and not a hotfix).

I've installed all the correct chipset drivers etc and my card is accepting an overclock with 4.1.1 with no issues whatsoever. I installed GPU Tweak II (although I never run them together) and it confirms my card is operating at 106% with an OC of +65Mhz on the core and +50Mhz on the HBM, so afterburner did it's thing.

I'm assuming there is something about my specific setup that is causing the issue, so I've updated all my system info accordingly. I'm happy to provide any log files or other bits of information as required to see if I can help you guys pin it down.

Thanks again for making such an excellent bit of software! I've used it for years without issues.

 

MSI Afterburner issue.

4.2.0 worked fine with windows7 ult 64bit
4.2.0 works fine on my windows 8.1 upgrade to windows 10 pro 64 bit

when I upgrade the windows 7 machine to windows 10, MSI Afterburner does load at start. I do have OSD. but I have to close afterburner then start xsplit then my game then relaunch MSI Afterburner.

AB doesn't load. no system tray icon. no osd. but when looking at task manager it is there.

what am I missing here.

when I close AB and reopen it, it does not show up on taskbar or load the GUI.
RTSS does not load either.

Windows 10 pro 64bit upgrade to windows 7 is updated. version 11099

ive uninstalled RTSS and AB, deleted directories and reinstalled. no change.

 

@Liquor

Did you uninstall AB prior to upgrading Windows? If not, uninstall all traces of AB from HD and registry > reboot and reinstall clean.

 

no, but ill hit the registry. HDD (SSD) was cleaned during troubleshooting after AB RTSS uninstall/reinstall. but I did not hit the registry.



EDIT:
no registry entries and nothing in AppData after uninstall completed and a reboot.

EDIT 2:
after install and selecting start MSI Afterburner. it does not start.

EDIT 3:

no change after a reboot, I thought I had to do a .dll move or copy for windows 8.1 on my laptop. though unable to find that guide

 

Is AB shown in task scheduler library? Are you an Admin?

 

@Unwinder

Did something changed majorly in the New Driver Branch around Nvapi Counters and Afterburners readout ?




Looks so strange running with 10% into the Powerlimit

Could you add GPU Power Level as well ?

Nevermind seems to be a stability issue in the new 361 driver branch it happens randomly now that the counter just get stuck on 10% and doesn't change it's value then anymore.

Only a System restart fixes it then.