DATA_BUS_ERROR BSOD Fix Windows 11: What to Test First
Start by checking the most recent hardware or driver change. Then test memory after any RAM swap, storage after any SSD or cable change, drivers after updates, and BIOS after tuning or flashing. Skipping that order can turn one bad setting into repeat crashes, lost files, and wasted parts money. This guide gives a Windows 11 DATA_BUS_ERROR triage path that tells you what to test first based on the change that happened right before the blue screen.
This guide is part of our Windows BSOD stop codes: full list and fixes series.
What DATA_BUS_ERROR means on Windows 11
DATA_BUS_ERROR is a blue-screen stop code with bug check value 0x0000002E. It usually points to a parity error in system memory, which is why memory, slot, cache, or bus instability moves to the front before software-only fixes. The crash is usually hardware-related, though a bad driver or disk corruption can be involved. (per Microsoft support)
The fastest first move is to ask what changed right before the crash. That answer usually tells you whether to start with RAM, a driver rollback, storage checks, or BIOS settings instead of guessing.
What changed right before the BSOD?
Look for one recent change: new RAM, a new GPU or SSD, a driver update, a Windows update, or a BIOS setting change such as XMP or EXPO. If the crash started after one of those, test that change first. If nothing changed, move to memory diagnostics and Event Viewer.
Likely causes, ranked by how often they show up
- Faulty or incompatible RAM — especially after a new stick, mismatched kit, or memory profile change.
- Bad or recently changed drivers — chipset, storage, and graphics drivers are the first suspects.
- Storage faults and bad sectors, disk corruption can trigger the stop code.
- BIOS or memory profile instability, XMP or EXPO can be unstable even when Windows boots.
- Motherboard slot or controller problems, more likely when one slot keeps failing or errors return after clean RAM tests.
| Latest change or symptom pattern | Most likely cause | First test to run | If that fails, escalate to |
|---|---|---|---|
| New RAM, reseat, or memory profile change | RAM or slot instability | Windows Memory Diagnostic | Test one stick per slot, then different slots |
| Crash after driver install or Windows update | Driver regression | Device Manager rollback or uninstall | Install the OEM driver package or pause the update path |
| Crash while copying files or booting from drive | Storage corruption | CHKDSK /f /r /x | Vendor storage diagnostics and drive replacement |
| Clean memory test, repeat BSODs, one slot always fails | Motherboard or controller fault | Swap sticks and slots one by one | BIOS update, then board service or replacement |
According to Fix DATA_BUS_ERROR Blue Screen Of Death on Windows 11/10 — DATA_BUS_ERROR bug check value is 0x0000002E.
How do I fix DATA_BUS_ERROR in Windows 11?
Start with the last change, then move through memory, drivers, storage, and BIOS in that order. If Windows will not boot normally, use Safe Mode or Advanced startup first; if it does boot, use Event Viewer and Device Manager before reinstalling anything. That keeps the fix path narrow and avoids random part swapping. (per Microsoft support)
- Open Settings > System > Recovery > Advanced startup > Restart now if Windows is unstable.
- Use Troubleshoot > Advanced options > Startup Settings to reach Safe Mode.
- Check Event Viewer > Windows Logs > System, then filter for Error and Critical.
- Run the memory test, then test storage and recent drivers.
- Only after those steps, review BIOS updates and memory profile settings.
Safe Mode entry: Settings > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > Startup Settings Memory test: mdsched.exe Storage check: chkdsk /x /f /r System File Checker + DISM: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
How do you test RAM first?
Run Windows Memory Diagnostic first because the stop code often points to system memory, and then verify the result in the System log in Event Viewer. If the result is clean but the crash continues, isolate each stick and each slot, because a bad slot can look like bad RAM. (per Microsoft support)
- Press Win+R, type mdsched.exe, and choose Restart now and check for problems.
- After Windows reloads, open Event Viewer > Windows Logs > System.
- Filter by Source: MemoryDiagnostics-Results or search for the test result entry.
- Power off, reseat the DIMMs, then test one stick at a time.
- Move the same stick into a different slot. If one slot repeats the crash, suspect the board or memory channel.
If Memory Diagnostic finds errors, treat the stick as suspect first. If the test is clean and the BSOD returns only under load or in one slot, that points away from simple bad RAM and toward slot, board, or BIOS instability.
Is DATA_BUS_ERROR caused by RAM or drivers?
Most often it is RAM or another hardware fault, but a bad driver can also trigger the stop code. A recent chipset, storage, or graphics driver is often the first driver path to test, especially if the crash started after an update or after installing new hardware. (per Microsoft support)
- Open Device Manager.
- Expand Display adapters, IDE ATA/ATAPI controllers, Storage controllers, and System devices.
- Right-click the newest or suspicious device, then choose Properties > Driver > Roll Back Driver or Uninstall device.
- Restart and retest before installing anything else.
- Check Windows Update > Advanced options > Optional updates for a newer OEM driver if rollback helps.
If Event Viewer points to a device right before the crash, that device gets priority. If the crash started immediately after a driver swap, the fastest fix is often rollback, not another update.
Can bad hard drive sectors cause DATA_BUS_ERROR?
Yes. Hard disk corruption can trigger this stop code, so CHKDSK belongs in the path when the crash follows file copies, booting, updates, or storage changes. It is less useful when the failure clearly tracks to new RAM or a BIOS memory profile. (per Microsoft support)
