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

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.

:)

 

Please help with RDR_FILE_SYSTEM (0x27) on Windows 10 during RDP

While connected over RDP (Remote Desktop Connection) and transferring files to the server, I've experienced the RDR_FILE_SYSTEM (0x27) BSOD. This just started happening now, the server was upgraded to Windows 10 several months ago and did not experience
this until now. It even crashed while being connected over RDP when no file transfer was being performed.

I ran memtest86 for 24 hours straight (5 full passes) and no errors were found.

I'm posting a link to several minidumps, all of which show RDR_FILE_SYSTEM BSODs during a file transfer except for the last 122316-45328-01 dump and accompanying memory.dmp that happened without a file transfer:

OneDrive

I'd really like some insight into what might be wrong.

Thanks.

 

Migrate Locale Profile to Domain

I removed my reply because watching those instructions on TechNet I started wondering if they really work with Windows 10.

Anyway, whatever you try create first a dummy profile, customize it a bit and move it to domain. If everything works, you can then move real profiles.

 

RDR_FILE_SYSTEM BSOD on specific model of PC?

We are using Windows 10 LTSB 2016 on some PCs in our organisation (the rest are still on Windows 7).

The majority of these do not have any issues but we have noticed that on one particular model of PC, users are sometimes getting an RDR_FILE_SYSTEM BSOD when accessing their network drive area.

I've collected the dump files from the most recent of these - a zipped copy of these can be found on OneDrive at https://1drv.ms/u/s!Aidjz33-lg04kGbCwwVWxG0mDv4g - can anyone suggest what might be causing the issue?

Thanks,

Dan Jackson (Senior ITServices Technician)

Long Road Sixth Form College

Cambridge, UK.