Discussion in 'Videocards - AMD Radeon Drivers Section' started by mtrai, Dec 8, 2016.
Sorry, who the F is RAGNAR(OK)?
DDU is made by Wagnard. Unless, you mean something else.
Calm down. Undying is not a fanboy. He is actually pretty cool.
UVD bug is hit or miss on GCN 1.0 and can be dependent on the bios.
My 7950 boost's never had but my 7850s had it. My R9 280 did not have but the 280x did.
Are you really running Windows 7 32-bit?
If so, is there some specific reason you must have 32-bit?
4GB max RAM - video card RAM - probably some other stuff.
Yeah,sorry,I associated his first name with a major event in scandinavian mythology... :eyes:
As for the 32 bits,cyclone3d,it's just that I didn't want to have any hassle at all,plus traumatic readings about updates on WU just impacting 64 bits OS and other things I guess.I don't play so much so...
My experience with the new driver has been OK so far. No crashes, but I did have some issues pop up whenever I use a second monitor.
1. Relive works great when it works, but several of the games I tried didn't work at all. It made flawless recordings in MXGP, but in Ark:Survival it made slideshows no matter what I tried.
2. WattMan "kind of works" for me. I couldn't get the game profile to apply for Ark:Survival. The histogram didn't show any info when running Ark:Survival. The global profile did work.
3. Chill might work? I didn't try it because I only own 1 supported game.
4. VP9 Decoding seems to be working in Chrome.
Weird stuff I noticed:
After a few unsuccessful attempts at underclocking with WattMan(profile just never kicked in) I reset the profile and then I noticed the VRAM was stuck at 150Mhz even in games. I disabled secondary monitor and everything went back to normal. After a couple hours gaming with no issues I enabled my secondary monitor again. I had horizontal lines on both screens whenever anything moved like the mouse cursor or a window. It didn't look like the usual artifacts you might see, and my guess is that it was a DVI issue(both screens attached by DVI). Disabling the second monitor cleared up the issue on the first monitor. Reinstalled with "Clean Install" option(NO DDU) and everything was fine again on both monitors.
*More weird stuff:
After playing The Witcher for a few hours without issue, I exited the game and enabled my secondary monitor. VRAM clock jumped from 150 to 1450Mhz.
Updated the realtek driver, chipset driver is the latest too, ReLive.
About the BSOD even with a fresh install i got a bsod.
Made a bug report in MS support forums with this crash dumps and they told me that was amd drivers fault.
A lot of people have this same bsod with amd APU's in W10. the solution for now is wait AMD fix this in a future release or use Windows 7 with 15.11.1.
Let's hope that AMD has this bug in mind.
Thank you for your time to look the logs.
Not long, 15 minutes I guess. But no crashes on alt-tab and the game was on Fullscreen mode.
I have the UVD bug but I get no crashes. Sometimes I believe it might be down to the vBios version.
I'm running Windows 10 x64 14393.576
msinfo32, sorry not in english
I hope they take at least one pass at fixing bugs for a somewhat more stable driver before the holidays. The daily black screen is still annoying.
Running Firefox (hardware acceleration disabled), I was watching a Youtube video when I decided to try ReLive streaming again, but with Twitch this time. I launch Origin, open AMD Settings, go to the ReLive tab, drag the upload rate a little lower, black screen. Sound from youtube kept playing for a few seconds before freezing. My upload rate wasn't changed in the ReLive tab once I rebooted, so it looks like changing it (or opening AMD settings) might have been part of the black screen this time around.
This driver is working great the second time around. This time no ReLive and it works much better.
We need a lil' better and more stable drivers for the holidays. I don't like this driver much, something is weird. Many drivers with Fast Ring Windows Insiders builds make me feel unstable and anxious about the unknown. Only from AMD.
If you are participating in the Fast Ring the part of your installation that you need to be least nervous about is the GPU driver.
16.12.1 vs 16.10.2
Look at Physics Score. It's Cool
Repeating my previous post which no one replied to.... Does anyone else find that setting the GPU fan to manual isn't working as expected? Either setting it to manual takes a few tries and once you do the fan speed reverts to the automatic speed at some point even though it is still set to manual? A restart of Windows will also set the speed to the automatic one. Just looking to confirm so I can report it to AMD.
AFAIK physics score has nothing to do with gfx, its a CPU test, so in one of your test you had something running in background.
Also the last 2 updates to 3dmark in the last couple of days listed some pretty large score improvement results for tests.
What's new in 3DMark 2.2.3509
This update fixes a GUI issue that resulted in marginally lower than expected scores when starting a test from the Benchmark Details screen in 3DMark versions 2.1.2852 and later. Benchmark runs started from the Home screen or the Command Line were not affected.
It is normal for 3DMark scores to vary by up to 3% between runs since there are factors in a modern, multitasking operating system that cannot be completely controlled.
With this update, overall scores are expected to increase by up to 0.3%. Scores from the Physics and CPU parts of benchmark tests may improve by up to 2.5%. Scores from this version of 3DMark are consistent with results from previous versions that did not have the GUI issue.
Added a two-minute timeout to the SystemInfo scan to prevent it from stalling for long periods on some specific systems.
:bang:I guess most do not bother to read the 3dmark release notes. :bang:
For anyone having trouble recording (combo doesn't work in-game, need to alt/tab to desktop to start etc):
Check RadeonSettings-Gaming, if said game (BF1, my case) is listed more than once.
If so, just delete the game's shortcut from desktop, delete one of the gaming profiles (doesn't matter which one) and close/open RadeonSettings.
In-game recording should work from now on.
Yes, I've found the fan settings not working as expected, but I have not had any issues like you describe. When I click "apply" the new setting takes effect instantly, and remains in effect - no multiple attempts and no reverting to auto, even after a reset.
When I switch to manual it's set to 1200, and I get 1330 rpms. Increasing the slider to 1300 drops rpms to 1065. I have to set it to 1850 to get the 1330rpms that I started with(when it was initially set to 1200).
IMO if you can reproduce a bug consistently, then you should report it. A fan setting not sticking could be bad news.
There was a bug in 3DMark that resulted in System Info getting stuck and keeping a whole core busy during testing and even after closing 3DMark. This resulted in noticeably lower physics score and also lower graphics score. Based on the changelog, they seem to have fixed it now. As other also mentioned, Physics score is not at all affected by GPU driver; the difference you are seeing is most likely caused by what I mentioned.
I fixed my 16.12.1 woes!
Getting frustrated that this memory speed downclock & lock fiasco was killing my AMD buzz, I decided to try and get things working. First I tried using only one monitor, and no this did not fix the wonderful fluctuating memory clocks.
So I decided to uninstall everything, again, and this time I used the 16.12.1 Minimal Web installer. I noted that this installer has an option to install Application Profiles, unlike the full installer, and it reported installing a different build number.
Long story short: I can now use multimonitors properly, and my memory clocks are staying at fullspeed. :banana:
Will do some more testing, to see if TRIXX and AB are working properly, but I feel someone botched the original full installer. I don't know if it's been silently updated with same filename, but worth trying, or just use the Minimal Web installer.
UPDATE: Using AB or TRIXX causes return of memory clock issues and subsequent visual glitching. Wattman working, tho I do not like the voltage values it uses, and I'll try to see if I can use TRIXX or AB to control fan speeds.