rdr_file_system 0x27 BSOD After Windows 10 2004 update, but only on domain profiles

Anonymous
2020-06-08T14:50:36+00:00

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.

0 comments

167 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-05T02:58:57+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.

    I've found, no matter the sync amount, I still get a BSOD on sign on. However, if I'm connected to ANY network, phone hotspot, public WIFI, etc., it will NOT BSOD. My issue only happens when i have absolutely no network connectivity what so ever, upon network logon. 

    I may try the Insider Ring to see if it fixes the issue

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-05T23:39:57+00:00

    I upgraded one of the machines I have to Build 20161 and looked like it worked but only allowed me to login once.

    I did update all the systems drivers along with antivirus and still continued to get BSOD's.

    Uninstalled AVG and still had issue.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-13T00:16:14+00:00

    Any update from Microsoft? Maybe a fix coming?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-13T10:34:22+00:00

    I have the same problem. I have tried everything I have found on the Internet so far. But it was not successful.

    Only when I deactivate offline files, I have no BSoD.

    Does anybody have an idea?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-07-15T06:00:57+00:00

    I'm now installing:

    2020-07 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4565503)

    2020-07 Servicing Stack Update für Windows 10 Version 2004 für x64-basierte Systeme (KB4566785)

    I will reply, in case something changes.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments