How to Fix the DATA_BUS_ERROR BSOD in Windows

The DATA_BUS_ERROR is a Blue Screen of Death (BSOD) that can appear when Windows encounters a serious problem while communicating with hardware or accessing memory. It is commonly associated with faulty RAM, corrupted system files, storage problems, incompatible drivers, or hardware instability.

When this error occurs, Windows may suddenly restart and display a message such as “DATA_BUS_ERROR” or a stop code related to memory and hardware access. Although the error can look alarming, you can often identify and fix the underlying problem with a systematic troubleshooting process.

This guide explains the most practical ways to fix the DATA_BUS_ERROR BSOD in Windows, starting with simple software checks and progressing to hardware diagnostics.

What Causes the DATA_BUS_ERROR?

The DATA_BUS_ERROR can have several possible causes. Common ones include:

• Faulty or improperly seated RAM
• Corrupted Windows system files
• Defective storage drives
• Outdated or incompatible device drivers
• Recently installed hardware
• BIOS or firmware problems
• Memory overclocking or unstable XMP/EXPO settings
• Windows update problems
• Malware or software conflicts
• Overheating or unstable hardware

Because the error can originate from either software or hardware, it is best to troubleshoot in stages.

Before You Start

If Windows still starts normally, back up important files before performing hardware or system repairs.

If the computer is stuck in a BSOD restart loop, try entering Safe Mode. Safe Mode loads Windows with a limited set of drivers and services, making it easier to determine whether recently installed software or drivers are responsible.

1. Restart Your Computer

Start with the simplest solution: restart Windows.

A temporary hardware communication problem can sometimes trigger a BSOD that does not return after rebooting.

If the DATA_BUS_ERROR appears repeatedly, continue with the steps below rather than assuming the problem is resolved.

2. Disconnect Recently Added Hardware

If the problem started after installing new hardware, temporarily remove or disconnect it.

Examples include:

• New RAM
• PCIe expansion cards
• External storage
• USB devices
• New graphics cards
• Docking stations
• Other recently installed peripherals

Restart Windows after disconnecting the device.

If the BSOD stops occurring, reconnect devices one at a time to identify the hardware associated with the problem.

3. Check Your RAM

Memory problems are one of the first things worth investigating when Windows reports a hardware-related BSOD.

Run Windows Memory Diagnostic

Press Windows + R, type:

mdsched.exe

Press Enter.

Choose Restart now and check for problems.

Windows will restart and perform a memory test.

If errors are reported, the RAM may be defective, improperly installed, or operating outside stable settings.

Physically Reseat the RAM

If you’re comfortable working inside your PC:

1. Shut down the computer.
2. Disconnect the power.
3. Open the case.
4. Remove the RAM modules.
5. Check for visible dust or damage.
6. Reinstall the modules firmly.
7. Start the computer again.

For systems with multiple memory modules, testing them individually can help identify a faulty stick.

Important: Shut down and disconnect power before handling internal components.

4. Disable Memory Overclocking

Unstable memory settings can cause intermittent BSODs.

If you recently enabled:

• XMP
• EXPO
• Memory overclocking
• Manual RAM timings
• CPU overclocking

return the BIOS/UEFI settings to their default values temporarily.

Then test Windows again.

If the DATA_BUS_ERROR disappears after reverting overclocking settings, the system may not be stable at the previous configuration.

5. Update Device Drivers

A damaged or incompatible driver can cause Windows to communicate incorrectly with hardware.

Pay particular attention to:

• Chipset drivers
• Storage drivers
• Graphics drivers
• Network drivers
• Motherboard drivers

Open Device Manager by right-clicking the Start button and selecting Device Manager.

Look for devices displaying a warning icon.

You can also install current drivers from your computer or motherboard manufacturer’s official support website.

Avoid downloading drivers from unknown third-party websites.

6. Run System File Checker

Corrupted Windows files can contribute to system crashes.

Open Windows Terminal or Command Prompt as administrator and run:

sfc /scannow

Wait for the scan to finish.

If Windows finds damaged system files, it will attempt to repair them automatically.

