| Previous | Next |
| VHD_BOOT_INITIALIZATION_FAILED | INVALID_EXTENDED_PROCESSOR_STATE |
DYNAMIC_ADD_PROCESSOR_MISMATCH
The DYNAMIC_ADD_PROCESSOR_MISMATCH bug check has a value of 0x00000130. This bugcheck indicates that a new processor added to the system is incompatible with the current configuration.
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.
DYNAMIC_ADD_PROCESSOR_MISMATCH Parameters
None
Dump evidence for DYNAMIC_ADD_PROCESSOR_MISMATCH
For DYNAMIC_ADD_PROCESSOR_MISMATCH, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “DYNAMIC_ADD_PROCESSOR_MISMATCH”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for DYNAMIC_ADD_PROCESSOR_MISMATCH
- Run WinDbg
!analyze -v, then inspect the documented meaning of each DYNAMIC_ADD_PROCESSOR_MISMATCH parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with dynamic / add / processor / mismatch.
- For DYNAMIC_ADD_PROCESSOR_MISMATCH, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by DYNAMIC_ADD_PROCESSOR_MISMATCH before collecting the dump and event logs. For DYNAMIC_ADD_PROCESSOR_MISMATCH, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.