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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-02-05T15:14:26+00:00

    Anyone have a solution for this ?

    it's really an issue that i can not use offline files anymore

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-01-22T15:14:10+00:00

    It's interesting that the drive map problems are also tied to use of redirects & offline files. The mapped drive problem happened before and after the December CU. Perhaps MS wasn't aware of the drive map issue and focused only on the BSOD. Not sure where that leaves us; maybe I'll have to try the SMBv1 hack.

    What's weird to me is that I have one site where every2004/20H2 computer has BSOD & drive map issues, and others without a single 0x27 BSOD or drive map failure.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-18T20:35:38+00:00

    Yes, this solution has already been mentioned. But it is not completely satisfactory because problems persist.

    For me, since KB4586853 fix, I haven't encountered the Blue Screen of Death again.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-18T14:28:49+00:00

    I updated with KB4592438, no BSOD, but the map drive also stop working. Does anyone have this issue? or any solution?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-11T06:57:39+00:00

    Hello all,

    I wanted to test the patch today and see if the problem still occurs in our company.

    In the meantime we also had an adjustment to the mapped network drives.

    Our employees had a user drive pointing to Userhome$.But this was now changed to a share with userhome without $.

    Since then I have not been able to generate a BSOD when log in offline.

    Was this answer helpful?

    0 comments