Rdr File System 0x27 Rdbss Sys
RDR_FILE_SYSTEM (0x27) usually points to the Windows redirector stack, often rdbss.sys, a file-share or Offline Files path, or a bad storage or network filter, not a generic RAM fault. Misreading it can send you after the wrong driver, waste outage time, and miss a repeat crash on domain or SMB clients. This guide shows how to separate redirector failures, Offline Files issues, update regressions, and real corruption before you apply fixes.
What RDR_FILE_SYSTEM 0x27 means
RDR_FILE_SYSTEM is bug check 0x00000027. Microsoft says it points to a problem in the SMB redirector file system, so the crash often appears when Windows is reaching a file share, processing a domain logon, or handling cached network files. The named driver, rdbss.sys, is usually the crash surface, not proof of the original fault. (Microsoft Learn)

That distinction matters. A blue screen that names rdbss.sys can come from redirector activity, Offline Files, folder redirection, a recent update, a filter driver, or, less often, broader corruption. The first clue is where the crash happens, not just which file appears in the dump.
Why Windows names rdbss.sys in the crash
rdbss.sys is the Redirected Drive Buffering SubSystem driver. It is a kernel-mode file system driver located in C:\Windows\System32\drivers, and it appears often in BSOD reports tied to network file access. That makes it a common name in the dump, but not a final diagnosis by itself.
When the stop code happens during SMB access, Windows may also list mrxsmb20.sys.
What the crash report can point
Microsoft Learn lists depletion of nonpaged pool memory as one possible cause. That means the system can run out of a kernel memory pool needed for redirector work, and the crash follows the shortage. It is a trigger path, not a synonym for “bad RAM.”
Offline Files and folder redirection matter because they change how Windows reaches profile data and shared folders. If the crash appears only when a user signs in to a domain profile or opens a redirected folder, the SMB redirector path deserves attention before you start replacing drivers at random.
RDR_FILE_SYSTEM scenario matrix
| Scenario | Likely cause | Fastest test | Recommended next step |
|---|---|---|---|
| Domain login only | SMB redirector path, profile load, or folder redirection | Log on with a local account or a cached domain logon | Check Offline Files, folder redirection, and mrxsmb20.sys in the dump |
| Offline Files enabled | Sync Center cache or CSC interaction | Temporarily disable Offline Files and retry the same path | Keep it off as a workaround while you inspect the share and profile path |
| Cached logon works, live logon fails | Network share access, domain profile, or server-side folder redirection | Compare cached sign-in with a sign-in that must contact the server | Focus on the share, credentials, and redirector components |
| After a Windows update | Update regression or driver mismatch | Check the last quality update or driver change before the first crash | Roll back or hide the suspect update, then retest SMB access |
| Crash on file copy or network share access | SMB redirector, filter driver, or share corruption | Copy a small file to a different share or local folder | Review network filters, security software, and share health |
| Random boot crash without network activity | Broader corruption, storage fault, or memory pressure | Boot into safe mode or disconnect from the network | Run SFC, DISM, CHKDSK, and hardware checks |
Say your laptop bluescreens only after a user clicks a mapped drive on a domain profile, but it boots and stays stable on a local admin account. That pattern is far more consistent with redirector or share-path trouble than with a disk that fails during every boot.
📊 RDR_FILE_SYSTEM bug check has the value 0x00000027. Source: Bug Check 0x27 RDR_FILE_SYSTEM.
Is Offline Files causing it?
Offline Files can be a likely trigger when the crash happens in a domain profile, particularly if cached files are involved. If disabling Offline Files stops the blue screen, that is a strong clue that the CSC path, not the entire machine, is the active fault line.

How Sync Center settings fit the failure pattern
Offline Files creates a cached path for network content. When a profile depends on that cache, Windows may hit the redirector stack during sign-in or when it reconciles the local cache with the server. That is why some reports mention domain profiles, network shares, and offline sync in the same thread.
One comment in the Microsoft Q&A thread ties the issue to offline files on a network share, and another says disabling offline sync fixed it. That does not prove every 0x27 crash is an Offline Files bug, but it makes Sync Center worth testing early if the crash follows domain logon or share access.
When disabling Offline Files is a useful test
- Open the Sync Center settings and note whether Offline Files is enabled.
- Disable Offline Files on a test system or a single affected machine.
- Retry the exact logon or share action that caused the crash.
- Watch whether the failure disappears for a full sign-in cycle, not just one app launch.
If the blue screen stops, keep the setting off while you investigate the share, folder redirection, or domain policy behind it. If the crash remains, move attention to the update path, filters, or broader corruption.
Picture a user whose redirected Documents folder points to a server share, with Offline Files enabled. A local copy opens fine, but the next domain sign-in crashes before desktop load completes. That points you toward cached profile content and Sync Center before you blame the storage controller.
How to tell Offline Files from share or profile corruption
Offline Files usually shows a pattern: crashes line up with domain sign-in, redirected folders, or network reconnection. Share corruption tends to show up when a specific server path is touched. Profile corruption is more likely if the same user account fails across multiple shares, while another account on the same machine does not.
Folder redirection is also common in affected domain-profile scenarios. If Documents, Desktop, or AppData is redirected to a server share, the crash can follow the redirected path even when the local system files are fine.
How do I fix it after a Windows update?
If the first crash started right after a recent Windows update, treat the update as the lead suspect before deeper repair. The Microsoft Q&A report tied the issue to Windows 10 2004, and third-party writeups have linked it to bad updates such as KB2823324. A recency check is faster than a full rebuild. (Microsoft Learn)
Check for a recent driver or cumulative update
Start by matching the crash date to the last quality update, storage driver update, or security product change. If the stop code began immediately after a change, that sequence is more useful than a broad “update everything” approach because it narrows the suspect list.
Windows 10 and Windows 11 both appear in current reports. That means this is not limited to old systems, and the same triage logic still applies: look for the change that came just before the blue screens started.
Rollback or hide the suspect update
If the timing fits, uninstall the newest cumulative update or roll it back through the recovery path available on that machine. If the update is known to recur, hide it so Windows does not reinstall it during the next scan. Then retest the same SMB or domain-login path.
Do not move straight to driver surgery if the crash appeared only after one update cycle. If a rollback stops the failure, the problem was likely the update path, not the redirector stack itself.
Retest SMB access before moving to deeper repair
After rollback or hide steps, retest the exact action that failed: domain login, mapped drive access, redirected folder open, or file copy to a share. If the crash is gone, you have confirmed the trigger. If it remains, continue with system-file repair and storage checks.
Standard repair steps
When the pattern is not clearly tied to Offline Files or a single update, use the standard repair pair first: SFC and DISM. Then run CHKDSK if storage or file-system corruption is part of the picture. These steps do not explain the trigger, but they can remove damaged Windows components from the list.

