Microsoft Teams crashes everytime I open it

%3CLINGO-SUB%20id%3D%22lingo-sub-46729%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46729%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20as%20of%20today%20unable%20to%20use%20Team%20anymore%2C%20as%20it's%20frozen%20when%20I%20open%20it%2C%20and%20I'm%20unable%20to%20click%20anyhting.%20Uninstalled%20it%20fully%20and%20reinstalled%20it%20again%2C%20but%20still%20no%20luck.%20Even%20tried%20system%20restore.%3C%2FP%3E%3CP%3EMemory%20usage%20goes%20up%20to%201.5GB%20for%20the%20app%2C%20where%20it%20used%20to%20be%20max%2060MB.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBelow%20is%20what%20I%20could%20find%20in%20the%20event%20log%3A%3C%2FP%3E%3CP%3EFaulting%20application%20name%3A%20Teams.exe%2C%20version%3A%200.7.0.3803%2C%20time%20stamp%3A%200x583f2660%3CBR%20%2F%3EFaulting%20module%20name%3A%20Teams.exe%2C%20version%3A%200.7.0.3803%2C%20time%20stamp%3A%200x583f2660%3CBR%20%2F%3EException%20code%3A%200xc0000005%3CBR%20%2F%3EFault%20offset%3A%200x00000000000e3fb2%3CBR%20%2F%3EFaulting%20process%20id%3A%200xa08%3CBR%20%2F%3EFaulting%20application%20start%20time%3A%200x01d288fdba3674c2%3CBR%20%2F%3EFaulting%20application%20path%3A%20C%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CMicrosoft%5CTeams%5Ccurrent%5CTeams.exe%3CBR%20%2F%3EFaulting%20module%20path%3A%20C%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CMicrosoft%5CTeams%5Ccurrent%5CTeams.exe%3CBR%20%2F%3EReport%20Id%3A%204c233978-f4f1-11e6-827a-002564e6ef5a%3CBR%20%2F%3EFaulting%20package%20full%20name%3A%3CBR%20%2F%3EFaulting%20package-relative%20application%20ID%3A%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E----------------------------------------------%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EFault%20bucket%20%2C%20type%200%3CBR%20%2F%3EEvent%20Name%3A%20AppHangB1%3CBR%20%2F%3EResponse%3A%20Not%20available%3CBR%20%2F%3ECab%20Id%3A%200%3C%2FP%3E%3CP%3EProblem%20signature%3A%3CBR%20%2F%3EP1%3A%20Teams.exe%3CBR%20%2F%3EP2%3A%200.7.0.3803%3CBR%20%2F%3EP3%3A%20583f2660%3CBR%20%2F%3EP4%3A%202019%3CBR%20%2F%3EP5%3A%2067246080%3CBR%20%2F%3EP6%3A%3CBR%20%2F%3EP7%3A%3CBR%20%2F%3EP8%3A%3CBR%20%2F%3EP9%3A%3CBR%20%2F%3EP10%3A%3C%2FP%3E%3CP%3EAttached%20files%3A%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CRoaming%5CMicrosoft%5CTeams%5Clogs.txt%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CRoaming%5CMicrosoft%5CTeams%5Csettings.json%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CTemp%5CWER8ABE.tmp.version.xml%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CTemp%5CWER8ACF.tmp.xml%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CTemp%5CWER8BAC.tmp.WERInternalMetadata.xml%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CMicrosoft%5CWindows%5CWER%5CReportQueue%5CCritical_Teams.exe_eb1afa6e45dc7d323ee0aed3ea1bc7d7af2e7318_22835d53_cab_0cfc8ba9%5Cmemory.hdmp%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CMicrosoft%5CWindows%5CWER%5CReportQueue%5CCritical_Teams.exe_eb1afa6e45dc7d323ee0aed3ea1bc7d7af2e7318_22835d53_cab_0cfc8ba9%5Ctriagedump.dmp%3C%2FP%3E%3CP%3EThese%20files%20may%20be%20available%20here%3A%3CBR%20%2F%3EC%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CMicrosoft%5CWindows%5CWER%5CReportQueue%5CCritical_Teams.exe_eb1afa6e45dc7d323ee0aed3ea1bc7d7af2e7318_22835d53_cab_0cfc8ba9%3C%2FP%3E%3CP%3EAnalysis%20symbol%3A%3CBR%20%2F%3ERechecking%20for%20solution%3A%200%3CBR%20%2F%3EReport%20Id%3A%2046a5f626-f4f1-11e6-827a-002564e6ef5a%3CBR%20%2F%3EReport%20Status%3A%204%3CBR%20%2F%3EHashed%20bucket%3A%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E-----------------------------------------------%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20program%20Teams.exe%20version%200.7.0.3803%20stopped%20interacting%20with%20Windows%20and%20was%20closed.%20To%20see%20if%20more%20information%20about%20the%20problem%20is%20available%2C%20check%20the%20problem%20history%20in%20the%20Action%20Center%20control%20panel.%3CBR%20%2F%3E%26nbsp%3BProcess%20ID%3A%20df8%3CBR%20%2F%3E%26nbsp%3BStart%20Time%3A%2001d288fd530e4daa%3CBR%20%2F%3E%26nbsp%3BTermination%20Time%3A%204294967295%3CBR%20%2F%3E%26nbsp%3BApplication%20Path%3A%20C%3A%5CUsers%5CMyUser%5CAppData%5CLocal%5CMicrosoft%5CTeams%5Ccurrent%5CTeams.exe%3CBR%20%2F%3E%26nbsp%3BReport%20Id%3A%2046a5f626-f4f1-11e6-827a-002564e6ef5a%3CBR%20%2F%3E%26nbsp%3BFaulting%20package%20full%20name%3A%3CBR%20%2F%3E%26nbsp%3BFaulting%20package-relative%20application%20ID%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20help.%20Thanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-46729%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-233670%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-233670%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20found%20a%20resolution%20for%20this%20issue%20beyond%20what%20has%20been%20listed%20in%20this%20thread%20already%3F%20i%20have%20the%20same%20issue%20and%20have%20tried%20all%20the%20above%20mentioned%20things%20to%20try.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215987%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215987%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20man.%20My%20Teams%20managed%20to%20sort%20it%20self%20out%20at%20the%20end.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215984%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215984%22%20slang%3D%22en-US%22%3E%3CP%3EHi!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20experienced%20the%20same%20problems.%20The%20error%20is%20with%26nbsp%3B%3CEM%3E%3CSTRONG%3Eigc64.dll%26nbsp%3B%3C%2FSTRONG%3E%3C%2FEM%3Ewhich%20seems%20to%20be%20an%26nbsp%3B%3CSTRONG%3EIntel%20Graphics%20Driver%3C%2FSTRONG%3E.%20I%20just%20installed%20the%20latest%20driver%20and%20Teams%20(%2Bsome%20other%20apps%20that%20were%20closing%20for%20no%20reason)%20are%20working%20again.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3ESolution%20that%20worked%20for%20me%3A%26nbsp%3B%3C%2FSTRONG%3E(Re)install%20Intel%20Graphics%20drivers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95134%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95134%22%20slang%3D%22en-US%22%3EWas%20getting%20the%20same%20problems%20tried%20to%20uninstall%20and%20reinstall%20...crashes%20with%20squirrel%20installer%20problems....%20installed%20old%20version%20from%20february%20..%20works%20great%20until%20it%20tries%20to%20self%20update.%20now%20stuck%20in%20updater%20loop%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-90690%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-90690%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F179%22%20target%3D%22_blank%22%3E%40Lana%20O'Brien%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhere%20do%20we%20go%20to%20submit%20a%20support%20ticket%20regarding%20this%3F%20%26nbsp%3BEvery%20time%20I%20start%20a%20Team%20Meeting%2C%20I%20go%20through%20an%20endless%20loop%20of%20crashing%20and%20relaunching....%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20the%20launch%20splash%20screen%20I%20get%20when%20relaunching%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F17778i351DC09053AB615A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Glitch.png%22%20title%3D%22Glitch.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BThanks!%3C%2FP%3E%3CP%3EChet%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48604%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48604%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%20please%20open%20a%20support%20ticket%20so%20that%20this%20issue%20can%20be%20tracked%20and%20escalated.%20Thank%20you.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47893%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47893%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20the%20couple%20users%20in%20today%20that%20had%20the%20issue%20it%20is%20working%20for%20them%20as%20well%20now.%20%26nbsp%3BNo%20changes%20on%20my%20end.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47884%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47884%22%20slang%3D%22en-US%22%3EWorking%20here%20too.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47706%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47706%22%20slang%3D%22en-US%22%3EAt%20the%20moment%20everything%20is%20working.%3CBR%20%2F%3EI%20didn't%20do%20anything.%3CBR%20%2F%3EThe%20same%20version%20of%20Teams%20client%3A%200.7.0.3803%3CBR%20%2F%3EIt's%20unexplained.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47659%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47659%22%20slang%3D%22en-US%22%3EToday%20for%20the%20problematic%20user%2C%20Teams%20got%20updated%20and%20works%20fine%20now.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47655%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47655%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20user%20that%20was%20having%20the%20issue%2C%20tried%20to%20launch%20the%20app%20from%20the%20taskbar%20shortcut.%20When%20I%20ran%20the%20.exe%20directly%20from%20the%20installation%20directory%20it%20opened%20without%20a%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20try%20that.%20Then%20just%20create%20a%20new%20shortcut%20from%20the%20.exe%20file.%20I%20suspect%20that%20the%20launch%20parameters%20on%20the%20shortcut%20was%20causing%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47653%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47653%22%20slang%3D%22en-US%22%3EThe%20same%20issue.%3CBR%20%2F%3EIt%20happened%20for%20now%20on%20three%20computers%20(Win7x64)%20in%20our%20company.%3CBR%20%2F%3EOn%20one%20of%20them%20we%20resolved%20it%20through%20full%20reinstall%20(were%20deleted%20remaining%20folders%20and%20registry%20records%20after%20uninstalling).%3CBR%20%2F%3EOthers%20weren't%20so%20lucky.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47541%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47541%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%3C%2FP%3E%3CP%3EServer%202016%20as%20the%20workstation%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47474%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47474%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20experiencing%20exactly%20the%20same%20problem%2C%20app%20just%20crashes%20whenever%20I%20try%20to%20use%20it.%3C%2FP%3E%3CP%3EEvent%20Viewer%20shows%3A%26nbsp%3BFaulting%20application%20name%3A%20Teams.exe%2C%20version%3A%200.7.0.3803%3C%2FP%3E%3CP%3EException%20code%3A%200xc0000005%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%20on%20Windows%2010%20Pro%20x64.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETried%20rebooting%20PC%20and%20uninstall%20%2F%20reinstall%2C%20but%20simply%20doesn't%20work%20anymore.%3C%2FP%3E%3CP%3EIt%20was%20working%20perfectly%20up%20till%2017th%20Feb%2C%20but%20hasn't%20worked%20since.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47301%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47301%22%20slang%3D%22en-US%22%3E%3CP%3EI%20assume%20that%20Microsoft%20is%20aware%20of%20this%20issue%2C%20but%20there%20is%20no%20acknowledgement%20or%20official%20words%20from%20the%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47271%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47271%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here.%202%20of%20my%20users%20are%20facing%20this%20issue.%20The%20app%20its%20just%20loading%20on%20a%20specific%20Team%20but%20no%20interaction%20can%20be%20made.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20the%20error%20i%20get%20on%20the%20log%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%26nbsp%3B%26lt%3B3708%26gt%3B%20--%20error%20--%20Renderer%20process%20unresponsive%20with%20url%20%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%2F_%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%2F_%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlready%20tried%20reinstalling%2C%20deleting%20the%20Teams%20folder%20on%20AppData%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47253%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47253%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20experiencing%20the%20same%20issue.%206%20persons%20in%20my%20company%20cant%20access%20the%20desktop%20app%20for%20Teams.%20Not%20sure%20if%20it%20is%20a%20coincidence%20but%20everyone%20who%20is%20having%20issues%20are%20on%20desktops.%20No%20one%20on%20a%20laptop%20has%20had%20any%20issues%20yet.%20We%20have%20teams%20on%20about%20100%20PCs.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47215%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47215%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20thing%20happening%20to%20about%208%20users%20in%20my%20company%3F%3F%3F%20No%20issues%20yet%20for%20the%20other%26nbsp%3B15%20using%20Team.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47202%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47202%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20suggestion%2C%20but%20I%20tried%20that%20several%20times%20prior%20to%20posting%20here%20as%20well.%20%26nbsp%3BI've%20set%20users%20up%20on%20web%20client%20for%20now.%20%26nbsp%3BReally%20need%20a%20solution%20though%20as%20that%20isn't%20ideal.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47086%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47086%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Chad%2C%20That%20was%20one%20of%20the%20things%20I%20have%20tried%2C%20but%20with%20no%20success.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46933%22%20slang%3D%22en-US%22%3ERE%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46933%22%20slang%3D%22en-US%22%3EI%20have%20fixed%20quite%20a%20few%20similar%20issues%20by%20deleting%20the%20Teams%20folder%20in%20AppData%20-%26gt%3B%20Microsoft%20-%26gt%3B%20rename%20or%20delete%20Teams.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46895%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46895%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20transitioning%20my%20company%20to%20Teams%20and%204%20users%20having%20the%20same%20problem.%20%26nbsp%3BUninstalling%20and%20re-installing%20doesn't%20solve%20the%20issue.%20%26nbsp%3BI've%20tried%20both%2032-bit%20and%2064-bit%20apps%20with%20no%20luck.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46740%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46740%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20also%20facing%20the%20same%20problem%20in%26nbsp%3B%3CSPAN%3E0.7.0.3803.%20I%20am%20running%20on%20Windows%202008%20R2%20Enterprise.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46737%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46737%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20for%20one%20of%20collegues%2C%20the%20Teams%20got%20updated%20and%20later%20he%20faces%20the%20same%20problem.%20The%20RAM%20consumption%20spikes%20and%20crashes%20then.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1216563%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20crashes%20everytime%20I%20open%20it%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1216563%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20Problem%20here...after%20last%20win%20updates....%20I'm%20not%20able%20also%20to%20unistall%20the%20app%2C%20i've%20unistalled%20all%20office%20softewares....%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I am as of today unable to use Team anymore, as it's frozen when I open it, and I'm unable to click anyhting. Uninstalled it fully and reinstalled it again, but still no luck. Even tried system restore.

