rdr_file_system 0x27 BSOD After Windows 10 2004 update, but only on domain profiles

Anonymous

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.

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

Anonymous

2020-07-15T11:24:02+00:00

Same issue even after installing the following updates.

2020-07 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4565503)

2020-07 Servicing Stack Update für Windows 10 Version 2004 für x64-basierte Systeme (KB4566785)
Was this answer helpful?

0 comments No comments
Anonymous

2020-07-15T21:14:04+00:00

I am still having the exact same problem, even after installing the two updates released today (KB4565503 & KB4566785).

I don't have much to add other than the following:

The server that the redirected folders reside on is rather old, running Windows Server 2003.

Also, on the offending computers, I notice a NETLOGON error in the event viewer. Details are:

Event ID 5719

This computer was not able to set up a secure session with a domain controller in domain XXXXXXX due to the following:

We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.

ADDITIONAL INFO

If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

I have no idea if these are related or not, but it seems like too much of a coincidence. The domain controllers are up and available, and applications that use AD authentication work just fine, however offline files remain disconnected, and network shares are disconnected as well. However, using an IP address in the UNC will allow them to authenticate and connect.

Computers still running build 1909 are completely unaffected, and rolling back to 1909 fixes the problem, as stated before. Luckily I have a few computers I don't desperately need to roll back that I can play with at least up until the rollback window expires (I bumped it out to 30 days), if anyone has any ideas.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Anonymous

2020-07-16T08:03:13+00:00

I have the same problem with a HP Zbook 15 G1 in a workgroup, the blue screen appear the moment I logon without a network connection. If I turn my network connection on in my home office, there is no problem at all.... only sometimes it will give a BSOD when I start her up, but the next start-up will be without a problem.

When I am outside my home office and I connect to a "strange network" I can logon, but after a short time it will crash with a BSOD. (probably the point when she start to sync....) Disable offline folders solve the problem.... but I need offline folders badly... :( I think the only thing we can do is waiting till someone from MS or HP comes with a patch.... We need a fix for this issue...!
Was this answer helpful?

0 comments No comments
Anonymous

2020-07-17T07:06:59+00:00

I have same problem with a Surface Go 2 Business. The bluescreen appears directly after login without connection to my network.

Unfortunately I noticed it too late, it's a new surface I've installed an updated to 2004 (deleted the old version) and have all installed and configured. All was working fine. The next time I was a few days out of my office I was not able to work because of the bluescreen at logon. Back on my office, all is working fine on my business network.

I hope Microsoft release the fix soon.
Was this answer helpful?

0 comments No comments