Run SFC
System File Checker checks protected Windows files and replaces known-bad copies with correct ones. It is the right first pass when rdbss.sys appears in dumps and system corruption is possible, because it can fix damaged OS files without changing the redirector configuration.
Run DISM
Deployment Image Servicing and Management repairs the Windows image that SFC depends on. Use it when SFC reports problems it cannot fix, or when you suspect the servicing stack itself is damaged. Run SFC again after DISM so the repaired image can supply clean files.
Run CHKDSK
CHKDSK is the disk error check utility to use when file-system corruption or bad storage is plausible. Some volumes require a restart for the scan to run, so plan downtime before you schedule it. If the crash is tied to local files as well as shares, this step matters.
Check RAM and storage if the crashes continue
MiniTool also recommends checking hardware such as the hard drive and memory. That is sensible when the machine crashes outside network activity, at boot, or after the system files look clean. If the pattern still looks random, hardware moves up the list.
A common first-timer mistake is to start replacing network drivers before checking whether the crash follows a single domain profile. If a different account signs in cleanly and only one redirected profile fails, the machine is pointing to the profile path, not to the whole adapter stack.
Can drivers or network components stop it?
Yes, but only after you separate redirector symptoms from generic corruption. If the crash appears during SMB access, domain login, or file redirection, updating or replacing the network and storage components can help. If it happens at random boot with no network activity, broader repair and hardware checks deserve priority.
Update network and storage drivers
Use the current chipset, storage, and network adapter packages from the device or system vendor. This is especially relevant when dumps mention mrxsmb20.sys or other network path components, because the redirector depends on the path beneath it.
Review VPN, filter, and security software
VPN clients, endpoint security, and file-system filter drivers can sit in the same path as SMB traffic. If the crash starts after one of those tools is added or updated, remove it or disable it for a test. Then retest the exact domain or share action.
Recheck domain logon after each change
If you change a driver, a filter, or a policy, test the same domain login that failed before. That matters because cached logon success can hide the live-network failure. You need to verify the path that actually crashed, not just an unrelated local boot.
Frequently asked questions
What does rdr_file_system 0x27 mean in Windows?
It is Windows bug check 0x00000027, and Microsoft says it points to a problem in the SMB redirector file system. In practice, that often means a crash during logon, file-share access, or Offline Files activity rather than a plain desktop or GPU problem.
Is rdbss.sys the cause of the blue screen?
Not necessarily. rdbss.sys is the driver named in many reports, and it is part of the redirector path, but that does not prove it is the original fault. The real trigger can be Offline Files, folder redirection, an update regression, a filter driver, or nonpaged pool depletion.
Can offline files or folder redirection trigger rdr_file_system?
Yes. Offline Files and folder redirection both route profile data through the SMB redirector stack, which is why domain-profile crashes often mention them. If disabling Offline Files stops the crash, that is a strong diagnostic clue, especially when the problem appears only on network sign-in.
Why does the crash happen only on domain logins?
Because the failure may be tied to live access to a server share, profile redirection, or cached-vs-live logon behavior. A local account can boot normally while a domain profile hits the redirector path and crashes. That pattern usually points away from general boot corruption.
How do I fix rdr_file_system after a Windows update?
Check whether the crash began right after a cumulative update or driver update, then roll back or hide the suspect update and retest SMB access. If the issue followed Windows 10 2004 or another recent change, treat that update as the lead suspect before deeper repairs.
What does what is rds in windows have to do with this error?
Nothing direct. RDR_FILE_SYSTEM is about the SMB redirector path, not Remote Desktop Services. If the search term “what is rds in windows” brought you here, the important distinction is that this blue screen is about file redirection and network shares, not terminal services.






