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-09T09:44:10+00:00

    Hi 

    The same problem. I hope Microsoft will fix ASAP.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-09T07:25:12+00:00

    Hi,

    i googled a lot and found nothing. You seem to be the only one who was able to solve this problem without switching off offline files.

    Could you please discribe your solution a little more  in detail.

    Is your Groupe Policy the one of your netzwork or the one of the computer. How is the correct title of the groupe policy you changed. In which folder can i find the policy?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-08T16:19:12+00:00

    We've been able to re-enable Offline Files.

    We had this problem with 4 of 10 v2004 PCs. With one, the user could log on without BSOD'ing but it would BSOD upon browsing a network drive. The rest BSOD'd during logon until I disabled Offline Files via remote registry edit. The other 6 are getting along just fine so far.

    In all 4 cases, we've worked around it by resetting Offline Files (create a FormatDatabase DWORD value set to 1 in HKLM\System\CurrentControlSet\Services\CSC\Parameters, re-enable Offline Files service and reboot the computer). Then the users can log on with Offline Files enabled.

    However, the mapped drive (which maps to a DFS share, if that's relevant) is inaccessible after logon. The workaround for that has been to add a logon script that unmaps the drive, then remaps it to the non-DFS share. Initially, only the redirected folder share (also DFS) is browsable. Later, the rest of the DFS shares become browseable, perhaps after they're onlined by Offline Files.

    Small sample size. Don't know how universal this workaround is, but hope it helps somebody!

    [22 Sep 2020 update] The first computer I tried this workaround on had the same BSOD at logon today. So clearing the cache is not a permanent fix, as others here have since said. I've now disabled Offline Files on desktops.[sigh] On laptops, will have to continue clearing the cache for now. At least it buys a few weeks.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-09-04T20:29:09+00:00

    Same issue here

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-09-04T07:35:42+00:00

    we have the same problem in dozens of customer environments. RDR_FILE_SYSTEM when they login outside of office....hopefully Microsoft will fix this in the next update

    Was this answer helpful?

    0 comments