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
| Boot condition | Recent change clue | Storage clue | Mode clue | Most likely subsystem | First test to run |
|---|---|---|---|---|---|
| Boots normally | No recent hardware or driver change | No clear disk warning | Crashes seem random | Defective RAM or memory path | Run Windows Memory Diagnostic, then system-maker hardware diagnostics if needed |
| Boots normally | Started after a driver update or device install | Varies | One device or action seems to trigger it | Driver or newly added hardware | Open Device Manager, roll back or uninstall the newest driver, or remove the newly added hardware and retest |
| Boots normally | No useful recent-change clue | File errors, paging trouble, or disk events | No clear pattern | Storage corruption | Run chkdsk /f /r from an elevated Command Prompt |
| Safe Mode only | Crash disappears in Safe Mode | Inconsistent | Normal mode fails | Driver or startup-loaded adapter software | Use Safe Mode with Networking, then uninstall or roll back the changed driver |
| Safe Mode only | No recent software clue | No clear disk pattern | Still unstable under load | RAM, cache, video memory, or other hardware | Run memory diagnostics and system-maker hardware diagnostics |
| No boot | No recent clue available | Possible | Unavailable | Storage corruption or hard hardware fault | From WinRE, open Command Prompt and run chkdsk /f /r; if that passes, move to hardware diagnostics |
| No boot after new hardware | Failure starts immediately after the change | Any | Unavailable | Firmware, seating, or incompatible hardware | Remove the new part, reseat adapter cards, then check BIOS or adapter updates |
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
- Press Win + R, type mdsched.exe, and choose Restart now and check for problems.
- After the test, open Event Viewer > Windows Logs > System and look for memory-diagnostic results.
- If crashes continue, run the hardware diagnostics supplied by the system manufacturer to help identify the failed component, as officially recommended by Microsoft.
- If existing hardware is confirmed faulty, remove or replace the faulty component.
2) A new or updated device driver
- 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.
- Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 5 for Safe Mode with Networking (reported by bleepingcomputer.com). (support.eset.com)
- Open Device Manager, right-click the recently changed device, then use Properties > Driver > Roll Back Driver or Uninstall Device.
- 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
- Open Command Prompt (Admin).
- Run
chkdsk /f /r. Accept the prompt to schedule it for the next restart if Windows is using the volume. - After restart, open Event Viewer > Windows Logs > System and look for disk, NTFS, storahci, controller, or bad-block entries.
- 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
- Run the system-maker hardware diagnostics, especially any memory, graphics, or motherboard tests, as officially recommended by Microsoft.
- 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.
- 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
- 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.
- Check the PC maker or motherboard support page for BIOS updates.
- 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.
- 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.
