THREAD_STUCK_IN_DEVICE_DRIVER BSOD

It seems that a lot of GPU problems revolve around specific versions of drivers. Though AMD has their own support structure, you can often learn from information reported by others who fold.

Moderators: Site Moderators, PandeGroup

THREAD_STUCK_IN_DEVICE_DRIVER BSOD

Postby halvorsen82 » Sun Mar 13, 2016 6:37 pm

Lately, now and then I get a Bluescreen. I looked into the minidumps I get and see that the process causing this is FahCore_21.exe.

My graphics card is AMd Radeon 7700 series, driver version 15.300.1025.1001

I uninstalled my graphic card driver, and then ran AMDs autodetectutility.exe which installed the latest drivers (which I initially already had). I got a new BSOD after this, so it didn't help.

My minidump was last modified at ‎13. ‎mars ‎2016, ‏‎10:22:24.

FAH log file
Code: Select all
*********************** Log Started 2016-03-13T09:23:15Z ***********************
09:23:15:************************* Folding@home Client *************************
09:23:15:      Website: http://folding.stanford.edu/
09:23:15:    Copyright: (c) 2009-2014 Stanford University
09:23:15:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
09:23:15:         Args:
09:23:15:       Config: C:/Users/Martin/AppData/Roaming/FAHClient/config.xml
09:23:15:******************************** Build ********************************
09:23:15:      Version: 7.4.4
09:23:15:         Date: Mar 4 2014
09:23:15:         Time: 20:26:54
09:23:15:      SVN Rev: 4130
09:23:15:       Branch: fah/trunk/client
09:23:15:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
09:23:15:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
09:23:15:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
09:23:15:     Platform: win32 XP
09:23:15:         Bits: 32
09:23:15:         Mode: Release
09:23:15:******************************* System ********************************
09:23:15:          CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
09:23:15:       CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
09:23:15:         CPUs: 8
09:23:15:       Memory: 15.96GiB
09:23:15:  Free Memory: 13.70GiB
09:23:15:      Threads: WINDOWS_THREADS
09:23:15:   OS Version: 6.1
09:23:15:  Has Battery: false
09:23:15:   On Battery: false
09:23:15:   UTC Offset: 1
09:23:15:          PID: 5792
09:23:15:          CWD: C:/Users/Martin/AppData/Roaming/FAHClient
09:23:15:           OS: Windows 7 Ultimate
09:23:15:      OS Arch: AMD64
09:23:15:         GPUs: 1
09:23:15:        GPU 0: ATI:5 R575A [Radeon R7 250X/HD 7700/8760]
09:23:15:         CUDA: Not detected
09:23:15:Win32 Service: false
09:23:15:***********************************************************************
09:23:15:<config>
09:23:15:  <!-- Slot Control -->
09:23:15:  <power v='FULL'/>
09:23:15:
09:23:15:  <!-- User Information -->
09:23:15:  <passkey v='********************************'/>
09:23:15:  <team v='227353'/>
09:23:15:  <user v='Martin'/>
09:23:15:
09:23:15:  <!-- Folding Slots -->
09:23:15:  <slot id='0' type='CPU'>
09:23:15:    <idle v='true'/>
09:23:15:  </slot>
09:23:15:  <slot id='1' type='GPU'>
09:23:15:    <idle v='true'/>
09:23:15:  </slot>
09:23:15:</config>
09:23:15:Trying to access database...
09:23:15:Successfully acquired database lock
09:23:15:Enabled folding slot 00: PAUSED cpu:7 (waiting for idle)
09:23:15:Enabled folding slot 01: PAUSED gpu:0:R575A [Radeon R7 250X/HD 7700/8760] (waiting for idle)
09:38:14:WU02:FS01:Starting
09:38:14:WU02:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Martin/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_21.fah/FahCore_21.exe -dir 02 -suffix 01 -version 704 -lifeline 5792 -checkpoint 15 -gpu 0 -gpu-vendor ati
09:38:14:WU02:FS01:Started FahCore on PID 4348
09:38:14:WU02:FS01:Core PID:7708
09:38:14:WU02:FS01:FahCore 0x21 started
09:38:14:WU00:FS00:Starting
09:38:14:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Martin/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 5792 -checkpoint 15 -np 7
09:38:14:WU00:FS00:Started FahCore on PID 7632
09:38:14:WU00:FS00:Core PID:3556
09:38:14:WU00:FS00:FahCore 0xa4 started
09:38:14:WU02:FS01:0x21:*********************** Log Started 2016-03-13T09:38:14Z ***********************
09:38:14:WU02:FS01:0x21:Project: 9441 (Run 11, Clone 10, Gen 34)
09:38:14:WU02:FS01:0x21:Unit: 0x0000002aab436c9d56af1b29654eb237
09:38:14:WU02:FS01:0x21:CPU: 0x00000000000000000000000000000000
09:38:14:WU02:FS01:0x21:Machine: 1
09:38:14:WU02:FS01:0x21:Digital signatures verified
09:38:14:WU02:FS01:0x21:Folding@home GPU Core21 Folding@home Core
09:38:14:WU02:FS01:0x21:Version 0.0.17
09:38:14:WU00:FS00:0xa4:
09:38:14:WU00:FS00:0xa4:*------------------------------*
09:38:14:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
09:38:14:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
09:38:14:WU00:FS00:0xa4:
09:38:14:WU00:FS00:0xa4:Preparing to commence simulation
09:38:14:WU00:FS00:0xa4:- Ensuring status. Please wait.
09:38:15:WU02:FS01:0x21:  Found a checkpoint file
09:38:23:WU02:FS01:0x21:Completed 2000000 out of 2500000 steps (80%)
09:38:23:WU02:FS01:0x21:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
09:38:24:WU00:FS00:0xa4:- Looking at optimizations...
09:38:24:WU00:FS00:0xa4:- Working with standard loops on this execution.
09:38:24:WU00:FS00:0xa4:- Previous termination of core was improper.
09:38:24:WU00:FS00:0xa4:- Files status OK
09:38:24:WU00:FS00:0xa4:- Expanded 826024 -> 1403472 (decompressed 169.9 percent)
09:38:24:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=826024 data_size=1403472, decompressed_data_size=1403472 diff=0
09:38:24:WU00:FS00:0xa4:- Digital signature verified
09:38:24:WU00:FS00:0xa4:
09:38:24:WU00:FS00:0xa4:Project: 9037 (Run 388, Clone 0, Gen 90)
09:38:24:WU00:FS00:0xa4:
09:38:24:WU00:FS00:0xa4:Entering M.D.
09:38:30:WU00:FS00:0xa4:Using Gromacs checkpoints
09:38:30:WU00:FS00:0xa4:Mapping NT from 7 to 7
09:38:30:WU00:FS00:0xa4:Resuming from checkpoint
09:38:30:WU00:FS00:0xa4:Verified 00/wudata_01.log
09:38:30:WU00:FS00:0xa4:Verified 00/wudata_01.trr
09:38:30:WU00:FS00:0xa4:Verified 00/wudata_01.xtc
09:38:30:WU00:FS00:0xa4:Verified 00/wudata_01.edr
09:38:30:WU00:FS00:0xa4:Completed 157465 out of 250000 steps  (62%)
09:38:32:WU00:FS00:0xa4:Completed 157500 out of 250000 steps  (63%)
09:40:03:WU00:FS00:0xa4:Completed 160000 out of 250000 steps  (64%)
09:41:34:WU00:FS00:0xa4:Completed 162500 out of 250000 steps  (65%)
09:43:04:WU00:FS00:0xa4:Completed 165000 out of 250000 steps  (66%)
09:44:35:WU00:FS00:0xa4:Completed 167500 out of 250000 steps  (67%)
09:46:05:WU00:FS00:0xa4:Completed 170000 out of 250000 steps  (68%)
09:47:35:WU00:FS00:0xa4:Completed 172500 out of 250000 steps  (69%)
09:49:07:WU00:FS00:0xa4:Completed 175000 out of 250000 steps  (70%)
09:49:14:WU02:FS01:0x21:Completed 2025000 out of 2500000 steps (81%)
09:50:41:WU00:FS00:0xa4:Completed 177500 out of 250000 steps  (71%)
09:52:12:WU00:FS00:0xa4:Completed 180000 out of 250000 steps  (72%)
09:53:45:WU00:FS00:0xa4:Completed 182500 out of 250000 steps  (73%)
09:55:14:WU00:FS00:0xa4:Completed 185000 out of 250000 steps  (74%)
09:56:46:WU00:FS00:0xa4:Completed 187500 out of 250000 steps  (75%)
09:58:17:WU00:FS00:0xa4:Completed 190000 out of 250000 steps  (76%)
09:59:49:WU00:FS00:0xa4:Completed 192500 out of 250000 steps  (77%)
10:01:19:WU00:FS00:0xa4:Completed 195000 out of 250000 steps  (78%)
10:02:07:WU02:FS01:0x21:Completed 2050000 out of 2500000 steps (82%)
10:02:51:WU00:FS00:0xa4:Completed 197500 out of 250000 steps  (79%)
10:04:21:WU00:FS00:0xa4:Completed 200000 out of 250000 steps  (80%)
10:05:53:WU00:FS00:0xa4:Completed 202500 out of 250000 steps  (81%)
10:06:51:FS00:Shutting core down
10:06:51:FS01:Shutting core down
10:06:51:WU02:FS01:0x21:WARNING:Console control signal 1 on PID 7708
10:06:51:WU02:FS01:0x21:Exiting, please wait. . .
10:06:57:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
10:06:58:WU02:FS01:0x21:Folding@home Core Shutdown: INTERRUPTED
10:06:58:WU02:FS01:FahCore returned: INTERRUPTED (102 = 0x66)
10:43:55:WU02:FS01:Starting
10:43:55:WU02:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Martin/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_21.fah/FahCore_21.exe -dir 02 -suffix 01 -version 704 -lifeline 5792 -checkpoint 15 -gpu 0 -gpu-vendor ati
10:43:55:WU02:FS01:Started FahCore on PID 4416
10:43:55:WU02:FS01:Core PID:10404
10:43:55:WU02:FS01:FahCore 0x21 started
10:43:55:WU00:FS00:Starting
10:43:55:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Martin/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 5792 -checkpoint 15 -np 7
10:43:55:WU00:FS00:Started FahCore on PID 9036
10:43:55:WU00:FS00:Core PID:9912
10:43:55:WU00:FS00:FahCore 0xa4 started
10:43:56:WU02:FS01:0x21:*********************** Log Started 2016-03-13T10:43:55Z ***********************
10:43:56:WU02:FS01:0x21:Project: 9441 (Run 11, Clone 10, Gen 34)
10:43:56:WU02:FS01:0x21:Unit: 0x0000002aab436c9d56af1b29654eb237
10:43:56:WU02:FS01:0x21:CPU: 0x00000000000000000000000000000000
10:43:56:WU02:FS01:0x21:Machine: 1
10:43:56:WU02:FS01:0x21:Digital signatures verified
10:43:56:WU02:FS01:0x21:Folding@home GPU Core21 Folding@home Core
10:43:56:WU02:FS01:0x21:Version 0.0.17
10:43:56:WU02:FS01:0x21:  Found a checkpoint file
10:43:56:WU00:FS00:0xa4:
10:43:56:WU00:FS00:0xa4:*------------------------------*
10:43:56:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
10:43:56:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
10:43:56:WU00:FS00:0xa4:
10:43:56:WU00:FS00:0xa4:Preparing to commence simulation
10:43:56:WU00:FS00:0xa4:- Looking at optimizations...
10:43:56:WU00:FS00:0xa4:- Files status OK
10:43:56:WU00:FS00:0xa4:- Expanded 826024 -> 1403472 (decompressed 169.9 percent)
10:43:56:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=826024 data_size=1403472, decompressed_data_size=1403472 diff=0
10:43:56:WU00:FS00:0xa4:- Digital signature verified
10:43:56:WU00:FS00:0xa4:
10:43:56:WU00:FS00:0xa4:Project: 9037 (Run 388, Clone 0, Gen 90)
10:43:56:WU00:FS00:0xa4:
10:43:56:WU00:FS00:0xa4:Assembly optimizations on if available.
10:43:56:WU00:FS00:0xa4:Entering M.D.
10:44:02:WU00:FS00:0xa4:Using Gromacs checkpoints
10:44:02:WU00:FS00:0xa4:Mapping NT from 7 to 7
10:44:02:WU00:FS00:0xa4:Resuming from checkpoint
10:44:02:WU00:FS00:0xa4:Verified 00/wudata_01.log
10:44:02:WU00:FS00:0xa4:Verified 00/wudata_01.trr
10:44:02:WU00:FS00:0xa4:Verified 00/wudata_01.xtc
10:44:02:WU00:FS00:0xa4:Verified 00/wudata_01.edr
10:44:02:WU00:FS00:0xa4:Completed 182085 out of 250000 steps  (72%)
10:44:04:WU02:FS01:0x21:Completed 2050000 out of 2500000 steps (82%)
10:44:04:WU02:FS01:0x21:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
10:44:17:WU00:FS00:0xa4:Completed 182500 out of 250000 steps  (73%)
10:45:42:WU00:FS00:0xa4:Completed 185000 out of 250000 steps  (74%)
10:47:07:WU00:FS00:0xa4:Completed 187500 out of 250000 steps  (75%)
10:48:32:WU00:FS00:0xa4:Completed 190000 out of 250000 steps  (76%)
10:49:57:WU00:FS00:0xa4:Completed 192500 out of 250000 steps  (77%)
10:51:23:WU00:FS00:0xa4:Completed 195000 out of 250000 steps  (78%)
10:52:48:WU00:FS00:0xa4:Completed 197500 out of 250000 steps  (79%)
10:53:12:WU02:FS01:0x21:Completed 2075000 out of 2500000 steps (83%)
10:54:14:WU00:FS00:0xa4:Completed 200000 out of 250000 steps  (80%)
10:55:39:WU00:FS00:0xa4:Completed 202500 out of 250000 steps  (81%)
10:57:04:WU00:FS00:0xa4:Completed 205000 out of 250000 steps  (82%)
10:58:29:WU00:FS00:0xa4:Completed 207500 out of 250000 steps  (83%)
10:59:55:WU00:FS00:0xa4:Completed 210000 out of 250000 steps  (84%)
11:01:20:WU00:FS00:0xa4:Completed 212500 out of 250000 steps  (85%)
11:01:47:FS00:Shutting core down
11:01:47:FS01:Shutting core down
11:01:47:WU02:FS01:0x21:WARNING:Console control signal 1 on PID 10404
11:01:47:WU02:FS01:0x21:Exiting, please wait. . .
11:01:47:WU02:FS01:0x21:Folding@home Core Shutdown: INTERRUPTED
11:01:47:WU02:FS01:FahCore returned: INTERRUPTED (102 = 0x66)
11:01:56:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
14:01:09:FS00:Paused
14:01:09:FS01:Paused
14:01:49:Removing old file 'configs/config-20150301-191608.xml'
14:01:49:Saving configuration to config.xml
14:01:49:<config>
14:01:49:  <!-- Slot Control -->
14:01:49:  <power v='FULL'/>
14:01:49:
14:01:49:  <!-- User Information -->
14:01:49:  <passkey v='********************************'/>
14:01:49:  <team v='227353'/>
14:01:49:  <user v='Martin'/>
14:01:49:
14:01:49:  <!-- Folding Slots -->
14:01:49:  <slot id='0' type='CPU'>
14:01:49:    <idle v='true'/>
14:01:49:    <paused v='true'/>
14:01:49:  </slot>
14:01:49:  <slot id='1' type='GPU'>
14:01:49:    <idle v='true'/>
14:01:49:    <paused v='true'/>
14:01:49:  </slot>
14:01:49:</config>


