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-07-26T16:07:59+00:00

    If you have the problem "log on is only possible with an active network connection to your domain" the following worked for me.

    Workaround:

    You need one local account not in the network domain and of course no offline files connected for this account

    If you have the local account created and you are now NOT connected to the domain or a network

    • start the PC
    • logon with the local account, for me it is my local admin account.
    • wait until the start up has finished
    • go to the Windows Logo in the taskbar and right click with the mouse
    • select the "Shutdown or Log Off" menu (I have a German version if the translated wording in different for you :-))
    • LOG OFF from the local account
    • LOG ON with your domain account and I, hopefully you are also, do not run into the BSOD and can work with the synchonized files.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-07-27T06:54:25+00:00

    I just wanted to add my experience of this - I use 3 or 4 machines which are updated to build 2004, both domain and standalone, with different folder redirections synced. I've only had the BSOD at login on one desktop PC so far, and I'm not sure why this one would be affected while the others aren't. Thanks to this thread I managed to get round the fault by going into safe mode and disabling offline file sync in the registry. As this is a desktop machine there isn't any real problem doing this, as I don't need these files outside the office.

    As a domain user I don't have the local admin password to try that workaround, but before getting into safe mode using my cached domain credentials, I got the BSOD whether I was connected to the LAN or not. Also, I am not sure how long after installing 2004 the fault appeared (the PC was switched off for a couple of weeks), but it wasn't immediate - suggesting an update is responsible.

    I hope MS are taking note of this and working on a fix...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-27T08:23:34+00:00

    Hi,

    Please disregard this update, problem is back, took a while before the BSOD appeared. Sorry,

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-27T21:59:19+00:00

    Seems kinda crazy that you would have to stand up a new server running 2019 when 2012 R2 still supported and sure still used by a lot of shops.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-07-28T07:58:33+00:00

    I have Server 2019 as file and dfs server and i still have the problem.

    Was this answer helpful?

    0 comments