Share via

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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-10T13:16:34+00:00

    @LYoungESP: That's consistent with Offline Files having offlined the share. By using a "server name" for which Offline Files doesn't have anything cached, you regain access. I think that's what I'm seeing with my DFS shares, too.

    There's a Microsoft script, CSCtransition.vbs, that lets you force a share online. Next time I visit my affected site I want to see if it helps (or causes blue-screens). If it helps, that's a much better workaround than accessing the same data through a different route. As soon as CSC caches data from the alternate UNC, it will likely start offlining it the same way.

    This is where the script is documented: https://support.microsoft.com/en-us/help/2610379/the-folder-redirection-policy-does-not-work-if-a-previous-user-sets-a

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-10T10:06:08+00:00

    We've been able to re-enable Offline Files.

    We had this problem with 4 of 10 v2004 PCs. With one, the user could log on without BSOD'ing but it would BSOD upon browsing a network drive. The rest BSOD'd during logon until I disabled Offline Files via remote registry edit. The other 6 are getting along just fine so far.

    In all 4 cases, we've worked around it by resetting Offline Files (create a FormatDatabase DWORD value set to 1 in HKLM\System\CurrentControlSet\Services\CSC\Parameters, re-enable Offline Files service and reboot the computer). Then the users can log on with Offline Files enabled.

    However, the mapped drive (which maps to a DFS share, if that's relevant) is inaccessible after logon. The workaround for that has been to add a logon script that unmaps the drive, then remaps it to the non-DFS share. Initially, only the redirected folder share (also DFS) is browsable. Later, the rest of the DFS shares become browseable, perhaps after they're onlined by Offline Files.

    Small sample size. Don't know how universal this workaround is, but hope it helps somebody!

    Thanks for this tip, I've just managed to re-enable offline files on one of my PCs by following this. Weirdly though, File Explorer won't resolve the name of the device where the share is hosted - I can ping it by name and I can access other shares by name, but I've had to change my shortcuts to use the IP address instead.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-10T09:00:07+00:00

    I can read every message, but yes, problem with domain login when at home, doesn't matter connected or not (there is no domain)

    Offline files is enabled, but I left it enabled.

    What I noticed this far, when changing from a Office domain connected environment to a home not connected environment at startup and strangely other way around also, so maybe that is caused from wireless to wired. I've this BSOD.

    I created simple local account (of course without offline files), before changing environment or after blue screen (BSOD), I login to this local account first, logout and login to domain account. Problem gone.

    Now my question : Can I create something in maybe task scheduler, which does this job for me before login?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-09T21:51:10+00:00

    Interesting, René. 

    It looks like your observation is that the problem occurs when the computer switches between offline and online mode; is that correct? So you're trying to keep it...offline? Or online?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-09-09T20:10:08+00:00

    We have same issue on serveral updated Windows 10 Pro 2004 Systems when domain user logging on with offline files activated.

    A reset of the CSC cache has not helped permanently.

    The following policy entry has at least fixed for us the bluescreen

    rdr_file_system 0x27 BSOD

    when in Airplane mode and/or not connected to any network during domainlogon in conjunction with reset of CSC Cache Folder, but reset was not on all devices needed.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetCache]

    "GoOfflineAction"=dword:00000000

    "SlowLinkEnabled"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetCache\SlowLinkParams]

    "*"="Latency=8"

    The point is that the latencycheck for going offline will be here lowered down from higher standardsettings and set to 8ms (Tested with LAN and WLAN connection to Server to avoid red cross on drive for offline share connection when connection comes back) and we have tested this sucessfully with no bluescreens now since several days on affected systems

    Link to Microsoft article where usage is described:

    https://docs.microsoft.com/en-us/windows-server/storage/folder-redirection/enable-always-offline

    Was this answer helpful?

    0 comments