A customer of ours is experiencing the same issue at this moment. By disabling the "offline files" function through control panel on the client fixed the BSOD issue during the logon process.
rdr_file_system 0x27 BSOD After Windows 10 2004 update, but only on domain profiles
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Good morning, I am having an issue on some PCs recently after some PCs received the Windows 10 2004 build update. After receiving said update, the machines will BSOD with a 0x027 error code when logging into a domain profile while connected to the network.
If I remove the network cable from the PC and log into a domain account that was cached on the machine before the update, it will log in without issues and then I can connect it to the network and it seems to resume function. I can also sign into a local account on the machine, with and without network connectivity.
I used Bluescreen View to look at the dumps which seem to be showing rdbss.sys and mrxsmb20.sys as drivers that are causing the issue. I have tried updating network drivers etc from the vendors websites and not relying on Windows to, but am still having the issue.
The other bizarre thing is if the PC crashes 3 times, boots into the recovery mode to try and repair your PC and I restart it, it will then log in once to a domain account and seem to be functioning, however if the PC is restarted it will BSOD on log in.
Has anyone seen or heard of any issues like this since this update? Could it be something out dated on the server that is causing the issue to happen to the machines on the newer OS? I can't help but feel like it has something to do with folder redirection and that is why cached accounts will work with no network connection however I am stumped how to get around this other than not updating every other machine, and rolling back if possible (I had a PC that was upgraded from Windows 7 to 10 and went straight to the 2004 build and BSOD'd, I tried to roll back to Win7 and system will not boot at the moment saying it is missing system files etc.).
I have some mini dumps I can share if that would help as I would like to get to the bottom of this if possible.
Windows for home | Windows 10 | Performance and system failures
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.
167 answers
Sort by: Newest
-
Anonymous
2020-07-01T12:22:41+00:00 -
Anonymous
2020-06-30T11:52:33+00:00 Same misbehaviour here - I got Folder Redirection & Offline Files and I get a BSOD when the network drives are not available after successfully signing on Win 10 2004.
Fix?
-
Anonymous
2020-06-29T17:53:05+00:00 I got a chance to perform some more in-depth analysis of the network types that work and do not work and also verify the workaround presented by user PhilippZeile.
The issue of course occurs if you are using offline files/folder redirection. If you are not connected to a network that will allow offline sync the computer will bsod immediately after initial sign-in. Connecting via wired or wifi connection will bypass the issue, so long as you are connected to a network that can offline sync, including pre-sign in VPN. Connecting to any other network will still fail. The issue therefore appears to be prompted by a failure to be able to offline sync.
The workaround presented by PhilippZeile will work if you are unable to access a valid network: sign-in as a local user, then sign out and your normal user account will work properly whether you are on the network or not.
I'm checking whether completing a full offline sync resolves this issue. I'm hoping so, because this issue has seemed to occur more for existing users getting emplacement computer (and therefore having more offline files to sync) vs new users that have nothing to sync.
EDIT: completing a full offline intial sync does not help, so the only workarounds are to be connected to a sync-capable network or first logging in with a local account.
-
Anonymous
2020-06-28T00:52:25+00:00 This issues seemed to occur for any computers relying on user profile redirection that were updated to the Win10 2004 update. If the computer is booted with no network connectivity, upon sign-in the computer bluescreen's, giving an error referencing mrxsmb20.sys and rdr_file_system.
I found that if you connect to a network before sign-in the issue does not occur. I connected via wired connection. I am not sure if connecting via WIFI would also work. I am likewise not certain if you are required to actually connect to the network that actually allows profile redirection or if it can just be ANY network. The first time I wired into the redirection network and then could not get the issue to reoccur afterward, so I am not certain on the network type requirements at all.
It seems like you only need to do this once because I could not replicate the issue afterward.
I have the identical problem. While signing into AD Network, with NO Network Connection at all, i get a BSOD immediately after logon.
However, if i connect to ANY network (Wifi, Hotspot, etc.) it logs on fine, with cached credentials, and NO BSOD.
I can disable LAN, reboot, and replicate the problem every time, and have yet to figure it out. Only started this problem after updating to 2004
-
Anonymous
2020-06-26T19:48:11+00:00 I have the problem also on my own Notebook. When i work in Home Office it appers on any Connection. When i work in my Office there ist no Problem.
My Work around for Home Office is in the Moment that i us my Local Admin Acxount for the first login. Than i can log off and Log in to my Domain Account wirh no Problems.