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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-16T11:32:30+00:00

    ... but are you able to log in via RDP? ...

    I can log into my computer from my laptop with RDP. The reverse is also possible. There never was a BSOD.

    In my estimation, the error occurs when offlinefiles are activated and configured and/or when a network component requires SMB1 and the firewall is blocking the old Netbios ports.

    At least it helped on my local network:

    • ProviderFlags DWORD 32Bit to 1 for each individual share in "HKEY_CURRENT_USER \ Network"
    • In the private network of the Windows firewall, release ports 137-139, 445 for NetBios and SMB, TCP and UDP incoming and outgoing.

    In my opinion there must be a bug in the timing with SMB1 and the login, in which a module of the RDR_FILE_SYSTEM, with deactivated SMB1 then when processing mrxsmb20.sys and with activated SMB1 then when processing mrxsmb10.sys, the BSOD triggers the user login.

    In the end, only Microsoft itself will know where the trouble is and at some point there will be a small fix in the major updates ...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-16T10:57:30+00:00

    Morning,

    Same problem here, BOD continues in machines. 

    Please microsoft Fix this with one update.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-16T06:44:16+00:00

    Ive been getting lots of calls from clients having temp profile login and roaming profiles breaking. Had to rebuild several accounts so far.

    Was 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-13T08:41:52+00:00

    ... it already had the registry DWORD "ProviderFlags" and it was already set to 1. ...

    In addition to setting the ProviderFlags, it seems to me that the following setting in the Windows firewall is necessary:

    Enable ports 137, 138, 139 and 445 in the private network in the Windows firewall.

    Since then, the BSOD has disappeared when I log into the local network with the use of offline files, regardless of whether my old faithful Buffalo is on or off.

    Tested on two systems (HP ProDesk and Lenovo Notebook, with a Buffalo LS-WSXL in a workgroup).

    Was this answer helpful?

    0 comments