2. Fórumok
  3. OS, alkalmazások
  4. Októberben jön a Windows 8.1

Új hozzászólás Aktív témák

  • #44 Glenda addikt Dr. Akula #43
    Új Válasz #44
    Új hozzászólás
    Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra
    Privát üzenet küldése

    Glenda

    addikt

    válasz Dr. Akula #43 üzenetére

    DIVIDE_BY_ZERO_ERROR

    This error is caused by an application trying to divide by zero. If you receive this error and don't know which application caused it, you might try examining the memory dump.

    IRQL_NOT_LESS_OR_EQUAL

    The IRQL_NOT_LESS_OR_EQUAL error is caused by a buggy device driver or an actual hardware conflict.

    KMODE_EXCEPTION_NOT_HANDLED

    An incorrectly configured device driver usually causes this type of error.

    REGISTRY_ERROR

    Such an error indicates a catastrophic failure in the system's registry. However, this error can sometimes be caused by failure to read the registry from the hard disk rather than because the registry itself is corrupt.

    INACCESSIBLE_BOOT_DEVICE

    Just as the name implies, this error indicates that Windows NT is having trouble reading from the hard disk. This error can be caused by a faulty device driver or a bad small computer systems interface (SCSI) terminator.

    UNEXPECTED_KERNEL_MODE_TRAP

    This error message is almost always caused by your computer's memory.

    BAD_POOL_HEADER

    This is, perhaps, the most obscure error message. In most cases, if you receive this error, it's related to the most recent change you've made on your system. Try undoing the change to get rid of the error.

    NTFS_FILE_SYSTEM

    An NTFS_FILE_SYSTEM error indicates hard disk corruption.

    KERNEL_DATA_INPAGE_ERROR

    This error indicates that Windows NT wasn't able to read a page of kernel data from the page file. Bad memory, a bad processor, incorrectly terminated SCSI devices, or a corrupt PAGEFILE.SYS file may cause this situation.

    NMI_HARDWARE_FAILURE

    This is a generic error message in which the hardware abstraction layer can't report on the true cause of the error. In such a situation, Microsoft recommends calling the hardware vendor. This error can sometimes be caused by mixing parity and non-parity SIMMs, or by bad SIMMs.

Új hozzászólás Aktív témák