Eastcoasthandle:

I hope they actually delete when you hit the clear cache button now. I've been manually deleting them for a while now.

I can't even find where it's hidden. The damn program makes no sense.

As i understood it is normal(means abnormal) behavior for radeon soft causing green dots,blinking monitor. I have Philips 246v was plugged via dvi and i got every once a while non active monitor while boot. i had to switch off my pc and in couple times i got windows10 boot screen.while a gaming i had green dots or at surf internet or whatever has a picture.Switching off the monitor solved the problem for a while but at next boot i got black screen.Thought it is spoiled monitor or cable or my 7850 and in the last hope plug my monitor via hdmi adapter and since it looks like work.Just once monitor blinked on a bit of second. So as i understand it is still AMD buggy software?

elaganza:

As i understood it is normal(means abnormal) behavior for radeon soft causing green dots,blinking monitor. I have Philips 246v was plugged via dvi and i got every once a while non active monitor while boot. i had to switch off my pc and in couple times i got windows10 boot screen.while a gaming i had green dots or at surf internet or whatever has a picture.Switching off the monitor solved the problem for a while but at next boot i got black screen.Thought it is spoiled monitor or cable or my 7850 and in the last hope plug my monitor via hdmi adapter and since it looks like work.Just once monitor blinked on a bit of second. So as i understand it is still AMD buggy software?

No, I think there is something wrong with that card.

New gfx driver 18.5.2 installed. Windows 10 Pro x64 fully updated. I have 2 HD7970 mounted in crossfire mode although they are not working in CFX mode. Last AMD driver when CFX worked was 18.3.4. i7 3770K 8 GB RAM DDR3 MB ASUS P8Z77-V PSU Corsair HX1000W Is this my rig, Windows or AMD driver issue?

Spoiler: "http://danielkawakami.blogspot.com/2017/01/sb-x-fi-series-support-pack-40.html"

spectatorx:

1803 is the very first stable build of windows ever which makes some really big problems to me which i can't resolve by myself, to be specific i am owner of creative x-fi titanium pci-ex and i got weird sound issues and according to this thread i'm not alone: http://forums.creative.com/showthread.php?t=742278 This is first time when i strongly recommend to downgrade (if possible) windows build to previous which didn't have problem you are facing.

Try to use XFI SupportPack 4.0, for me they work with no problem at all on win 10 1803. Supports the following Sound Blaster X-Fi cards (based on the CA20Kx DSPs): - Creative SB X-Fi PCI (except Xtreme Audio) - Creative SB X-Fi PCI OEM SB077x (Dell, HP, Lenovo, Fujitsu etc) - Creative SB X-Fi Titanium PCI-E - Creative SB X-Fi Titanium PCI-E OEM (HP / Fujitsu) - Creative SB X-Fi Titanium HD PCI-E - Auzentech X-Fi Prelude 7.1 - Auzentech X-Fi Forte 7.1 - Auzentech X-Fi HomeTheater HD - Gigabyte SB X-Fi Titanium PCI-E onboard - Onkyo Wavio SE-300PCIE (R2) [SPOILER]http://danielkawakami.blogspot.com/2017/01/sb-x-fi-series-support-pack-40.html[/SPOILER]

Octopuss:

I can't even find where it's hidden. The damn program makes no sense.

Go to Global Settings > Global Graphics > Reset (its just a word to the far right side) But yeah, I agree this should have been put inside the Global Graphics along with AA, vsync, tessellation mode and other options. But on the other hand they should bring back Flip Queue size and LodAdj as well. Instead we have to resort to regediting it or using RadeonMod. Don't even get me started man! Although Nvidia's CP is very dated they haven't taken features like that away like AMD has done. I should say ATI or AMD's Graphics Dept. And they take a very hard "No" position to adding it too. Don't think we've not asked before (another forum were we had Radeon support). I just don't understand the thinking involved. Nvidia gives you everything in CP. AMD thinks you might "mess something up". But I'm thinking back to years ago though.

spectatorx:

1803 is the very first stable build of windows ever which makes some really big problems to me which i can't resolve by myself, to be specific i am owner of creative x-fi titanium pci-ex and i got weird sound issues and according to this thread i'm not alone: http://forums.creative.com/showthread.php?t=742278 This is first time when i strongly recommend to downgrade (if possible) windows build to previous which didn't have problem you are facing.

