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
    2020-12-10T17:02:01+00:00

    Baked the update 2020-12 KB4592438 into our 20H2 images. It works, no-more BSOD's, finally able to use them without issues. :)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-12-10T16:45:14+00:00

    I think the more interesting question (at least for many of us) would be: Do these computers you set up with v2004 or v20H2 have the 2020-12 W10 CU, KB4592438, that includes the fix?

    If they were patched up to last week, then no, they don't...unless they didhave the optional preview update released 30 Nov, KB4586853, which also includes the fix.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-10T16:18:34+00:00

    Solved for me: see below.

    I had the same issue for one or two domain users. We use a combination of:

    • roaming user profiles (set in the AD user account properties)
    • drive maps (by Group Policy Prefs)
    • home areas set in the AD User Account AND mapped by GPP as above
    • folder redirection
    • DFS (all paths specified in settings above are referenced by DFS i.e. \domain.local\root\blah)
    • CSC / Offline Files turned on for some machines, also EFS encryption for home area where offline files is on

    I deployed some new PCs with latest Windows updates to about 10 users last week and one of the computers blue screened DURING LOGON for the affected user accounts. Did not affect other accounts logging on.

    I noticed the 2 users in question had no roaming profile set and no home areas set in the AD user account. The computer reliably blue screened at login (stop code: RDR_FILE_SYSTEM. What failed: mrxsmb20.sys) whilst processing the Drive Mapping extension of Group Policy Prefs. (I have detailed startup messages turned on, which helps me know where the logon process had got to before blue screening.)

    After entering in the paths for roaming profile and home area in the AD user object, previously empty, the computer no longer blue screened at logon for these users.

    Obvs I haven't found the source of the problem here, but maybe this will help someone else at least figure out where to start troubleshooting.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-09T16:34:46+00:00

    Update on my case that is open with MS. Here is their recent reply to me that I have not yet tested.

    "Good afternoon,

    Thank you so much for your email and also appreciate you have been on top of this case.

    I have been pushing and also checking to get you the best option.

    We got a notification a fix for the issue you are reporting was recently release and we provided a couple of days for testing,

    I would encourage to check the following fix.

    November 30, 2020—KB4586853 (OS Builds 19041.662 and 19042.662) Preview (microsoft.com)

    Basicallly we recommend to proceed to update your unit

    Go to Settings > Update & Security > Windows Update. In the Optional updates availablearea, you’ll find the link to download and install the update.

    If you have already done this, please share your comments letting us know if the issue was resolved.

    Again I apprecaite the opportunity you gave me to help with this case."

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-09T16:33:23+00:00

    Interesting. Learned something new. Thanks!

    We redirect AppData\Roaming, and have a few users that hate change and cling desperately to their beloved IE, so those would be problems. Also have a LOB that requires IE at another site. But it's something to consider.

    Was this answer helpful?

    0 comments