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-08T20:55:50+00:00

    I installed December set of patches on one pilot computer (that was certainly crashing before) - and problem seems to disappeared. It will require some further testing. It was tested on Widnows 10 v. 2003 (H1).

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-12-07T08:47:07+00:00

    Hi,

    I've installed KB4586853 today and it seems to have resolved the issue.

    I can now build, capture and deploy a Windows 10 Education x64 20H2 image with all my GPOs (including mapped drives and enabling offline files) in place.

    Thanks,

    Matt

    A BIG THANK YOU to @mattcourtman for making me aware of this patch:

    After installation of KB4586853BSOD has disappeared on both of my laptops - Halleluja!

    Let's hope it survives the next patch day ...

    For the record: I'm not in an enterprise environment, just syncing (a lot of) data from a NAS to my laptops. Had a BSOD since update from 1903 to 2004 (old laptop), right from the start (with 2004) on a brand new laptop, resp.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-03T12:23:48+00:00

    Patch installed but issue still exists here,

    as soon as i remap drive with offline files enabled (CSC) instant blue screen.

    edit: enabling provider flag 1 has allowed me to map and not bluescreen. I had to manually make the entries in registry and then map drive.

    Heres what i used to map my H:\

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Network\H]

    "RemotePath"="\\INSERTDOMAINNAMEDFS\restricted\users\philcowg"

    "UserName"=""

    "ProviderName"="Microsoft Windows Network"

    "ProviderType"=dword:00020000

    "ConnectionType"=dword:00000001

    "ProviderFlags"=dword:00000001

    "ConnectFlags"=dword:00000000

    "DeferFlags"=dword:00000004

    WHere im still confused is i thought this enabled smb v1 but when i run

    PS C:\WINDOWS\system32> Get-SmbConnection

    none of my results show connections over smb1

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-01T20:18:47+00:00

    Yes, the commonality to all the scenarios here is Offline Files, and logon as the trigger.

    Which makes me wonder why, if this really is The Fix, the changelog doesn't simply say "Logon to computer with files in CSC causes 0x27 stop error." Instead, it goes off on a security context tangent that appears to be irrelevant. Most of us are logging on using domain credentials on domain members with CSC content from remote domain members.

    Time will tell, I guess.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-01T19:50:53+00:00

    There is a discussion running on which combinations are causing the problem.

    I made a simple test case. I installed a clean machine (HP EliteBook), Win 10 2020 H2, latest updates (November set). I connected a machine to peer-to-peer network, made a drive mapping (manual, no GPO) and made one folder with few small files offline (1 MB approx.).

    I made a reboot - and BSOD was there.

    So it is easy to replicate the problem.

    Martin Beran

    Was this answer helpful?

    0 comments