Windows 7 / Getting Started

Stop 0x2E or DATA_BUS_ERROR

The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including motherboard, Level 2 (L2) cache, or video memory), incompatible or mismatched memory hardware, or a device driver attempting to access an address in the 0x8xxxxxxx range that does not exist (meaning that it does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by viruses or other problems.

Interpreting the Message

This Stop message has four parameters:

  1. Virtual address that caused the fault
  2. Physical address that caused the fault
  3. Processor status register
  4. Faulting instruction register

Resolving the Problem

The following suggestions are specific to Stop 0x2E errors. For additional troubleshooting suggestions that apply to all Stop errors, see the section titled "Stop Message Checklist" later in this tutorial.

  • Stop 0x2E is typically the result of defective, malfunctioning, or failed memory hardware, such as memory modules, L2 SRAM cache, or video adapter RAM. If you added new hardware recently, remove the hardware and replace it to determine whether it is causing or contributing to the problem. Run Windows Memory Diagnostics to determine whether the feature has failed.
  • Stop 0x2E messages can also occur after you install faulty drivers or system services. If a driver file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
  • Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity.
  • The problem might also be due to cracks, scratched traces, or defective features on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
[Previous] [Contents] [Next]

In this tutorial:

  1. Troubleshooting Stop Messages
  2. Stop Message Overview
  3. Identifying the Stop Error
  4. Finding Troubleshooting Information
  5. Stop Messages
  6. Bugcheck Information
  7. Technical Information
  8. Debug Port and Dump Status Information
  9. Types of Stop Errors
  10. Memory Dump Files
  11. Configuring Small Memory Dump Files
  12. Configuring Kernel Memory Dump Files
  13. Configuring Complete Memory Dump Files
  14. How to Manually Initiate a Stop Error and Create a Dump File
  15. Using Memory Dump Files to Analyze Stop Errors
  16. Using Windows 7 Error Reporting
  17. Using Symbol Files and Debuggers
  18. Being Prepared for Stop Errors
  19. Record and Save Stop Message Information
  20. Check Software Disk Space Requirements
  21. Install a Kernel Debugger and Symbol Files
  22. Stop 0xA or IRQL_NOT_LESS_OR_EQUAL
  23. Stop 0x1E or KMODE_EXCEPTION_NOT_HANDLED
  24. Understanding Kernel Stack Overflows
  25. Stop 0x24 or NTFS_FILE_SYSTEM
  26. Stop 0x2E or DATA_BUS_ERROR
  27. Stop 0x3B or SYSTEM_SERVICE_EXCEPTION
  28. Stop 0x3F or NO_MORE_SYSTEM_PTES
  29. Stop 0x50 or PA GE_FAULT_IN_NONPA GED_AREA
  30. Stop 0x77 or KERNEL_STACK_INPA GE_ERROR
  31. Stop 0x7A or KERNEL_DATA_INPA GE_ERROR
  32. Stop 0x7B or INACCESSIBLE_BOOT_DEVICE
  33. Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP
  34. Stop 0x9F or DRIVER_POWER_STATE_FAILURE
  35. Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
  36. Stop 0xC2 or BAD_POOL_CALLER
  37. Stop 0xCE or DRIVER_UNLOADED_WITHOUT_CANCELLING_ PENDING_OPERATIONS
  38. Stop 0xD1 or IRQL_NOT_LESS_OR_EQUAL
  39. Stop 0xD8 or DRIVER_USED_EXCESSIVE_PTES
  40. Stop 0xEA or THREAD_STUCK_IN_DEVICE_DRIVER
  41. Stop 0xED or UNMOUNTABLE_BOOT_VOLUME
  42. Stop 0xFE or BUGCODE_USB_DRIVER
  43. Stop 0x00000124
  44. Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED
  45. Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
  46. Hardware Malfunction Messages
  47. Stop Message Checklist
  48. Check Your Software
  49. Use the Last Known Good Configuration
  50. Restart the System in Safe Mode
  51. Check Event Viewer Logs
  52. Install Compatible Antivirus Tools
  53. Report Your Errors
  54. Install Operating System and Driver Updates
  55. Install and Use a Kernel Debugger
  56. Check Your Hardware
  57. Check for Nondefault Firmware Settings
  58. Check for Non-Default Hardware Clock Speeds
  59. Check by Running Hardware Diagnostic Tools
  60. Check for SCSI Disk and Controller Settings
  61. Check Memory Compatibility
  62. Check by Temporarily Removing Devices
  63. Check by Replacing a Device