23 Replies Latest reply on Dec 26, 2015 4:43 AM by chriskolossal

    AMD Radeon R9 200 Driver Crashes in Windows 10

    djryan7

      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

        • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
          xtr3mer

          Same problem here using Windows 10 x64 and a Radeon HD 5850.

           

          When the computer is going into standby following events appear in this order:

           

          Protokollname: Application

          Quelle:        .NET Runtime

          Datum:        21.08.2015 04:51:54

          Ereignis-ID:  1026

          Aufgabenkategorie:Keine

          Ebene:        Fehler

          Schlüsselwörter:Klassisch

          Benutzer:      Nicht zutreffend

          Computer:      DESKTOP

          Beschreibung:

          Anwendung: MOM.exe

          Frameworkversion: v4.0.30319

          Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.

          Ausnahmeinformationen: System.Reflection.TargetInvocationException

          Stapel:

            bei System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)

            bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])

            bei System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)

            bei System.RuntimeType.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[], System.Reflection.ParameterModifier[], System.Globalization.CultureInfo, System.String[])

            bei System.Type.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[])

            bei ATI.ACE.MOM.EXE.MOM.Main(System.String[])

           

          Ereignis-XML:

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

            <System>

              <Provider Name=".NET Runtime" />

              <EventID Qualifiers="0">1026</EventID>

              <Level>2</Level>

              <Task>0</Task>

              <Keywords>0x80000000000000</Keywords>

              <TimeCreated SystemTime="2015-08-21T02:51:54.000000000Z" />

              <EventRecordID>5205</EventRecordID>

              <Channel>Application</Channel>

              <Computer>DESKTOP</Computer>

              <Security />

            </System>

            <EventData>

              <Data>Anwendung: MOM.exe

          Frameworkversion: v4.0.30319

          Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.

          Ausnahmeinformationen: System.Reflection.TargetInvocationException

          Stapel:

            bei System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)

            bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])

            bei System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)

            bei System.RuntimeType.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[], System.Reflection.ParameterModifier[], System.Globalization.CultureInfo, System.String[])

            bei System.Type.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[])

            bei ATI.ACE.MOM.EXE.MOM.Main(System.String[])

          </Data>

            </EventData>

          </Event>

           

          followed by

           

          Protokollname: Application

          Quelle:        Application Error

          Datum:         21.08.2015 04:51:54

          Ereignis-ID:   1000

          Aufgabenkategorie:(100)

          Ebene:         Fehler

          Schlüsselwörter:Klassisch

          Benutzer:      Nicht zutreffend

          Computer:      DESKTOP

          Beschreibung:

          Name der fehlerhaften Anwendung: MOM.exe, Version: 4.5.0.0, Zeitstempel: 0x53ad0e3f

          Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.10240.16384, Zeitstempel: 0x559f38c3

          Ausnahmecode: 0xe0434352

          Fehleroffset: 0x000000000002a1c8

          ID des fehlerhaften Prozesses: 0xd30

          Startzeit der fehlerhaften Anwendung: 0x01d0dbbc56a9f72f

          Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\MOM.exe

          Pfad des fehlerhaften Moduls: C:\Windows\system32\KERNELBASE.dll

          Berichtskennung: f78a7fbb-9d27-43df-93c1-ea0093bb1ef2

          Vollständiger Name des fehlerhaften Pakets:

          Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

          Ereignis-XML:

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

            <System>

              <Provider Name="Application Error" />

              <EventID Qualifiers="0">1000</EventID>

              <Level>2</Level>

              <Task>100</Task>

              <Keywords>0x80000000000000</Keywords>

              <TimeCreated SystemTime="2015-08-21T02:51:54.000000000Z" />

              <EventRecordID>5206</EventRecordID>

              <Channel>Application</Channel>

              <Computer>DESKTOP</Computer>

              <Security />

            </System>

            <EventData>

              <Data>MOM.exe</Data>

              <Data>4.5.0.0</Data>

              <Data>53ad0e3f</Data>

              <Data>KERNELBASE.dll</Data>

              <Data>10.0.10240.16384</Data>

              <Data>559f38c3</Data>

              <Data>e0434352</Data>

              <Data>000000000002a1c8</Data>

              <Data>d30</Data>

              <Data>01d0dbbc56a9f72f</Data>

              <Data>C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\MOM.exe</Data>

              <Data>C:\Windows\system32\KERNELBASE.dll</Data>

              <Data>f78a7fbb-9d27-43df-93c1-ea0093bb1ef2</Data>

              <Data>

              </Data>

              <Data>

              </Data>

            </EventData>

          </Event>

           

          followed by

           

          Protokollname: Application

          Quelle:        ATIeRecord

          Datum:         21.08.2015 04:52:24

          Ereignis-ID:   16396

          Aufgabenkategorie:EEU

          Ebene:         Fehler

          Schlüsselwörter:Klassisch

          Benutzer:      Nicht zutreffend

          Computer:      DESKTOP

          Beschreibung:

          ATI EEU PnP start/stop failed

          Ereignis-XML:

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

            <System>

              <Provider Name="ATIeRecord" />

              <EventID Qualifiers="49152">16396</EventID>

              <Level>2</Level>

              <Task>16</Task>

              <Keywords>0x80000000000000</Keywords>

              <TimeCreated SystemTime="2015-08-21T02:52:24.000000000Z" />

              <EventRecordID>5208</EventRecordID>

              <Channel>Application</Channel>

              <Computer>DESKTOP</Computer>

              <Security />

            </System>

            <EventData>

            </EventData>

          </Event>

           

          Please can somebody at AMD take care of this?

           

          Thanks

          • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
            _g_

            I have the exact same problem, AMD fix your drivers please.

            -----------------------------------------------------------------------------------------

             

            Windows version: Windows 10 , 10.0, build: 10240

            Windows dir:

            C:\WINDOWS

            Hardware: XPS 8700, Dell Inc., 0KWVT8

            CPU: GenuineIntel

            Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Intel586, level: 6

            8 logical

            processors, active mask: 255

            RAM: 34308579328 bytes

            total

             

            Graphics Card Manufacturer Built by AMD
            Graphics Chipset AMD Radeon (TM) R9 200 Series
            Device ID 6811
            Vendor ID 1002
            Subsystem ID 0B04
            Subsystem Vendor ID 1002
            Revision ID 00
            Graphics Bus Capability PCI Express 3.0
            Maximum Bus Setting PCI Express 3.0x16
            BIOS Version 015.041.000.000
            BIOS Part Number 113-C6300500-102
            BIOS Date 2013/11/26
            Memory Size 2048 MB
            Memory Type GDDR5
            Core Clock in MHz 925 MHz
            Memory Clock in MHz 1400 MHz
            Total Memory Bandwidth in GByte/s 179.2 GByte/s

             

            Driver Packaging Version 15.20.1062.1004-150803a1-187674C
            Catalyst Version 15.7.1
            Provider Advanced Micro Devices, Inc.
            2D Driver Version 8.01.01.1500
            2D Driver File Path /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0000
            Direct3D Version 9.14.10.01128
            OpenGL Version 6.14.10.13399
            Mantle Driver Version 9.1.10.0077
            Mantle API Version 98308
            AMD Catalyst Control Center Version 2015.0804.21.41908
            AMD Audio Driver Version 10.0.0.01

             

             

             

             


            Crash Dump Analysis


             

             

            Crash dump
            directory: C:\WINDOWS\Minidump

             

            Crash dumps are enabled on your
            computer.

            On
            Mon 7/09/2015 10:04:10 AM GMT your computer crashed

            crash dump file:
            C:\WINDOWS\Minidump\090715-7375-01.dmp
            This was probably caused by the
            following module: dxgkrnl.sys (dxgkrnl+0x1E0EC)
            Bugcheck code:
            0x100000EA (0xFFFFE001F9049680, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Mon 7/09/2015 10:04:10 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\memory.dmp
            This was probably
            caused by the following module: atikmdag.sys (atikmdag+0x42043)
            Bugcheck code: 0xEA
            (0xFFFFE001F9049680, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER
            file path:
            C:\WINDOWS\system32\drivers\atikmdag.sys
            product: ATI Radeon
            Family

            company: Advanced Micro Devices, Inc.
            description: ATI Radeon
            Kernel Mode Driver
            Bug check description: This indicates that a thread in a
            device driver is endlessly spinning.
            This appears to be a typical software
            driver bug and is not likely to be caused by a hardware problem.
            A third
            party driver was identified as the probable root cause of this system error. It
            is suggested you look for an update for the following driver: atikmdag.sys (ATI
            Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
            Google query:
            Advanced Micro Devices, Inc.
            THREAD_STUCK_IN_DEVICE_DRIVER



            On Sun 30/08/2015 5:07:21 AM GMT
            your computer crashed

            crash dump file:
            C:\WINDOWS\Minidump\083015-7312-01.dmp
            This was probably caused by the
            following module: dxgkrnl.sys (dxgkrnl+0x1E0EC)
            Bugcheck code:
            0x100000EA (0xFFFFE0015FF2B040, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Thu 27/08/2015 8:11:54 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\Minidump\082715-7343-01.dmp
            This
            was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E0EC)
            Bugcheck code:
            0x100000EA (0xFFFFE0010D2F3040, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Thu 27/08/2015 4:07:40 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\Minidump\082715-7390-01.dmp
            This
            was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E0EC)
            Bugcheck code:
            0x100000EA (0xFFFFE00070AF3040, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Thu 27/08/2015 1:41:44 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\Minidump\082715-7296-01.dmp
            This
            was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E0EC)
            Bugcheck code:
            0x100000EA (0xFFFFE001D352E040, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Sun 16/08/2015 4:23:10 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\Minidump\081615-7265-01.dmp
            This
            was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E0EC)
            Bugcheck code:
            0x100000EA (0xFFFFE001B48F7040, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Sat 15/08/2015 12:34:14 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\Minidump\081515-7687-01.dmp
            This
            was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E19C)
            Bugcheck code:
            0x100000EA (0xFFFFE000EEF13040, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Fri 14/08/2015 9:36:10 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\Minidump\081415-7437-01.dmp
            This
            was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E19C)
            Bugcheck code:
            0x100000EA (0xFFFFE000892F3040, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


            On Tue 11/08/2015 9:24:59 AM GMT your computer
            crashed

            crash dump file: C:\WINDOWS\Minidump\081115-7312-01.dmp
            This
            was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E19C)
            Bugcheck code:
            0x100000EA (0xFFFFE0009EB12840, 0x0, 0x0, 0x0)
            Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
            file path:
            C:\WINDOWS\system32\drivers\dxgkrnl.sys
            product: Microsoft® Windows® Operating System
            company: Microsoft Corporation
            description: DirectX Graphics
            Kernel
            Bug check description: This indicates that a thread in a device driver
            is endlessly spinning.
            This appears to be a typical software driver bug and
            is not likely to be caused by a hardware problem.
            The crash took place in a
            standard Microsoft module. Your system configuration may be incorrect. Possibly
            this problem is caused by another driver on your system that cannot be
            identified at this time.


             

             


            Conclusion


             

             

            14 crash dumps
            have been found and analyzed. Only 10 are included in this report. A third party
            driver has been identified to be causing system crashes on your computer. It is
            strongly suggested that you check for updates for these drivers on their company
            websites. Click on the links below to search with Google for updates for these
            drivers:

            atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro
            Devices, Inc.)


            • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
              joelransom

              Why is  xtr3mer 's post marked as a "correct answer"?

              • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
                djryan7

                This has still not been addressed by AMD and I have not heard 1 item about any attempt to fix this issue. This is serious and I sure wish someone would take responsibility for this problem.

                 

                David Ryan

                • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
                  cloo

                  I have the same issue on my Dell XPS8700 with the R9 270. Has been an issue only since upgrading to Windows 10.

                   

                  I have tried a clean install of Windows 10, both the latest driver (15.7.1) and beta driver (15.8 beta) and still have the issue - when the PC turns off the monitor based on the power saving settings (eg. after 10 mins) the system crashes and reboots shortly after the screen turns off. If you wake it up quickly just after the screen turns off (eg. move the mouse or type on the keyboard) it is OK.

                   

                  Sometimes it saves a memory dumpfile, sometimes it doesn't (system will log an unexpected shutdown in the Event Viewer).

                   

                  I did, however notice that if you LOG OUT and just leave it on the Windows log-in screen with list of users, the monitor sleep function appears to work fine. The crash only occurs when there is a user logged into Windows at the time.

                   

                  Note: Also got a new motherboard yesterday (Dell tech replaced it with a refurbished one) to resolve another issue but this problem still remains.

                   

                  You guys having the same issue and finding it OK if logged out of Windows?

                   

                  Chris

                  • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
                    drbobo

                    Not sure what the protocol of this forum is, but this is still a problems and I haven't seen anyone from AMD comment at all on this. Must be a real bug as over 1800 views of this post in the last 6 weeks. Workaround I have discovered is to go into Win 10 SCREEN settings and set the screen to 'Never' turn off. Stopped BSODs coming out of hibernation on my Dell XPS 8700.

                      • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
                        ladyinmt

                        Just want to note that I'm also having an issue with this video card on Windows 10! 

                         

                        My machine was fine with Win7 but a couple nights ago, I finally narrowed down the lockups (since upgrading to Win10) to this video card.  Like other people have mentioned in this thread, I'm able to avoid the "lockups" by configuring my SYSTEM | SCREEN settings to never sleep. 

                         

                        Hoping for a permanent fix soon!

                         

                        ~Heather

                      • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
                        marcel

                        Same issue here, DELL XPS 8700 with AMD R9 200. Beta drivers have not provided a solution so far aswell...

                        • Re: AMD Radeon R9 200 Driver Crashes in Windows 10
                          chriskolossal

                          Anyone figured anything out with this yet? Built a rig for a friend and am having this same issue. Tried the newest crimson driver and the beta with no luck. Get the Thread_stuck_in_device_driver bsod with any game I try and run. Its on a fresh install of windows 10 with a clean install of the crimson drivers. I hope they figure this issue out.