BSOD Video Scheduler Error Message

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.

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

davebeck said:

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

Good luck

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

I have attached the dump file information.

Code:

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. :)

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?

davebeck said:

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.

writhziden said:

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

davebeck said:

writhziden said:

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. :)