Article ID: 942972 - Last Review: October 26, 2007 - Revision: 1.2 Event ID 1801 may be logged in the System log on a computer that is running Windows VistaOn This PageSYMPTOMSA computer that is running Windows Vista may stop responding. Or, programs that are running on this computer may stop responding. Also, you may receive a Stop error in Windows Vista. Moreover, an event that resembles the following may be logged in the System log:
CAUSEThe following issues may cause the problems that are mentioned in the "Symptoms" section. Cause 1This problem may occur because of physical memory errors.Cause 2This problem may occur because of incorrect random access memory (RAM) timing issues in the basic input/output system (BIOS).Cause 3This problem may occur because the processor is overclocked.Cause 4This problem may occur is memory overwrites direct memory access (DMA).Note Memory chips that have Parity bits or error-correction coding (ECC) bits also experience memory errors that occur because of the first three causes that are listed in this section. To detect possible memory problems, Windows Vista performs a consistency check on a subset of all the physical memory pages. When Windows Vista satisfies a memory request by removing a page from the zeroed list, it may first check the page to confirm whether the contents are still completely zero. For performance reasons, this check is not performed on every page. However, sampling is performed on a subset of all the allocations. If a page that is checked does not consist of all zeros, memory corruption has occurred. The event that is described in the "Symptoms" section is logged in the System log. Then, the memory is rezeroed, and the system continues. RESOLUTIONTo resolve this problem, find the most likely cause that is described in the Cause section. Then, use the resolution that is appropriate for the cause. Resolution for Cause 1Use directed swapping to find the memory chip that is experiencing data loss.Resolution for Cause 2Contact the computer vendor for a BIOS update.Resolution for Cause 3Change the system configuration to use supported clock frequencies.Resolution for Cause 4Remove recently-added hardware or drivers that may be causing the problem.MORE INFORMATIONThe following is the raw data from the event that is described in the "Symptoms" section: Offset 0xC : C0000709 = STATUS_HARDWARE_MEMORY_ERROR. Offset 0x10: Stop code that we would have crashed with: PAGE_NOT_ZERO == 0x127 FAULTY_HARDWARE_CORRUPTED_PAGE == 0x12B Offset 0x20 & 0x24 : physical address (4-byte aligned) of memory location with the first data error. Note space is left for the full 64-bit physical address. Offset 0x28 : 4-byte contents of the physical address that the first data error. If there is multiple bits set, a DMA-style overwrite is possible.
APPLIES TO
| Article Translations
|

Back to the top