Try going into your bios and enabling a feature called PCIe Spectrum or "Spectrum" Or anything else that reduces EMI/RFI. It was discussed years ago that creating a "ground" between the PC Case and motherboard helped in this area. IE: A copper wire from the motherboard tray area on one end and a metal ground of some sort on the other copper wire end. The motherboard itself sits on the stand offs. That should ground the motherboard to the motherboard tray (you usually see metal balls around the screw holes of the motherboard. In hindsight I would suggest (if all else fails) to take the motherboard apart. Remove the MB from the MB Tray and make sure you don't have any missing stand offs. Or misaligned stand offs (very common). IE: This is were you have 9 holes on the MB, 9 Stand Offs. But you only use 8 screws (you don't realize that though). You find a screw hole where you can't screw down. That means the stand off is misaligned to the screw hole somewhere. The only fix is take everything apart. Now I want to remind you this is a last resort if you cannot find a software solution to the problem.

YY911SF:

Any idea if the new 18.5.2 gaming driver is for the Vega Frontier Edition? When I tried the 18.5.2 on the FE from the pro section of AMD's download site, it doesn't allow install of the gaming driver. Thx.

Try, it should work NP

spectatorx:

No, it is software related issue as hardware is still fine. On llinux i do not have such problem, on previous build of windows it also didn't exist and started to happen with latest build. I've tried to find spectrum setting in bios but unfortunately can't find it anywhere. I think for some reason my motherboard has limited bios options because i also do not have switch for s.m.a.r.t. Motherboard is gigabyte ga-990fxa-ud3 rev. 4.0.

Hmm, well aint that something? They released realtek drivers for your board 2 days ago. Unrelated/Related finding. 🙂 https://www.gigabyte.com/Motherboard/GA-990FXA-UD3-rev-40#support-dl-driver-audio As a "backup plan" at least you could rely on that to get your audio working if you don't find a solution. I can understand that what you are saying though. It was working fine before but now it doesn't work with new windows build 1803 (I assume). Just covering all the bases here. One person fixed their problem by putting electrical tape (one layer) around the metal tab of their sound card where you insert the screw. That prevented whatever was going on with the MB/Chasis to interfere with the sound card. Although that prevented it from being grounded IMO. But here is some food for though. MS still uses something called DEP (Data Execution Prevention), a long forgotten gremlin that's well known for messing old apps, games and drivers. It's always set (even in win10 to "Turn on DEP for essential Windows Programs and Services Only". This "feature" is rarely talked about now but was part of a known tweak to disable back during win7 days. MS has a very peculiar way of deprecating old "stuff" (hardware/software) for thingsthat haven't been supported for a few years. Zboard comes to mind. But that was a result of a KB patch. But what happens is that the keyboard didn't just "stop working" it would "act funny". You press the L key and it would be the + key. Unusual lag response in key presses, etc. Then eventually would stop working. This kinda reminds me of what you described with your sound card. MS does depreciate certain older hardware via it's drivers (if it was already installed at the time of the implementation of the depreciation) and you have to do a lot of research to find a list, if it exist . As most of the time it's through complaints one learns of it. I would start with disabling DEP 1st though. See if things get better. If not then revert it back. Wish you luck in finding a fix. I don't want to stray to far off topic here. To turn it off: CMD (ADMIN Priv) bcdedit.exe /set {current} nx AlwaysOff Reboot To turn it back to default: bcdedit.exe /set {current} nx OptIn Reboot ------------------------------ As for the Adrenalin Edition 18.5.2 Driver, I found that BF1 DX12 now hitches when scoping or getting out of vehicles. Things like that. I didn't experience that with the older drivers I had. Granted, BF1 DX12 was no saint. DX11 is still better overall for smoothness.

YY911SF:

I tried to, it didn't give me the option to install the gaming driver on 18.5.2, just the pro driver.

Maby try Q2 2018? (if you playing Forza or UWP games make sure to copy amdxc32.dll & amdxc64.dll from Windows\System32 folder, then replace the Q2 with older one)

Eastcoasthandle:

