Forum Discussion
Machine-Wide Teams - White screen and crashing often
- May 04, 2023
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.
We have worked on a Microsoft support ticket for this and essentially went nowhere so any help you or anyone can provide would be much appreciated. Troubleshooting info etc
I'm using FSLogix 2.9.8440.42104 with Teams 64-bit machine-wide install version 1.6.0.6754. (I also used an earlier version of FSLogix and Teams prior, same issue).
I also disable GPU acceleration and excluded Teams cache using the redirections.xml, following the guide here: https://techcommunity.microsoft.com/t5/azure-virtual-desktop/wvd-fslogix-reduce-profile-container-size-exclude-teams-cache/m-p/1503683 (The GPU and Teams cache exclusions did not help).
The weird thing I've noticed is if I log into a Win11 AVD host, Teams will launch fine. As soon as I login to that same host as the 2nd test user and Teams opens, it will display the teams app info normally for about 5 seconds, then white screen. If I quit and re-open Teams, that does not fix it either. If I do the reverse and login with my test user 1st, Teams opens just fine and as soon as I login with the 2nd user is when Teams white screens.
Luckily I'm just testing and we have no users in this environment. I feel your pain though, I probably spent 10+ hours troubleshooting this, spinning up new VMs, re-installing Teams, FSLogix, Recreating FSLogix user profiles, no dice.
- PaulStirlingMay 01, 2023Iron ContributorWow 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.- jmccracken112112May 02, 2023Copper ContributorThis 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 - jmccracken112112May 02, 2023Copper Contributor
PaulStirling I wish you the best of luck with the architecture change. I also saw a forum post about problems with v5 hosts and the solution is to use v4, but that is about a year old now.
I'm use Standard B2s VM size, which shows as a v2 gen architecture, so I'm puzzled as to what's happening.
Just curious, what is your authentication method for the FSLogix profiles? We're cloud-only, so in order to use FSLogix profiles, I needed to spin up an Azure AD DS resource so Azure-AD objects sync back to the Azure AD DS domain in order to properly authenticate to the Azure file share (What a mess this is), but yeah just curious if you're using an on-premise DC with ADConnect or doing what I'm doing. Maybe something here can help us connect the dots.- PaulStirlingMay 02, 2023Iron ContributorHi jmc,
We are using onprem domain joined SH. FSlogix profiles are in azure using a storage account.
Onprem DC using AD connect, however we have a DC in azure which AVD is set to prefer for latency reasons.
The V5 vs v4 suggestion is something we saw yesterday which makes a lot of sense. We ran 3x v4 SH yesterday along with our 12x V5 SH, no apparent white screen issue on the V4 (could be dumb luck). So overnight I switched all our SH to v4. I hope to assess the results in the next couple of days.
To me it is starting to make some sense IF this v4 sorts the issue. For the mere fact it has temp storage and a large page file. Where as the v5 did not. That's interesting because we had users complain from time they would get 'low memory' pop ups on edge just before edge crash and teams white screen. Despite the 'free' RAM being 20% or so on the VM.
This along with the fact we usually got the white screens in the afternoons. Which COULD be the RAM was getting overloaded over time and thus crashing RAM heavy applications such as edge and Teams.
All still a theory but we did find the v4 seems to manage RAM allocation better and has a large pagefile (35gb) humming away on the temp drive.
I will report by the end of the week if the issues suddenly disappear.
thanks again for your help.