Teams (for work) crashes when sharing screen

Anonymous
2022-12-09T17:02:46+00:00

Shortly after sharing a screen (within ~15 seconds), Teams will crash.

This happens consistently, and repeatedly -- it is therefore impossible to share my screen.

The crashing began roughly 2 weeks ago -- previously to that, it was working flawlessly.

Related System/Hardware/Settings information:

  • OS: Windows 11 Pro - 22H2 - Build 22621.819
  • CPU: AMD Ryzen 9 7900X
  • RAM: 32GB
  • GPU: Nvidia RTX 3080
  • Teams: GPU hardware acceleration - ENABLED
  • Windows: Hardware-accelerated GPU scheduling - ON

Thing I have tried:

  • Reinstalled Teams
  • Disabled GPU hardware acceleration inside of Teams

I collected and analyzed the diagnostic logs, and found the related crash event:

Thu Dec 08 2022 16:35:09 GMT-0500 (Eastern Standard Time) <31224> -- info -- StatusIndicatorStateService: Added Presenting (current state: NewActivity -> NewActivity) 
Thu Dec 08 2022 16:35:13 GMT-0500 (Eastern Standard Time) <31224> -- event -- eventpdclevel: 3, rendererName: pluginHost, crashType: crashed, url: file:, causesRestart: true, watchdogBlockingApi: null, watchdogLastPing: null, profileType: undefined, exitCode: -1073741819, electronBuild: 16654718, appRuntime: 25679.594, appCoreServicesReady: true, appInitialized: true, activities: experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,desktop_systray_app_state_update,desktop_systray_app_state_update,desktop_systray_app_state_update,ips:window-command,desktop_systray_app_state_update,desktop_systray_app_state_update, timeSinceActivity: 4.342, appStates: Started,SSOStart,SSOSuccess,Initialized,LazyLoadStage,CheckingUpdates,Initialized,LazyLoadStage,InCall,CallEnded,CheckingUpdates,UpdatesInstalled,InCall,CallEnded,InCall, timeSinceAppState: 35.664000034332275, webAppStates: Inactive,Unloaded,IndexInitialize,IndexJsLoaded,IndexHtmlLoaded,Inactive,Interactive,InCall,Interactive,Inactive,LongInactive,Interactive,Inactive,Interactive,Inactive,Interactive,InCall,Interactive,InCall,Presenting, timeSinceWebAppState: 5.386000156402588, diagnosticEvents: ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,wa:InCall,as:InCall,ua:desktop_systray_app_state_update,ua:desktop_systray_app_state_update,ua:desktop_systray_app_state_update,wa:Presenting,ua:ips:window-command,ua:desktop_systray_app_state_update,ua:desktop_systray_app_state_update, lastDiagnosticEvent: ua:desktop_systray_app_state_update, timeSinceLastDiagnosticEvent: 4.3420000076293945, timeSinceSecondLastDiagnosticEvent: 5.3459999561309814, isHotSwapUsed: false, isHotSwapEnabled: false, slimCoreBuiltInVersion: 2022.39.3, slimCoreVersion: 2022.39.3, tsCallingVersion: undefined, isOnBattery: false, remainingBatteryPercentage: unknown, status: success, scenario: 8a8ed9bc-5e84-4232-9fc2-e564293bfc75, scenarioName: desktop_renderer_process_crash, name: desktop_renderer_process_crash, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 25679594, stepDelta: 0, Scenario.Mode: 1, AppInfo.Language: en-gb, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 26667704, freeMemory: 19712348160, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 1, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: systray, UserInfo.TimeZone: -05:00, vdiMode: 0, Scenario.Name: desktop_renderer_process_crash, Scenario.Step: start, Scenario.Status: success,  
Thu Dec 08 2022 16:35:13 GMT-0500 (Eastern Standard Time) <31224> -- event -- eventpdclevel: 3, rendererName: pluginHost, crashType: crashed, url: file:, causesRestart: true, watchdogBlockingApi: null, watchdogLastPing: null, profileType: undefined, exitCode: -1073741819, electronBuild: 16654718, appRuntime: 25679.594, appCoreServicesReady: true, appInitialized: true, activities: experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,experience-renderer-console-error,desktop_systray_app_state_update,desktop_systray_app_state_update,desktop_systray_app_state_update,ips:window-command,desktop_systray_app_state_update,desktop_systray_app_state_update, timeSinceActivity: 4.342, appStates: Started,SSOStart,SSOSuccess,Initialized,LazyLoadStage,CheckingUpdates,Initialized,LazyLoadStage,InCall,CallEnded,CheckingUpdates,UpdatesInstalled,InCall,CallEnded,InCall, timeSinceAppState: 35.664000034332275, webAppStates: Inactive,Unloaded,IndexInitialize,IndexJsLoaded,IndexHtmlLoaded,Inactive,Interactive,InCall,Interactive,Inactive,LongInactive,Interactive,Inactive,Interactive,Inactive,Interactive,InCall,Interactive,InCall,Presenting, timeSinceWebAppState: 5.386000156402588, diagnosticEvents: ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,ua:experience-renderer-console-error,wa:InCall,as:InCall,ua:desktop_systray_app_state_update,ua:desktop_systray_app_state_update,ua:desktop_systray_app_state_update,wa:Presenting,ua:ips:window-command,ua:desktop_systray_app_state_update,ua:desktop_systray_app_state_update, lastDiagnosticEvent: ua:desktop_systray_app_state_update, timeSinceLastDiagnosticEvent: 4.3420000076293945, timeSinceSecondLastDiagnosticEvent: 5.3459999561309814, isHotSwapUsed: false, isHotSwapEnabled: false, slimCoreBuiltInVersion: 2022.39.3, slimCoreVersion: 2022.39.3, tsCallingVersion: undefined, isOnBattery: false, remainingBatteryPercentage: unknown, status: success, scenario: 8a8ed9bc-5e84-4232-9fc2-e564293bfc75, scenarioName: desktop_renderer_process_crash, name: desktop_renderer_process_crash, step: stop, sequence: 1, delta: 0, scenarioDelta: 0, elapsed: 25679594, stepDelta: 0, Scenario.Mode: 1, AppInfo.Language: en-gb, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 26738200, freeMemory: 19712348160, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 1, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: systray, UserInfo.TimeZone: -05:00, vdiMode: 0, Scenario.Name: desktop_renderer_process_crash, Scenario.Step: stop, Scenario.Status: success,  
Thu Dec 08 2022 16:35:13 GMT-0500 (Eastern Standard Time) <31224> -- error -- Renderer process crashed; rendererName=pluginHost; crashType=crashed; url=file:; restarting app=YES 
Thu Dec 08 2022 16:35:13 GMT-0500 (Eastern Standard Time) <31224> -- info -- PluginHost #2: render-process-gone: {"reason":"crashed","exitCode":-1073741819,"watchdog":null} 
Thu Dec 08 2022 16:35:14 GMT-0500 (Eastern Standard Time) <31224> -- info -- Restart info set with a reason of crash 
Thu Dec 08 2022 16:35:14 GMT-0500 (Eastern Standard Time) <31224> -- info -- Restarting app Teams with reason crash 
Thu Dec 08 2022 16:35:14 GMT-0500 (Eastern Standard Time) <31224> -- event -- eventpdclevel: 3, appState: 19, status: success, scenario: 3b81ef27-b444-4a43-8440-21ffba5ce8be, scenarioName: desktop_app_quit, name: desktop_app_quit, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 25680598, stepDelta: 0, Scenario.Mode: 1, AppInfo.Language: en-gb, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 26994048, freeMemory: 19914854400, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 1, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: systray, UserInfo.TimeZone: -05:00, vdiMode: 0, Scenario.Name: desktop_app_quit, Scenario.Step: start, Scenario.Status: success,  
Thu Dec 08 2022 16:35:14 GMT-0500 (Eastern Standard Time) <31224> -- info -- Quitting app Teams with session of c073daf4-14e0-c444-02d1-b11078ad6101 and desktop session of desktop-e33a5c47-f70f-4cde-a3c1-982d6f343e51 
Thu Dec 08 2022 16:35:14 GMT-0500 (Eastern Standard Time) <31224> -- info -- Sending IPC to web content: mainWindow for app quitting...

It appears the renderer process crashed, with an exit code -1073741819.

Why is Teams crashing when I share my screen, and more importantly, how can this be fixed?

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Screen sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

62 answers

Sort by: Most helpful
  1. Anonymous
    2023-06-20T16:32:59+00:00

    Today i connected my Samsung Odyssey and had HDR on.
    I was on calls and sharing screen made the app crash.

    After restarting teams, clearing cache, uninstalling and re-installing what worked for me was disabling the HDR.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-06-15T03:13:26+00:00

    True, we always need to make up for the lack of coding skills @ Microsoft.
    I bought a screen exactly for the purpose of HAVING HDR (with a matching graphics card), the monitor alone cost $AUS300 more than the one WITHOUT HDR.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-06-09T14:26:25+00:00

    I am also experiencing this issue. It doesn't happen every time someone shares their screen but probably 1 in 5 times it results in Teams completely crashing. I do not have HDR-enabled monitors and I have removed my USB hub from my computer (noting the finding above) to see if that resolved the issue for me, unfortunately, I am still experiencing this crash.

    I hope Microsoft try and fix this, it looks very unprofessional in work meetings.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-06-09T11:54:53+00:00

    Since sharing a HDR screen crashes Teams; if the crash is not going to be fixed (or will take a while at least), could Teams just not allow us to pick HDR screens from the Share dropdown in the mean time - I'm always scared I'll misclick and crash the call. Thanks

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-06-08T16:43:41+00:00

    Hi All,

    I thought I would share a finding. I have been having this problem, as mentioned in a previous post, for some time Teams meetings crashing when sharing screen and/or video. Even taking out the internet connection. I have resolved my particular issue so thoughts I'd share...

    I use a USB-c multi-port adapter to connect my monitor, ethernet and some USB devices. I've used it for a while now, pretty much always. All along I have used Zoom and other video sharing platforms with little to no perceived impact but Teams meetings were always an issue. I discovered the other day on a Teams call that it worked fine. There was no adaptor connected at the time. Tried various different ways with adaptor not connected and everything worked fine. Tested again with adaptor, call crashed. Tried a different multiport adaptor and everything worked fine. So it would appear the adaptor (Belkin 6 in 1) is either faulty or just can't support it.

    Summary, if you're having this issue with this scenario trying swapping out multiport adaptors.

    Was this answer helpful?

    0 comments No comments