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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-09-02T10:10:16+00:00

    I'm experiencing the same issue, although not as badly as I can log in with BSOD.  My issue occurs when connecting my VPN and then at a random point soon after I get the BSOD.  We use Offline Files for our profiles and therefore can't realistically disable it.

    I was able to log a paid support incident for the issue and Microsoft confirmed this is a known issue, although it's not documented anywhere.  The only fixes are to roll back to 1909 or disable Offline Files.  As I'm past my 10 day rollback period this is a real pita 😡

    As this has been going on for some time, I find it somewhat rediculous that Microsoft don't have a fix for this or at least have it documented and based on other threads it may only be fixed by going to the next version of Windows...

    Nick

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-30T23:14:04+00:00

    I too have a similar issue. I did post here an hour ago thinking I had a workaround. This turned out to be a fail in the end.

    Below is my post from this topic "BSOD stop code on Windows 10 start (RDR File System - mxrsmb20.sys) after installing Synology 218+" https://answers.microsoft.com/en-us/windows/forum/all/bsod-stop-code-on-windows-10-start-rdr-file-system/6e2bafea-8ad8-4372-9ca1-e84203999405?page=1 which could be of some use.

    I too have a Synology (DS916+) which I offload excess data for Domain users which hoard too many files. I thought it was this "rdr_file_system 0x27 BSOD After Windows 10 2004 update, but only on domain profiles" from here https://answers.microsoft.com/en-us/windows/forum/all/rdrfilesystem-0x27-bsod-after-windows-10-2004/c34f5703-1367-4788-a4f3-2d75f7dfaa07?page=1 which sadly it is not.

    I offline these files on the Synology for some users who insist having access to everything. I also offline their My Documents which is being redirected to my Server 2016 Domain Controller (and for some to a crusty old SBS2008 that is waiting to be decommissioned).

    Formatting the CSC cache to zero the state and only making My Documents offline does not produce the BSOD. Adding the Synology target back as well does make it BSOD. I would guess then there is something broken when trying to spin up Offline Files that come from the Synology. I did initially get a strange error on one machine I configured last week implying a security mismatch of sorts related to the Synology location which I dismissed and failed to take complete note of what it was describing.

    The Synology is up-to-date.

    The Windows machines that fail are build 2004 and are up to date.

    Entering user credentials to start the logon process will create the BSOD once the authentication process starts.

    This does not occur if the offending WIN10 machines are connected to the Domain network and the Synology hosted files are deemed Online.

    I read that giving the Windows machines ANY network to access will allow successful login; I got only so far with that suggestion but cannot fully say that is a viable workaround as it seems to me the files made offline from the Synology are broken somehow. When I "fix" this issue the BSOD returns. I tried installing the Microsoft Loopback adapter to fake an always connected network but that trick broke once I "fixed" the offline file issue with data made offline from the Synology.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2020-08-25T22:52:00+00:00

    Same problem here.

    No problem if I disable offline files but that is no option.

    No problem when I login with a local account - but BSOD when I login with my domain account.

    We use domain namespaces (DFS) - I don't know if this is part of the problem.

    I had no other choice than uninstalling the 2004 build....

    Any help would be appreciated!

    Luc Dierick

    My BSODs returned so I did a bit more troubleshooting.  It seems that in my case at least, the offline files and caching were not enough to trigger the BSOD but if I mapped as a drive the network share that has offline files and caching enabled, then the BSOD happens on the next reboot.  Again, if after rebooting I log onto the machine with a local account first, then log off and then come back in using my domain account, I have no issues.  Go figure.  The August updates did not rectify the problem so I've put any feature updates on hold for 365 days hoping that Microsoft will address the issue before that expires.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-22T12:44:33+00:00

    Same problem here with my Surface Laptop 3.

    Was this answer helpful?

    0 comments