Download: AMD Radeon Adrenalin Edition 18.12.3 Beta

Published by

Click here to post a comment for Download: AMD Radeon Adrenalin Edition 18.12.3 Beta on our message forum
data/avatar/default/avatar06.webp
bernek:

I keep getting messages of some HDMI Audio Bus driver installing over and over again and windows 10 wants to restart also it asks to install 18.12.2 which is older ? over and over again .. endless loop.
Hi. Do you have a gigabyte motherboard? I have some weird issues with gb motherboards and amd cards. And was getting that message from time to time and not sure if its driver related or the s***pid motherboard.
https://forums.guru3d.com/data/avatars/m/133/133128.jpg
Trihy:

Hi. Do you have a gigabyte motherboard? I have some weird issues with gb motherboards and amd cards. And was getting that message from time to time and not sure if its driver related or the s***pid motherboard.
MSI B350 PRO VD PLUS ...
https://forums.guru3d.com/data/avatars/m/251/251706.jpg
The HD Audio Bus driver thing is a known issue, from what I can tell. There's reports on Reddit about it happening.
data/avatar/default/avatar08.webp
I have the weird issue with gigabyte z97 and prior platforms that hdmi audio starts crackling and graphics starts to show weird stuff from time to time. Only fix is setting pcie to gen 2 on bios. And only happens with amd gpu cards. I hate this motherboard so bad. Had the same problem on z77, z87, etc. While on the green team, forgot about this bug 🙁
data/avatar/default/avatar10.webp
3D blu ray playback no longer works for me with this driver.
https://forums.guru3d.com/data/avatars/m/180/180870.jpg
Awesome Donkey:

The HD Audio Bus driver thing is a known issue, from what I can tell. There's reports on Reddit about it happening.
i have it also with 18.9.3 drivers seems more windows related than amd
data/avatar/default/avatar15.webp
sideeffect:

3D blu ray playback no longer works for me with this driver.
Also not working in 18-12-2. Working fine in Win10-64Bit-Radeon-RX590-Software-Adrenalin-Edition-Nov15.
data/avatar/default/avatar26.webp
Awesome Donkey:

The HD Audio Bus driver thing is a known issue, from what I can tell. There's reports on Reddit about it happening.
I was getting this on and off with the 18.12.2s as well. Seems to have stopped though. Had to revert to this driver because of the Zero RPM issue with the .3s.
https://forums.guru3d.com/data/avatars/m/260/260114.jpg
Fox2232:

General behavior of 18.12 drivers is bad. Voltages in vBIOS are practically ignored even with wattman disabled. One has to switch wattman voltages from automatic to manual and set there same as in vBIOS. But that lasts only till restart as then manual voltages which are still enabled get ignored. So one has to switch to automatic, apply, back to manual and apply again. Or use OverdriveNTool aster every restart. As for Fan speed, it did stop working in linear fashion with 18.12.2/3, it now works in those huge steps, pretty annoying. But I messed up with buttons in Afterburner and wattman and some unknown combination made Afterburner control to work and persist even reboot. AMD has quite some work to be done in wattman again. But I wonder what broke it in 1st place. Maybe updates for Navi.
Hmm, You can try Save/Load (this manual settings) Try and report.
data/avatar/default/avatar29.webp
testcy:

I use a Gigabyte z97 motherboard too and occasionally hdmi/displayport audio is distorted and screen goes green/black. The issue happens regardless of the driver version (including 18.12.3). I opened a separate thread about this and I received no replies, but luckily I came across your post. I changed the PCIe Slot Configuration from Auto to Gen2 in the BIOS. Will it fix the issue?
Hi. Yes, that will fix it (unless you have a bad hdmi cable) I opened many tickets on gigabyte web, but they wont help. They always says they cannot reproduce the problem. Obviously pcie bus is going out of sync. Who knows why. Maybe ram, maybe base clock. Dont know. Gigabyte doesnt care. And it affects the entire gigabyte line from z77 to z97 at least. Also obviously it wont happen to everyone. Some requirements should be present to make the problem appear. But no one knows what triggers this. Im using two hdmi to tv's. Ddr3 at 2400mhz. Other stuff is pretty much stock. They somehow know about this problem, cause with bios updates, I cant reproduce the bug on nvidia anymore. But on amd is still there. On z77 were much worst. On cold boot you sometimes got half the gpu fps and only a restart will fix it. There are some forums talking about this. But there are only a few people with this problem. Or they didnt notice it. And since z77, the only real solution is setting pcie gen to 2 on bios. I just keep buying gigabyte boards cause they leave you set fan speed with a 0 to 100C scale. Asus limit this to 75C. And for a HTPC this is a deal breaker. I have to find which other manufacturers offer this. So i can get out of gigabyte for good.
data/avatar/default/avatar10.webp
testcy:

