locked
SRSv2 systems crashing RRS feed

  • Question

  • Hello, 

    In our organisation we are currently deploying a new video conference system based on SRS. We are using the Lenovo ThinkSmart Hub 500 as our hardware.

    However, we have ran in to a issue where the system crashes during video Skype meetings with multiple participants.

    We have 1 HDMI monitor and 1 Logitech MeetUp camera connected to the Lenovo Hub.

    When the system crashes the screen just turns black and the next thing we see is the BIOS boot screen. We do not see a bluescreen but in the system log we always find a Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR.

    These crashes can occur after 15 seconds as well as after 1,5 hours. We have seen this behaviour on 4 Lenovo ThinkSmart Hub 500 and a Surface Pro.

    Please let me know if you have any ideas on what that could cause this isssue or need more information.

    The output of analyze-v from the memory.dmp follows below: 

    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\dld\Downloads\MEMORY (1).DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
    
    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 17134 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff801`d76a5000 PsLoadedModuleList = 0xfffff801`d7a52150
    Debug session time: Thu May 23 10:32:55.790 2019 (UTC + 2:00)
    System Uptime: 0 days 0:01:32.475
    Loading Kernel Symbols
    .....................................Page 2001a4721 too large to be in the dump file.
    Page 200184020 too large to be in the dump file.
    ..........................
    ................................................................
    ................................................................
    ...
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000000ac`d23af018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ...........
    For analysis of this file, run !analyze -v
    0: 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: 0000000000100000, The subtype of the bugcheck:
    Arg2: 0000000000000001
    Arg3: 0000000000000001
    Arg4: ffff9c8a283a2000
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 401
    
    BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804
    
    SYSTEM_MANUFACTURER:  LENOVO
    
    SYSTEM_PRODUCT_NAME:  10V50002MT
    
    SYSTEM_SKU:  LENOVO_MT_10V5_BU_Think_FM_ThinkSmart Hub 500
    
    SYSTEM_VERSION:  ThinkSmart Hub 500
    
    BIOS_VENDOR:  LENOVO
    
    BIOS_VERSION:  M23KT17A
    
    BIOS_DATE:  03/28/2018
    
    BASEBOARD_MANUFACTURER:  LENOVO
    
    BASEBOARD_PRODUCT:  313F
    
    BASEBOARD_VERSION:  SEK0M97011 IOT 1801932133213
    
    DUMP_TYPE:  1
    
    BUGCHECK_P1: 100000
    
    BUGCHECK_P2: 1
    
    BUGCHECK_P3: 1
    
    BUGCHECK_P4: ffff9c8a283a2000
    
    CPU_COUNT: 4
    
    CPU_MHZ: a98
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 9e
    
    CPU_STEPPING: 9
    
    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 8E'00000000 (cache) 8E'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x119
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  STOCL073
    
    ANALYSIS_SESSION_TIME:  05-28-2019 11:05:13.0084
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8089911331e to fffff801d784fab0
    
    STACK_TEXT:  
    ffffd50d`87fe6a08 fffff808`9911331e : 00000000`00000119 00000000`00100000 00000000`00000001 00000000`00000001 : nt!KeBugCheckEx
    ffffd50d`87fe6a10 fffff808`9aef981d : ffff9c8a`2bd7d470 ffff9c8a`29a23010 ffff9c8a`2971fc20 ffff9c8a`28839700 : watchdog!WdLogEvent5_WdCriticalError+0xce
    ffffd50d`87fe6a50 fffff808`98f95d0d : ffffd50d`00000001 ffff9c8a`29a23010 00000000`00837825 ffff9c8a`283a2000 : dxgmms2!VidSchSubmitCommand+0x24a5d
    ffffd50d`87fe6ba0 fffff808`9902b687 : 00000000`00000000 ffff9c8a`29a23010 00000000`00000081 00000000`00000000 : dxgkrnl!DXGCONTEXT::SubmitCommandToImplicitQueue+0x5d
    ffffd50d`87fe6bd0 fffff808`9902a366 : ffff9c8a`29a23010 ffffd50d`87fe7050 ffff9c8a`29a23010 ffffc10b`7de0c010 : dxgkrnl!DXGCONTEXT::SubmitPresentMultiPlaneOverlays3+0xd77
    ffffd50d`87fe6f00 fffff808`9902cdde : ffffffff`c000000d 00000000`00000001 00000000`00000001 0000026e`e0dbfc80 : dxgkrnl!DXGCONTEXT::PresentMultiPlaneOverlay3+0x11ca
    ffffd50d`87fe7810 fffff9e3`e925d0e1 : 000000ac`00000000 ffffc10b`7de0c010 ffff9c8a`28839700 00000000`00000003 : dxgkrnl!DxgkPresentMultiPlaneOverlay3+0x5ee
    ffffd50d`87fe7a50 fffff801`d7860143 : ffff9c8a`28839700 00000000`00000000 ffff9c8a`29638f20 00000000`00000003 : win32kbase!NtGdiDdDDIPresentMultiPlaneOverlay3+0x11
    ffffd50d`87fe7a80 00007ffd`60e252a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000ac`d25fceb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`60e252a4
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  9ec6f4d8ba03e1e3ff62b272fc295d66cee6c156
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0c595c1537745b13f7cddcc0387d31fc77fbf10e
    
    THREAD_SHA1_HASH_MOD:  cbf042813f0ae9112e40c080ceefbece3910bb00
    
    FOLLOWUP_IP: 
    dxgmms2!VidSchSubmitCommand+24a5d
    fffff808`9aef981d cc              int     3
    
    FAULT_INSTR_CODE:  e0ba0fcc
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  dxgmms2!VidSchSubmitCommand+24a5d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms2
    
    IMAGE_NAME:  dxgmms2.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  10.0.17134.765
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  24a5d
    
    FAILURE_BUCKET_ID:  0x119_100000_UNKNOWN_dxgmms2!VidSchSubmitCommand
    
    BUCKET_ID:  0x119_100000_UNKNOWN_dxgmms2!VidSchSubmitCommand
    
    PRIMARY_PROBLEM_CLASS:  0x119_100000_UNKNOWN_dxgmms2!VidSchSubmitCommand
    
    TARGET_TIME:  2019-05-23T08:32:55.000Z
    
    OSBUILD:  17134
    
    OSSERVICEPACK:  0
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2019-05-03 07:57:58
    
    BUILDDATESTAMP_STR:  180410-1804
    
    BUILDLAB_STR:  rs4_release
    
    BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804
    
    ANALYSIS_SESSION_ELAPSED_TIME:  7b7e
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x119_100000_unknown_dxgmms2!vidschsubmitcommand
    
    FAILURE_ID_HASH:  {97839a13-0e8d-d543-9056-52e90bf3ff67}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm dxgmms2
    Browse full module list
    start             end                 module name
    fffff808`9ae60000 fffff808`9af26000   dxgmms2    (pdb symbols)          C:\ProgramData\dbg\sym\dxgmms2.pdb\3D16A2919104EDECE8919B6C28B7CDCC1\dxgmms2.pdb
        Loaded symbol image file: dxgmms2.sys
        Image path: \SystemRoot\System32\drivers\dxgmms2.sys
        Image name: dxgmms2.sys
        Browse all global symbols  functions  data
        Image was built with /Brepro flag.
        Timestamp:        D099677F (This is a reproducible build file hash, not a timestamp)
        CheckSum:         000C8D88
        ImageSize:        000C6000
        File version:     10.0.17134.765
        Product version:  10.0.17134.765
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        Information from resource tables:
            CompanyName:      Microsoft Corporation
            ProductName:      Microsoft® Windows® Operating System
            InternalName:     dxgmms2.sys
            OriginalFilename: dxgmms2.sys
            ProductVersion:   10.0.17134.765
            FileVersion:      10.0.17134.765 (WinBuild.160101.0800)
            FileDescription:  DirectX Graphics MMS
            LegalCopyright:   © Microsoft Corporation. All rights reserved.

    Best regards, 

    Dennis Lundblad


    Tuesday, May 28, 2019 12:15 PM

