The following issues seem to be fixed with the recently released 19.2.3 Adrenalin drivers.
I just installed the latest 19.1.1 beta driver and noticed a weird and even gamebreaking issue in World of Warcraft, running with DirectX 12 API setting. Flying around in busy Stormwind causes heavy stuttering in shorter periods, the screen freezes for a second or two, goes back to normal, stays like that for a few more seconds, before it freezes again. The game eventually crashes, with Windows 10 showing an error notofication:
"Access to graphics hardware has been blocked for wow.exe."
I noticed within Wattman, every freeze causes a massive clock spike in a negative way: The clocks reset to lowest P-State, before stabilizing for a short time, just to spike down again. I know it's not much, but here is a screenshot showing the issue:
As you can see, there is a spike quite soon after I started the game, which is when the picture froze for the first time. Got back to normal, moved around a bit, the next three spikes caused freezes in short periods, again before going back to normal. The last spike crashed the game, giving me the error notification stated above.
Now I reinstalled the 18.12.3 drivers, and everything works fine as usual. I again decided to try the 19.1.1 Beta, this time however I went for a clean, "new installation". The issues appeared again, regardless of the Wattman settings by the way, doesn't matter whether "Balanced", "Turbo", "Energy Saving" or "Custom" is set.
Again I reinstalled the previous 18.12.3 drivers and the game works just fine.
Mainboard: Asrock X370 Gaming Professional (5.10 BIOS)
CPU: AMD Ryzen 7 2700X
RAM: 32 GB G.Skill RGB optimized for Ryzen, running at 3200MHz
GPU: Sapphire Radeon Vega 64 Nitro
OS: Windows 10 Home 64 Bit (latest official version)
SSDs: Samsung 960 Evo NVME, SanDisk Ultra II SATA, Crucial MX500 SATA
HDDs: Samsung 500 GB SATA, WD Blue 1 TB SATA
GPU drivers: Radeon Adrenaline 19.1.1 / 18.12.3
Chipset drivers: 18.10.1810
Solved! Go to Solution.
Things seem working to me. I didn't do anything special besides install the driver and re-enable DX12. I've been playing for 30min or so without a single issue, whereas before I'd crash withing the first couple min. I'll keep you updated
*Update after two hours of continuous play I didn't have a single crash. Looks like they got it fixed
Same thing was happening to me, game freezes, monitor goes all black for a second, then the desktop is shown with game minimized for another second and then the game continues again. And that might happen several times until it stabilizes. If it stabilizes it doesn't happen for another 5 minutes or so. I tried completely reinstalling 19.1.1 using DDU but it didn't help so I had to downgrade to 18.12.3.
Edit: As OP said there are also Windows notifications that read "Access to graphics hardware has been blocked for wow.exe."
Edit 2: My graphics card is R9 380X Sapphire Nitro 4GB.
Motherboard: Gigabyte GA-990XA-UD3
CPU: FX-6300 overclocked at 4.5GHz
Memory: 2x4 GB DDR3 1866MHz
GPU: R9 380X Sapphire Nitro 4GB.
GPU VBIOS: 113-4E3081U-X58
Driver: Adrenalin 19.1.1
OS: Windows 10 Pro
OS Version: 1809
OS Build: 17763.253
I'm also having issues now on WoW.
I haven't played wow in about a month, I don't even recall which driver was installed then but all I know is that it was working perfectly fine, no crashes or anything, but I resubbed today and now when I'm playing something crashes, I assume it's the drivers, my monitor turns black as if it was disconnected and I get the "no video input" message for a few seconds while all the background sounds (music, game sounds etc) are playing normally, then the screen goes back on and the game resumes, this has happened liked 10 times in the matter of a few minutes.
I thought maybe it could have been temperature, but I kept HWMonitor open to see it and during the few times it crashed the temperature was around 60~65ºC, which is perfectly fine.
I also opened the Wattman settings and when it crashed I had the same "negative spike" as OP did, however radeon settings also crashed with it so I couldn't screenshot it.
My setup is as follows:
Intel Core i5 7600k
Gigabyte RX 580 4GB
Windows 10 Pro x64 (fully updated as far as I can tell)
Adrenalin 19.1.1 (clean install with DDU to remove previous installation as usual).
World of Warcraft is set to Directx12
No overclock whatsoever, all stock speeds
I've been playing Mafia 3, Assassin's Creed Odyssey, CS:GO and Rainbow 6 Siege these last few days without any issue or crash, so it seems whatever this issue is, it's conflicting exclusively with World of Warcraft, at least on my computer.
After getting increasingly frustrated with it I decided to DDU it and revert back to the previous driver and so far I have had zero crashes.
I suggest doing it until AMD fixes it.
I get them from guru3d. There's no other place to my knowledge. https://www.guru3d.com/files-categories/videocards-ati-catalyst-vista-win-7.html
In the past we were able to get older drivers directly from AMD's website but since the Adrenalin drivers came out, I believe that's not possible anymore.
I actually reported it that way, thanks. In addition I linked this topic, so they might take another look at further reports and developments.
Have same problems since 19.1.1 now downgraded to 18.12.1 and now its better, my problem was that i cant even got in one game of my libary on steam because it started lagging by the intro of the game. My GPU is a vega 56 and a ryzen 1600 OC 1,375v and ram on 2933mhz oc 16gb
Thanks for the response Matt, very appreciated.
In addition I just also wanted to point out I got a reply from AMDs Support Team stating they already got a number of tickets regarding the mentioned WoW issues and will also contact the concern team.
after update to adrenalin 19.1 when I see twitch or youtube, while I swap to any quality(1080 to 160p), the monitor goes all black for a second, only i can see the taskbar then back to normal, happen to me much times in day.
Ryzen 3 2200g - stock(vega 8)
Gskill 2x4GB 2800Mhz
Prime B350M-A with last Bios update (4207)
Driver Adrenalin 19.1 (20 January)
OS: Windows 10 Pro Version: 1809 Build: 17763.253
Hello I have same issue, here is analysis of my dump file. AMD fix it quickly please!!!
Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff802`f2006000 PsLoadedModuleList = 0xfffff802`f23b4150
Debug session time: Tue Jan 22 17:20:05.523 2019 (UTC + 2:00)
System Uptime: 0 days 20:54:36.282
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
fffff808`744dd66c 488b4f38 mov rcx,qword ptr [rdi+38h] ds:002b:ffffc700`56b45d68=????????????????
6: kd> !analyze -v
ERROR: FindPlugIns 80070001
ERROR: Some plugins may not be available 
* Bugcheck Analysis *
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arg1: ffffc700553fe010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff808749a070c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000003a5c, Optional internal context dependent data.
Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
BUILD_VERSION_STRING: 10.0.17134.523 (WinBuild.160101.0800)
fffff808`749a070c ?? ???
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
ANALYSIS_SESSION_TIME: 01-23-2019 01:34:55.0589
ANALYSIS_VERSION: 10.0.18303.1000 amd64fre
ffffd706`8a587570 fffff808`7413cd37 : ffffc700`553fe010 ffffc700`553fe010 ffffd706`8a587710 ffffc700`56b45d30 : watchdog!WdDbgReportRecreate+0x10c
ffffd706`8a5875c0 fffff802`f09ac665 : ffffc700`00000000 ffffc700`543f1030 ffffc700`553fe010 ffffc700`499d4000 : dxgkrnl!TdrUpdateDbgReport+0xe7
ffffd706`8a587610 fffff802`f0a3c98a : ffffc700`499d4000 00000000`00000000 00000000`00000001 ffffc700`495dd001 : dxgmms2!VidSchiResetEngine+0x73d
ffffd706`8a587900 fffff802`f0a19f68 : ffffc700`499d4000 00000000`00000001 00000000`00000000 00000055`d84db47b : dxgmms2!VidSchiResetEngines+0xaa
ffffd706`8a587950 fffff802`f09f6aa6 : 00000000`00000002 00000000`00498249 00000000`0032a27b 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x23498
ffffd706`8a5879c0 fffff802`f098a75a : ffffc700`49324750 ffffc700`495dd000 00000000`ffffffff ffffc700`499d4000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x326
ffffd706`8a587a90 fffff802`f0a00e90 : ffffc700`546d1c00 ffffc700`52fd3a00 ffffc700`546d1c00 ffffc700`52fd3ac0 : dxgmms2!VidSchiScheduleCommandToRun+0x39a
ffffd706`8a587b80 fffff802`f0a00e4e : ffffc700`495dd500 fffff802`f0a00dc0 ffffc700`495dd000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x30
ffffd706`8a587bd0 fffff802`f21362d7 : ffffc700`495da700 fffff802`f0a00dc0 ffffdc01`0bfb9180 00000425`b59bbfff : dxgmms2!VidSchiWorkerThread+0x8e
ffffd706`8a587c10 fffff802`f21b7516 : ffffdc01`0bfb9180 ffffc700`495da700 fffff802`f2136290 00ffaf06`bf34c744 : nt!PspSystemThreadStartup+0x47
ffffd706`8a587c60 00000000`00000000 : ffffd706`8a588000 ffffd706`8a582000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
fffff808`749a070c ?? ???
STACK_COMMAND: .thread ; .cxr ; kb
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OSBUILD_TIMESTAMP: 2019-01-01 08:44:13
Same thing happening to me. Glad to hear this is a driver issue and I hope AMD fix this in the next update. Have people already reported it? Do I need to report it again to them, will it help at all?
Because if they receive one report...what do you think they will think? Just another stupid noob messing around with settings they don't know anything about or what they're doing. If they receive 50 reports...they realize somethings up and look in to it. That's why.
Fair enough, reported it anyway, thanks for the help additionally I was using DX11 and not DX12 but this is issues is getting reported on WoW forums also but I don't think they realise it is to do with drivers.
I was getting this pop up a lot as well: powered down my pc completely switched it back on at the socket after 5 seconds, message still came up. Done the same thing again this time waited roughly 30 secs before turning back on, it did not come up on this occasion. Additionally I have tested other high graphics games, e.g. kingdom come and hitman 2 without any issues, lag or any problems with crashing, it seems to be only world of warcraft.
Because it only happens in warcraft...that's a clue. The form is very detailed as to the computer specifications...they will try and reproduce the issue on similar equipment. If they have the same results...it goes a step further. If they can't reproduce it....read the previous post.
Hey. Registered to say I've got the same problem. Just that my screen shuts down completely and all I can do is restart the PC. Also funny thing it happens only in the newer zones with talking head quests and stuff. I was leveling in <60 zone for hours but when I log in with another character in Legion/Bfa I crash in under 5 minutes every time. For me It's something with accepting quests/ talking heads.
Anyway what should I do. Can I rollback in AMD control panel? Not good with this stuff.
For now, you can simply download and install older drivers. In my case I went back to the 18.12.3 drivers:
Select your graphics card and submit the form.
Now you can find a link for "Previous Drivers" (right above the "Knowledge Base" typing), click that and select one of the older drivers to download. Haven't had any issues with 18.12.3 or 18.11.x for example. Just download the package, install the drivers and maybe check to do a clean, "new" installation.
So far we have reproduced the stutter, but not the crashing.
Please can folks provide clear examples of how to reproduce the crashing and a screenshot of the image quality settings you are using in game?
I don't remember any pattern how the crash happend, I think at least few times it happend while I was doing something with UI, but it wasn't exclusive to that. So sorry I can't help with that unless I reinstall the new drivers.
I also posted crash dump file analysis above, if you need any additional information I'm happy to help if I can. However I reverted back to older drivers already as well.
Edit: To be precise, my issue is the same but I get Wattman settings restored msg as another user described couple posts above.
I cannot provide a screenshot at the time (it's everything on 10 except shadows and SSAO though).
But the crashing apparently was happening randomly, in some places (like Arathi) it was happening several times in a matter of a few minutes (particularly when the silver dragon addon detected a rare creature, it would still crash without it though, just less frequently) and others, such as the horde capital in zandalar was taking like 10 to 20 minutes between crashes.
Inside raids and dungeons it would also take between 10 and 20 minutes.
Sorry i cannot provide you with updates on the debugging of this issue. I would suggest using an earlier driver or to use the DX11 path for now.
I can reproduce the issue on vega 56, preset 6 with CMAA and freesync enabled. The issue happens when you enter an area or start a quest where the talking head appears. (the voice over dialogue when starting certain world quests). The game will pause and sometimes recover whilst the talking head is narrating, sometimes the game exits to windows with DX12 error and warcraft unable to start 3d acceleration (this is rare, is usually recovers). adrenaline 19.1.1 - 19.2.2 have the same issue.