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-18T20:13:57+00:00

    I don't know if this has been posted, but someone on reddit has a possible solution. It worked for us.

    This fix is for domain computers with offline files. 

    -on the users account open regedit

    -go to Computer\HKEY_CURRENT_USER\Network

    -you will see all of the mapped drives

    • on each drive create a new DWORD
    • Name it: ProviderFlags
    • Set it to 1

    -Then log out of the user account, disconnect from network, and have user log in to test.

    This enables SMBv1 on client for those drives and we no longer get bluescreen on login.

    Our file server is server 2016 with SMBv1 disabled, so this makes no sense at all, yet it fixes the bluescreen for all our 2004-builds...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-12-09T13:46:54+00:00

    Hello everybody,

    Today I installed kb4592438 and gave it a new try with activating offline files.

    So far no BSOD.

    Greetings from Germany,

    Torsten

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-11-13T15:06:27+00:00

    I have a fresh install of 2004 and ran all updates recently - still had the issue.

    I installed KB5846781 today and all good so far...

    A search for KB5846781 comes up with no results.  Can you double check that and/or provide a link please?

    We are experiencing this problem with both Win10 v2004 (aka build 19041) and v20H2 (19042).  We only have/had our laptop OU running Offline Files.  Disabling offline files 'fixes' it, but that's not really a solution when your end users are used to it (and didn't even know it was happening until it broke).  

    Unfortunately setting the Policy 'Allow or Disallow use of the Offline Files feature' to Disabled (Computer Configuration > Administrative Templates > Network > **Offline Files)**and setting Offline Settings of the file server share to 'No files or programs from the shared folder are available offline' did NOT disable Offline Files on the affected devices/users.  Had to sign in as them and disable Offline Files in the Sync Center...then they were OK when off the domain network.  New users logging onto affected devices are good now - Offline Files disabled by default.

    Question to self: Being stuck in this spot, do I also disable file redirection or not?  Either way, now the end users need educated on new behavior.

    Question to MS: Why has this not gotten a true fix yet?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-13T15:18:25+00:00

    Not sure if someone has mentioned this before, but are you able to log in via RDP? We have had this issue with some of our users, and it's been real hit or miss, and then it dawned on me: with all the working from home due to covid, a lot of our users are using RDP to connect to their PCs in the office. So, I decided to test this theory. I am in the office, and when I try to log in at the PC, it blue screens repeatedly. But if I RDP in via another computer, I am able to log in. Then, at the PC I can login to that session, thus terminating the remote connection, and remain logged in with no blue screen.

    I know this isn't a fix, but if other people can replicate it, maybe it will help us get a better grasp on what's going on.

    Can anyone else confirm this works for them?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-10-06T12:46:09+00:00

    In precision : Create the registry DWORD "ProviderFlags" and set it to 1 for each offline-synced network drive (a letter) under HKEY_CURRENT_USER\Network (this enables SMBv1 on client for those drives)! Check which drive is synced/connected!

    See also https://www.winhelponline.com/blog/mapped-network-drives-fix-windows-10-v2004/

    jPNRgc

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments