AnsweredAssumed Answered

Radeon R9 200 series System reboots when waking from monitor sleep THREAD_STUCK_IN_DEVICE_DRIVER bugcheck

Question asked by joelransom on Aug 13, 2015
Latest reply on Dec 21, 2015 by cloo

I just upgraded to Windows 10 and installed the latest driver (15.200.1062.1002). I had a similar problem with Windows 8 but I'll focus on Windows 10 here.

 

I have all power save options turned off except for putting the monitor to sleep after n minutes.

When the monitors are asleep and I try to "wake" the computer the system reboots.

If I turn off sleep for the monitors everything works fine for days on end.

 

I'm not experienced inspecting crash dump files but I managed to get the following from SysInternals process monitor:

Any help would be appreciated.

Regards,

 

Joel

 


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16430.amd64fre.th1.150807-2049
Machine Name:
Kernel base = 0xfffff801`b4490000 PsLoadedModuleList = 0xfffff801`b47b5030
Debug session time: Thu Aug 13 18:59:36.436 2015 (UTC - 7:00)
System Uptime: 0 days 4:45:14.131
Loading Kernel Symbols
.............................................................Page 13523 not present in the dump file. Type ".hh dbgerr004" for details
..
................................................................
...............................................................
Loading User Symbols

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {ffffe0016ea6f040, 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+24 )

Followup:     MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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.
Arguments:
Arg1: ffffe0016ea6f040, 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:
------------------


SYSTEM_SKU:  0x05B7

BIOS_DATE:  07/09/2015

BASEBOARD_PRODUCT:  0KWVT8

BASEBOARD_VERSION:  A02

BUGCHECK_P1: ffffe0016ea6f040

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  6ea6f040

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: d40

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER:  from fffff801cef4e0ec to fffff801b45ddd00

STACK_TEXT: 
ffffd000`8a67e1d8 fffff801`cef4e0ec : 00000000`000000ea ffffe001`6ea6f040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`8a67e1e0 fffff801`cef4e1ae : ffffd000`8a67e2b8 fffff801`d21b06dc ffffd000`8a67e2b8 ffffd000`8a67e380 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x24
ffffd000`8a67e250 fffff801`d2162003 : ffffe001`75582000 ffffd000`8a67e3b1 ffffd000`8a67e380 fffff801`d21b06c8 : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffd000`8a67e290 fffff801`d215c09e : ffff663a`23f3300d fffff801`d21b06dc ffffe001`73f18b18 00000000`00000000 : atikmdag+0x42003
ffffd000`8a67e310 fffff801`d21b05f3 : 00000000`00000001 00000000`00000000 ffffd000`8a67e3b1 00000000`00000000 : atikmdag+0x3c09e
ffffd000`8a67e350 fffff801`d2df98f7 : fffff801`d25b069c 00000000`000014e5 ffffe001`73f18b18 00000000`00000000 : atikmdag+0x905f3
ffffd000`8a67e410 fffff801`d2e94aef : ffffe001`73c92504 ffffe001`0000000e 00000000`0101000c 00000000`00001000 : atikmdag+0xcd98f7
ffffd000`8a67e4a0 fffff801`d21b604a : 00000000`00000001 fffff801`d25e06b8 00000000`80020000 ffffd000`8a67e5f8 : atikmdag+0xd74aef
ffffd000`8a67e4e0 fffff801`d2df40ea : ffffe001`6ea520b4 ffffd000`8a67e589 ffffd000`8a67e570 00000000`00000046 : atikmdag+0x9604a
ffffd000`8a67e520 fffff801`d2ddcd88 : ffffd000`8a67e6c8 ffffd000`8a67e501 ffffd000`8a67e6c8 fffff801`ce0063e0 : atikmdag+0xcd40ea
ffffd000`8a67e550 fffff801`d2de17d4 : ffffe001`6ea751d4 00000000`00000046 00000000`00000001 fffff801`d2157e63 : atikmdag+0xcbcd88
ffffd000`8a67e5f0 fffff801`d216f04b : ffffe001`74bd4440 00001fa0`004d001d 00000004`00000048 ffffd000`8a67e670 : atikmdag+0xcc17d4
ffffd000`8a67e670 fffff801`d216fdaf : ffffe001`74bd4460 ffffe001`738487c0 ffffe001`738487c0 00000000`00000001 : atikmdag+0x4f04b
ffffd000`8a67e6f0 fffff801`d2130f1f : 00000000`00000001 00000000`00000001 00000000`ffffffff 00000000`00000000 : atikmdag+0x4fdaf
ffffd000`8a67e720 fffff801`d213729d : ffffe001`738487c0 00000000`ffffffff 00000000`00000001 00000000`00000000 : atikmdag+0x10f1f
ffffd000`8a67e750 fffff801`cfa9464b : 00000000`00000000 00000000`00000000 ffffe001`73870300 00000000`ffffffff : atikmdag+0x1729d
ffffd000`8a67e7c0 fffff801`cfa8a033 : 00000000`c0000001 00000000`00000000 00000000`ffffffff 00000000`ffffffff : atikmpag+0x1464b
ffffd000`8a67e810 fffff801`cefdf179 : 00000000`00000000 00000000`ffffffff 00000000`00000001 00000000`00000000 : atikmpag+0xa033
ffffd000`8a67e8a0 fffff801`cefdebdd : 00000000`00000000 ffffe001`73f133e0 00000000`00000002 ffffe001`73f13588 : dxgkrnl!DpiDxgkDdiSetPowerState+0x51
ffffd000`8a67e900 fffff801`cefdf5cc : ffffd000`8a67e902 00000000`00000001 00000000`00000001 00000000`00000000 : dxgkrnl!DpiFdoSetAdapterPowerState+0x24d
ffffd000`8a67e9a0 fffff801`cefe08bb : ffffe001`73f13300 ffffe001`738c2190 ffffe001`73f133e0 fffff801`b4597d42 : dxgkrnl!DpiFdoHandleDevicePower+0x2fc
ffffd000`8a67ea30 fffff801`b45b3a2e : 00000000`00000001 00000000`00000001 00000000`00000001 ffffe001`00000000 : dxgkrnl!DpiDispatchPower+0x8b
ffffd000`8a67eb50 fffff801`b4576948 : 420fc6b6`0f411afe ffffe001`6ea6f040 ffffe001`6ea84840 ffffd000`8634ccc0 : nt!PopIrpWorker+0x2d6
ffffd000`8a67ec00 fffff801`b45e2de6 : ffffd000`86340180 ffffe001`6ea6f040 ffffd000`8634ccc0 c683c033`3474c084 : nt!PspSystemThreadStartup+0x58
ffffd000`8a67ec60 00000000`00000000 : ffffd000`8a67f000 ffffd000`8a679000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .thread 0xffffe0016ea6f040 ; kb

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24
fffff801`cef4e0ec cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55bebfed

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

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

Followup:     MachineOwner
---------

6: kd> lmvm dxgkrnl
Browse full module list
start             end                 module name
fffff801`cef30000 fffff801`cf11a000   dxgkrnl    (pdb symbols)          c:\symbols\dxgkrnl.pdb\92FD8780CC0E4E2D92505DA3E934CD881\dxgkrnl.pdb
    Loaded symbol image file: dxgkrnl.sys
    Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
    Image name: dxgkrnl.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Aug 02 18:12:13 2015 (55BEBFED)
    CheckSum:         001E8273
    ImageSize:        001EA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Outcomes