Memory usage goes up to 1.5GB for the app, where it used to be max 60MB.

 

Below is what I could find in the event log:

Faulting application name: Teams.exe, version: 0.7.0.3803, time stamp: 0x583f2660
Faulting module name: Teams.exe, version: 0.7.0.3803, time stamp: 0x583f2660
Exception code: 0xc0000005
Fault offset: 0x00000000000e3fb2
Faulting process id: 0xa08
Faulting application start time: 0x01d288fdba3674c2
Faulting application path: C:\Users\MyUser\AppData\Local\Microsoft\Teams\current\Teams.exe
Faulting module path: C:\Users\MyUser\AppData\Local\Microsoft\Teams\current\Teams.exe
Report Id: 4c233978-f4f1-11e6-827a-002564e6ef5a
Faulting package full name:
Faulting package-relative application ID:


----------------------------------------------


Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Teams.exe
P2: 0.7.0.3803
P3: 583f2660
P4: 2019
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Users\MyUser\AppData\Roaming\Microsoft\Teams\logs.txt
C:\Users\MyUser\AppData\Roaming\Microsoft\Teams\settings.json
C:\Users\MyUser\AppData\Local\Temp\WER8ABE.tmp.version.xml
C:\Users\MyUser\AppData\Local\Temp\WER8ACF.tmp.xml
C:\Users\MyUser\AppData\Local\Temp\WER8BAC.tmp.WERInternalMetadata.xml
C:\Users\MyUser\AppData\Local\Microsoft\Windows\WER\ReportQueue\Critical_Teams.exe_eb1afa6e45dc7d323ee0aed3ea1bc7d7af2e7318_22835d53_cab_0cfc8ba9\memory.hdmp
C:\Users\MyUser\AppData\Local\Microsoft\Windows\WER\ReportQueue\Critical_Teams.exe_eb1afa6e45dc7d323ee0aed3ea1bc7d7af2e7318_22835d53_cab_0cfc8ba9\triagedump.dmp

