Forum Discussion
Solved
Machine-Wide Teams - White screen and crashing often
Azure Virtual Desktop version of Teams crashes often for staff displaying a white screen. When this occurs, often Edge and sometimes Explorer will also freeze and crash. Teams Machine Wide versio...
our Teams issue got fixed after re-deploying all Win10 AVD hosts in the Host pool from the gold template (we use Nerdio). Our FSlogix was a bit behind and I also installed the latest version 2.9.8440.42104. I doubt FSlogix was the root cause.
Wow interesting experience, thank you for sharing. Certainly is an annoying and tricky issue to pin down.
So to confirm from my recent testing. Excluding cache, disabling GPU acceleration did not help for us either. Monday morning went by fine for our 150 users, then in the afternoon around 2-3pm we started having the random white screen for some users, but not others.
Here is a log we captured on our MS ticket in Feb (which ended up being closed with no resolution). I can confirm we still get the exact same error in our logs now.
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- warning -- ExperienceRenderer: unable to find experience renderer for metadata
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- info -- Middleware:: Action:
{"type":"RENDERER_CRASHED","rendererId":"main-renderer","time":2420977.4839999974}
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- info -- Middleware:: Action:
{"type":"WEBCONTENTS_CRASHED","webContentsId":"1","time":2420977.6998999976}
I am currently spinning up an AMD version of our SH - Standard NV16as v4 (with a GPU and enable GPU acceleration again) to see if that helps by changing the architecture
Previously we have been using - Intel - Standard D16s v5 (no GPU)
Clutching at straws now...
Another note is we have exclusively Surface pro 7/7+/8's as our client devices, not sure if this is a factor, although it really shouldn't be.
Any other suggestions of what I can try would be greatly appreciated.
So to confirm from my recent testing. Excluding cache, disabling GPU acceleration did not help for us either. Monday morning went by fine for our 150 users, then in the afternoon around 2-3pm we started having the random white screen for some users, but not others.
Here is a log we captured on our MS ticket in Feb (which ended up being closed with no resolution). I can confirm we still get the exact same error in our logs now.
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- warning -- ExperienceRenderer: unable to find experience renderer for metadata
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- info -- Middleware:: Action:
{"type":"RENDERER_CRASHED","rendererId":"main-renderer","time":2420977.4839999974}
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- info -- Middleware:: Action:
{"type":"WEBCONTENTS_CRASHED","webContentsId":"1","time":2420977.6998999976}
I am currently spinning up an AMD version of our SH - Standard NV16as v4 (with a GPU and enable GPU acceleration again) to see if that helps by changing the architecture
Previously we have been using - Intel - Standard D16s v5 (no GPU)
Clutching at straws now...
Another note is we have exclusively Surface pro 7/7+/8's as our client devices, not sure if this is a factor, although it really shouldn't be.
Any other suggestions of what I can try would be greatly appreciated.
This is the post I made, about my experience with much more details - if there's any similarities, might be good to follow:
https://learn.microsoft.com/en-us/answers/questions/1274356/teams-white-screen-and-crashing-on-win11-avd-multi?page=1&orderby=Helpful&comment=answer-1244359#newest-answer-comment
https://learn.microsoft.com/en-us/answers/questions/1274356/teams-white-screen-and-crashing-on-win11-avd-multi?page=1&orderby=Helpful&comment=answer-1244359#newest-answer-comment