AnsweredAssumed Answered

AMD Radeon R9 200 Driver Crashes in Windows 10

Question asked by djryan7 on Jul 31, 2015
Latest reply on Dec 25, 2015 by chriskolossal

Latest drivers continue to crash windows 10. Multiple entires in the event log make it apparent it is the video driver.

 

 

 

ATI EEU PnP start/stop failed

 

 

Log Name:      System

Source:        Microsoft-Windows-WER-SystemErrorReporting

Date:          7/31/2015 1:03:48 PM

Event ID:      1001

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      ASTRAIOS

Description:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ea (0xffffe0015766f040, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\073115-35312-01.dmp. Report Id: 073115-35312-01.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />

    <EventID Qualifiers="16384">1001</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-07-31T20:03:48.000000000Z" />

    <EventRecordID>4763</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>ASTRAIOS</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">0x000000ea (0xffffe0015766f040, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)</Data>

    <Data Name="param2">C:\WINDOWS\Minidump\073115-35312-01.dmp</Data>

    <Data Name="param3">073115-35312-01</Data>

  </EventData>

</Event>

 

Crash occurs in atikmdag.sys driver.

 

 

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

Use !analyze -v to get detailed debugging information.

BugCheck EA, {ffffe001d584d540, 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
---------

2: 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: ffffe001d584d540, 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:  XPS 8700

BIOS_DATE:  12/08/2014

BASEBOARD_PRODUCT:  0KWVT8

BASEBOARD_VERSION:  A03

BUGCHECK_P1: ffffe001d584d540

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  d584d540

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: e08

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 x86fre

LAST_CONTROL_TRANSFER:  from fffff801dcaae15c to fffff80016dcb220

STACK_TEXT: 
ffffd000`fc57f1d8 fffff801`dcaae15c : 00000000`000000ea ffffe001`d584d540 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`fc57f1e0 fffff801`dcaae21e : ffffd000`fc57f2b8 fffff801`df9906dc ffffd000`fc57f2b8 ffffd000`fc57f380 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x24
ffffd000`fc57f250 fffff801`df942003 : ffffe001`da282000 ffffd000`fc57f3b1 ffffd000`fc57f380 fffff801`df9906c8 : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffd000`fc57f290 fffff801`df93c09e : ffff02fb`9729cbfc fffff801`df9906dc ffffe001`da447b18 00000000`00000000 : atikmdag+0x42003
ffffd000`fc57f310 fffff801`df9905f3 : 00000000`00000001 00000000`00000000 ffffd000`fc57f3b1 00000000`00000000 : atikmdag+0x3c09e
ffffd000`fc57f350 fffff801`e05d98f7 : fffff801`dfd9069c 00000000`000014e5 ffffe001`da447b18 00000000`00000000 : atikmdag+0x905f3
ffffd000`fc57f410 fffff801`e0674aef : ffffe001`da513014 ffffe001`0000000e 00000000`0101000c 00000000`00001000 : atikmdag+0xcd98f7
ffffd000`fc57f4a0 fffff801`df99604a : 00000000`00000001 fffff801`dfdc06b8 00000000`80020000 ffffd000`fc57f5f8 : atikmdag+0xd74aef
ffffd000`fc57f4e0 fffff801`e05d40ea : ffffe001`da5336b4 ffffd000`fc57f589 ffffd000`fc57f570 00000000`00000046 : atikmdag+0x9604a
ffffd000`fc57f520 fffff801`e05bcd88 : ffffd000`fc57f6c8 ffffd000`fc57f501 ffffd000`fc57f6c8 fffff801`db5563e0 : atikmdag+0xcd40ea
ffffd000`fc57f550 fffff801`e05c17d4 : ffffe001`da5321d4 fffff800`00000046 00000000`00000001 fffff801`df937e63 : atikmdag+0xcbcd88
ffffd000`fc57f5f0 fffff801`df94f04b : ffffe001`da46c010 00001f80`00000000 00000004`00000048 ffffd000`fc57f670 : atikmdag+0xcc17d4
ffffd000`fc57f670 fffff801`df94fdaf : ffffe001`da46c030 ffffe001`da2aad00 ffffe001`da2aad00 00000000`00000001 : atikmdag+0x4f04b
ffffd000`fc57f6f0 fffff801`df910f1f : 00000000`00000001 00000000`00000001 00000000`ffffffff 00000000`00000000 : atikmdag+0x4fdaf
ffffd000`fc57f720 fffff801`df91729d : ffffe001`da2aad00 00000000`ffffffff 00000000`00000001 00000000`00000000 : atikmdag+0x10f1f
ffffd000`fc57f750 fffff801`dd61464b : 00000000`00000000 00000000`00000000 ffffe001`da375300 00000000`ffffffff : atikmdag+0x1729d
ffffd000`fc57f7c0 fffff801`dd60a033 : 00000000`c0000001 00000000`00000000 00000000`ffffffff 00000000`ffffffff : atikmpag+0x1464b
ffffd000`fc57f810 fffff801`dcb3f0a9 : 00000000`00000000 00000000`ffffffff 00000000`00000001 00000000`00000000 : atikmpag+0xa033
ffffd000`fc57f8a0 fffff801`dcb3eb0d : 00000000`00000000 ffffe001`da345010 00000000`00000002 ffffe001`da3451b8 : dxgkrnl!DpiDxgkDdiSetPowerState+0x51
ffffd000`fc57f900 fffff801`dcb3f4fc : ffffd000`fc57f902 00000000`00000001 00000000`00000001 00000000`00000000 : dxgkrnl!DpiFdoSetAdapterPowerState+0x24d
ffffd000`fc57f9a0 fffff801`dcb407cb : ffffe001`da345000 ffffe001`da2fc2b0 ffffe001`da345010 fffff800`16d85252 : dxgkrnl!DpiFdoHandleDevicePower+0x2fc
ffffd000`fc57fa30 fffff800`16da0f3e : 00000000`00000001 00000000`00000001 00000000`00000001 00000000`00000000 : dxgkrnl!DpiDispatchPower+0x8b
ffffd000`fc57fb50 fffff800`16d63698 : e8c90348`c86348c0 ffffe001`d584d540 ffffe001`d5883840 ffffd000`f79cccc0 : nt!PopIrpWorker+0x2d6
ffffd000`fc57fc00 fffff800`16dd0306 : ffffd000`f79c0180 ffffe001`d584d540 ffffd000`f79cccc0 5c8b4850`1c8966ea : nt!PspSystemThreadStartup+0x58
ffffd000`fc57fc60 00000000`00000000 : ffffd000`fc580000 ffffd000`fc57a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .thread 0xffffe001d584d540 ; kb

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24
fffff801`dcaae15c 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:  55af128a

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
---------

 

Message was edited by: David Ryan

 

This seems to only occur when the screen is set to turn it self off after a period of time via the power settings. If I leave the set to never it does not crash. This appears to always happen when it is in sleep mode.

 

Thanks,

Dave Ryan

 

 

Well evidently no one at AMD is working this issue. I upgraded to the Beta version and it still crashes. I don't think I've seen support this bad.

 

David Ryan

9/25/2015

Outcomes