Solved BSOD when watching Netflix

[IoNGeNeRaL]

Hey guys. Long time since I've posted here about my computer giving issues and quite frankly my system has been running perfectly fine since the last time I posted until now. I get a BSOD when watching Netflix and have attempted analysis myself and apparently my ATI display driver is causing it(?)

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {fffffa800c893b50, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\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
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa800c893b50, 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 "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------


FAULTING_THREAD:  fffffa800c893b50

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88004e0bf63 to fffff800056c5bc0

STACK_TEXT:  
fffff880`05b38298 fffff880`04e0bf63 : 00000000`000000ea fffffa80`0c893b50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`05b382a0 fffff880`04e0c112 : fffff880`05b38378 fffff880`1130f228 fffff880`05b38378 00000000`00000246 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`05b38310 fffff880`1131f6af : fffffa80`0c22e000 00000000`00000000 fffffa80`0c22e000 fffff880`1130f200 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`05b38350 fffffa80`0c22e000 : 00000000`00000000 fffffa80`0c22e000 fffff880`1130f200 00000000`01c9c380 : atikmdag+0x406af
fffff880`05b38358 00000000`00000000 : fffffa80`0c22e000 fffff880`1130f200 00000000`01c9c380 fffff880`11300028 : 0xfffffa80`0c22e000


STACK_COMMAND:  .thread 0xfffffa800c893b50 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`04e0bf63 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

I've tried removing everything to do with AMD ATI drivers, ran CCleaner and reinstalled a fresh copy of the latest AMD Catalyst (amd-catalyst-14-9-win7-win8.1-64bit-dd-ccc-whql) but I still got a BSOD. I am unsure whether it's directly the cause of my ATI drivers, DX-11 or something else.

Could someone look into it please?

Thanks.

 

[Laith]

Run Display Driver Uninstaller in safemode. Display Driver Uninstaller Download version 13.5.2.0 Click on your Graphics card witch in this case is ATI(AMD) Press Clean and restart.
After that goto your manufacture website and download your ATI graphic drivers again. If it is a custom PC goto your graphics card manufacturer website and download it there. The BSOD should have been fixed. Report if something happens.

 

[IoNGeNeRaL]

I did as you suggested, Laith, but again, it crashed with the ATI driver being the cause.

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {fffffa800c678a00, 0, 0, 0}

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa800c678a00, 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 "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------


FAULTING_THREAD:  fffffa800c678a00

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880122b9f63 to fffff800056c7bc0

STACK_TEXT:  
fffff880`0555b598 fffff880`122b9f63 : 00000000`000000ea fffffa80`0c678a00 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0555b5a0 fffff880`122ba112 : fffff880`0555b678 fffff880`11279228 fffff880`0555b678 fffff880`112896bc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`0555b610 fffff880`112896af : fffffa80`0bfc2000 00000000`00000000 fffffa80`0bfc2000 fffff880`11279200 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`0555b650 fffffa80`0bfc2000 : 00000000`00000000 fffffa80`0bfc2000 fffff880`11279200 00000000`01c9c380 : atikmdag+0x406af
fffff880`0555b658 00000000`00000000 : fffffa80`0bfc2000 fffff880`11279200 00000000`01c9c380 fffff880`11270028 : 0xfffffa80`0bfc2000


STACK_COMMAND:  .thread 0xfffffa800c678a00 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`122b9f63 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
---------

 

[Laith]

Well we have confirmed that the ATI isnt the fault. Now is the time to remove DirectX.

 

[IoNGeNeRaL]

Should I remove DirectX and then reinstall it?

 

[Laith]

Well uninstall DirectX and watch a netflix movie or something like that. If the BSOD goes away you can try to install DirectX again and see netflix if the bsod happens report again.

 

[IoNGeNeRaL]

It's not just on Netflix, when I try to play COD Advanced Warfare it just crashes the game.

 

[Laith]

Than it is for sure that DirectX is causing the problem. Un-install DirectX and all of its drivers and re-install DirectX. When installing DirectX make sure you use DirectX 10 or 9. Do you have your computer on sleepmode or shutdown when going from the computer? If you put it in sleepmode then Shutdown it.

In the bugcheck it says:
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.

 

[IoNGeNeRaL]

My game crashed (not a BSOD) with a DirectX3DDevice error last night. Not sure what to do. I can't uninstall DX because as you said, it's integrated into Windows 7.

 

[Laith]

In the bugcheck it says: 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.
That could be a failing RAM or Harddrive. Run Memtest86+ for 8 passes.

 

[IoNGeNeRaL]

Can't be my RAM considering the sticks are brand new..and Hard Disk is an OCZ SSD. I reinstalled Windows as a last resort but the AMD display driver still keeps crashing and recovering..so I guess it's either my Graphics Card, OR AMD's drivers.

 

[Laith]

Before you do anything, Boot into safemode and run Display Driver Uninstaller again, But now choose Delete C:/NIVIDIA and C:/AMD Folders. After that install your graphics card driver again. If it didnt work then you must replace graphics card.