Windows 7 BSODs during playing games
- Thread starter Vexar
- Start date
Looks like the problem is most likely due to your graphics card driver. If this is a branded computer (HP, Dell etc) go to the vendor website and download and install the most current driver. Otherwise go to AMD's site and search your GPU, download and install the most current driver.
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {fffffa8006425060, 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
---------
5: 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: fffffa8006425060, 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).
5: kd> kb
*** Stack trace for last set context - .thread/.cxr resets it
# RetAddr : Args to Child : Call Site
00 fffff880`048c2f63 : 00000000`000000ea fffffa80`06425060 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
01 fffff880`048c3112 : fffff880`03eac688 fffff880`1304cc28 fffff880`03eac688 fffffa80`05227000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
02 fffff880`1305d043 : fffffa80`05227000 00000000`00000000 fffffa80`05227000 fffff880`1304cc00 : dxgkrnl!TdrTimedOperationDelay+0xbe
03 fffffa80`05227000 : 00000000`00000000 fffffa80`05227000 fffff880`1304cc00 00000000`01c9c380 : atikmdag+0x42043
04 00000000`00000000 : fffffa80`05227000 fffff880`1304cc00 00000000`01c9c380 fffff880`03ea0028 : 0xfffffa80`05227000
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {fffffa8006425060, 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
---------
5: 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: fffffa8006425060, 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).
5: kd> kb
*** Stack trace for last set context - .thread/.cxr resets it
# RetAddr : Args to Child : Call Site
00 fffff880`048c2f63 : 00000000`000000ea fffffa80`06425060 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
01 fffff880`048c3112 : fffff880`03eac688 fffff880`1304cc28 fffff880`03eac688 fffffa80`05227000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
02 fffff880`1305d043 : fffffa80`05227000 00000000`00000000 fffffa80`05227000 fffff880`1304cc00 : dxgkrnl!TdrTimedOperationDelay+0xbe
03 fffffa80`05227000 : 00000000`00000000 fffffa80`05227000 fffff880`1304cc00 00000000`01c9c380 : atikmdag+0x42043
04 00000000`00000000 : fffffa80`05227000 fffff880`1304cc00 00000000`01c9c380 fffff880`03ea0028 : 0xfffffa80`05227000
Just to add, that bugcheck is always associated with AMD cards and the driver.
Try removing the driver as advised but use an app called DDU or Display drivers uninstaller. This will also remove any corruption built up by previous driver installs.
You download it from here: Display Driver Uninstaller (DDU) V17.0.8.6 Released. - Wagnardsoft Forum
Unzip the folder to wherever you wish and boot into safe mode. Once in safe mode right click on the start up exe of the DDU and run as admin.
You want the top option 'Clean and reboot'.
Install gpu driver once back in windows.
Try removing the driver as advised but use an app called DDU or Display drivers uninstaller. This will also remove any corruption built up by previous driver installs.
You download it from here: Display Driver Uninstaller (DDU) V17.0.8.6 Released. - Wagnardsoft Forum
Unzip the folder to wherever you wish and boot into safe mode. Once in safe mode right click on the start up exe of the DDU and run as admin.
You want the top option 'Clean and reboot'.
Install gpu driver once back in windows.