These files may be available here:
C:\Users\MyUser\AppData\Local\Microsoft\Windows\WER\ReportQueue\Critical_Teams.exe_eb1afa6e45dc7d323ee0aed3ea1bc7d7af2e7318_22835d53_cab_0cfc8ba9

Analysis symbol:
Rechecking for solution: 0
Report Id: 46a5f626-f4f1-11e6-827a-002564e6ef5a
Report Status: 4
Hashed bucket:


-----------------------------------------------


The program Teams.exe version 0.7.0.3803 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: df8
 Start Time: 01d288fd530e4daa
 Termination Time: 4294967295
 Application Path: C:\Users\MyUser\AppData\Local\Microsoft\Teams\current\Teams.exe
 Report Id: 46a5f626-f4f1-11e6-827a-002564e6ef5a
 Faulting package full name:
 Faulting package-relative application ID:

 

 

Please help. Thanks

 

26 Replies

Today for one of collegues, the Teams got updated and later he faces the same problem. The RAM consumption spikes and crashes then.

I am also facing the same problem in 0.7.0.3803. I am running on Windows 2008 R2 Enterprise.

Just transitioning my company to Teams and 4 users having the same problem.  Uninstalling and re-installing doesn't solve the issue.  I've tried both 32-bit and 64-bit apps with no luck.

