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
Deferred srv*
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
Machine Name:
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
watchdog!WdDbgReportRecreate+0x10c:
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 [80070001]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
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.
Debugging Details:
------------------
Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17134.523 (WinBuild.160101.0800)
DUMP_TYPE: 2
BUGCHECK_P1: ffffc700553fe010
BUGCHECK_P2: fffff808749a070c
BUGCHECK_P3: 0
BUGCHECK_P4: 3a5c
FAULTING_IP:
atikmpag+1070c
fffff808`749a070c ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
CPU_COUNT: 8
CPU_MHZ: d46
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
BUGCHECK_STR: 0x141
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST:
ANALYSIS_SESSION_TIME: 01-23-2019 01:34:55.0589
ANALYSIS_VERSION: 10.0.18303.1000 amd64fre
STACK_TEXT:
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
THREAD_SHA1_HASH_MOD_FUNC: 38ff1601a490f5ffd3426ba59d83f8532ab501a0
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 41d4a678fd2b5de7647f70e4b7606b47dab2cb8a
THREAD_SHA1_HASH_MOD: d61bf2826c83f42798f71aa711aa4f2cb3225799
FOLLOWUP_IP:
atikmpag+1070c
fffff808`749a070c ?? ???
SYMBOL_NAME: atikmpag+1070c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5c368a17
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: LKD_0x141_IMAGE_atikmpag.sys
BUCKET_ID: LKD_0x141_IMAGE_atikmpag.sys
PRIMARY_PROBLEM_CLASS: LKD_0x141_IMAGE_atikmpag.sys
TARGET_TIME: 2019-01-22T15:20:05.000Z
OSBUILD: 17134
OSSERVICEPACK: 523
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-01-01 08:44:13
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17134.523
ANALYSIS_SESSION_ELAPSED_TIME: 184e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:lkd_0x141_image_atikmpag.sys
FAILURE_ID_HASH: {c4561d61-ffbc-583d-5e1a-6fd6e42466ee}
Followup: MachineOwner
---------
Where do you find older drivers like 18.x? I was only able to revert back to 17.x from windows device manager.
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.
Thx I'll give it ago later.
Previous drivers are available on the driver download page...scroll down.
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?
Yes you should report it > Online Service Request | AMD
Why report the same thing numerous times?
Anyway reported, also see: Game doesn't work after 8.1 patch - Technical Support - World of Warcraft Forums