All replies

  • Hi Dennis,

    About this “Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR”, it is mostly related to Windows OS issue. Did it happen before or just occur after some update? I suggest you could make the OS and drivers to use the latest update. 

    And which version of SRS do you use? The latest version is released at April 10, 2019, have a try it to see if it helps.


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by Shaw_Lu Wednesday, May 29, 2019 7:23 AM
    Wednesday, May 29, 2019 7:23 AM
  • Hi Dennis,

    About this “Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR”, it is mostly related to Windows OS issue. Did it happen before or just occur after some update? I suggest you could make the OS and drivers to use the latest update. 

    And which version of SRS do you use? The latest version is released at April 10, 2019, have a try it to see if it helps.


    Best Regards,
    Shaw Lu



    Hi, 

    It happens both before and after updates on both our ThinkSmart Hub 500 systems and Surface Pro systems.

    I've tried both the latest (image was created last week) and older versions of SRS.

    I find it weird that we have this issue on both the Surface Pro and ThinkSmart Hub 500 systems. We have tried to run them with/without AD domain and on internal/external networks.

    It feels like a configuration error on the Skype server shouldn't crash the whole endpoint system. I would understand if a call dropped, but it is the whole system crashing and restarting from BIOS.

    Best regards, 

    Dennis Lundblad


    Wednesday, May 29, 2019 2:19 PM
  • Hi Dennis,

    It is quite strange, how about update the BIOS version?

    In another way, what I think is try different external equipment (monitor or camera).


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by Shaw_Lu Thursday, May 30, 2019 8:44 AM
    Thursday, May 30, 2019 8:44 AM
  • Hi Dennis,

    It is quite strange, how about update the BIOS version?

    In another way, what I think is try different external equipment (monitor or camera).


    Best Regards,
    Shaw Lu



    Hi Shaw, 

    Thank you for your reply.

    BIOS is updated and I have tried with different monitors and cameras. Please note that this is happening on four different devices (all I tested) 1 Surface Pro and 4 Lenovo Hub 500.

    Could any configuration in Skype (either the client or server side cause this) ?

    Best regards, 

    Dennis Lundblad

    Friday, May 31, 2019 6:32 AM
  • Hi Dennis,

    I haven’t seen such an option about the Skype.

    Maybe you could review the deployment according the article.

    https://docs.microsoft.com/en-us/MicrosoftTeams/room-systems/room-systems-v2


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by Shaw_Lu Friday, May 31, 2019 10:00 AM
    Friday, May 31, 2019 10:00 AM
  • Hi Dennis,

    I haven’t seen such an option about the Skype.

    Maybe you could review the deployment according the article.


    Best Regards,
    Shaw Lu




    Hi Shaw, 

    I've checked the deployment guide several times and havn't found anything that could cause this.

    As you mentioned in your first reply, it feels like this is a Windows issue but I haven't seen this behaviour outside of Skype meetings. I ran several loadtests and benchmarks to test if this is something related to the hardware. Also, since I experience this with the Surface Pro as well it can't be anything with the Lenovo Hub 500 hardware.

    The image that has been installed is based on a Windows image that has been downloaded directly from Microsoft and the Windows image itself works flawlessly on other machines.

    Do you have any idea if something in Windows could cause this? Other than drivers since these are updated and different between the two hardware platforms.

    Best regards, 

    Dennis Lundblad

    Friday, May 31, 2019 11:39 AM
  • Hi Dennis,

    I did some research and found this thread, according it, have a try to use the latest Intel video drivers and add the registry:

    Go to regedit

    Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers

    Add > new DWORD

    Name of DWORD: DisableSecondaryIFlipSupport

    Value of DWORD: 1

    Restart the system.

    https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/It-s-here-Microsoft-Teams-Rooms-Update-4-0-85-0-is-live/ba-p/428800


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Shaw_Lu Monday, June 10, 2019 1:20 AM
    Tuesday, June 4, 2019 7:39 AM
  • Hi,

    Do you have any further issue on this topic?

    Meanwhile, if there is no issue, please remember to mark helpful reply as answer to close the thread. Your action would be helpful to other users who encounter the same issue and read this thread.

    Thanks for your understanding.


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, June 10, 2019 1:20 AM