I have fixed quite a few similar issues by deleting the Teams folder in AppData -> Microsoft -> rename or delete Teams.

Thanks Chad, That was one of the things I have tried, but with no success.

Thanks for the suggestion, but I tried that several times prior to posting here as well.  I've set users up on web client for now.  Really need a solution though as that isn't ideal.

Same thing happening to about 8 users in my company??? No issues yet for the other 15 using Team.

I have been experiencing the same issue. 6 persons in my company cant access the desktop app for Teams. Not sure if it is a coincidence but everyone who is having issues are on desktops. No one on a laptop has had any issues yet. We have teams on about 100 PCs. 

Same here. 2 of my users are facing this issue. The app its just loading on a specific Team but no interaction can be made.

 

This is the error i get on the log:

 

 <3708> -- error -- Renderer process unresponsive with url https://teams.microsoft.com/_

 

Already tried reinstalling, deleting the Teams folder on AppData, etc.

I assume that Microsoft is aware of this issue, but there is no acknowledgement or official words from the Teams.

I'm experiencing exactly the same problem, app just crashes whenever I try to use it.

Event Viewer shows: Faulting application name: Teams.exe, version: 0.7.0.3803

Exception code: 0xc0000005

 

Running on Windows 10 Pro x64.

 

Tried rebooting PC and uninstall / reinstall, but simply doesn't work anymore.

It was working perfectly up till 17th Feb, but hasn't worked since.

 

Same problem

Server 2016 as the workstation

The same issue.
It happened for now on three computers (Win7x64) in our company.
On one of them we resolved it through full reinstall (were deleted remaining folders and registry records after uninstalling).
Others weren't so lucky.

The user that was having the issue, tried to launch the app from the taskbar shortcut. When I ran the .exe directly from the installation directory it opened without a problem.

 

Maybe try that. Then just create a new shortcut from the .exe file. I suspect that the launch parameters on the shortcut was causing this issue.

Today for the problematic user, Teams got updated and works fine now.
At the moment everything is working.
I didn't do anything.
The same version of Teams client: 0.7.0.3803
It's unexplained.
Working here too.

For the couple users in today that had the issue it is working for them as well now.  No changes on my end.

Hello all, please open a support ticket so that this issue can be tracked and escalated. Thank you.