I am not that concerned about fps, but assuming we are talking about the same thing, the sound issue (either with hdmi or displayport cables) is annoying, as well as the screen going green or switching off and on randomly. At the beginning I though it was the monitor, but it works fine with other devices, so the issue must be related to the graphics card or the motherboard. And obviously it's not the cables. I did not have the issue since yesterday that I changed the bios setting, but I can't be sure yet that it's fixed.
Hi, then pretty sure is that. Dont remember very well the graphics problem. I think I even got like pixel rain onscreen, like when you have a bad hdmi cable. Changed many cables, all with the same problem. The distorted sound was crazy. Even on spotify or windows sounds. Weird thing is that sometimes you can start the pc without this problem. And will appear later. So im sure the pcie bus goes crazy. Then I had a deja vu and remembered the bug on older gigabyte platforms. Changed to pcie gen 2 and thats it. Sometimes I change back to gen 3 or auto and the problem appear inmediatelly or after a few minutes.
https://forums.guru3d.com/data/avatars/m/198/198862.jpg
Fox2232:

And as you wrote, games work just fine, Nothing is breaking them. But leaving drivers to handle voltage results in card hitting power limit which I already upped a lot. Setting 1.125V delivers lovely low power consumption and higher fps.
Isnt that a low voltage to be running such a high clocks?
data/avatar/default/avatar24.webp
testcy:

What do I loose by setting PCIe Slot Configuration to Gen2? The graphics card is PCIe x16 Gen3, but uses x8.
On performance you wont loose anything. For 1 card pcie gen 2 x16 is fine. If you want to crossfire or use future cards with more graphics power, it could be a problem. Or if a newer card has a pcie 3.0 requirement, you will have to change your entire platform. So, if you can, open tickets on gigabyte support. And if you send them some videos showing the problem, it will be even better. Also send them links to forums discussing this.
data/avatar/default/avatar06.webp
testcy:

Based on previous correspondence, I don't expect help from Gigabyte Support. I very much doubt that the will investigate a problem for an "old" motherboard they stopped producing and for which they stopped releasing bios updates. GPU-Z reports that Bus Interface is PCIe x8 3.0 @ x8 1.1 and PCIe x8 3.0 @ x8 2.0 when running the Render Test. Is this normal?
I think it should show x16 2.0. Not sure about this. Did you use the pcie connector near the cpu? The other ones are x8 I think. Will check later. Here is the response from gigabyte
We no longer have this particular motherboard available on our end to test, therefore we've asked our headquarter to test for us, according to their testing, they couldn't replicate any issue with the following configuration, have tried playing music, 4k medias, youtube etc. We're thinking that there's a potential handshake issue in between your HDMI monitor/ TV and this particular card.
So, run from this platform before it will have real limitations. They wont fix the problem. You are locked at pci-e 2.0 x8 or 2.0 x16 at best (like sandy bridge). Crossfire and anything beyond vega will probably suffer performance drop.
data/avatar/default/avatar32.webp
Can't use 18.12.2 or 18.12.3 with my vega 56. Every game my display goes black and loosing signal (with freesync, no issues without freesync). Via google I found out I'm not the only one having this issue so I'm back to 18.11.2.
https://forums.guru3d.com/data/avatars/m/119/119475.jpg
testcy:

Based on previous correspondence, I don't expect help from Gigabyte Support. I very much doubt that the will investigate a problem for an "old" motherboard they stopped producing and for which they stopped releasing bios updates. GPU-Z reports that Bus Interface is PCIe x8 3.0 @ x8 1.1 and PCIe x8 3.0 @ x8 2.0 when running the Render Test. Is this normal?
If your slot is set to pcie 2.0, that should be the normal behavior of a 8x (max) card. On idle all of my amd 16x cards only run in pcie 1.1 16x, and then switch to 2.0 16x or 3.0 16x on load (depending on mb capability), or 1.1 8x idle + 2.0 8x load on a 2.0 slot manually set to 8x.
data/avatar/default/avatar26.webp
Strijker:

Can't use 18.12.2 or 18.12.3 with my vega 56. Every game my display goes black and loosing signal (with freesync, no issues without freesync). Via google I found out I'm not the only one having this issue so I'm back to 18.11.2.
Same issue, but on old PC with 7970 (stock). Monitor losts video signal under 3d load in games (and after reboot even in BIOS, before windosw starts - several reboots / on/off PC fixed this) or artifacts while browsing web (coloured squares). I thought card dying, reverting to 18.11.2 fixes all this issues.
data/avatar/default/avatar16.webp
testcy:

Yes, I am using the pciex16 slot. But I think the card has a pcie 3.0 x8 bus interface, so I should be normal? If Gigabyte motherboards are the only ones with this issue and their support is not helpful, then I think choices will be fewer next time I upgrade.
Tried gpuz render and shows 2.0 x16. You could try switching to 3.0 again and try other possible fixes. Maybe setting base clock manual to 100mhz or 99 or 101. Enabling spread spectrum, lowering ddr3 speed, disabling oc, who knows what else could work.