Restart the computer afterward and check whether the BSOD returns.

7. Run DISM

If SFC cannot repair all corrupted files, use the Deployment Image Servicing and Management tool.

Open an administrator Command Prompt or Windows Terminal and run:

DISM /Online /Cleanup-Image /RestoreHealth

Allow the operation to complete.

Then run SFC again:

sfc /scannow

Restart Windows when finished.

Running DISM followed by SFC can repair problems with the Windows component store and system files.

8. Check Your Storage Drive

Storage problems can cause Windows crashes, corrupted files, and unexpected BSODs.

You can use the built-in CHKDSK utility to check a drive.

Open Windows Terminal as administrator and enter:

chkdsk C: /scan

If Windows reports disk problems, you may need a more extensive repair operation.

You should also check the health of your SSD or hard drive using the manufacturer’s diagnostic software when available.

If the drive is showing signs of failure, back up important data immediately before performing extensive repairs.

9. Install Windows Updates

Microsoft regularly releases Windows updates that contain security fixes, bug fixes, and compatibility improvements.

Go to:

Settings → Windows Update

Select Check for updates.

Install available updates and restart the computer.

If the DATA_BUS_ERROR began immediately after a particular update, however, the update itself may be worth investigating.

10. Roll Back a Recently Updated Driver

If the BSOD started shortly after a driver update, rolling the driver back may help.

Open Device Manager and:

1. Locate the recently updated device.
2. Right-click it.
3. Select Properties.
4. Open the Driver tab.
5. Select Roll Back Driver, if available.
6. Restart Windows.

This is particularly useful when crashes began immediately after installing a graphics, storage, or chipset driver.

11. Check for Overheating

Excessive temperatures can make hardware unstable.

Check temperatures while the computer is under normal workloads and look for signs such as:

• Sudden shutdowns
• Fans constantly running at high speed
• Performance throttling
• Crashes during gaming or heavy workloads
• Excessive dust buildup

Clean dust from the PC’s ventilation system and make sure fans are working properly.

For laptops, make sure air vents aren’t blocked.

12. Scan Windows for Malware

Malware can damage system files or interfere with normal Windows operations.

Open Windows Security and select:

Virus & threat protection → Scan options

Start with a Quick scan.

If you suspect an infection, perform a more thorough scan.

After the scan completes, restart the computer and monitor whether the DATA_BUS_ERROR continues.

13. Use Safe Mode to Find Software Conflicts

If the BSOD occurs during normal Windows operation but disappears in Safe Mode, a third-party driver, service, or application may be involved.

To troubleshoot:

1. Open Settings.
2. Go to System → Recovery.
3. Select Advanced startup → Restart now.
4. Choose Troubleshoot → Advanced options → Startup Settings.
5. Restart.
6. Select the Safe Mode option.

Use the computer normally for a while.

If Windows remains stable in Safe Mode, investigate recently installed drivers, applications, and startup programs.

14. Use System Restore

If the problem began recently, System Restore may allow you to return Windows to an earlier configuration.

Search Windows for Create a restore point.

Open System Properties, select System Restore, and choose an available restore point created before the BSOD started.

System Restore can reverse certain system changes without deleting personal documents.

15. Check the BIOS or UEFI

An outdated or incorrectly configured BIOS can sometimes contribute to hardware instability.

Check your motherboard or computer manufacturer’s support page for BIOS updates.

Before updating BIOS firmware, carefully follow the manufacturer’s instructions. A failed firmware update can prevent a computer from booting.

If you recently changed BIOS settings, restoring optimized or default settings may also help identify unstable configurations.

16. Examine the BSOD Minidump

Advanced users can investigate Windows crash dump files to identify the driver or component associated with the crash.

Windows commonly stores small memory dump files in:

C:\Windows\Minidump

These files can be analyzed with debugging tools to determine whether a particular driver or module appears repeatedly in crash reports.

If the same driver is repeatedly identified, update, reinstall, or roll back that driver.

Keep in mind that a driver appearing in a crash dump is not always the original cause. A hardware problem can sometimes cause another driver to appear involved.

