Most of the Blue Screen of Deaths occur because of drivers. It can happen when you update the existing driver to the latest version, or when you plan to upgrade to the next feature update of Windows 11/10. One such issue is RDR FILE SYSTEM Blue Screen on Windows 11/10, and in this post, we will share multiple solutions to the problem. You will need admin permission to resolve the issue.
The RDR_FILE_SYSTEM bug check has a value of 0x00000027. This indicates that a problem occurred in the SMB redirector file system.
Why does RDR FILE SYSTEM (Rdbss.sys) Blue Screen appear?
This problem occurs because of the Redirected Drive Buffering SubSystem (Rdbss.sys), kernel-mode file system driver.
One possible cause of this bug check is the depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
What is the RDR FILE SYSTEM (Rdbss.sys)?
It is a file system driver, aka Redirected Drive Buffering SubSystem (RDBSS), and is provided as a kernel-mode file system in the Windows OS. It is used only by the Microsoft SMB mini-redirector. It is responsible to connect or communicate with the I/O Manager, Cache Manager, Memory Manager, network mini-redirectors, and other kernel systems.
Fix RDR_FILE_SYSTEM (Rdbss.sys) Blue Screen
The RDR FILE SYSTEM error occurs when something is interfering with the display drivers. You can follow these steps one by one, and make sure to check if the issue was resolved after every offered solution.
- Update or Rollback Display Drivers
- Check for Recently Installed Software
- Run DISM Tool
- Run a Memory test
- Add new physical memory to the computer.
You will need administrator privileges to carry out troubleshooting.
1] Update or Rollback Display Drivers
To find if the driver is causing the problem, you can use the Driver Verifier program in Windows to figure that out. It is a utility bull into Windows and can tell us which driver was causing the problem. The program will crash when testing the driver, and tell you what driver caused the problem. That said, make sure to remove the over-clicking of GPU and CPU.
If Verifier finds the driver, then you may have to check if the driver was recently updated or if Windows updated. Either case, driver and Windows version is not compatible. The only way out is to roll back the driver or the Windows version.
- Run the Driver Verifier program for non-Microsoft driver
- Once you have figured out the driver, you have two options.
- Rollback drivers from the Device Manager
- Use a third-party app to find the version that works.
- You can also choose to remove the driver altogether and reinstall instead do updating.
Restart the computer after installation, and check if the issue still exists. If BSOD occurs randomly, then you may have to wait for some time to verify if everything is as expected.
2] Check for Recently Installed Software
Many a time recently installed software, especially those related to intensive GPU and Memory interaction, cause BSOD. If its a program you installed before it started crashing the system, then you can find it in the Programs and Features section.
- Type “control” in the Run Prompt, and then press the Enter key
- Click on Programs or Programs and Features (depends on the view of the control panel)
- Then click on Uninstall a program. It will show a list of software installed on the PC.
- Click on Installed on to sort it in descending order.
Now you need to check if any of the programs can have issues and remove it one by one to resolve the issue. Make sure they are recent programs and not, which have been there for a few months.
3] Run DISM tool
SFC and DISM are system tools that can replace corrupt system files with fresh copies from original Windows images. They are handy, and usually the last resort if the problem is because of corruption. However, in our case, we need to use DISM to ix any system image corruption from a Windows Update source.
- Open PowerShell with Admin permission
- Type the following command to fix any corruption with Windows components or system files
Dism /Online /Cleanup-Image /RestoreHealth
- You may need internet access or an offline copy that is available in the Windows installation drive.
4] Run a Memory test
Running a memory test is not a bad idea, especially if your Windows PC is a bit old. Memtest can found out if there is a problem with your existing memory card or if the slot on the motherboard has an issue. You may also have to troubleshoot for each memory card. Make sure that memory care is not overclocked when running these tests.
5] Add new physical memory to the computer
As we are mostly running out of nonpaged pool memory because of physical limitations, adding a new physical memory will increase the quantity of nonpaged pool memory available to the kernel. However, you will have to estimate how much memory you need to increase. If the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Depending on the number of physical slots, existing memory amount, you will have to choose smartly to avoid this problem.
I hope the post was easy to follow, and you were able to Fix the RDR FILE SYSTEM Blue Screen issue on Windows 11/10.
