0x0000002E DATA_BUS_ERROR: Diagnose Causes and Fixes

0x0000002E (DATA_BUS_ERROR) has a bug check value of 0x0000002E and, according to official Microsoft documentation, typically indicates that a parity error in system memory has been detected. It is almost always caused by a hardware problem such as a configuration issue, defective hardware, or incompatible hardware. This guide lays out a bootable or unbootable triage path to help separate memory, storage, firmware, hardware seating, and driver-related possibilities.

This guide is part of our Windows BSOD stop codes: full list and fixes series.

If the PC still starts normally, a practical first step is to run memory testing before CHKDSK, unless the issue started right after a driver or hardware change or there are already storage-related errors in Event Viewer.

What do the 0x0000002E bug check parameters mean?

For home troubleshooting, do not rely on parameter-by-parameter decoding here. The supplied official Microsoft source for this bug check does not provide end-user definitions for Parameters 1 through 4. A more reliable first branch is whether the PC boots normally, only reaches Safe Mode, or will not boot at all, plus whether the crashes began after a hardware or driver change.

Parameter 1: the virtual address that caused the fault

Official Microsoft documentation says this bug check can be caused when a device driver attempts to access an address in the 0x8 xxxxxxx range that does not exist. That can make a recently changed driver or device worth checking, especially if the BSOD began right after that change.

Parameter 2: the physical address involved

Use this value only as supporting information if you are already doing advanced crash analysis. For normal troubleshooting, memory testing and system-maker hardware diagnostics are the safer first steps.

Parameter 3 and Parameter 4: context, not the first branch

These values are best treated as advanced debugging details. For most systems, recent hardware changes, memory tests, storage checks, and manufacturer diagnostics provide a clearer path.

What this code is not

This stop code should not be treated as a RAM-only failure. Official Microsoft documentation also lists defective L2 RAM cache, video RAM errors, hard disk corruption, incompatible hardware, configuration problems, and some driver memory-access faults as possible causes.

According to Bug Check 0x2E DATA_BUS_ERROR – Windows drivers — The DATA_BUS_ERROR bug check has a value of 0x0000002E. (source)

Should I run CHKDSK or Windows Memory Diagnostic first?

Run Windows Memory Diagnostic first when the system boots normally, the crashes look random, or nothing changed right before they started. Run CHKDSK first when the machine will not boot, Event Viewer shows disk or controller errors, or file damage appeared before the BSOD. Boot state and recent changes pick the branch more reliably than guesswork.

Decision table: first test by parameters and boot state

Likely causes, in the order worth testing

Most cases start with hardware, and bad RAM sits at the top, then storage corruption, then cache or video RAM, then BIOS or adapter firmware on new or recently changed systems, with some crashes also caused by a device driver attempting to access a nonexistent address in the 0x8 xxxxxxx range. Official Microsoft documentation says common sources include defective RAM, L2 RAM cache errors, video RAM errors, and hard disk corruption.

1) Defective RAM or a bad memory path

1. Press Win + R, type mdsched.exe, and choose Restart now and check for problems.
2. After the test, open Event Viewer > Windows Logs > System and look for memory-diagnostic results.
3. If crashes continue, run the hardware diagnostics supplied by the system manufacturer to help identify the failed component, as officially recommended by Microsoft.
4. If existing hardware is confirmed faulty, remove or replace the faulty component.

2) A new or updated device driver

1. Boot into Safe Mode. On Windows 11: Settings > System > Recovery > Advanced startup > Restart now. On Windows 10: Settings > Update & Security > Recovery > Advanced startup > Restart now.
2. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 5 for Safe Mode with Networking (reported by bleepingcomputer.com). (support.eset.com)
3. Open Device Manager, right-click the recently changed device, then use Properties > Driver > Roll Back Driver or Uninstall Device.
4. If the BSOD started after a device install, remove that newly added hardware and retest, which matches official Microsoft guidance for recently added hardware.

