Windows 10: Video Scheduler Internal Error! Windows 10

Hallo. Today I experienced a BSOD in win 10 64bit Home, my mouse started to lag then completely lagged and after a few seconds a BSOD with mention to search for Video Scheduler Internal Error.
My pc is fully up to date.
My gpu is MSI GTX 760 2GB.
Is there something wrong with my gpu?

:)

 

video scheduler internal error (windows10 X64)

Windows10 blue screen error causes: video Scheduler internal error, how to solve?

Windows10 蓝屏，报错原 ：video scheduler internal error，怎么解决？

 

new computuer keeps crashing when streaming video with message video schedule internal error in Windows 10

I have a brand new computer that keeps crashing when streaming video, I get the message; video schedule internal error. then the computer reboots . This happens each time I stream video in Windows 10

 

Please use the BSOD posting instruction to provide theDumpfile BSOD - Posting Instructions - Windows 10 Forums

 

Here is the zip file as mentioned in 10 forums! Hope you can help me!

 

Code: 1: 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: 000000000006afb1 Arg3: 000000000006afb9 Arg4: ffffe001329203a0 Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: dxgkrnl!DXGADAPTER *** *** *** ************************************************************************* CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x119 PROCESS_NAME: System CURRENT_IRQL: 9 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre LAST_CONTROL_TRANSFER: from fffff801e92e3e1d to fffff8021e550760 STACK_TEXT: ffffd001`b73b22e8 fffff801`e92e3e1d : 00000000`00000119 00000000`00000001 00000000`0006afb1 00000000`0006afb9 : nt!KeBugCheckEx ffffd001`b73b22f0 fffff801`ec3fa848 : 00000000`00000001 00000000`00000000 ffffe001`329c3380 00000000`00000008 : watchdog!WdLogEvent5_WdCriticalError+0xcd ffffd001`b73b2330 fffff801`ec3ed077 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2! ?? ::FNODOBFM::`string'+0x3c08 ffffd001`b73b23d0 fffff801`ec4028b5 : ffffd001`0006afb1 00000000`00000000 ffffd001`b73b2560 fffff801`ec402860 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x2b7 ffffd001`b73b2410 fffff802`1e551452 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000f : dxgmms2!VidSchiCallNotifyInterruptAtISR+0x55 ffffd001`b73b2440 fffff801`e87ab7ef : ffffe001`30cddef0 fffff801`ec402860 ffffd001`b73b2560 00000000`00000000 : nt!KeSynchronizeExecution+0x42 ffffd001`b73b2480 fffff801`ec402c53 : ffffe001`329c2000 ffffd001`b73b25d0 ffffe001`370ff010 ffffe001`329a2000 : dxgkrnl!DpSynchronizeExecution+0xaf ffffd001`b73b24d0 fffff801`ec4015e9 : 00000000`00000000 00000000`0006afb1 00000000`00000000 ffffe001`329c2000 : dxgmms2!VidSchiCompletePendingCommandInNodeHwQueue+0x213 ffffd001`b73b2640 fffff801`ec46a988 : ffffe001`329c2000 00000000`00000000 00000000`00000003 ffffe001`329a2001 : dxgmms2!VidSchiResetEngine+0x7c1 ffffd001`b73b2920 fffff801`ec457751 : ffffe001`329c2000 ffffe001`329a2000 00000000`00000000 ffffe001`329a2000 : dxgmms2!VidSchiResetEngines+0x84 ffffd001`b73b2960 fffff801`ec43de6d : 00000000`00000002 00000000`0002bf62 00000000`002f9363 00000000`00000003 : dxgmms2! ?? ::NNGAKEGL::`string'+0x7021 ffffd001`b73b29c0 fffff801`ec3eb8b7 : ffffe001`384ff300 ffffe001`329a2000 ffffe001`384ff308 00000000`00000002 : dxgmms2!VidSchiWaitForSchedulerEvents+0x31d ffffd001`b73b2a80 fffff801`ec44a5fd : ffffe001`32a72010 ffffd001`b73b2bd0 ffffe001`32a72000 ffffe001`329a2000 : dxgmms2!VidSchiScheduleCommandToRun+0x3a7 ffffd001`b73b2b80 fffff801`ec44a5c0 : ffffe001`329a2500 ffffe001`329a2000 00000000`00000080 ffffe001`2eead700 : dxgmms2!VidSchiRun_PriorityTable+0x2d ffffd001`b73b2bd0 fffff802`1e417125 : 00000005`b59bbfff fffff802`1e5557cf 00000000`00010023 00000000`00b98d9f : dxgmms2!VidSchiWorkerThread+0x80 ffffd001`b73b2c10 fffff802`1e555906 : fffff802`1e72b180 ffffe001`329a3840 fffff802`1e4170e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd001`b73b2c60 00000000`00000000 : ffffd001`b73b3000 ffffd001`b73ad000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms2! ?? ::FNODOBFM::`string'+3c08 fffff801`ec3fa848 cc int 3 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgmms2! ?? ::FNODOBFM::`string'+3c08 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms2 IMAGE_NAME: dxgmms2.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5632d236 IMAGE_VERSION: 10.0.10586.0 BUCKET_ID_FUNC_OFFSET: 3c08 FAILURE_BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!_??_::FNODOBFM::_string_ BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!_??_::FNODOBFM::_string_ ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x119_1_driver_reported_invalid_fence_id_dxgmms2!_??_::fnodobfm::_string_ FAILURE_ID_HASH: {1e3e5dd8-c408-6829-a01b-21aa1aab0bd3} Followup: MachineOwner --------- 1: kd> lmvm dxgmms2 start end module name fffff801`ec3e0000 fffff801`ec472000 dxgmms2 (pdb symbols) c:\symbols\dxgmms2.pdb\2A6B21FA23504147BDFDEC026FE127F81\dxgmms2.pdb Loaded symbol image file: dxgmms2.sys Mapped memory image file: c:\symbols\dxgmms2.sys\5632D23692000\dxgmms2.sys Image path: \SystemRoot\System32\drivers\dxgmms2.sys Image name: dxgmms2.sys Timestamp: Fri Oct 30 03:13:10 2015 (5632D236) CheckSum: 00090F33 ImageSize: 00092000 File version: 10.0.10586.0 Product version: 10.0.10586.0 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: dxgmms2.sys OriginalFilename: dxgmms2.sys ProductVersion: 10.0.10586.0 FileVersion: 10.0.10586.0 (th2_release.151029-1700) FileDescription: DirectX Graphics MMS LegalCopyright: © Microsoft Corporation. All rights reserved.[/quote] The dumpfile is not really a help
But i found this WER (windows Error Reporting)
Code: ÁõôÜ ôá áñ÷åßá ìðïñåß íá åßíáé äéáèÝóéìá åäþ: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_d79f99e56b5a6558c350d7b2803f1e7e3bc9a21_00000000_cab_1f15ffa8 Óýìâïëï áíÜëõóçò: ÅðáíÝëåã÷ïò ãéá ëýóç: 0 Áíáãíùñéóôéêü áíáöïñÜò: d41ca4fd-dfdc-415a-a338-1c3e00c95aa3 ÊáôÜóôáóç áíáöïñÜò: 0 ÊÜäïò (bucket) êáôáêåñìáôéóìïý: +++ WER2 +++: Åëáôôùìáôéêüò êÜäïò (bucket) LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, ôýðïò 0 ¼íïìá óõìâÜíôïò: LiveKernelEvent Áðüêñéóç: Äåí õðÜñ÷åé Áíáãíùñéóôéêü Cab: 12a50135-6996-4e23-91fc-08e5e1adc880 ÕðïãñáöÞ ðñïâëÞìáôïò: P1: 141 P2: ffffe0006fdb1010 P3: fffff800ca2b8fd0 P4: 0 P5: 1170 P6: 10_0_10586 P7: 0_0 P8: 768_1 P9: P10:[/quote] And this mention nvlddmkm.sys, This is the driver of your Geforce GPU.
Check if you have the latest windows 10 driver avaliable.
When googling this error there seems to be many people who have this problem. (but no clear solution i believe).

There are some older drivers on your system, do not know if this could be related with the Video Scheduler.
Your Logitech Wingman device drivers are from 2010.
A USB PNP sound device with drivers from 2012 CM10864 Fri Sep 21 07:36:16 2012
Driver Update Site: http://www.cmedia.com.tw/EN/Download...no=0&dtype=ALL
Look if your Razer gamedevices need windows 10 drivers.

 

My GPU drivers are up to date to the latest drivers.
I dont have any logitech devices installed and/or connected to my system!
My razer keyboard and mouse drivers getting updated through razer synapse whenever a new driver is available.
I ran furmark gpu benchmark to see any instability, but nothing. Idle temp at 30c and full load after 3 mins of running the test at 71c.

 

Did you upgrade from an earlier windows OS to windows 10.
Because there are a few older pre-windows 10 drivers on your system.

CM10864 Fri Sep 21 07:36:16 2012
A USB PNP sound device
Driver Update Site: http://www.cmedia.com.tw/EN/Download...no=0&dtype=ALL

RtNdPt60 Mon Jul 20 04:27:32 2009
Driver Description: Realtek NDIS User mode I/O Driver - Ethernet
Driver Update Site: http://www.realtek.com.tw/downloads/...Level=3&Conn=2

WmBEnum Tue Apr 27 22:10:19 2010
Driver Description: Logitech WingMan Virtual Bus Enumerator Driver
WmXlCore Tue Apr 27 22:09:26 2010
Driver Description: Logitech WingMan Translation Driver
Driver Update Site: http://www.logitech.com/index.cfm/su...ads/downloads/

wna3100m Wed Aug 01 11:42:36 2012
N300 Wireless USB Adapter
WNA3100M - N300 Wireless USB Adapter

Please update or uninstall the drivers.