BSOD Video Scheduler Error Message

[writhziden]

It appears there may be a graphics card hardware problem. That is a valid conclusion. There are some hardware tests at the end of this post that may help determine whether that is the case.


Problem Devices:

Realtek NDIS Protocol Driver	ROOT\LEGACY_RTNDPT60\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Antivirus Software:

avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	524	8	200	1380	5/03/2012 2:48 PM	12.0.0.1786	507.34 KB (519,520 bytes)	15/08/2011 5:21 AM
avgemca.exe	c:\program files (x86)\avg\avg2012\avgemca.exe	3712	8	200	1380	5/03/2012 2:49 PM	12.0.0.1854	1.52 MB (1,593,696 bytes)	21/09/2011 6:53 PM
avgidsagent.exe	c:\program files (x86)\avg\avg2012\avgidsagent.exe	2696	8	200	1380	5/03/2012 2:49 PM	12.0.0.1855	4.23 MB (4,433,248 bytes)	12/10/2011 6:25 AM
avgnsa.exe	c:\program files (x86)\avg\avg2012\avgnsa.exe	3692	8	200	1380	5/03/2012 2:49 PM	12.0.0.1883	1.90 MB (1,987,424 bytes)	13/09/2011 9:33 AM
avgtray.exe	c:\program files (x86)\avg\avg2012\avgtray.exe	3108	8	200	1380	5/03/2012 2:49 PM	12.0.0.1912	2.30 MB (2,416,480 bytes)	24/01/2012 5:24 PM
avgwdsvc.exe	c:\program files (x86)\avg\avg2012\avgwdsvc.exe	2240	8	200	1380	5/03/2012 2:49 PM	12.0.0.1773	188.26 KB (192,776 bytes)	2/08/2011 5:09 AM

Possible out of date drivers:

SSPORT	fffff880`09f5f000	fffff880`09f67000	Thu Aug 11 17:07:32 2005 (42fbda34)	0000d894		SSPORT.sys
LVUSBS64	fffff880`07e6c000	fffff880`07e76980	Sat Jul 26 09:06:36 2008 (488b3d7c)	00019bfe		LVUSBS64.sys
DgiVecp	fffff880`08fbe000	fffff880`08fce000	Thu Oct 30 21:38:29 2008 (490a7db5)	00011776		DgiVecp.sys
GEARAspiWDM	fffff880`04f8a000	fffff880`04f97000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
LHidFilt	fffff880`07f15000	fffff880`07f28000	Wed Jun 17 10:49:39 2009 (4a391ea3)	00014ede		LHidFilt.Sys
LMouFilt	fffff880`07f43000	fffff880`07f57000	Wed Jun 17 10:49:43 2009 (4a391ea7)	0001d7ff		LMouFilt.Sys

SSPORT.sys
LVUSBS64.sys
GEARAspiWDM.sys
LHidFilt.Sys
LMouFilt.Sys

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\davebeck\Windows_NT6_BSOD_jcgriff2\030512-23197-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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`03213000 PsLoadedModuleList = 0xfffff800`03458670
Debug session time: Sun Mar  4 20:46:58.659 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:01.580
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800b7fb010, fffff880052438b8, 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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800b7fb010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880052438b8, 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`052438b8 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`046f19c8 fffff880`06704000 : 00000000`00000116 fffffa80`0b7fb010 fffff880`052438b8 00000000`00000000 : nt!KeBugCheckEx
fffff880`046f19d0 fffff880`06703d0a : fffff880`052438b8 fffffa80`0b7fb010 fffffa80`0bc1ed50 fffffa80`0bb6f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`046f1a10 fffff880`067aaf07 : fffffa80`0b7fb010 00000000`00000000 fffffa80`0bc1ed50 fffffa80`0bb6f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`046f1a40 fffff880`067d4b75 : 00000000`ffffffff 00000000`00000edf 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`046f1b20 fffff880`067d32bb : 00000000`00000102 00000000`00000000 00000000`00000edf 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`046f1b50 fffff880`067a62c6 : ffffffff`ff676980 fffffa80`0bb6f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`046f1bf0 fffff880`067d2e7a : 00000000`00000000 fffffa80`0b7edd50 00000000`00000080 fffffa80`0bb6f010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`046f1d00 fffff800`0352afee : 00000000`fffffc32 fffffa80`0bbfb620 fffffa80`066a6b30 fffffa80`0bbfb620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`046f1d40 fffff800`032815e6 : fffff880`009e8180 fffffa80`0bbfb620 fffff880`009f30c0 5035766f`70433052 : nt!PspSystemThreadStartup+0x5a
fffff880`046f1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78b8
fffff880`052438b8 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
---------

This was another Video Card 0x116 error...


Monitor temperatures during the following tests.

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.

• 
  Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
  
  
  
• Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

 

[davebeck]

After running the FurMark test for only a couple of minutes the graphics card temperature increased to 73°C in the computer crashed. The CPU temperature was around 60°C at the same time.

I have a mate coming over this afternoonwith a spare graphics card that we are going to swap into my system to see if that makes a difference.

 

[writhziden]

Alright, sounds like a good step. Let us know how the system responds to a different card.

 

[davebeck]

Interestingly, we placed in a cheap GeForce graphics card and ran the FurMark test to find that the graphic card temperature quickly increased to around 97°C while the CPU temperature remained steady on 38°C. Do you find it surprising that the old video card would cause the CPU temperature to increase?

We ran the test for around 5 min and the system did not crash.

The plan is to now place the old video card into another system and run some tests on it.

 

[writhziden]

Thanks for posting the results. If the card was not working properly, I could understand the CPU having to do more work. Let us know how your card does in another system, as well.