3) Hard disk corruption affecting system files or paging

1. Open Command Prompt (Admin).
2. Run chkdsk /f /r. Accept the prompt to schedule it for the next restart if Windows is using the volume.
3. After restart, open Event Viewer > Windows Logs > System and look for disk, NTFS, storahci, controller, or bad-block entries.
4. If disk errors keep appearing, back up important data before deeper testing, then use the storage checks in the system-maker diagnostics.

4) L2 cache or video RAM faults

1. Run the system-maker hardware diagnostics, especially any memory, graphics, or motherboard tests, as officially recommended by Microsoft.
2. If the crash appears mainly during games, video playback, or GPU-heavy work, remove the display driver from Device Manager > Display adapters, then restart and install a stable driver version.
3. If a discrete graphics card was recently installed, shut down and reseat it. Official Microsoft guidance also says to check that all adapter cards are properly seated and that card contacts are clean if needed.

5) BIOS or adapter firmware on a new or changed system

1. If the machine is newly built, newly upgraded, or the fault began right after a hardware change, remove the newly added hardware first and retest, as officially recommended by Microsoft.
2. Check the PC maker or motherboard support page for BIOS updates.
3. If the system uses add-in storage or network hardware, check for updates for the BIOS, the SCSI controller, or network cards where applicable, which Microsoft specifically calls out for newly installed systems.
4. After updating firmware, load default BIOS settings once, save, and test again.

Is DATA_BUS_ERROR caused by RAM or a driver?

Usually start with RAM or other hardware, because official Microsoft documentation says this error is almost always caused by a hardware problem. Move a driver higher on the list when the machine is stable in Safe Mode, the failure began right after a driver change, or the crash points to a driver branch through a recent device or software change.

Clues that push RAM to the top

• Crashes happen at random times, including early boot.
• Windows Memory Diagnostic reports errors, or the system-maker diagnostics flag memory.
• The system also shows broader hardware instability.
• No recent driver or device change lines up with the first crash.

Clues that push a driver to the top

• The BSOD started right after a driver update or new hardware install.
• The system reaches Safe Mode but not normal mode.
• Official Microsoft documentation says a device driver can cause this bug check by attempting to access a nonexistent address in the 0x8 xxxxxxx range.
• Event Viewer System logs show device, controller, or driver warnings just before the crash.

Can a bad hard drive cause 0x0000002E?

Yes. Official Microsoft documentation says hard disk corruption can also cause this error. Storage faults fit especially well when boot files, paging files, or repeated read errors are involved. Run CHKDSK first if Windows will not boot, if Event Viewer shows disk errors, or if the BSOD followed obvious file corruption.

When Windows still boots

1. Open Command Prompt (Admin).
2. Run chkdsk /f /r and approve the restart schedule if prompted.
3. After Windows returns, open Event Viewer > Windows Logs > System and check for disk or controller errors near the crash time.
4. If storage warnings remain, run the drive test included in the system-maker diagnostics.

When the PC will not boot

1. Boot to Windows Recovery Environment.
2. Select Troubleshoot > Advanced options > Command Prompt.
3. Run chkdsk C: /f /r. If Windows is on another letter in WinRE, use that letter instead.
4. If the PC still fails after CHKDSK, switch to hardware diagnostics and firmware checks rather than repeating disk repairs.

Why Event Viewer matters here

Storage-caused 0x0000002E often leaves a trail. In Event Viewer > Windows Logs > System, look around the crash time for disk, controller, bad-block, or file-system events. Media or read/write errors have also been reported as fitting this pattern (reported by bleepingcomputer.com).

Can BIOS or firmware updates fix DATA_BUS_ERROR?

Yes, but firmware is a targeted branch, not the default first step. It becomes a stronger suspect on a newly installed system, after a motherboard or adapter change, or when the problem began right after new hardware was added. In that case, check BIOS and adapter updates before broad software cleanup.

When firmware deserves early attention

