Overclock.net - An Overclocking Community - Reply to Topic
Thread: [AMD] Radeon Software Adrenalin 2019 19.11.1 Highlights Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
11-11-2019 02:33 AM
treetops422
Quote: Originally Posted by Mr. Mojo View Post
It hasn't been applying any of my Wattman settings on reboot up until I installed the latest driver earlier today. With all previous drivers, after a reboot, all my Wattman settings would be back at default. I have just been loading and applying my saved profile after every reboot. I went to do it after a reboot this afternoon, and my settings were already applied - min and max voltage, max clock, power limit, memory clocks

One thing I've noticed with AMD drivers...you never know what you're going to get. Someone with the exact same build, settings, and software as I run could have a completely different experience.
Sound like you haven't updated your drivers in a few months.
11-10-2019 06:09 PM
WannaBeOCer
Quote: Originally Posted by BeeDeeEff View Post
To those trying to overclock R VII on newer drivers, many are reporting having success using the tool from this thread: https://www.overclock.net/forum/67-a...-software.html
I've been using Asus GPU Tweak II without an issue.
11-10-2019 05:59 PM
BeeDeeEff To those trying to overclock R VII on newer drivers, many are reporting having success using the tool from this thread: https://www.overclock.net/forum/67-a...-software.html
11-10-2019 05:36 PM
Mr. Mojo It hasn't been applying any of my Wattman settings on reboot up until I installed the latest driver earlier today. With all previous drivers, after a reboot, all my Wattman settings would be back at default. I have just been loading and applying my saved profile after every reboot. I went to do it after a reboot this afternoon, and my settings were already applied - min and max voltage, max clock, power limit, memory clocks

One thing I've noticed with AMD drivers...you never know what you're going to get. Someone with the exact same build, settings, and software as I run could have a completely different experience.
11-10-2019 02:35 PM
Falkentyne
Quote: Originally Posted by Mr. Mojo View Post
FWIW, I just noticed that Wattman actually auto-loads my OC profile after a reboot now. On all previous driver versions, I would have to open up Wattman and manually select my saved profile after every reboot.
This has been happening for awhile now, has it not?
Wattman auto-loading a saved profile every time you reboot. But NOT adjusting the GPU voltage--at least this happened before. That was the cause of the old "290x black screen reboot death" when you set a memory clock that required a higher GPU voltage (!) to not black screen on you, then if you rebooted, it would re-load the clocks but not the voltage. Fun stuff.

That was when MSI Afterburner started deleting the Crimson/Wattman entries after closing the program, to prevent the CCC from reloading the clocks again.
I'm guessing AMD either removes or reactivates this ability whenever they want?
11-10-2019 01:07 PM
Mr. Mojo FWIW, I just noticed that Wattman actually auto-loads my OC profile after a reboot now. On all previous driver versions, I would have to open up Wattman and manually select my saved profile after every reboot.
11-10-2019 06:39 AM
PontiacGTX
Quote: Originally Posted by SoloCamo View Post
See, I'd believe that if AMD actually offered anything worthwhile to anyone on V56 or up. Who goes from Vega to mid range Navi at this point? The only option for me right now on V64 would be Nvidia. The big thing is HBM and until it's used across an entire product stack it's going to keep getting shafted as they don't want to devote the driver resources to it.

I must admit, I don't think I'll get anywhere near the life out of this V64 as I did my 290x due to this. That and the whole RDNA vs GCN thing of course. The whole fine wine thing doesn't work when you abandon your old arch.
Life cycle should last another 3years before AMD abandons it completely, But I dont see much of a difference between RDNA and GCN the games arent performing a lot better in some new titles as they should on navi, Maybe developers havent bothered to optimized for RDNA?
11-10-2019 06:30 AM
SoloCamo
Quote: Originally Posted by Alastair View Post
I remain skeptical about a companies intentions. I don't think it is out of the relm of possibilities that Amd would push some "nerfing" updates to push people onto newer cards.
See, I'd believe that if AMD actually offered anything worthwhile to anyone on V56 or up. Who goes from Vega to mid range Navi at this point? The only option for me right now on V64 would be Nvidia. The big thing is HBM and until it's used across an entire product stack it's going to keep getting shafted as they don't want to devote the driver resources to it.

I must admit, I don't think I'll get anywhere near the life out of this V64 as I did my 290x due to this. That and the whole RDNA vs GCN thing of course. The whole fine wine thing doesn't work when you abandon your old arch.
11-09-2019 03:09 PM
paulerxx Anyone else getting a memory leak in MW now? I didn't have this problem with the previous drivers...The game will use all my ram then crash.
11-09-2019 12:03 PM
Falkentyne
Quote: Originally Posted by Alastair View Post
I did try the power play tables registery mod for 150% power limit. It didn't help the extreme throttling caused by the new drivers.
I did not try upping the Temp limits as on a full cover block I had no reason to believe that would cause the issue.
What about the 'sub values' (like those weird entries no one knows about?)
did you try comparing the air bios entries (the reg file I gave you) with the LC Bios entries and see which other ones were different?

Basically, what I want you to do is to take the air cooled Bios's reg entries shown in softpowerplayeditor and copy all of them into the LC Bios reg, and then import that (so that you basically turn your LC Bios into an LC Bios with air bios reg entries), restart the driver and see if your stuttering is fixed.

I hope you followed that.

Then IF the stuttering is fixed, then slowly start changing back 1 value at a time (even though its time consuming!), restarting the driver, until you find the stinker that triggers the thottling.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off