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-11-17T18:59:39+00:00

    Removing the drive letter mapping to networks hare indeed resolves the issue. 

    I got it working by entering safe mode with no network functions enabled and remove the drive map and reboot. 

    Before I remove drive mappings: Can anyone comment if this requires rebuilding the whole offline cache? What happens to programs that have been configured to use drive letters (eg. to config files, or paths to music in iTunes)? Will they work with UNC paths just like this?

    I just spent a full day on restoring my ~700GB offline cache and would be glad if I didn't have to do it again ...

    Just as additional datapoint here is my configuration and observations:

    • In all my systems I redirected the CSC location from C:\Windows to D:\
    • BSOD occured

        on (old) Lenovo L520 and brandnew Lenovo L15 - both on Win10 2004

        if a certain amount of synchronized files on share X:\ consist of *.lnk files referring to files located on share Y:\

        when booting without a (W)LAN connection to the NAS hosting the shares

    • BSOD did not occur

        never on L520 with Win7 and Win10 1903 (I skipped 1909, being forced into 2004)

        if I manually delete all target files of the said *.lnk's from the Manage Offline files > View Offline files

           (impractical as a solution as *.lnk's are all over the place in all the shares I want to synchronize)

        after switching the method of redirection of CSC from via registry key (CacheLocation) to via symlink-- but only with a smaller set of offline files (including *lnk's). Error returned after full size of ~800GB got sync'ed.

    FWIW: I have KB4586781 installed.

    In a way my desperation has subsided to a "me too" after reading ths thread :-\

    Seems I'm not alone out there and there is some hope that CSC will continue to live (again) ....

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-11-16T13:43:17+00:00

    Are there any other fixes to get people logged in?  I have a few users that are pretty much stuck.  They boot up, try to log in, and then blue screen.  They do this over and over with the same results.  Turning off Wifi doesn't seem to help.

    I'm ticked off though.  I've had this frickin update since it's been out.  As soon as I roll it out to my small IT dept to help test, I run into the issue.  People are mad because they can't get anything done.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-16T10:12:48+00:00

    Is there are available "Official" Microsoft statement visible somewhere on the issue, and when a fix will be released, or what the KB is / will be?

    I've read somewhere that this is due 3rd week of Nov, today is monday of the third full week of Nov - is the patch coming?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-15T18:18:01+00:00

    So far I kept policy to delay upgrades for 180 days. Obviously this is not sufficient do to MS ignoring problems.

    Why do they have insider testing and diagnostic reporting if they completely ignore the feedback?

    Idiots. And on the top of everything - this problem seems to be too easy to reproduce.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-11-15T12:12:24+00:00

    Removing the drive letter mapping to networks hare indeed resolves the issue. 

    I got it working by entering safe mode with no network functions enabled and remove the drive map and reboot.

    Was this answer helpful?

    0 comments