Mmpool Driver Is Corrupted
- TechNet Blogs The troubleshooters and problem solvers You got a B.S.O.D. Blue Screen of Death, known as Bug Checks, now what.
- The MACHINE_CHECK_EXCEPTION bug check has a value of 0x0000009C. This bug check indicates that a fatal machine check exception has occurred.
- John Carrona,BSOD crash analysis support, BSOD debugging and error reports and help for Microsoft Windows Operating Systems, driver research,crash dump analysis.
STOP 메시지 일반적인 해결방법 블루스크린 참고사이트입니다.. STOP: 0x0000000A 메시지해결 knowledge base.
ブルースクリーンエラー バグチェックコードstop 0x000000d1 driver_irql_not_less_or_equalエラーの解説 driver_irql_not_less_or_equalは.
Subscribe to the RSS feed Last updated: 22 Oct 2015 bugcodes.txt Win10 SDK BugChecks and what to do about them: Bugchecks with no descriptions are either.
You got a B.S.O.D. (Blue Screen of Death, known as Bug Checks), now what?
The MACHINE_CHECK_EXCEPTION bug check has a value of 0x0000009C. This bug check indicates that a fatal machine check exception has occurred.
Important This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see
Troubleshoot blue screen errors.
MACHINE_CHECK_EXCEPTION Parameters
The four parameters that are listed in the message have different meanings, depending on the processor type.
If the processor is based on an older x86-based architecture and has the Machine Check Exception MCE feature but not the Machine Check Architecture MCA feature for example, the Intel Pentium processor, the parameters have the following meaning.
The low 32 bits of P5_MC_TYPE Machine Service Report MSR
The address of the MCA_EXCEPTION structure
The high 32 bits of P5_MC_ADDR MSR
The low 32 bits of P5_MC_ADDR MSR
If the processor is based on a newer x86-based architecture and has the MCA feature and the MCE feature for example, any Intel Processor of family 6 or higher, such as Pentium Pro, Pentium IV, or Xeon, or if the processor is an x64-based processor, the parameters have the following meaning.
The high 32 bits of MCi_STATUS MSR for the MCA bank that had the error
The low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
On an Itanium-based processor, the parameters have the following meaning.
Note Parameter 1 indicates the type of violation.
Parameter 1Parameter 2Parameter 3Parameter 4Cause
The system abstraction layer SAL returned an error for SAL_GET_STATEINFO while processing MCA.
SAL returned an error for SAL_CLEAR_STATEINFO while it processed MCA.
Firmware FW reported a fatal MCA.
There are two possible causes:
SAL reported a recoverable MCA, but this recovery is not currently supported.
SAL generated an MCA but could not produce an error record.
SAL returned an error for SAL_GET_STATEINFO while processing an INIT event.
SAL returned an error for SAL_CLEAR_STATEINFO while it processed an INIT event.
In Windows Vista and later operating systems, this bug check occurs only in the following circumstances.
WHEA is not fully initialized.
All processors that rendezvous have no errors in their registers.
For other circumstances, this bug check has been replaced with bug Check 0x124: WHEA_UNCORRECTABLE_ERROR in Windows Vista and later operating systems.
For more information about Machine Check Architecture MCA, see the Intel or AMD Web sites.
For example, when you get a Stop A. What do those Arguments mean.
Once you install the Debugging Tools for Windows, which is available from here:
Download and Install Debugging Tools for Windows
Arguments 00000000 00000018 00000000 00000002 00000000 00000000 fffff802 d154b7bf
The arguments are Parameters that can be passed.
In the example above, we got a Stop A. You could use the Debugger.CHM file to find out what the Arguments/Parameters mean for that specific bug check.
Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
4 Address which referenced memory
I m also able to get this information by typing . analyze -show A
An attempt was made to access a pageable or completely invalid address at an
interrupt request level IRQL that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: 0000000000000000, memory referenced
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 read operation, 1 write operation
bit 3 : value 0 not an execute operation, 1 execute operation only on chips which support this level of status
Arg4: 0000000000000000, address which referenced memory
Based on this information, I know that in the example above for my Stop A:
And the address which referenced memory was fffff802 d154b7bf.
The nice thing about the Debugger.CHM and the MSDN library link below is that they list the common
This has all the list of every single bug check code that we have:
0x00000001 APC_INDEX_MISMATCH
INVALID_PROCESS_ATTACH_ATTEMPT
INVALID_PROCESS_DETACH_ATTEMPT
NO_EXCEPTION_HANDLING_SUPPORT
MAXIMUM_WAIT_OBJECTS_EXCEEDED
CREATE_DELETE_LOCK_NOT_LOCKED
LAST_CHANCE_CALLED_FROM_KMODE
KERNEL_APC_PENDING_DURING_EXIT
UNEXPECTED_INITIALIZATION_CALL
DEVICE_REFERENCE_COUNT_NOT_ZERO
INTERRUPT_EXCEPTION_NOT_HANDLED
MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
MULTIPLE_IRP_COMPLETE_REQUESTS
CANCEL_STATE_IN_COMPLETED_IRP
PAGE_FAULT_WITH_INTERRUPTS_OFF
IRQL_GT_ZERO_AT_SYSTEM_SERVICE
INSTRUCTION_COHERENCY_EXCEPTION
SECURITY_INITIALIZATION_FAILED
PROCESS_INITIALIZATION_FAILED
OBJECT1_INITIALIZATION_FAILED
SECURITY1_INITIALIZATION_FAILED
SYMBOLIC_INITIALIZATION_FAILED
MEMORY1_INITIALIZATION_FAILED
PROCESS1_INITIALIZATION_FAILED
SESSION1_INITIALIZATION_FAILED
SESSION2_INITIALIZATION_FAILED
SESSION3_INITIALIZATION_FAILED
SESSION4_INITIALIZATION_FAILED
SESSION5_INITIALIZATION_FAILED
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KERNEL_MODE_EXCEPTION_NOT_HANDLED
SESSION_HAS_VALID_POOL_ON_EXIT
VIDEO_DRIVER_DEBUG_REPORT_REQUEST
SESSION_HAS_VALID_VIEWS_ON_EXIT
NETWORK_BOOT_INITIALIZATION_FAILED
NETWORK_BOOT_DUPLICATE_ADDRESS
ATTEMPTED_WRITE_TO_READONLY_MEMORY
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
DRIVER_VERIFIER_DETECTED_VIOLATION
DRIVER_CAUGHT_MODIFYING_FREED_POOL
DRIVER_VERIFIER_IOMANAGER_VIOLATION
DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
PAGE_FAULT_IN_FREED_SPECIAL_POOL
PAGE_FAULT_BEYOND_END_OF_ALLOCATION
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
DRIVER_IRQL_NOT_LESS_OR_EQUAL
DRIVER_PORTION_MUST_BE_NONPAGED
SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
DRIVER_UNMAPPING_INVALID_VIEW
LOCKED_PAGES_TRACKER_CORRUPTION
WORKER_THREAD_RETURNED_AT_BAD_IRQL
DRIVER_VERIFIER_DMA_VIOLATION
ACTIVE_EX_WORKER_THREAD_TERMINATION
THREAD_STUCK_IN_DEVICE_DRIVER
DIRTY_MAPPED_PAGES_CONGESTION
SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT
SCSI_VERIFIER_DETECTED_VIOLATION
PCI_VERIFIER_DETECTED_VIOLATION
RAMDISK_BOOT_INITIALIZATION_FAILED
DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
DIRTY_NOWRITE_PAGES_CONGESTION
THIRD_PARTY_FILE_SYSTEM_FAILURE
CRITICAL_STRUCTURE_CORRUPTION
APP_TAGGING_INITIALIZATION_FAILED
FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION
VIDEO_MEMORY_MANAGEMENT_INTERNAL
RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED
VIDEO_SHADOW_DRIVER_FATAL_ERROR
VIDEO_SCHEDULER_INTERNAL_ERROR
DRIVER_RETURNED_HOLDING_CANCEL_LOCK
ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE
FAULTY_HARDWARE_CORRUPTED_PAGE
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
UNEXPECTED_KERNEL_MODE_TRAP_M
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
THREAD_STUCK_IN_DEVICE_DRIVER_M
STATUS_CANNOT_LOAD_REGISTRY_FILE
STATUS_SYSTEM_PROCESS_TERMINATED
STATUS_IMAGE_CHECKSUM_MISMATCH
Bug Check 0x9C: MACHINE_CHECK_EXCEPTION
다음은, 일명 공포의 블루 스크린이나 메모리 덤프시에 기록 되는 버그 체크 코드 목록 입니다. 주로 몇 십개 정도만 자주.