Minidump details
Code: Select all
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031316-14133-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*U:\Symbols*http://msdl.microsoft.com/download/symbols;U:\Symbols
Executable search path is: srv*U:\Symbols*http://msdl.microsoft.com/download/symbols
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19110.amd64fre.win7sp1_gdr.151230-0600
Machine Name:
Kernel base = 0xfffff800`03262000 PsLoadedModuleList = 0xfffff800`034a9730
Debug session time: Sun Mar 13 02:18:08.821 2016 (UTC + 1:00)
System Uptime: 0 days 14:13:16.263
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {fffffa801228fb50, 0, 0, 0}

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )

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

5: 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: fffffa801228fb50, 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:  fffffa801228fb50

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  FahCore_21.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88003ef2f63 to fffff800032d5c00

STACK_TEXT: 
fffff880`0964e8f8 fffff880`03ef2f63 : 00000000`000000ea fffffa80`1228fb50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0964e900 fffff880`03ef3112 : fffff880`0964e9d8 fffff880`0f0dc2c0 fffff880`0964e9d8 fffff880`0964eaa0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`0964e970 fffff880`0f088703 : fffffa80`0d47a000 fffff880`0964ead1 fffff880`0964eaa0 fffff880`0f0dc2ac : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`0964e9b0 fffffa80`0d47a000 : fffff880`0964ead1 fffff880`0964eaa0 fffff880`0f0dc2ac 00000000`01312d00 : atikmdag+0x44703
fffff880`0964e9b8 fffff880`0964ead1 : fffff880`0964eaa0 fffff880`0f0dc2ac 00000000`01312d00 fffff800`03220028 : 0xfffffa80`0d47a000
fffff880`0964e9c0 fffff880`0964eaa0 : fffff880`0f0dc2ac 00000000`01312d00 fffff800`03220028 fffff880`0f0886d7 : 0xfffff880`0964ead1
fffff880`0964e9c8 fffff880`0f0dc2ac : 00000000`01312d00 fffff800`03220028 fffff880`0f0886d7 00000000`00000101 : 0xfffff880`0964eaa0
fffff880`0964e9d0 00000000`01312d00 : fffff800`03220028 fffff880`0f0886d7 00000000`00000101 00000000`00000080 : atikmdag+0x982ac
fffff880`0964e9d8 fffff800`03220028 : fffff880`0f0886d7 00000000`00000101 00000000`00000080 00000000`00321247 : 0x1312d00
fffff880`0964e9e0 fffff880`0f08205e : 00000000`00000064 fffff800`03228a7b 00000000`0000000a 00000000`00000063 : hal!HalInitializeProcessor+0x88
fffff880`0964ea30 00000000`00000064 : fffff800`03228a7b 00000000`0000000a 00000000`00000063 fffff880`0964ea01 : atikmdag+0x3e05e
fffff880`0964ea38 fffff800`03228a7b : 00000000`0000000a 00000000`00000063 fffff880`0964ea01 00000000`01000002 : 0x64
fffff880`0964ea40 fffff880`0f0dc1ce : 00000000`00000001 00000000`00000064 fffff880`0f2674c0 fffffa80`0d47a000 : hal!KeStallExecutionProcessor+0x183
fffff880`0964ea70 00000000`00000001 : 00000000`00000064 fffff880`0f2674c0 fffffa80`0d47a000 fffff880`04400000 : atikmdag+0x981ce
fffff880`0964ea78 00000000`00000064 : fffff880`0f2674c0 fffffa80`0d47a000 fffff880`04400000 00000000`0000e000 : 0x1
fffff880`0964ea80 fffff880`0f2674c0 : fffffa80`0d47a000 fffff880`04400000 00000000`0000e000 fffffa80`0e63dac8 : 0x64
fffff880`0964ea88 fffffa80`0d47a000 : fffff880`04400000 00000000`0000e000 fffffa80`0e63dac8 ffffffff`0000008c : atikmdag+0x2234c0
fffff880`0964ea90 fffff880`04400000 : 00000000`0000e000 fffffa80`0e63dac8 ffffffff`0000008c fffffa80`00000000 : 0xfffffa80`0d47a000
fffff880`0964ea98 00000000`0000e000 : fffffa80`0e63dac8 ffffffff`0000008c fffffa80`00000000 00000000`0000008b : 0xfffff880`04400000
fffff880`0964eaa0 fffffa80`0e63dac8 : ffffffff`0000008c fffffa80`00000000 00000000`0000008b 00000009`00000048 : 0xe000
fffff880`0964eaa8 ffffffff`0000008c : fffffa80`00000000 00000000`0000008b 00000009`00000048 fffff880`0f0dc2ac : 0xfffffa80`0e63dac8
fffff880`0964eab0 fffffa80`00000000 : 00000000`0000008b 00000009`00000048 fffff880`0f0dc2ac fffff880`0964eaa0 : 0xffffffff`0000008c
fffff880`0964eab8 00000000`0000008b : 00000009`00000048 fffff880`0f0dc2ac fffff880`0964eaa0 00000001`000007d0 : 0xfffffa80`00000000
fffff880`0964eac0 00000009`00000048 : fffff880`0f0dc2ac fffff880`0964eaa0 00000001`000007d0 00000000`00000000 : 0x8b
fffff880`0964eac8 fffff880`0f0dc2ac : fffff880`0964eaa0 00000001`000007d0 00000000`00000000 00000000`00000000 : 0x9`00000048
fffff880`0964ead0 fffff880`0964eaa0 : 00000001`000007d0 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x982ac
fffff880`0964ead8 00000001`000007d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0964eaa0
fffff880`0964eae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`000007d0


STACK_COMMAND:  .thread 0xfffffa801228fb50 ; kb

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`03ef2f63 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

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