This is the branch for a new desktop build, a laptop that started crashing after hardware service, or a system that only began failing after a new GPU, NIC, storage controller, or similar adapter went in. Official Microsoft guidance specifically says to check for updates for the BIOS, the SCSI controller, or network cards on a newly installed system.

What if 0x0000002E happens after installing new hardware or a driver?

1. Remove the newly added hardware and retest, following official Microsoft guidance.
2. Open the case and reseat adapter cards. Microsoft also advises cleaning card contacts if needed.
3. If the change was a driver, use Device Manager > device > Properties > Driver > Roll Back Driver.
4. Then check for BIOS, SCSI controller, or network card updates where those parts were changed.

How do I fix 0x0000002E on Windows 10 or 11?

Use an escalation ladder. Start with memory testing if the PC boots, switch to Safe Mode and driver rollback if normal mode fails, then run CHKDSK when storage signs appear or Windows will not start. If those branches miss, move to firmware and vendor hardware diagnostics before replacing parts.

If that did not work, try this next

1. Run mdsched.exe and review results in Event Viewer > Windows Logs > System.
2. If normal mode crashes but Safe Mode works, remove or roll back the newest driver from Device Manager.
3. If file corruption or boot failure appears, run chkdsk /f /r in Windows or WinRE.
4. Run the system-maker hardware diagnostics.
5. Only after those checks, update BIOS or adapter firmware on recently changed systems.

Prevention

After the fix, avoid stacking changes. Test one RAM change, one driver change, or one firmware change at a time. That single habit makes the next 0x0000002E much easier to sort.

Still not working?

If the system keeps crashing after memory tests, Safe Mode driver rollback, CHKDSK, and firmware checks, stop doing repair work inside Windows. Repeated 0x0000002E crashes after those steps usually justify board-level diagnostics, vendor service, or part replacement guided by the system-maker test results.

When to stop testing in Windows

• Windows Memory Diagnostic reports faults.
• System-maker diagnostics flag RAM, motherboard, or graphics hardware.
• The machine crashes before Safe Mode, or during WinRE work.
• Event Viewer keeps showing storage or controller faults after CHKDSK repairs.

Frequently asked questions

What does stop code 0x0000002E mean in Windows?

Start by sorting the machine into one of three states: boots normally, Safe Mode only, or no boot. Then work through the most likely branches in order: memory and other hardware, recently added hardware, drivers, storage corruption, and firmware on newly changed systems.

Is DATA_BUS_ERROR caused by RAM or a driver?

RAM or other hardware is the default first suspect because official Microsoft documentation says the fault is almost always hardware and commonly involves defective RAM, L2 cache, or video RAM. Move a driver higher when Safe Mode works, the crash started after a driver change, or the affected device lines up with the first failure.

How do I fix 0x0000002E on Windows 10 or 11?

On both versions, start with mdsched.exe if Windows still boots. If it only reaches Safe Mode, use Settings > Recovery > Advanced startup, then roll back or uninstall the newest driver in Device Manager. If the machine will not boot or file corruption is obvious, run chkdsk /f /r from WinRE.

Can a bad hard drive cause 0x0000002E?

Yes. Hard disk corruption is a documented cause, and it fits best when the system shows read errors, missing files, paging trouble, or repeated disk events in Event Viewer > Windows Logs > System. In that branch, run chkdsk /f /r before replacing hardware at random.

What do the 0x0000002E bug check parameters mean?

For practical troubleshooting, use them only as supporting details. The supplied official Microsoft source here does not provide end-user definitions for Parameters 1 through 4, so boot behavior, recent changes, diagnostics, and Event Viewer are the better first guides.

Can BIOS or firmware updates fix DATA_BUS_ERROR?

They can, especially on a newly installed system or right after a hardware change. Check the PC or motherboard support page for BIOS updates, and check any add-in storage or network hardware for controller or card updates. Do that after basic memory, hardware, and driver triage unless the fault began immediately after the hardware swap.