Hmm, well aint that something? They released realtek drivers for your board 2 days ago. Unrelated/Related finding. 🙂 https://www.gigabyte.com/Motherboard/GA-990FXA-UD3-rev-40#support-dl-driver-audio .....

This Gigabyte driver is useless - only a 24MB in size it's not a complete driver hence will not install properly/forget it - this is typical Gigabyte putting up trash like that for download..

Hmm, with this drive the osd doesn't appear to be working correctly. I know ealier version of Crimson worked but this version's osd is clunky, slow, laggy for starters. Games seem to run fine but osd info isn't accurate (fan speed, fps, etc). Compared to MSI A/B. Another thing I noticed is that fps target limiter doesn't seem to work either. Has anyone tested this in BF1? Edit: Ok MSI AB was the issue. I had to uncheck every option in General Tab to get fan and fps target control working again. Funny thing is that uninstalling MSI A/B or simply not running it wasn't enough. You have to uncheck all of the General Tab options to get Radeon Settings > Global Settings and Wattman working again.

Afterburner would likely overtake Wattman's settings by forcing a absolute value for fan speed depending on how you set that up, I am however surprised that affected the OSD but it might have been querying Wattman and not the override that Afterburner can set for having a custom fan curve or minimum speed enforced though if not set up carefully this can also be a constant speed which can be a problem if the GPU starts heating up and not accelerating to max fan speeds to cool down. (Instead of setting target GPU temps and max speeds though this varies depending on GPU model for Wattman.) Although newer GPU's should throttle after certain thresholds but that might not be fast enough to bring down temps so monitoring the various sensor points comes in real handy if you're trying to set a lower fan speed or less aggressive curve. 🙂 And yes the values in Afterburner applies even after shutting the program down, it's retained in memory to put it in a simplified manner so a reboot clears it or disabling the option, Unwinder has likely explained how this works in the forums for the program in some of the threads for new releases since I'd imagine it can pop up as a question every now and again same as how the injection works and it taking a bit of time to unload from processes for the Rivatuner component if installed. On the other hand this allows controlling speeds and other values more completely and with less limits from Wattman though bios limits would still apply. (Allowing for setting a fan speed for Vega GPU's for example without it being automatic until it hits the power states the user can adjust.) And the release notes for the latest drivers and what users are posting about AMD's OSD makes it clear it's not entirely bug free either, prone to errors and glitches particularly for recording but hopefully that's something AMD can fix up sooner rather than later in the next few driver releases whenever those come out.

Have these installed since they were published, no issues so far. Pretty stable ones Win 10x64 1803 + R9 290

bro !! also no issues for my setup so far.!!! win 10 insider preview 1803/17682 +R9 290 tested bf1+the crew 2 cloced beta http://i214.photobucket.com/albums/cc242/ultraex2003/hdfdccgncvn.jpg

I was/am expecting a driver yesterday/today for - Vampyr/Warhammer 40,000: Inquisitor – Martyr/MotoGP 18 Lets see 🙂

chispy:

It seems this driver don't support Ryzen 2400G with Vega 11 graphics 😏, anyone tested this driver on their Ryzen APUs ? https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Adrenalin-Edition-18.5.2-Release-Notes.aspx

inouext:

Does not support my APU either 7860k, 18.5.1 was the last with support for me.

I checked too on AMD's website, it states 18.5.1 as the current driver for the 2400G for instance.

Does this fix the black screen in UE4 games? I keep getting it whenever i receive a pop-up from any app/windows. I can fix it by running tho's games in windowed fullscreen but Sea of Thieves does not.

Does anyone get a locked base clock while playing BF1 using wattman with this driver?

@JonasBeckman any 18.6.1 link came up?

So far it just redirects to a not found message but it's just afternoon and with the time zone difference here drivers are usually posted late at night or past midnight with the URL changing from not found to forbidden a few hours ahead of release. 🙂 Occasionally there are situations where a delay could shift the release window and sometimes the drivers are released earlier or later but so far there's nothing showing for 18.6.1 though curiously after checking if there was any new hotfix updates both 18.5.1 and 18.5.2 are linked to from the hotfix page. https://support.amd.com/en-us/download/catalyst-hotfixes EDIT: Ah I See now, that's the Pro series drivers for e.g Vega Frontier.