📄 bugcodes.h
字号:
//
// Disable or remove any newly installed hardware and drivers. Disable or
// remove any newly installed software. If you need to use Safe Mode to
// remove or disable components, restart your computer, press F8 to select
// Advanced Startup Options, and then select Safe Mode.
//
// Refer to your Getting Started manual for more information on
// troubleshooting Stop errors.
//
#define BUGCODE_PSS_MESSAGE_7F ((ULONG)0x000000B3L)
//
// MessageId: VIDEO_DRIVER_INIT_FAILURE
//
// MessageText:
//
// The video driver failed to initialize
//
#define VIDEO_DRIVER_INIT_FAILURE ((ULONG)0x000000B4L)
//
// MessageId: BOOTLOG_LOADED
//
// MessageText:
//
// Loaded driver
//
#define BOOTLOG_LOADED ((ULONG)0x000000B5L)
//
// MessageId: BOOTLOG_NOT_LOADED
//
// MessageText:
//
// Did not load driver
//
#define BOOTLOG_NOT_LOADED ((ULONG)0x000000B6L)
//
// MessageId: BOOTLOG_ENABLED
//
// MessageText:
//
// Boot Logging Enabled
//
#define BOOTLOG_ENABLED ((ULONG)0x000000B7L)
//
// MessageId: ATTEMPTED_SWITCH_FROM_DPC
//
// MessageText:
//
// A wait operation, attach process, or yield was attempted from a DPC routine.
//
#define ATTEMPTED_SWITCH_FROM_DPC ((ULONG)0x000000B8L)
//
// MessageId: CHIPSET_DETECTED_ERROR
//
// MessageText:
//
// A parity error in the system memory or I/O system was detected.
//
#define CHIPSET_DETECTED_ERROR ((ULONG)0x000000B9L)
//
// MessageId: SESSION_HAS_VALID_VIEWS_ON_EXIT
//
// MessageText:
//
// SESSION_HAS_VALID_VIEWS_ON_EXIT
//
#define SESSION_HAS_VALID_VIEWS_ON_EXIT ((ULONG)0x000000BAL)
//
// MessageId: NETWORK_BOOT_INITIALIZATION_FAILED
//
// MessageText:
//
// An initialization failure occurred while attempting to boot from the network.
//
#define NETWORK_BOOT_INITIALIZATION_FAILED ((ULONG)0x000000BBL)
//
// MessageId: NETWORK_BOOT_DUPLICATE_ADDRESS
//
// MessageText:
//
// A duplicate IP address was assigned to this machine while attempting to
// boot from the network.
//
#define NETWORK_BOOT_DUPLICATE_ADDRESS ((ULONG)0x000000BCL)
//
// MessageId: INVALID_HIBERNATED_STATE
//
// MessageText:
//
// The hibernated memory image does not match the current hardware configuration.
//
#define INVALID_HIBERNATED_STATE ((ULONG)0x000000BDL)
//
// MessageId: ATTEMPTED_WRITE_TO_READONLY_MEMORY
//
// MessageText:
//
// An attempt was made to write to read-only memory.
//
#define ATTEMPTED_WRITE_TO_READONLY_MEMORY ((ULONG)0x000000BEL)
//
// MessageId: MUTEX_ALREADY_OWNED
//
// MessageText:
//
// MUTEX_ALREADY_OWNED
//
#define MUTEX_ALREADY_OWNED ((ULONG)0x000000BFL)
//
// MessageId: PCI_CONFIG_SPACE_ACCESS_FAILURE
//
// MessageText:
//
// An attempt to access PCI configuration space failed.
//
#define PCI_CONFIG_SPACE_ACCESS_FAILURE ((ULONG)0x000000C0L)
//
// MessageId: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
//
// MessageText:
//
// SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
//
#define SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION ((ULONG)0x000000C1L)
//
// MessageId: BAD_POOL_CALLER
//
// MessageText:
//
// BAD_POOL_CALLER
//
#define BAD_POOL_CALLER ((ULONG)0x000000C2L)
//
// MessageId: BUGCODE_PSS_MESSAGE_SIGNATURE
//
// MessageText:
//
//
// A system file that is owned by Windows 2000 was replaced by an application
// running on your system. The operating system detected this and tried to
// verify the validity of the file's signature. The operating system found that
// the file signature is not valid and put the original, correct file back
// so that your operating system will continue to function properly.
//
#define BUGCODE_PSS_MESSAGE_SIGNATURE ((ULONG)0x000000C3L)
//
// MessageId: DRIVER_VERIFIER_DETECTED_VIOLATION
//
// MessageText:
//
//
// A device driver attempting to corrupt the system has been caught.
// The faulty driver currently on the kernel stack must be replaced
// with a working version.
//
#define DRIVER_VERIFIER_DETECTED_VIOLATION ((ULONG)0x000000C4L)
//
// MessageId: DRIVER_CORRUPTED_EXPOOL
//
// MessageText:
//
//
// A device driver has corrupted the executive memory pool.
//
// If this is the first time you've seen this Stop error screen,
// restart your computer. If this screen appears again, follow
// these steps:
//
// Check to make sure any new hardware or software is properly installed.
// If this is a new installation, ask your hardware or software manufacturer
// for any Windows 2000 updates you might need.
//
// Run the driver verifier against any new (or suspect) drivers.
// If that doesn't reveal the corrupting driver, try enabling special pool.
// Both of these features are intended to catch the corruption at an earlier
// point where the offending driver can be identified.
//
// If you need to use Safe Mode to remove or disable components,
// restart your computer, press F8 to select Advanced Startup Options,
// and then select Safe Mode.
//
// Refer to your Getting Started manual for more information on
// troubleshooting Stop errors.
//
#define DRIVER_CORRUPTED_EXPOOL ((ULONG)0x000000C5L)
//
// MessageId: DRIVER_CAUGHT_MODIFYING_FREED_POOL
//
// MessageText:
//
//
// A device driver attempting to corrupt the system has been caught.
// The faulty driver currently on the kernel stack must be replaced
// with a working version.
//
#define DRIVER_CAUGHT_MODIFYING_FREED_POOL ((ULONG)0x000000C6L)
//
// MessageId: TIMER_OR_DPC_INVALID
//
// MessageText:
//
//
// A kernel timer or DPC was found in memory which must not contain such
// items. Usually this is memory being freed. This is usually caused by
// a device driver that has not cleaned up properly before freeing memory.
//
#define TIMER_OR_DPC_INVALID ((ULONG)0x000000C7L)
//
// MessageId: IRQL_UNEXPECTED_VALUE
//
// MessageText:
//
//
// The processor's IRQL is not valid for the currently executing context.
// This is a software error condition and is usually caused by a device
// driver changing IRQL and not restoring it to its previous value when
// it has finished its task.
//
#define IRQL_UNEXPECTED_VALUE ((ULONG)0x000000C8L)
//
// MessageId: DRIVER_VERIFIER_IOMANAGER_VIOLATION
//
// MessageText:
//
//
// The IO manager has detected a violation by a driver that is being verified.
// The faulty driver that is being verified must be debugged and
// replaced with a working version.
//
#define DRIVER_VERIFIER_IOMANAGER_VIOLATION ((ULONG)0x000000C9L)
//
// MessageId: PNP_DETECTED_FATAL_ERROR
//
// MessageText:
//
//
// Plug and Play detected an error most likely caused by a faulty driver.
//
#define PNP_DETECTED_FATAL_ERROR ((ULONG)0x000000CAL)
//
// MessageId: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
//
// MessageText:
//
// DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
//
#define DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS ((ULONG)0x000000CBL)
//
// MessageId: PAGE_FAULT_IN_FREED_SPECIAL_POOL
//
// MessageText:
//
//
// The system is attempting to access memory after it has been freed.
// This usually indicates a system-driver synchronization issue.
//
#define PAGE_FAULT_IN_FREED_SPECIAL_POOL ((ULONG)0x000000CCL)
//
// MessageId: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
//
// MessageText:
//
//
// The system is attempting to access memory beyond the end of the allocation.
// This usually indicates a system-driver synchronization issue.
//
#define PAGE_FAULT_BEYOND_END_OF_ALLOCATION ((ULONG)0x000000CDL)
//
// MessageId: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
//
// MessageText:
//
// DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
//
#define DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS ((ULONG)0x000000CEL)
//
// MessageId: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
//
// MessageText:
//
// TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
//
#define TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE ((ULONG)0x000000CFL)
//
// MessageId: DRIVER_CORRUPTED_MMPOOL
//
// MessageText:
//
//
// A device driver has corrupted the system memory management pool.
//
// If this is the first time you've seen this Stop error screen,
// restart your computer. If this screen appears again, follow
// these steps:
//
// Check to make sure any new hardware or software is properly installed.
// If this is a new installation, ask your hardware or software manufacturer
// for any Windows 2000 updates you might need.
//
// Run the driver verifier against any new (or suspect) drivers.
// If that doesn't reveal the corrupting driver, try enabling special pool.
// Both of these features are intended to catch the corruption at an earlier
// point where the offending driver can be identified.
//
// If you need to use Safe Mode to remove or disable components,
// restart your computer, press F8 to select Advanced Startup Options,
// and then select Safe Mode.
//
// Refer to your Getting Started manual for more information on
// troubleshooting Stop errors.
//
#define DRIVER_CORRUPTED_MMPOOL ((ULONG)0x000000D0L)
//
// MessageId: DRIVER_IRQL_NOT_LESS_OR_EQUAL
//
// MessageText:
//
// DRIVER_IRQL_NOT_LESS_OR_EQUAL
//
#define DRIVER_IRQL_NOT_LESS_OR_EQUAL ((ULONG)0x000000D1L)
//
// MessageId: BUGCODE_ID_DRIVER
//
// MessageText:
//
// This driver may be at fault :
//
#define BUGCODE_ID_DRIVER ((ULONG)0x000000D2L)
//
// MessageId: DRIVER_PORTION_MUST_BE_NONPAGED
//
// MessageText:
//
// The driver mistakenly marked a part of it's image pagable instead of nonpagable.
//
#define DRIVER_PORTION_MUST_BE_NONPAGED ((ULONG)0x000000D3L)
//
// MessageId: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
//
// MessageText:
//
// The driver unloaded without cancelling pending operations.
//
#define SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD ((ULONG)0x000000D4L)
//
// MessageId: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
//
// MessageText:
//
//
// The driver is attempting to access memory after it has been freed.
//
#define DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL ((ULONG)0x000000D5L)
//
// MessageId: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
//
// MessageText:
//
//
// The driver is attempting to access memory beyond the end of the allocation.
//
#define DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION ((ULONG)0x000000D6L)
//
// MessageId: DRIVER_UNMAPPING_INVALID_VIEW
//
// MessageText:
//
//
// The driver is attempting to unmap an invalid memory address.
//
#define DRIVER_UNMAPPING_INVALID_VIEW ((ULONG)0x000000D7L)
//
// MessageId: DRIVER_USED_EXCESSIVE_PTES
//
// MessageText:
//
//
// The driver has used an excessive number of system PTEs.
//
#define DRIVER_USED_EXCESSIVE_PTES ((ULONG)0x000000D8L)
//
// MessageId: LOCKED_PAGES_TRACKER_CORRUPTION
//
// MessageText:
//
//
// The driver is corrupting the locked pages tracking structures.
//
#define LOCKED_PAGES_TRACKER_CORRUPTION ((ULONG)0x000000D9L)
//
// MessageId: SYSTEM_PTE_MISUSE
//
// MessageText:
//
//
// The driver is mismanaging system PTEs.
//
#define SYSTEM_PTE_MISUSE ((ULONG)0x000000DAL)
//
// MessageId: DRIVER_CORRUPTED_SYSPTES
//
// MessageText:
//
//
// A driver has corrupted the memory management system PTEs.
//
#define DRIVER_CORRUPTED_SYSPTES ((ULONG)0x000000DBL)
//
// MessageId: DRIVER_INVALID_STACK_ACCESS
//
// MessageText:
//
//
// A driver accessed a stack address that lies below the current stack pointer
// of the stack's thread.
//
#define DRIVER_INVALID_STACK_ACCESS ((ULONG)0x000000DCL)
//
// MessageId: BUGCODE_PSS_MESSAGE_A5
//
// MessageText:
//
//
// The BIOS in this system is not fully ACPI compliant. Please contact your
// system vendor or visit http://www.hardware-update.com for an updated BIOS.
// If you are unable to obtain an updated BIOS or the latest BIOS supplied by
// your vendor is not ACPI compliant, you can turn off ACPI mode during text
// mode setup. To do this, simply press the F7 key when you are prompted to
// install storage drivers. The system will not notify you that the F7 key
// was pressed - it will silently disable ACPI and allow you to continue
// your installation.
//
#define BUGCODE_PSS_MESSAGE_A5 ((ULONG)0x000000DDL)
//
// MessageId: POOL_CORRUPTION_IN_FILE_AREA
//
// MessageText:
//
//
// A driver corrupted pool memory used for holding pages destined for disk.
//
#define POOL_CORRUPTION_IN_FILE_AREA ((ULONG)0x000000DEL)
//
// MessageId: HARDWARE_PROFILE_UNDOCKED_STRING
//
// MessageText:
//
// Undocked Profile
//
#define HARDWARE_PROFILE_UNDOCKED_STRING ((ULONG)0x40010001L)
//
// MessageId: HARDWARE_PROFILE_DOCKED_STRING
//
// MessageText:
//
// Docked Profile
//
#define HARDWARE_PROFILE_DOCKED_STRING ((ULONG)0x40010002L)
//
// MessageId: HARDWARE_PROFILE_UNKNOWN_STRING
//
// MessageText:
//
// Profile
//
#define HARDWARE_PROFILE_UNKNOWN_STRING ((ULONG)0x40010003L)
//
// MessageId: IMPERSONATING_WORKER_THREAD
//
// MessageText:
//
//
// A worker thread is impersonating another process. The work item forgot to
// disable impersonation before it returned.
//
#define IMPERSONATING_WORKER_THREAD ((ULONG)0x000000DFL)
//
// MessageId: ACPI_BIOS_FATAL_ERROR
//
// MessageText:
//
//
// Your computer (BIOS) has reported that a component in your system is faulty and
// has prevented Windows from operating. You can determine which component is
// faulty by running the diagnostic disk or tool that came with your computer.
//
// If you do not have this tool, you must contact your system vendor and report
// this error message to them. They will be able to assist you in correcting this
// hardware problem thereby allowing Windows to operate.
//
#define ACPI_BIOS_FATAL_ERROR ((ULONG)0x000000E0L)
//
// MessageId: WORKER_THREAD_RETURNED_AT_BAD_IRQL
//
// MessageText:
//
// WORKER_THREAD_RETURNED_AT_BAD_IRQL
//
#define WORKER_THREAD_RETURNED_AT_BAD_IRQL ((ULONG)0x000000E1L)
//
// MessageId: MANUALLY_INITIATED_CRASH
//
// MessageText:
//
//
// The end-user manually generated the crashdump.
//
#define MANUALLY_INITIATED_CRASH ((ULONG)0x000000E2L)
//
// MessageId: RESOURCE_NOT_OWNED
//
// MessageText:
//
//
// A thread tried to release a resource it did not own.
//
#define RESOURCE_NOT_OWNED ((ULONG)0x000000E3L)
//
// MessageId: WORKER_INVALID
//
// MessageText:
//
//
// A executive worker item was found in memory which must not contain such
// items. Usually this is memory being freed. This is usually caused by
// a device driver that has not cleaned up properly before freeing memory.
//
#define WORKER_INVALID ((ULONG)0x000000E4L)
/*
DTC added this message but that goes against MUI so we comment it out here
and add #define POWER_FAILURE_SIMULATE E5 to bugcheck.c make sure you skip E5
just in case cluster actually makes use of it.
MessageId=0x00E5 Facility=Kernel Severity=Fatal SymbolicName=POWER_FAILURE_SIMULATE
Language=English
.
*/
#endif // _BUGCODES_
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -