Windows 10: Video Scheduler Internal Error! Windows 10

  1.    11 Jan 2016 #1

    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?
      My ComputerSystem Spec

  2.    11 Jan 2016 #2

    Please use the BSOD posting instruction to provide theDumpfile

      My ComputerSystem Spec

  3.    11 Jan 2016 #3

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

  4.    11 Jan 2016 #4

     1: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    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                            ***
    ***                                                                   ***
    BUGCHECK_STR:  0x119
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    LAST_CONTROL_TRANSFER:  from fffff801e92e3e1d to fffff8021e550760
    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
    dxgmms2! ?? ::FNODOBFM::`string'+3c08
    fffff801`ec3fa848 cc              int     3
    SYMBOL_NAME:  dxgmms2! ?? ::FNODOBFM::`string'+3c08
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dxgmms2
    IMAGE_NAME:  dxgmms2.sys
    IMAGE_VERSION:  10.0.10586.0
    BUCKET_ID:  0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!_??_::FNODOBFM::_string_
    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.
    The dumpfile is not really a help
    But i found this WER (windows Error Reporting)
     Αυτά τα αρχεία μπορεί να είναι διαθέσιμα εδώ:
    Σύμβολο ανάλυσης: 
    Επανέλεγχος για λύση: 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
    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:
    Look if your Razer gamedevices need windows 10 drivers.
      My ComputerSystem Spec

  5.    11 Jan 2016 #5

    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.
      My ComputerSystem Spec

  6.    12 Jan 2016 #6

    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:

    RtNdPt60 Mon Jul 20 04:27:32 2009
    Driver Description: Realtek NDIS User mode I/O Driver - Ethernet
    Driver Update Site:

    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:

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

    Please update or uninstall the drivers.
      My ComputerSystem Spec

  7.    12 Jan 2016 #7

    [QUOTE=lifetec;531724]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:

    RtNdPt60 Mon Jul 20 04:27:32 2009
    Driver Description: Realtek NDIS User mode I/O Driver - Ethernet
    Driver Update Site:

    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:

    Yes. I updated from windows 7 in august! I cannot update or uninstall these drivers because they are not detected from My Unistaller to be uninstalled!
      My ComputerSystem Spec


Related Threads
Hello tenforums members, I upgraded my Lenovo U310 laptop from Windows 8.1 to Windows 10 a week ago. Everything seems to have upgraded successfully. The only problem that I can find is that none of the video streaming from Windows 10 apps can be...
New thread created as requested by Axe0 I just updated my Windows 8.1 desktop to Windows 10 Home and all is now running fine apart from this BSOD which occurs when restarting the PC from Sleep. As I use the PC as a Media Centre the ability to...
I'm getting the following error: Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Windows\Media Center\RegisterSearch definition. Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe. <Event...
Hello Guys, When I am viewing webpages with video's playing I am getting the odd BSD with the Video scheduler internal error, it happens roughly every other day but yesterday it happened twice. My video card is a Gigabyte GeForce GTX 660 2GB...
After an in-place upgrade from Windows 7 to Windows 10, Task Scheduler always comes with error popups for many tasks. "Task X: The task object version is either unsupported or invalid." After closing all of them, I can get into Task Scheduler but I...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:57.
Find Us