DATA_BUS_ERROR

Code: 0x2e (46)

As HRESULT:

S: 0 (Success)
C: 0 (Microsoft-defined)
N: 0 (Not an NTSTATUS value)
Facility: 0x000 (FACILITY_NULL: Default)
Code: 0x002e (46)

As NTSTATUS:

Sev: 0 (STATUS_SEVERITY_SUCCESS)
C: 0 (Microsoft-defined)
Facility: 0x000 (Default)
Code: 0x002e (46)

Parameters

Parameter	Description
1	Virtual address that caused the fault
2	Physical address that caused the fault
3	Processor status register (PSR)
4	Faulting instruction register (FIR)

Description

The DATA_BUS_ERROR bug check has a value of 0x0000002E. This typically indicates that a parity error in system memory has been detected.

Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Cause

This error is almost always caused by a hardware problem -- a configuration issue, defective hardware, or incompatible hardware.

The most common hardware problems that can cause this error are defective RAM, Level 2 (L2) RAM cache errors, or video RAM errors. Hard disk corruption can also cause this error.

This bug check can also be caused when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (in other words, that does not have a physical address mapping).

Resolution

Resolving a hardware problem: If hardware has recently been added to the system, remove it to see if the error recurs.

If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer to determine which hardware component has failed. For details on these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure that adapter card contacts are clean.

If the problem occurs on a newly installed system, check the availability of updates for the BIOS, the SCSI controller or network cards. Updates of this kind are typically available on the Web site or the bulletin board system (BBS) of the hardware manufacturer.

If the error occurs after installing a new or updated device driver, the driver should be removed or replaced. If, under this circumstance, the error occurs during startup and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver.

If the driver is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file.

For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching or shadowing in the BIOS might also resolve this error. In addition, check the system for viruses, using any up-to-date commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

Resolving a hard disk corruption problem: Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the file allocation table (FAT) file system, the long filenames used by Windows can be damaged if Scandisk or another Microsoft MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your Windows version.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

Module	Code	Found in	Description
EhStorAuthn.exe	0x2e	7	Host authentication successful
EventCreate.exe	0x2e	78.11011	%1
cipher.exe	0x2e	78.11011	Random Numbers
dsreg.dll	0x2e	1011	Unable to connect to Local Security Authority (LSA) server. Error: %1
dssec.dll	0x2e	78.11011	Open connector queue
ehepgres.dll	0x2e	7	%1
hvloader.dll	0x2e	11	Hypervisor launch failed; Processor does not support the minimum features required to run the hypervisor (MSR index %1, allowed bits %2, required bits %3).
hvservice.sys	0x2e	10	Hypervisor launch failed; Processor does not support the minimum features required to run the hypervisor (MSR index %1, allowed bits %2, required bits %3).
nslookup.exe	0x2e	78.11011	SetDefaultServer: invalid name: %1
reagentc.exe	0x2e	8.11011	%1: No valid image found in the specified path.
sc.exe	0x2e	78.11011	[SC] Will be unlocking database by exiting
w32time.dll	0x2e	1011	The time service encountered an error and was forced to shut down. The error was: %1
webservices.dll	0x2e	78.11011	The host portion of the URL did not match the host of the endpoint.
wecutil.exe	0x2e	78.11011	Retries inactive subscription by attempting to reactivate all or specified event sources by establishing a connection and sending a remote subscription request. Disabled sources are not retried. Usage: wecutil { rs \| retry-subscription } SUBSCRIPTION_ID [EVENT_SOURCE [EVENT_SOURCE] ...] SUBSCRIPTION_ID String that uniquely identifies a subscription, specified by the tag of the XML configuration file used to create the subscription EVENT_SOURCE String that identifies a machine serving as a source of events using fully-qualified domain name, NetBIOS name, or an IP address. Example: Retry all sources of a subscription named sub1. wecutil rs sub1
wevtutil.exe	0x2e	78.11011	Get configuration information for event publishers. Usage: wevtutil { gp \| get-publisher } [/OPTION:VALUE [/OPTION:VALUE] ...] String that uniquely identifies an event publisher. You can obtain a list of publisher names by typing wevtutil ep. Options: You can use either the short (for example, /f) or long (for example, /format) version of the option names. Options and their values are not case-sensitive. /{ge \| getevents}:[true\|false] Get metadata information for events that can be raised by this publisher. /{gm \| getmessage}:[true\|false] Display the actual message instead of the numeric message ID. /{f \| format}:[XML\|Text] Specify the log file format. The default is Text. If XML is specified, print output in XML format. If Text is specified, print output without XML tags. Example: The following example displays information about the Microsoft-Windows-Eventlog event publisher including metadata about the events that the publisher can raise. wevtutil gp Microsoft-Windows-Eventlog /ge:true
whealogr.dll	0x2e	71011	A fatal hardware error has occurred. Component: Memory Error Source: %1 The details view of this entry contains further information.
win32k.sys	0x2e	78.1	HilightText
win32kbase.sys	0x2e	1011	HilightText
18 entries