BSOD Video Scheduler Error Message

[davebeck]

Hi I have had an on-again off-again problem that's been going on for some months now but has escalated in the past week.

The problem occurs with unexpected BSOD error messages that always seems to point towards a video schedule error. The error can occur in any usage timeframe (e.g. 10 min or three hours) under varying usage conditions (watching YouTube yesterday, Reading e-mail this morning).

I have previously (a month or two back when experiencing the same problem) updated all drivers and updated to the latest BIOS version. This didn't initially fix the problem although a week or so later I did stop having problems for about a month after doing this.

Anyway, I'm hoping someone can help me get to the bottom of this. Please find attached a zip file with the crash information.

Windows 7 64-bit SP 1
Original OS on this system
Full retail version
System hardware approximately 2 years old
operating system is still original with service Pack 1 update applied

 

[zigzag3143]

Bug Check 0x119: VIDEO_SCHEDULER_INTERNAL_ERROR


The VIDEO_SCHEDULER_INTERNAL_ERROR bug check has a value of 0x00000119. This indicates that the video scheduler has detected a fatal violation.
Important Information If You Have Received a STOP Code

If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error.

Lets start by re-installing the newest video driver using these instructions.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using

Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

 

[davebeck]

I have removed and reinstall the latest drivers and will keep you updated with what happens stop

 

[zigzag3143]

I have removed and reinstall the latest drivers and will keep you updated with what happens stop

Good luck

 

[davebeck]

Unfortunately this morning while watching a couple of music videos on itunes I received another BS0D.

I have attached the dump file information.

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\davebeck\Windows_NT6_BSOD_jcgriff2\011212-23883-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`03212000 PsLoadedModuleList = 0xfffff800`03457670
Debug session time: Wed Jan 11 16:30:31.678 2012 (UTC - 7:00)
System Uptime: 0 days 0:34:48.600
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, 41c98, 41c9d, 41c9c}

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 : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )

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

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 0000000000041c98
Arg3: 0000000000041c9d
Arg4: 0000000000041c9c

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  a

LAST_CONTROL_TRANSFER:  from fffff88001c5322f to fffff8000328ec40

STACK_TEXT:  
fffff880`0358c488 fffff880`01c5322f : 00000000`00000119 00000000`00000001 00000000`00041c98 00000000`00041c9d : nt!KeBugCheckEx
fffff880`0358c490 fffff880`05c07eb9 : 00000000`00000000 00000000`00041c98 00000000`00000000 00000000`00041c9d : watchdog!WdLogEvent5+0x11b
fffff880`0358c4e0 fffff880`05c08125 : fffffa80`0bcc8000 fffff880`0358c610 fffff880`000011ac fffff800`03802b7f : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`0358c510 fffff880`05c07f76 : fffff880`00041c98 fffff880`05c080bc fffffa80`0bcf6000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff880`0358c560 fffff880`066e213f : fffffa80`0aefd480 00000000`000000ff 00000000`00000001 fffffa80`0aefd480 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`0358c590 fffff880`047752cc : fffffa80`0bb2a040 fffffa80`0aefe6c0 00000000`00000001 00000000`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`0358c5c0 fffffa80`0bb2a040 : fffffa80`0aefe6c0 00000000`00000001 00000000`00000000 fffff880`0358c670 : atikmpag+0x52cc
fffff880`0358c5c8 fffffa80`0aefe6c0 : 00000000`00000001 00000000`00000000 fffff880`0358c670 fffff880`066e213f : 0xfffffa80`0bb2a040
fffff880`0358c5d0 00000000`00000001 : 00000000`00000000 fffff880`0358c670 fffff880`066e213f fffffa80`0aefd480 : 0xfffffa80`0aefe6c0
fffff880`0358c5d8 00000000`00000000 : fffff880`0358c670 fffff880`066e213f fffffa80`0aefd480 00000000`00000000 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`05c07eb9 c744244053eeffff mov     dword ptr [rsp+40h],0FFFFEE53h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

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

Go through the steps for Diagnosing basic problems with DirectX and use zigzag3143's method with Driver Sweeper to swap out graphics card drivers if you do more swapping. Let us know if you need further assistance.

 

[davebeck]

I ran the diagnostic tool which showed no errors (I have saved and uploaded the text file to make sure I haven't missed anything).

When I removed the drivers the only ones that I touched were the ATI Radeon drivers. Are there any others that I should be looking at removing as well?

 

[writhziden]

I ran the diagnostic tool which showed no errors (I have saved and uploaded the text file to make sure I haven't missed anything).

When I removed the drivers the only ones that I touched were the ATI Radeon drivers. Are there any others that I should be looking at removing as well?

You may want to go through add/remove programs and remove the AMD Install Manager to remove all AMD software, as well. Then re-install the software if you want, but I would recommend running with just the drivers for testing purposes. The software can cause problems on some machines, and it also can overclock your display card without your permission.

 

[davebeck]

You may want to go through add/remove programs and remove the AMD Install Manager to remove all AMD software, as well. Then re-install the software if you want, but I would recommend running with just the drivers for testing purposes. The software can cause problems on some machines, and it also can overclock your display card without your permission.

Thanks, I have taken your advice and removed the AMD software.

I'm not sure what to do next

 

[writhziden]

You may want to go through add/remove programs and remove the AMD Install Manager to remove all AMD software, as well. Then re-install the software if you want, but I would recommend running with just the drivers for testing purposes. The software can cause problems on some machines, and it also can overclock your display card without your permission.

Thanks, I have taken your advice and removed the AMD software.

I'm not sure what to do next

Just let it run and report back whether you have any more crashes or it is fixed.

 

[davebeck]

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 !

 

[writhziden]

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 http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html.

 

[writhziden]

Any luck following that thread? Need further troubleshooting steps?

 

[davebeck]

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.

 

[writhziden]

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.

 

[davebeck]

that's great, thanks for the help.

 

[writhziden]

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

 

[davebeck]

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.

 

[writhziden]

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: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[davebeck]

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?