Частый BSOD "THREAD_STUCK_IN_DEVICE_DRIVER"

BlueScreenView shows, as always, a wrong cause. When analyzing the dmp in Windbg by running !analyze -v it shows that the crash is caused by the AMD GPU driver atikmdag.sys:

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea) 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 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: ffffe0015134d800, Pointer to a stuck thread object. Do .thread then kb on it to find the hung location. # Child-SP RetAddr Call Site 00 ffffd001`67194078 fffff801`d7e2e18c nt!KeBugCheckEx 01 ffffd001`67194080 fffff801`d7e2e24e dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x24 02 ffffd001`671940f0 fffff801`da002463 dxgkrnl!TdrTimedOperationDelay+0xbe 03 ffffd001`67194130 ffffe001`553cf000 atikmdag+0x42463 04 ffffd001`67194138 00000000`00000000 0xffffe001`553cf000 Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Sat Aug 22 04:10:03 2015 

Install the latest AMD Beta driver and look if this fixes it.