17. Test RAM More Thoroughly

If Windows Memory Diagnostic reports no problems but you continue experiencing DATA_BUS_ERROR crashes, consider performing a more extensive memory test.

A dedicated bootable memory-testing utility can test RAM outside the Windows environment.

Test each memory module individually if possible. This can help determine whether the problem follows a particular RAM stick or memory slot.

If one module repeatedly produces errors while another does not, the defective module may need replacement.

18. Check for Hardware Failure

If software troubleshooting does not resolve the problem, hardware may be responsible.

Potential components include:

• RAM
• SSD or hard drive
• Motherboard
• CPU
• Power supply
• Graphics card

Hardware failure becomes more likely when the BSOD occurs under different operating conditions, especially if Windows also experiences freezes, corrupted files, boot problems, or random restarts.

For persistent problems, professional hardware diagnostics may be appropriate.

19. Perform a Clean Windows Installation

A clean Windows installation should generally be considered a last-resort software troubleshooting step.

Before reinstalling Windows, back up your personal files and make sure you have access to important application licenses and installation files.

If a clean installation still produces DATA_BUS_ERROR crashes with updated drivers and default BIOS settings, that points more strongly toward a hardware or firmware issue rather than ordinary Windows corruption.

How to Prevent DATA_BUS_ERROR BSOD Problems

After fixing the crash, a few maintenance habits can reduce the likelihood of similar problems.

Keep Windows Updated

Install important Windows updates regularly.

Keep Drivers Current

Use official manufacturer sources for important hardware drivers.

Avoid Unstable Overclocking

If stability is more important than maximum performance, use conservative CPU and memory settings.

Monitor Hardware Health

Watch for unusual temperatures, storage warnings, memory errors, or unexpected restarts.

Maintain Backups

Regular backups protect your files if a storage device suddenly fails.

Don’t Ignore Repeated BSODs

One isolated crash may be temporary, but repeated crashes usually deserve investigation. Frequent BSODs can indicate an underlying hardware, driver, or system problem.

Frequently Asked Questions

What is DATA_BUS_ERROR?

DATA_BUS_ERROR is a Windows blue-screen problem associated with an issue involving memory, hardware communication, drivers, or system-level operations. The exact cause can vary from one computer to another.

Can faulty RAM cause DATA_BUS_ERROR?

Yes. Faulty, improperly seated, or unstable RAM can cause serious Windows crashes. Testing memory should therefore be one of the first troubleshooting steps.

Can a driver cause DATA_BUS_ERROR?

Yes. An incompatible, corrupted, or malfunctioning driver can cause Windows to interact incorrectly with hardware and trigger a BSOD.

How do I test RAM for DATA_BUS_ERROR?

Start with Windows Memory Diagnostic by running mdsched.exe. For persistent problems, you can perform more extensive memory testing and test individual RAM modules.

Should I reinstall Windows to fix DATA_BUS_ERROR?

Not necessarily. Reinstalling Windows is generally better treated as a later troubleshooting step. Check RAM, drivers, system files, storage, BIOS settings, and hardware first.

Can an SSD cause a DATA_BUS_ERROR?

Storage problems can contribute to system instability and corrupted Windows files. Check the SSD or hard drive for health problems if other troubleshooting steps don’t resolve the crashes.

Why does DATA_BUS_ERROR keep coming back?

Recurring crashes may indicate an unresolved hardware problem, unstable memory settings, a problematic driver, corrupted Windows files, storage failure, or another underlying issue. If the problem continues after software repairs, hardware diagnostics may be necessary.

Final Thoughts

The DATA_BUS_ERROR BSOD can be caused by several different problems, so there isn’t one universal fix. Start by checking RAM, recently installed hardware, drivers, Windows system files, and storage health. If the problem began after changing BIOS or overclocking settings, return the system to stable default settings.

For persistent crashes, use memory diagnostics, examine crash dumps, and test hardware components individually. A methodical approach can help identify whether the underlying problem is Windows, a driver, or a failing component.