Windows 10: Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl

Discus and support Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl in Windows 10 BSOD Crashes and Debugging to solve the problem; Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl I often get bsod Thread_stuck_in_device_driver while playing csgo. I have... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by rhscz, Jun 5, 2017.

  1. rhscz Win User

    Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl


    Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl
    I often get bsod Thread_stuck_in_device_driver while playing csgo. I have freshly(maybe 1 week ago) installed windows 10 creators update (i must reinstall because upgrade from anniversary update doesn't work). bsod was aslo on anniversary update and i somehow repaired but i can't remember how i fixed that. I think i somehow got another dxgkrrnl.sys for same os file and i replaced it.
    P.S. i have all drivers needed installed.
    Attachment 138246

    :)
     
    rhscz, Jun 5, 2017
    #1

  2. 0xEA Bugcheck causes "Critical" system reboot with BugcheckCode 234

    Since 08/09/15, my Windows 10 system has repeatedly rebooted -- and it is becoming more frequent.

    I downloaded and installed WinDbg and loaded MEMORY.DMP. The debugger seems to think the problem is in dxgkrnl.sys. After doing some research, I uninstalled all of the AMD utilities and drivers and reinstalled the current driver (15.200.1062.1004) for
    my AMD Radeon R9 200 Series display adapter without installing the CCC or Raptor. The problem continues to occur -- dxgkrnl.sys is showing as version 10.0.10240.16425. I am also getting a resource exhaustion error which may be related but I have 24GB of
    RAM so that doesn't really make sense to me.

    Any help would be appreciated.

    Here is the debug information:

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

    Kernel Bitmap Dump File: Only kernel address space is available

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

    Response Time (ms) Location

    Deferred srv*

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

    Response Time (ms) Location

    Deferred srv*

    Symbol search path is: srv*

    Executable search path is: srv*

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

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 10240.16463.amd64fre.th1.150819-1946

    Machine Name:

    Kernel base = 0xfffff802`58c83000 PsLoadedModuleList = 0xfffff802`58fa8030

    Debug session time: Mon Sep 7 10:31:24.128 2015 (UTC - 4:00)

    System Uptime: 0 days 1:23:04.833

    Loading Kernel Symbols

    ............................................................Page dc97f 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, {ffffe0005b06c040, 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

    ---------

    0: 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: ffffe0005b06c040, 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: ffffe0005b06c040

    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

    BUGCHECK_STR: 0xEA

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

    LAST_CONTROL_TRANSFER: from fffff8009e07e0ec to fffff80258dd1240

    STACK_TEXT:

    ffffd000`bffac1d8 fffff800`9e07e0ec : 00000000`000000ea ffffe000`5b06c040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

    ffffd000`bffac1e0 fffff800`9e07e1ae : ffffd000`bffac2b8 fffff800`a0f70700 ffffd000`bffac2b8 ffffd000`bffac380 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x24

    ffffd000`bffac250 fffff800`a0f22043 : ffffe000`5b009000 ffffd000`bffac3b1 ffffd000`bffac380 fffff800`a0f706ec : dxgkrnl!TdrTimedOperationDelay+0xbe

    ffffd000`bffac290 fffff800`a0f1c0ee : ffff0721`b3f1aa4e fffff800`a0f70700 ffffe000`5fce4018 00000000`00000000 : atikmdag+0x42043

    ffffd000`bffac310 fffff800`a0f70617 : 00000000`00000001 00000000`00000200 ffffd000`bffac3b1 00000000`00000200 : atikmdag+0x3c0ee

    ffffd000`bffac350 fffff800`a1bb98f7 : fffff800`a1370360 00000000`000014e5 ffffe000`5fce4018 00000000`00000000 : atikmdag+0x90617

    ffffd000`bffac410 fffff800`a1c54aef : ffffe000`60ab9014 ffffe000`0000000e 00000000`0101000c 00000000`00001000 : atikmdag+0xcd98f7

    ffffd000`bffac4a0 fffff800`a0f76092 : 00000000`00000001 fffff800`a13a06b8 00000000`80020000 ffffd000`bffac5f8 : atikmdag+0xd74aef

    ffffd000`bffac4e0 fffff800`a1bb40ea : ffffe000`5fce22f4 ffffd000`bffac589 ffffd000`bffac570 00000000`00000046 : atikmdag+0x96092

    ffffd000`bffac520 fffff800`a1b9cd88 : ffffd000`bffac6c8 ffffd000`bffac501 ffffd000`bffac6c8 fffff800`9c7363e0 : atikmdag+0xcd40ea

    ffffd000`bffac550 fffff800`a1ba17d4 : ffffe000`5fa201d4 00000000`00000046 00000000`00000001 fffff800`a0f17eb3 : atikmdag+0xcbcd88

    ffffd000`bffac5f0 fffff800`a0f2f0ab : ffffe000`5f995a90 fffff802`58dd46aa 00000004`00000048 ffffd000`bffac670 : atikmdag+0xcc17d4

    ffffd000`bffac670 fffff800`a0f2fe0f : ffffe000`5f995ab0 ffffe000`5e72b640 ffffe000`5e72b640 00000000`00000001 : atikmdag+0x4f0ab

    ffffd000`bffac6f0 fffff800`a0ef0f8f : 00000000`00000001 00000000`00000001 00000000`ffffffff 00000000`00000000 : atikmdag+0x4fe0f

    ffffd000`bffac720 fffff800`a0ef732d : ffffe000`5e72b640 00000000`ffffffff 00000000`00000001 00000000`00000000 : atikmdag+0x10f8f

    ffffd000`bffac750 fffff800`9eb6465b : 00000000`00000000 00000000`00000000 ffffe000`5faee300 00000000`ffffffff : atikmdag+0x1732d

    ffffd000`bffac7c0 fffff800`9eb5a043 : 00000000`c0000001 00000000`00000000 00000000`ffffffff 00000000`ffffffff : atikmpag+0x1465b

    ffffd000`bffac810 fffff800`9e10f179 : 00000000`00000000 00000000`ffffffff 00000000`00000001 00000000`00000000 : atikmpag+0xa043

    ffffd000`bffac8a0 fffff800`9e10ebdd : 00000000`00000000 ffffe000`5fcdcc10 00000000`00000002 ffffe000`5fcdcdb8 : dxgkrnl!DpiDxgkDdiSetPowerState+0x51

    ffffd000`bffac900 fffff800`9e10f5cc : ffffd000`bffac902 00000000`00000001 00000000`00000001 00000000`00000000 : dxgkrnl!DpiFdoSetAdapterPowerState+0x24d

    ffffd000`bffac9a0 fffff800`9e1108bb : ffffe000`5fcdcc00 ffffe000`5faf6190 ffffe000`5fcdcc10 fffff802`58d8b282 : dxgkrnl!DpiFdoHandleDevicePower+0x2fc

    ffffd000`bffaca30 fffff802`58da6f6e : 00000000`00000001 00000000`00000001 00000000`00000001 00000000`00000000 : dxgkrnl!DpiDispatchPower+0x8b

    ffffd000`bffacb50 fffff802`58d69e88 : 48602474`8b485824 ffffe000`5b06c040 ffffe000`5b04d840 ffffd000`ba77ecc0 : nt!PopIrpWorker+0x2d6

    ffffd000`bffacc00 fffff802`58dd6326 : ffffd000`ba772180 ffffe000`5b06c040 ffffd000`ba77ecc0 b4840ff6`85000000 : nt!PspSystemThreadStartup+0x58

    ffffd000`bffacc60 00000000`00000000 : ffffd000`bffad000 ffffd000`bffa7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

    STACK_COMMAND: .thread 0xffffe0005b06c040 ; kb

    FOLLOWUP_IP:

    dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24

    fffff800`9e07e0ec 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

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys

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

    Followup: MachineOwner

    ---------

    0: kd> lmvm dxgkrnl

    start end module name

    fffff800`9e060000 fffff800`9e24a000 dxgkrnl (pdb symbols) C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\sym\dxgkrnl.pdb\92FD8780CC0E4E2D92505DA3E934CD881\dxgkrnl.pdb

    Loaded symbol image file: dxgkrnl.sys

    Image path: \SystemRoot\System32\drivers\dxgkrnl.sys

    Image name: dxgkrnl.sys

    Timestamp: Sun Aug 02 21:12:13 2015 (55BEBFED)

    CheckSum: 001E8273

    ImageSize: 001EA000

    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
     
    BalderDad52, Jun 5, 2017
    #2
  3. Timmyctc Win User
    Thread Stuck in Device Driver while running games (usually graphic intensive)

    Has been an on going issue with my laptop for as long as I've used Windows 10. Have repeatedly fresh installed, system restore and rollbacks and clean reinstall of drivers.

    Have attached the dmp files from the 3 most recent BSODs hopefully some one who is capable of reading into them can help shed light on whats causing this frustrating issue.

    DMP Files

    ---

    Lenovo z50

    Processor : AMD FX7500 Radeon R7

    Memory : 8GB RAM

    GPU: 1GB R7
     
    Timmyctc, Jun 5, 2017
    #3
  4. axe0 New Member

    Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl

    Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to install as less as possible software using custom/advanced options, you can use this tutorial for the installation part *Arrow AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums

    Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl [​IMG]

    Code: 2: kd> lmvm atikmdag Browse full module list start end module name fffff80e`52190000 fffff80e`544c4000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: atikmdag.sys Image name: atikmdag.sys Browse all global symbols functions data Timestamp: Tue Apr 25 03:11:16 2017 (58FEA234) CheckSum: 022E00BC ImageSize: 02334000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
     
    axe0, Jun 5, 2017
    #4
  5. zbook New Member
    Please update......what is the status of your bsod?
     
    zbook, Apr 5, 2018
    #5
Thema:

Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl

Loading...
  1. Thread stuck in device driver while playing csgo - atikmdag+dxgkrnl - Similar Threads - Thread stuck device

  2. Thread stuck in device driver

    in Windows 10 Drivers and Hardware
    Thread stuck in device driver: Hello im need your help because i have Blue screen of death : Thread stuck in device driver. My laptop name is Lenovo G50-45 3,5 years old. First time i play game and my laptop freeze and i have error , i reset pc but when i download windows throught USB my pc work but when...
  3. Thread Stuck in Device Driver

    in Windows 10 Drivers and Hardware
    Thread Stuck in Device Driver: Hello i have problem with BSOD Thread Stuck in Device Driver.In my laptop Lenovo G50-45. Im doing everything: reset to factory settings, update or reinstall graphic adapters. when i install windows over usb i dont have bsod but when i restart i having blue screen.And i have...
  4. Thread stuck In device driver

    in Windows 10 Drivers and Hardware
    Thread stuck In device driver: So last week I bought an Asus fx505 with and Ryzen 7 3550H and I did the basic deiver updates when I got it, and from time to time I've been getting a BSOD that says Thread Stuck In Device drive. I already got the dumpfiles but I just don't know how to read them. This are...
  5. Thread Stuck in Device Driver

    in Windows 10 Drivers and Hardware
    Thread Stuck in Device Driver: Hi, My computer crashed 3 times now since I got it which is just 2 weeks. Windows 10 has completed all its updates 2 times it just froze and the 3rd time, the system also made a dump. Could you please help me to locate which driver that got frozen? Dump and NFO uploaded...
  6. thread stuck in device driver

    in Windows 10 Drivers and Hardware
    thread stuck in device driver: i know i need to update/rollback a driver but which one? https://drive.google.com/open?id=1R9sMN60GwuYUx1vuibwhyoqTc-iqg5of https://answers.microsoft.com/en-us/windows/forum/all/thread-stuck-in-device-driver/5f779244-cef1-43db-86f1-c8be24c98f5c
  7. Thread Stuck In Device Drivers While Playing Games

    in Windows 10 BSOD Crashes and Debugging
    Thread Stuck In Device Drivers While Playing Games: Hello! I have been having this BSOD error for the last 4-5 months, however it sometimes stops for multiple weeks, but it always comes back. Recently i have been getting this issue guaranteed every time i play a graphically intensive games. There's no set time for when this...
  8. Thread stuck in Device Driver

    in Windows 10 Drivers and Hardware
    Thread stuck in Device Driver: I had a generic question. i am using multiple GPU's overclocked. One of them randomly causes BSOD and I am trying to figure out which one is causing it. Is there a way to figure out pci-e id or device id with which I can narrow it down to the faulty GPU. p.s. The BSOD...
  9. BSOD While Gaming - Thread Stuck in Device Driver

    in Windows 10 BSOD Crashes and Debugging
    BSOD While Gaming - Thread Stuck in Device Driver: Hello TenForums, I've been battling a troublesome BSOD issue over the course of months now, and really getting frustrated. During gaming, I've been getting a BSOD saying Thread Stuck in Device Driver at strange times. It doesn't always seem to be consistant. Here are a few...
  10. BSoD Thread stuck in device driver - while gaming

    in Windows 10 BSOD Crashes and Debugging
    BSoD Thread stuck in device driver - while gaming: I have very recently started having issues while playing WOW were after a few minutes of play time I get a BSoD saying that there is a thread stuck in the device driver. I have tried everything online that I could find, tried updating drivers ( I have an AMD Radeon R7 card),...

Users found this page by searching for:

  1. csgo causes thread stuck in device driver