AnsweredAssumed Answered

blue screen radeon-software-crimson-16XX

Question asked by muka on Feb 7, 2016



I have the following nasty issue with new crimson 16.X drivers.

My system randomly crashes while browsing or gaming. It crashes when exiting a game but while gaming it has no issues.

It crashes while browsing, no video running at all. The main Blue Screen messages is: "thread stuck in device driver"


The problems started with any of the new crimson 16.X drivers.

I uninstalled and re-installed the for testing the Crimson-Edition-15.11.1 and Crimson-Edition-15.12, both work without a flaw I have no crashes at all.

No overclocking is done on any component in the system.


My hardware specs are:


Radeon Softwareversion - 16.1.1

Radeon Software Edition - Crimson

Grafik-Chipsatz - AMD Radeon R9 200 Series

Speichergröße - 4096 MB

Speichertyp - GDDR5

Systemtaktrate - 1000 MHz

Windows-Version - Windows 8.1

Systemspeicher - 16 GB

CPU-Typ - Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz



Please find debugging message below and attached with a dxdiag report too :



Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Only kernel address space is available



************* Symbol Path validation summary **************

Response                         Time (ms)     Location


Symbol search path is:

Executable search path is:

Windows 8 Kernel Version 9600 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9600.18185.amd64fre.winblue_ltsb.151230-0600

Machine Name:

Kernel base = 0xfffff800`82c8d000 PsLoadedModuleList = 0xfffff800`82f60630

Debug session time: Sun Feb  7 16:40:19.060 2016 (UTC + 1:00)

System Uptime: 0 days 0:43:57.703

Loading Kernel Symbols


...............................................................Page 143c89 not present in the dump file. Type ".hh dbgerr004" for details



Loading User Symbols

PEB is paged out (Peb.Ldr = 00007ff6`3b809018).  Type ".hh dbgerr001" for details

Loading unloaded module list



*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *



Use !analyze -v to get detailed debugging information.


BugCheck EA, {ffffe0018bae9080, 0, 0, 0}


*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d )


Followup: MachineOwner



0: kd> !analyze -v


*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *




The device driver is spinning in an infinite loop, most likely waiting for

hardware to become idle. This usually indicates problem with the hardware

itself or with the device driver programming the hardware incorrectly.

If the kernel debugger is connected and running when watchdog detects a

timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()

and detailed message including bugcheck arguments will be printed to the

debugger. This way we can identify an offending thread, set breakpoints in it,

and hit go to return to the spinning code to debug it further. Because

KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck

information in this case. The arguments are already printed out to the kernel

debugger. You can also retrieve them from a global variable via

"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).

On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is

interrupted by hardware interrupt and ISR or DPC routine is running at the time

of the bugcheck (this is because the timeout's work item can be delivered and

handled on the second CPU and the same time). If this is the case you will have

to look deeper at the offending thread's stack (e.g. using dds) to determine

spinning code which caused the timeout to occur.


Arg1: ffffe0018bae9080, Pointer to a stuck thread object.  Do .thread then kb on it to find

    the hung location.

Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.

Arg3: 0000000000000000, Pointer to offending driver name.

Arg4: 0000000000000000, Number of times this error occurred.  If a debugger is attached,

    this error is not always fatal -- see DESCRIPTION below.  On the

    blue screen, this will always equal 1.


Debugging Details:




FAULTING_THREAD:  ffffe0018bae9080






PROCESS_NAME:  plugin-contain




ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre


LAST_CONTROL_TRANSFER:  from fffff800688af755 to fffff80082ddb2a0



ffffd000`346a94e8 fffff800`688af755 : 00000000`000000ea ffffe001`8bae9080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

ffffd000`346a94f0 fffff800`688a8672 : ffffd000`346a95e8 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x4d

ffffd000`346a9560 fffff800`6911d7b3 : 00000000`00000000 ffffe001`8a728000 ffffd000`346a96e1 00000000`00000095 : dxgkrnl!TdrTimedOperationDelay+0x899e

ffffd000`346a95c0 fffff800`6911710e : ffffe001`8a706768 00000000`00000000 ffffe001`8a72d200 00000000`000007d0 : atikmdag+0x447b3

ffffd000`346a9640 fffff800`6917148e : 00000000`00000001 00000000`00000064 ffffd000`346a96e1 ffffe001`8a728000 : atikmdag+0x3e10e

ffffd000`346a9680 fffff800`69175d3b : ffffe001`8a6fc4c4 00000000`00000000 00000000`00000095 ffffe001`8bbe1000 : atikmdag+0x9848e

ffffd000`346a9740 fffff800`691775aa : ffffe001`8a6fc4c4 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x9cd3b

ffffd000`346a9780 fffff800`69eaea57 : ffffe001`96e27004 00000000`00000000 00000000`001f0e7c 00000000`00000fff : atikmdag+0x9e5aa

ffffd000`346a97b0 fffff800`69f2e5c7 : ffffe001`964c8e84 ffffd000`346a9879 00000000`00000000 ffffe001`8bbe1000 : atikmdag+0xdd5a57

ffffd000`346a97e0 fffff800`69e9f26f : 00000000`00000020 fffff800`69bb54e1 00000000`00000002 00000000`00000000 : atikmdag+0xe555c7

ffffd000`346a9810 fffff800`69e9d5cf : ffffe001`00000000 00000000`00000001 ffffe001`8bbe1000 ffffe001`00000001 : atikmdag+0xdc626f

ffffd000`346a98e0 fffff800`69e863c2 : ffffd000`346a9b08 00000000`00000020 00000000`00000001 ffffd000`346a9a70 : atikmdag+0xdc45cf

ffffd000`346a9950 fffff800`69e8d2d8 : 00000000`00000001 ffffe001`96d81694 00000000`00000000 00000000`00000000 : atikmdag+0xdad3c2

ffffd000`346a9a30 fffff800`6912cd4f : ffffe001`8a6feaa0 00000000`00000001 00000000`00000001 ffffe001`98a7de60 : atikmdag+0xdb42d8

ffffd000`346a9ab0 fffff800`691c8df1 : ffffe001`964bddc0 ffffe001`00000000 00000000`00000000 fffff800`00000000 : atikmdag+0x53d4f

ffffd000`346a9b60 fffff800`691d4286 : ffffd000`346a9c60 ffffe001`9756a040 ffffc001`3560f910 00000000`c0000001 : atikmdag+0xefdf1

ffffd000`346a9bb0 fffff800`68e1faaa : ffffd000`346a9e20 ffffd000`346a9e20 ffffd000`346a9c60 00000000`00000000 : atikmdag+0xfb286

ffffd000`346a9be0 fffff800`688fe25b : ffffd000`346aa950 00000000`00000200 ffffc001`3e6fa000 ffffd000`346a9dc0 : atikmpag+0xeaaa

ffffd000`346a9ca0 fffff800`688f6c35 : ffffc001`3e68d000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x43b

ffffd000`346aa7f0 fffff800`82de6ab3 : ffffe001`8bae9080 ffffe001`8bae9080 0000008d`477bf700 ffffe001`8b895640 : dxgkrnl!DxgkRender+0x325

ffffd000`346aab00 00007ffa`4b0c17fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

0000008d`477bf4e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`4b0c17fa



STACK_COMMAND:  .thread 0xffffe0018bae9080 ; kb




fffff800`688af755 cc              int     3




SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: dxgkrnl


IMAGE_NAME:  dxgkrnl.sys






BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys




FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys


FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}


Followup: MachineOwner




Many thanks in advanced for the help and support.


With best regards,