Forum Discussion

ecmillion's avatar
ecmillion
Copper Contributor
Jul 26, 2019

MS Teams crashes *sometimes* during Video calls/meetings

I've been researching an issue where several users are experiencing periodic Teams crashes always during a Video call/meeting. A call that crashes once is often successful right after, and the crashes don't follow any pattern. I haven't found any commonalities across hardware or drivers, and have been checking network quality pretty closely. It really seems like it's a Teams software issue. Is anyone else dealing with this kind of inconsistent stability?

 

The errors in logs (that I've seen) are always:

Renderer process crashed; rendererName=mainWindow; crashType=crashed; url=https://teams.microsoft.com; restarting app=YES

 

Other forum threads haven't been useful; they usually point to a software glitch that has since been patched, or some common hardware issue with a specific laptop model (Surface) or webcam (Logitech). 

 

I tried to figure out if I could disable GPU rendering (just as a test) and that doesn't appear to be an option. Is there another test we could try? This seems to be related to graphics rendering, particularly since it always happens during a beginning of a Video call or meeting, and the detail in the error logs...

 

I opened a Microsoft support case, but it's going no where fast, particularly since the issue isn't reproducible on-demand. 

 

In my various testing and research, I tried launching Teams from a command prompt window (thinking maybe "--disable-gpu" would be an option to launch with). It launched and then I stumbled upon this strange output; I eventually canceled with Ctrl+C and Teams closed. 

I think this is totally unrelated, but figured I'd share it in case it ends up being relevant. The messages sure look like Teams is experiencing a memory leak ("MaxListenersExceededWarning: Possible EventEmitter memory leak detected.").  In any case, this output was on a system where Teams has never crashed as described before, so probably not the best clue.

  • TIER4TS 

    Thanks, but I found what these instructions should say. (my updates are in BOLD)

     

    Go into Control Panel and then “Programs and Features”

    Remove the Realtek Audio Driver (Publisher Realtek Semiconductor Corp.) Program

    It will prompt you to reboot the computer, do not reboot yet

     

    Go into DEVICE MANAGER

    Scroll down to Sound, Video and Game Controllers (expand)

    Double Click "Realtek Audio"

    Click Driver Tab

    Click Update Driver

    Click “Browse My Computer for Driver Software” (Locate and install driver software manually)

    Click "Let me pick from a list of available drivers on my computer"

    Uncheck “Show compatible hardware”

    For “Manufacturer” select Microsoft

    For “Model” select High Definition Audio Device Version [most recent date]

    Click Next

    A pop-up will state "Installing this device driver is not recommended because Windows cannot verify that it is compatible with your hardware..."

    Click Yes to the pop-up

    You will receive a screen that states "Windows has successfully updated your drivers"

    Click Close

    Click Close again

    Answer yes to RESTART YOUR COMPUTER NOW

  • ecmillion no, and I typically have half a dozen teams meetings a day with always with video. The convention wisdom would be to look at the devices and drivers, is there really nothing common between the users with this issue?

    • ecmillion's avatar
      ecmillion
      Copper Contributor

      StevenC365 Not that we've been able to identify so far.  There are about 15 different model Dell laptops with a variety of drivers out there. Issue has affected both Windows 7 and Windows 10 on those laptops.  Typically only two types of headsets are used, though the issue has affected users that don't use headsets as well. We generally have only one model of webcam deployed, and again the issue has affected users not using an external webcam as well. We use two styles of docking hardware and a variety of dock models and firmware, and the issue has affected users that are not docked at the time of the issue. I've also seen this issue affect users with different versions of MS Teams.

       

      Users with half a dozen teams calls/meetings with video daily (like yourself) will not have any issues for a week or two, and then the one day they have issues the circumstances aren't out-of-the-ordinary compared to the other numerous calls they had with no problems. This is probably the most challenging part of troubleshooting this.

       

      As you might imagine, the diverse landscape is making it challenging to identify a common thread between users with the issue. We are continuously engaging users to ask about the circumstances of the crashes to try to identify any sort of pattern: are they docked, what dock are they using, what devices were they using (model headset, webcam, any Bluetooth or wireless devices), what was network speed & latency at the time, was VPN connected, what OS version are they using, what model laptop, what graphics, wifi and ethernet drivers do they have, what Teams version do they have, do they reboot their computer regularly, what other applications were open at the time of the crash. If you can think of any other data we should be gathering to aide in this investigation to narrow down a common cause, please do share! 

      • StevenC365's avatar
        StevenC365
        MVP

        ecmillion I would suggest using Call Quality Dashboard v3, and try to see if you can create a filter to identify failing calls, there may be little to show if it's a client-side hang (as you don't get reports form a failed client). CQD also records things like hardware used and driver versions, so it's useful to help identify common factors. It's hard when it's not easily repeatable, but the power of CQD is that you can analyse all your calls across the tenant.

  • ecmillion's avatar
    ecmillion
    Copper Contributor

    We've found that the crashes are typically occurring with Windows 7 and seem to be much more stable in Windows 10, even with identical hardware.

     

    Beyond this, it looks like Teams pushed an application update that may help alleviate this type of software crashing issue, which we are going to test with next.

     

  • Dennis1712's avatar
    Dennis1712
    Copper Contributor

    ecmillion Same Issue here. I have a Surface ProX. Happens randomly. Hope there will be a solution for this problem. 

    • TIER4TS's avatar
      TIER4TS
      Brass Contributor

      Dennis1712Can you clear your log and then once the issue does this again post your logs here? I had zero luck with Microsoft Support on this issue where they just kept doing rudimentary things under three separate tickets that didn't even correlate to the issue. My key issue that i can duplicate on some systems running 1903 and 1909 is that you make one good call / conference and then hang up, perform a second call afterwards it crashes the TEAMS app and also causes the audio/video drivers to become temporarily locked for a short duration of time. TEAMS restarts but remains unstable until computer reboot. What about you?

      • Dennis1712's avatar
        Dennis1712
        Copper Contributor
        What happens is that when I am in a meeting, teams crashes. And then teams will restart. Then I can join the meeting again. But then it will crash again after some time.
    • Jbaviello's avatar
      Jbaviello
      Copper Contributor
      I’m having same issue with my surface pro...have you found a fix. I updated my windows and firmware and still having issue
      • Dennis1712's avatar
        Dennis1712
        Copper Contributor
        No not yet. But it only happens when I use video. I will try this week what will happen when I don't use video. See if it then happens again.
  • TIER4TS's avatar
    TIER4TS
    Brass Contributor

    ecmillionHave you had any additional responses from Microsoft Support on this issue. It is like they are allowing the cases to die at the first support level. They claim to have analysts reviewing, but nothing makes sense on their replies so far. Rudimentary troubleshooting that was already communicated to them.

    • ecmillion's avatar
      ecmillion
      Copper Contributor

      TIER4TSNo, not at all. For a time I had one affected employee experiencing the crash so consistently I engaged with Microsoft regularly on the issue and it never escalated out of tier 1 support. It was a struggle to even convince them there was an issue needing investigation even after displaying the crash repeatedly with the support tech - It just never escalated and I kept repeating the same demonstrations and log gathering. It was a huge waste of time.

       

      I strongly suspect Microsoft is just not supporting/developing to account for some hardware. My most interesting data point was connecting with another enterprise through an employee's spouse, whose company NEVER experienced any Teams crashing org-wide. The employee and their spouse worked from the same network (at home), had the same version of Teams, and had high volume of Teams calls every day - my employee's Teams crashed all the time, their spouse's did not. After connecting with that company's IT department I found out the only notable difference from their org and mine is they have a more modern and higher-end laptop fleet (we both use W10 and Dell laptops) So, throwing money at the problem to upgrade laptops would be one fix... obviously that's not really a solution for those of us with tighter budgets / slower replacement schedules.

      Completely unrelated to Teams crashing problems, we've noticed that Microsoft isn't developing some Teams features for older hardware. Most recently we discovered the new "background effects" feature requires the AVX2 video extensions, which were introduced in Haswell processors (model is 4000 series). This means Dell Latitude 6330 and earlier laptops don't support it. 

      • natsgreg's avatar
        natsgreg
        Copper Contributor

        Seeing the same issue.  The common denominator here appears to be a Plugable dock that uses a Displaylink driver.  Issue appears under no other circumstances.

  • Forrest_H's avatar
    Forrest_H
    Steel Contributor

    I have been trying to troubleshoot similar app crash.  However our users are not using any docking stations with their Surface Pro devices.  The only clue I have is from the Event Viewer;

    Log Name:      Application

    Source:        Application Error

    Date:          4/21/2020 2:24:20 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      Asset-146

    Description:

    Faulting application name: Teams.exe, version: 1.3.0.8663, time stamp: 0x5e443048

    Faulting module name: VCRUNTIME140.dll, version: 14.13.26118.0, time stamp: 0x5a603d9f

    Exception code: 0xc0000005

    Fault offset: 0x000000000000ca27

    Faulting process id: 0xc18

    Faulting application start time: 0x01d61322cf52c961

    Faulting application path: C:\Users\FNameLName\AppData\Local\Microsoft\Teams\current\Teams.exe

    Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll

    Report Id: 969792b3-ae70-4a81-b9ed-5dc61c42164d

    Faulting package full name:

    Faulting package-relative application ID:

    Event Xml:

     

      <System>

        <Provider Name="Application Error" />

        <EventID Qualifiers="0">1000</EventID>

        <Level>2</Level>

        <Task>100</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2020-04-21T18:24:20.158379300Z" />

        <EventRecordID>34653</EventRecordID>

        <Channel>Application</Channel>

        <Computer>Asset-146</Computer>

        <Security />

      </System>

      <EventData>

        <Data>Teams.exe</Data>

        <Data>1.3.0.8663</Data>

        <Data>5e443048</Data>

        <Data>VCRUNTIME140.dll</Data>

        <Data>14.13.26118.0</Data>

        <Data>5a603d9f</Data>

        <Data>c0000005</Data>

        <Data>000000000000ca27</Data>

        <Data>c18</Data>

        <Data>01d61322cf52c961</Data>

        <Data>C:\Users\FNameLName\AppData\Local\Microsoft\Teams\current\Teams.exe</Data>

        <Data>C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll</Data>

        <Data>969792b3-ae70-4a81-b9ed-5dc61c42164d</Data>

        <Data>

        </Data>

        <Data>

        </Data>

      </EventData>

    </Event>

     

    I have searched Bing and Google and cannot find any clues.  This only happens once in a while so I am assuming there is some sort of memory leak that causes the Teams app to crash.

    • KDubs's avatar
      KDubs
      Copper Contributor

      Forrest_H The only machines experiencing crashes for us are the new Dell AIOs we purchased, all our other machines work fine. The AIOs do not have any sort of dock attached to them and we have found that on some removing the Realtek drivers from programs and features fixes the issue. On others it has no affect.

  • Smith_J's avatar
    Smith_J
    Brass Contributor

    Microsoft Teams crashing during a conference call and screen sharing. ... Go to Users\YOUR_USER\AppData\Local\Microsoft and delete Teams and Teams[Something]Addon. Go to Users\YOUR_USER\AppData\Roaming\Microsoft and delete Teams. Re-install Teams

    • MarkHodgkiss's avatar
      MarkHodgkiss
      Copper Contributor

      I am having the same issue , bizarrely only on Microsoft Surface Pro' 4 and 7's The rest of our estate is Dell and we dont have a problem.

      I hope there is a fix as we are trying to promote teams and out high end users who use teams with Surface pros are finding it unworkable 

       

  • Lorenz_Michels's avatar
    Lorenz_Michels
    Copper Contributor

    ecmillion Hi, I have the same or a similar issue for way over a year now. In my situation my complete computer setup freezes. All three screens stay visible but are 'dead', mouse doesn't move, ctrl+alt+del doesn't work, ctrl+shft+esc doesn't work and sometimes a nasty sound is coming from the speakers. The only way back is hold the power knob on the computer until it shuts down and restart the whole computer. I first suspected the logitech brio 4k webcam. More specific I feared that several applications were trying to use the microphone and/or camera of the brio. Teams even crashes when the webcam isn't connected. I reinstalled Windows 10. Shut down all unneccesary tsr programs, disabled the hardware acceleration in MS Teams. No matter what I do, it keeps freezing my computer, mostly one time per one hour meeting, sometimes even two times. I try to stay positive about MS Teams, but I also work with Discord for my work, and there I don't have any of these problems. Just for the record my graphics card is a NVIDIA GeForce GTX 1060 3GB. Oh, and by the way...HELP!

    • TIER4TS's avatar
      TIER4TS
      Brass Contributor

      Lorenz_MichelsDo you have REALTEK drivers installed and what is the make/model of your computer specifically. Thank you.

      • Lorenz_Michels's avatar
        Lorenz_Michels
        Copper Contributor

        TIER4TS 

        Yes, there is a device "Realtek PCIe GbE Family Controller" A NIC with driver RT640X64.SYS (9.1.410.2015, 695.28 KB(711.968 bytes), 2019-06-04 20:44.
           
        It isn't an of the shelve PC, it's built on specifications:
          
        ProcessorInteli7-4770 3.40GHz 4 Core(s) 8 logical processors
        CPU CoolerIntelwith processor
        MoederbordGigabyteGA-Z87M-D3H
        RamgeheugenKingston8GB DDR3 1600MHz Kit
        VideokaartNVIDIAGeForce GTX 1060 3GB
        DVD BranderSamsungSH-224BB DVD Brander
        VoedingBe-QuietPure Power L8 CM 430W
        BehuizingChieftecSD-01B-B
        DisksSamsungSSD 850 EVO 500GB
         SamsungSSD 860 EVO 1TB
         SeagateST1000DM03-1CH162
         SeagateST8000AS0002-1NA17Z
    • Lorenz_Michels's avatar
      Lorenz_Michels
      Copper Contributor

      Lorenz_Michels Hi, I finally found the SOLUTION to my specific problem. I turned of the onboard graphics card (Intel) via the BIOS and now all works fine!! So it wasn't a problem of MS Teams, neither the microphone nor the webcam. Since I use the NVIDIA graphics card to lighten up my three monitors and beamer, the onboard graphics card wasn't used. Apparently it still tried to interfere causing problems. 

      • ViktorCarrein's avatar
        ViktorCarrein
        Copper Contributor
        Hi,

        We're issueing this problem at the moment.
        Was the colution mentioned above a good solution?

        Kind regards, Viktor

Resources