5: 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: fffffa801228fb50, 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:  fffffa801228fb50

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  FahCore_21.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88003ef2f63 to fffff800032d5c00

STACK_TEXT: 
fffff880`0964e8f8 fffff880`03ef2f63 : 00000000`000000ea fffffa80`1228fb50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0964e900 fffff880`03ef3112 : fffff880`0964e9d8 fffff880`0f0dc2c0 fffff880`0964e9d8 fffff880`0964eaa0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`0964e970 fffff880`0f088703 : fffffa80`0d47a000 fffff880`0964ead1 fffff880`0964eaa0 fffff880`0f0dc2ac : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`0964e9b0 fffffa80`0d47a000 : fffff880`0964ead1 fffff880`0964eaa0 fffff880`0f0dc2ac 00000000`01312d00 : atikmdag+0x44703
fffff880`0964e9b8 fffff880`0964ead1 : fffff880`0964eaa0 fffff880`0f0dc2ac 00000000`01312d00 fffff800`03220028 : 0xfffffa80`0d47a000
fffff880`0964e9c0 fffff880`0964eaa0 : fffff880`0f0dc2ac 00000000`01312d00 fffff800`03220028 fffff880`0f0886d7 : 0xfffff880`0964ead1
fffff880`0964e9c8 fffff880`0f0dc2ac : 00000000`01312d00 fffff800`03220028 fffff880`0f0886d7 00000000`00000101 : 0xfffff880`0964eaa0
fffff880`0964e9d0 00000000`01312d00 : fffff800`03220028 fffff880`0f0886d7 00000000`00000101 00000000`00000080 : atikmdag+0x982ac
fffff880`0964e9d8 fffff800`03220028 : fffff880`0f0886d7 00000000`00000101 00000000`00000080 00000000`00321247 : 0x1312d00
fffff880`0964e9e0 fffff880`0f08205e : 00000000`00000064 fffff800`03228a7b 00000000`0000000a 00000000`00000063 : hal!HalInitializeProcessor+0x88
fffff880`0964ea30 00000000`00000064 : fffff800`03228a7b 00000000`0000000a 00000000`00000063 fffff880`0964ea01 : atikmdag+0x3e05e
fffff880`0964ea38 fffff800`03228a7b : 00000000`0000000a 00000000`00000063 fffff880`0964ea01 00000000`01000002 : 0x64
fffff880`0964ea40 fffff880`0f0dc1ce : 00000000`00000001 00000000`00000064 fffff880`0f2674c0 fffffa80`0d47a000 : hal!KeStallExecutionProcessor+0x183
fffff880`0964ea70 00000000`00000001 : 00000000`00000064 fffff880`0f2674c0 fffffa80`0d47a000 fffff880`04400000 : atikmdag+0x981ce
fffff880`0964ea78 00000000`00000064 : fffff880`0f2674c0 fffffa80`0d47a000 fffff880`04400000 00000000`0000e000 : 0x1
fffff880`0964ea80 fffff880`0f2674c0 : fffffa80`0d47a000 fffff880`04400000 00000000`0000e000 fffffa80`0e63dac8 : 0x64
fffff880`0964ea88 fffffa80`0d47a000 : fffff880`04400000 00000000`0000e000 fffffa80`0e63dac8 ffffffff`0000008c : atikmdag+0x2234c0
fffff880`0964ea90 fffff880`04400000 : 00000000`0000e000 fffffa80`0e63dac8 ffffffff`0000008c fffffa80`00000000 : 0xfffffa80`0d47a000
fffff880`0964ea98 00000000`0000e000 : fffffa80`0e63dac8 ffffffff`0000008c fffffa80`00000000 00000000`0000008b : 0xfffff880`04400000
fffff880`0964eaa0 fffffa80`0e63dac8 : ffffffff`0000008c fffffa80`00000000 00000000`0000008b 00000009`00000048 : 0xe000
fffff880`0964eaa8 ffffffff`0000008c : fffffa80`00000000 00000000`0000008b 00000009`00000048 fffff880`0f0dc2ac : 0xfffffa80`0e63dac8
fffff880`0964eab0 fffffa80`00000000 : 00000000`0000008b 00000009`00000048 fffff880`0f0dc2ac fffff880`0964eaa0 : 0xffffffff`0000008c
fffff880`0964eab8 00000000`0000008b : 00000009`00000048 fffff880`0f0dc2ac fffff880`0964eaa0 00000001`000007d0 : 0xfffffa80`00000000
fffff880`0964eac0 00000009`00000048 : fffff880`0f0dc2ac fffff880`0964eaa0 00000001`000007d0 00000000`00000000 : 0x8b
fffff880`0964eac8 fffff880`0f0dc2ac : fffff880`0964eaa0 00000001`000007d0 00000000`00000000 00000000`00000000 : 0x9`00000048
fffff880`0964ead0 fffff880`0964eaa0 : 00000001`000007d0 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x982ac
fffff880`0964ead8 00000001`000007d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0964eaa0
fffff880`0964eae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`000007d0


STACK_COMMAND:  .thread 0xfffffa801228fb50 ; kb

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`03ef2f63 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

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

