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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-09-29T12:26:43+00:00

    Is there any reaction from Microsoft. We have a reproduceable bug in windows10 2004 in domain networks.

    Even after a complete new install of a Notebook w/wo producer drivers we can 100% force the bsod if there are offline files active and there is no network connection to the domain network. I discovered:

    1. If there is a Network connection to domain - works fine, no bsod
    2. Network connection to another network - user can login but after some seconds bsod
    3. No network connection: bsod immediately when loging in.

    MS please solve this problem!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-29T13:21:51+00:00

    So far the only option in my environment is to rollback to to 1909, but now after we rollback we are getting a DLL error with some applications including Adobe:

    C:\windows\system32\msvcp140.dll is either not designed to run on Windows or it contains an error. Error status 0x000012f

    has anyone gotten this? any suggestions?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-10-05T11:17:51+00:00

    Tip is to try this that seem to have helped. (havent had any test case yet though) 

    https://www.reddit.com/r/sysadmin/comments/ipno8v/windows_10_x64_2004_19041450_offline_files_bug/g57vn0s/?context=3

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-05T13:08:36+00:00

    Yes, it seem's to work 💪

    I hope it will work well in next few days...

    I will tell you in next days.

    Thanks!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-05T18:24:34+00:00

    I checked on one of the affected computers and it already had the registry DWORD "ProviderFlags" and it was already set to 1.

    In my case, I tried logging in with no network and didn't get the BSOD, then restarted and plugged in the network and logged in before the network was ready and got the BSOD.

    Was this answer helpful?

    0 comments