New
#1
BSOD when watching Netflix
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(?)
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.Code: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
Could someone look into it please?
Thanks.