halvorsen82
 
Posts: 2
Joined: Sun Mar 13, 2016 10:14 am

Re: THREAD_STUCK_IN_DEVICE_DRIVER BSOD

Postby bruce » Mon Mar 14, 2016 6:33 am

I suspect it's a hardware problem, which is what your minidump suggests.
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.


Both are supplied by ATI/AMD and are not part of FahCore_21. Then, too, you're apparently the only person with this problem.

Is the GPU overclocked? If so, have you reset the clocks to the manufacturer's recommended settings.
Is your cooling adequate for a GPU that's running at maximum throughput?

Apparently FahCore_21 is equal to or more efficient than whatever test suite the manufacturer used to establish the maximum clock rates so many overclocked GPUs that are stable refreshing the OS desktop can become unstable.
bruce
 
Posts: 21413
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: THREAD_STUCK_IN_DEVICE_DRIVER BSOD

Postby halvorsen82 » Mon Mar 14, 2016 6:37 pm

bruce wrote:I suspect it's a hardware problem, which is what your minidump suggests.
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.


Both are supplied by ATI/AMD and are not part of FahCore_21. Then, too, you're apparently the only person with this problem.

Is the GPU overclocked? If so, have you reset the clocks to the manufacturer's recommended settings.
Is your cooling adequate for a GPU that's running at maximum throughput?

Apparently FahCore_21 is equal to or more efficient than whatever test suite the manufacturer used to establish the maximum clock rates so many overclocked GPUs that are stable refreshing the OS desktop can become unstable.

The GPU is not overclocked, or at least not as I can remember (had it for a couple of years now). I recall installing new drivers maybe two weeks ago, so I'll try downgrading the drivers to an earlier version. Thanks for your input:)
halvorsen82
 
Posts: 2
Joined: Sun Mar 13, 2016 10:14 am


Return to Problems with AMD/ATI drivers

Who is online

Users browsing this forum: No registered users and 1 guest

cron