BSOD Video Scheduler Error Message

Unfortunately I've had another crash. This time the BSOD occurred as the computer was loading up after an overnight shutdown.

I have attached the dump files.

Thanks in advance !

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\davebeck\Windows_NT6_BSOD_jcgriff2_22\Windows_NT6_BSOD_jcgriff2\012212-41324-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03208000 PsLoadedModuleList = 0xfffff800`0344d670
Debug session time: Sat Jan 21 22:09:31.961 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:54.882
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800be43010, fffff880053a68b8, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78b8 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800be43010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880053a68b8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+78b8
fffff880`053a68b8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`048f69c8 fffff880`066d6000 : 00000000`00000116 fffffa80`0be43010 fffff880`053a68b8 00000000`00000000 : nt!KeBugCheckEx
fffff880`048f69d0 fffff880`066d5d0a : fffff880`053a68b8 fffffa80`0be43010 fffffa80`0bcb9d50 fffffa80`0bbe8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`048f6a10 fffff880`0677cf07 : fffffa80`0be43010 00000000`00000000 fffffa80`0bcb9d50 fffffa80`0bbe8010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`048f6a40 fffff880`067a6b75 : 00000000`ffffffff 00000000`00000d31 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`048f6b20 fffff880`067a52bb : 00000000`00000102 00000000`00000000 00000000`00000d31 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`048f6b50 fffff880`067782c6 : ffffffff`ff676980 fffffa80`0bbe8010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`048f6bf0 fffff880`067a4e7a : 00000000`00000000 fffffa80`0be38010 00000000`00000080 fffffa80`0bbe8010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`048f6d00 fffff800`0351ffee : 00000000`fffffc32 fffffa80`0bc99060 fffffa80`066a6b30 fffffa80`0bc99060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`048f6d40 fffff800`032765e6 : fffff880`03786180 fffffa80`0bc99060 fffff880`037910c0 fffff880`01860384 : nt!PspSystemThreadStartup+0x5a
fffff880`048f6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78b8
fffff880`053a68b8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea760b6

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

You received a STOP 0x116 crash, which means your graphics card/graphics card driver failed to respond to the system in a timely manner. Closely follow the steps in the first three posts provided by usasma for STOP 0x116: VIDEO_TDR_ERROR troubleshooting.

Any luck following that thread? Need further troubleshooting steps?

At the moment everything is okay but I'm not convinced that I have actually fixed anything.

If you don't mind I would like to keep the thread open just a bit longer.

Keep it open as long as needed. I like to check in with those I am helping every few weeks if I have not heard anything.

that's great, thanks for the help.

You're welcome. How are things going at this time?

The system hasn't crashed for a little while, but I still get the feeling that it's not running 100%. Quite often video playback isn't totally smooth tiny little freezes. I will just continue to go about my daily tasks and hope that it stays stable.

My girlfriend has that problem on her laptop. Hers is related to an overheat issue. Have you checked your temperatures?

Use the following programs to monitor the temperatures.

• Real Temp is a good CPU temperature monitor.
• Speccy - System Information - Free Download will monitor all hardware temperatures.
• HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.

Could also be an application or service conflicting with the video: Troubleshoot Application Conflicts by Performing a Clean Startup

I haven't had a chance to test the temperature yet but just now have had three consecutive blue screen errors. I have attached the diagnosis.

Before crashing I had been watching a couple of video files but was only browsing a local news site in Firefox when the first crash occurred.

I will definitely check the temperature but do have some doubts about that being the problem as I have had this problem occur only minutes into starting a session after the computer being shut down all night.

Would I be totally off the market file were thinking that it may be a graphics card hardware problem?