WindowsAdvanced

How to Fix 0x00000131 INVALID_EXTENDED_PROCESSOR_STATE Blue Screen Error in Windows

Quick Answer 0x00000131 INVALID_EXTENDED_PROCESSOR_STATE is a Windows Blue Screen of Death (BSOD) error indicating that Windows detected an invalid combinati...

Bison Technical Team Enterprise IT specialists

Updated 10 Nov 2026 17 min read 0 total views

Structured technical guidanceSafety notes included where requiredSources listed below

Quick Answer

0x00000131 INVALID_EXTENDED_PROCESSOR_STATE is a Windows Blue Screen of Death (BSOD) error indicating that Windows detected an invalid combination of parameters while saving or restoring extended processor state.

Extended processor state refers to additional CPU execution-state information used by the operating system and processor-related software. Windows uses specific kernel routines to manage this state during thread execution and context switching.

Microsoft documents this bug check as a processor-state management failure. Its parameters identify the type of validity check that failed, including an invalid processor feature mask, an incorrect interrupt request level (IRQL), or an attempt to restore processor state associated with a different thread or execution level.

This error is primarily relevant to Windows kernel-mode developers and driver developers. For ordinary users, the appropriate troubleshooting approach is to investigate recent driver changes, Windows updates, firmware, processor configuration and the crash dump rather than assuming that the CPU itself is defective.

What Is INVALID_EXTENDED_PROCESSOR_STATE (0x00000131)?

INVALID_EXTENDED_PROCESSOR_STATE is a Windows bug check that occurs when the operating system detects an invalid operation involving extended processor state.

The processor maintains execution information that Windows must preserve and restore when switching between threads or performing other kernel operations. Extended processor state can include additional processor register information and supported processor features.

Windows provides kernel mechanisms that allow authorized kernel-mode components to save and restore this information under specific conditions. These operations must follow the processor-state management rules defined by Windows.

If a kernel-mode component violates these rules, Windows can detect the invalid operation and stop the system using bug check 0x00000131.

The technical details are documented by Microsoft in its Bug Check 0x131: INVALID_EXTENDED_PROCESSOR_STATE reference.

Error Identification

Property	Details
Bug Check Code	0x00000131
Symbolic Name	INVALID_EXTENDED_PROCESSOR_STATE
Error Category	Windows Kernel Bug Check
Related Component	Extended Processor State Management
Operating System	Windows
Typical Error Display	Your device ran into a problem and needs to restart.

What Does Extended Processor State Mean?

Modern processors maintain more execution information than the basic general-purpose registers used by traditional processor operations.

Depending on the processor architecture and supported features, extended processor state can include information associated with floating-point operations, vector processing and other processor capabilities.

Windows must preserve the appropriate processor state when a thread stops executing and restore it when that thread resumes.

Why Is Processor State Important?

Consider a system running multiple applications simultaneously. Windows regularly switches processor execution between different threads.

During these operations, the operating system must ensure that each thread resumes with its correct execution context. If processor state is saved or restored incorrectly, one thread could receive invalid execution information.

Windows enforces rules governing these operations to maintain system stability. Bug check 0x00000131 indicates that one of these rules was violated.

What Causes the 0x00000131 Blue Screen Error?

Microsoft's documentation defines the conditions that trigger this bug check, but it does not identify one universal hardware or software cause.

The actual source must be determined by examining the bug check parameters, memory dump, loaded drivers and recent system changes.

The following are areas worth investigating when this error occurs.

1. Faulty or Incompatible Kernel-Mode Drivers

Kernel-mode drivers operate with elevated privileges and can interact directly with operating system components and hardware.

A driver that incorrectly manages processor execution state or violates the required kernel calling rules may contribute to this type of failure.

Investigate recently installed or updated drivers, particularly when the blue screen began immediately after a driver change.

2. Processor-Related Software

Software that interacts with processor capabilities or execution-state management may require investigation.

This can include certain low-level system utilities, virtualization components and specialized hardware drivers. However, their presence alone does not establish that they caused the error.

3. BIOS or UEFI Firmware Issues

BIOS or UEFI firmware initializes the processor and provides the platform environment required by Windows.

Firmware compatibility problems or incorrect processor configuration may be relevant in some system-specific investigations.

Check for manufacturer-documented firmware updates, particularly when the problem started after a hardware change or firmware modification.

4. Processor Overclocking or Undervolting

Overclocking, undervolting and modified processor settings can introduce system instability.

Although Microsoft does not identify these settings as direct causes of bug check 0x00000131, they should be considered during troubleshooting when the system uses non-default processor settings.

5. Memory or Hardware Instability

Unstable RAM, motherboard problems or other hardware faults can sometimes produce corrupted system information and unpredictable crashes.

However, the 0x00000131 code does not independently prove that memory or the processor is defective. Hardware testing should be based on additional diagnostic evidence.

6. Windows or Driver Compatibility Problems

A Windows update, driver update or platform configuration change may expose a problem in a kernel-mode component.

Check whether the error started after a particular update, hardware installation or software deployment. This timeline can help narrow down the investigation.

Common Symptoms of INVALID_EXTENDED_PROCESSOR_STATE

A system experiencing bug check 0x00000131 may display one or more of the following symptoms:

A sudden Blue Screen of Death (BSOD).
The computer automatically restarts after displaying the stop code.
Unexpected crashes during normal Windows operation.
Repeated system crashes after startup.
Crashes occurring during specific workloads or applications.
Unexpected restarts following a driver or firmware update.
Multiple crash dump files appearing in the Windows Minidump folder.

These symptoms are not exclusive to this bug check. The displayed stop code and crash dump should be examined to confirm the actual error.

Understanding the 0x00000131 Bug Check Parameters

The four bug check parameters provide important diagnostic information. Microsoft specifies that Parameter 1 identifies which validity check failed, while the meanings of the remaining parameters depend on that value.

Examining these parameters can help kernel developers and experienced technicians understand the circumstances of the failure.

Parameter 1: Value 0

This condition indicates that an invalid feature mask was passed or extended processor state was not enabled.

Parameter	Meaning
Parameter 1	0 – Invalid feature mask or extended state not enabled
Parameter 2	Nonzero if extended state is enabled
Parameter 3	Low 32 bits of the feature mask
Parameter 4	High 32 bits of the feature mask

Parameter 1: Value 1

This condition indicates that an attempt to save or restore extended processor state was made at an interrupt request level (IRQL) higher than DISPATCH_LEVEL.

Parameter	Meaning
Parameter 1	1 – Invalid IRQL condition
Parameter 2	The IRQL at which the operation was attempted
Parameter 3	Reserved
Parameter 4	Reserved

IRQL is a Windows kernel mechanism that determines the priority level at which kernel operations execute. Certain processor-state operations are not permitted above their documented IRQL limits.

Parameter 1: Value 2

This condition indicates that the previously saved processor state belongs to an equal or higher execution level than the current level.

Parameter	Meaning
Parameter 1	2 – Invalid saved-state level relationship
Parameter 2	The saved level
Parameter 3	The current level
Parameter 4	Reserved

Parameter 1: Value 3

This condition indicates that the previously saved processor state belongs to a different thread from the thread currently attempting to use it.

Parameter	Meaning
Parameter 1	3 – Saved state belongs to a different thread
Parameter 2	The saved thread
Parameter 3	The current thread
Parameter 4	Reserved

Parameter 1: Value 4

This condition indicates that the previously saved processor state belongs to a different execution level.

Parameter	Meaning
Parameter 1	4 – Saved state belongs to a different level
Parameter 2	The saved level
Parameter 3	The current level
Parameter 4	Reserved

Important: These parameter definitions come from Microsoft's official bug check documentation. They describe the detected violation, not necessarily the original faulty driver or hardware component.

How to Fix 0x00000131 INVALID_EXTENDED_PROCESSOR_STATE

There is no single confirmed fix for every occurrence of this error. The appropriate solution depends on the failed validity check and the component responsible for the invalid operation.

Follow the troubleshooting steps below, beginning with the least disruptive actions.

1. Restart Windows and Check Whether the Error Repeats

If the blue screen occurred only once, restart the computer and observe its behaviour.

Allow Windows to restart normally.
Check whether the desktop loads successfully.
Use the computer normally and observe whether the same stop code appears again.
Record the error code if another crash occurs.

A single occurrence does not necessarily indicate permanent hardware damage. However, repeated crashes require further investigation.

2. Disconnect Recently Added Hardware

If the problem started after installing new hardware, temporarily disconnect the newly added component where it is safe to do so.

Shut down the computer completely.
Disconnect recently added external devices or expansion hardware, following the manufacturer's instructions.
Restart Windows.
Check whether the blue screen occurs again.

For internal hardware, switch off and disconnect power before making any changes. If the component requires specialist installation, contact a qualified technician.

3. Update or Roll Back Device Drivers

Driver investigation is particularly important because kernel-mode drivers can interact with processor-state management.

Right-click the Start button.
Select Device Manager.
Expand the relevant hardware categories.
Identify devices whose drivers were recently installed or updated.
Check the hardware manufacturer's website for a compatible driver.
Install the appropriate driver if an update is available.

If the problem started immediately after a driver update, consider reverting to the previous driver version.

To roll back a driver:

Open Device Manager.
Right-click the affected device.
Select Properties.
Open the Driver tab.
Select Roll Back Driver, if available.
Follow the instructions and restart the computer.

Do not randomly uninstall system-critical drivers. If the problematic driver is unclear, examine the crash dump before removing components.

4. Install Available Windows Updates

Windows updates may include operating system fixes, compatibility improvements and driver-related changes.

Press Windows + I to open Settings.
Select Windows Update.
Click Check for updates.
Install applicable updates.
Restart the computer when requested.

If the error began immediately after a particular Windows update, investigate whether Microsoft or the device manufacturer has documented a related issue before attempting to remove that update.

5. Reset Processor Settings to Default

If the processor or memory configuration has been modified, temporarily return the system to its standard manufacturer-supported settings.

Review settings such as:

CPU overclocking.
CPU undervolting.
Modified processor voltage.
Non-default memory overclocking profiles such as XMP or EXPO.
Other manually modified firmware performance settings.

Enter the BIOS or UEFI setup and restore the relevant settings to their normal defaults.

Before changing firmware settings, document the existing configuration. On business systems, consult the system administrator because firmware changes can affect boot configuration, encryption recovery and system security.

Do not update or reset the BIOS without checking the manufacturer's instructions and applicable recovery requirements.

6. Check BIOS and UEFI Firmware Updates

Outdated or incompatible firmware may be relevant when a crash begins after a processor, motherboard or platform change.

Identify the computer or motherboard manufacturer and exact model.
Visit the manufacturer's official support website.
Locate the BIOS or UEFI firmware section.
Review available updates and their release notes.
Check whether an update addresses a relevant processor, compatibility or stability issue.
Follow the manufacturer's firmware update instructions if an applicable update is available.

Warning: An interrupted firmware update can make a computer unusable. Use the correct firmware package, maintain stable power and do not interrupt the update process.

7. Test System Memory

Although bug check 0x00000131 does not specifically identify defective RAM, memory instability can complicate crash diagnosis.

Windows Memory Diagnostic can perform a basic memory test.

Press Windows + R.
Type mdsched.exe.
Press Enter.
Select Restart now and check for problems.
Allow the diagnostic test to complete.
After Windows restarts, review the diagnostic results.

If errors are detected, further testing may be required to identify the affected memory module, slot or memory configuration.

For systems experiencing repeated crashes, a qualified technician may perform additional memory and hardware diagnostics.

8. Start Windows in Safe Mode

If the computer repeatedly crashes during normal startup, Safe Mode can help isolate problems involving non-essential drivers and services.

Safe Mode starts Windows with a limited set of files and drivers.

Open Windows Recovery Environment (WinRE).
Select Troubleshoot.
Select Advanced options.
Open Startup Settings.
Click Restart.
Press 4 or F4 for Safe Mode.

If Windows does not boot normally, WinRE may be available after Windows detects repeated startup failures. Recovery can also be accessed using compatible Windows installation or recovery media.

If the system remains stable in Safe Mode, investigate third-party drivers, services and recently installed software. This observation helps narrow down the problem but does not independently identify the faulty component.

For additional instructions, refer to Microsoft's Windows Startup Settings documentation.

Advanced Troubleshooting Using Windows Memory Dump Files

If the error continues after basic troubleshooting, analyzing the crash dump is one of the most useful ways to investigate the underlying failure.

A memory dump records information about the system at the time of the crash. Depending on the dump type, it may contain information about the processor state, loaded drivers, kernel memory and the failing execution path.

1. Locate the Windows Minidump Files

Windows may automatically create a small memory dump after a blue screen.

Check the following directory:

C:\Windows\Minidump

For a kernel or automatic memory dump, check:

C:\Windows\MEMORY.DMP

If these files do not exist, verify the crash dump configuration.

2. Configure Windows to Create Memory Dumps

Press Windows + R.
Type sysdm.cpl and press Enter.
Open the Advanced tab.
Under Startup and Recovery, select Settings.
Locate the Write debugging information section.
Select Automatic memory dump or another suitable dump type.
Verify that the system drive has sufficient free space and that the page file is configured appropriately.
Click OK to save the changes.

Windows may require a restart for the configuration to take effect.

3. Analyze the Dump Using WinDbg

WinDbg is Microsoft's debugging tool for examining Windows crash dumps and kernel failures.

Follow these steps:

Install WinDbg from the official Microsoft source.
Open WinDbg.
Select the option to open a crash dump file.
Browse to the relevant file in the Minidump folder or open MEMORY.DMP.
Wait for the debugger to load the dump and available symbols.
Enter the following command in the debugger command window:

!analyze -v

This command requests a detailed analysis of the current bug check.

Review the following information where available:

BUGCHECK_CODE: Confirms the stop code.
BUGCHECK_P1 to BUGCHECK_P4: Shows the bug check parameters.
MODULE_NAME: Identifies a module associated with the analysis.
IMAGE_NAME: Identifies a relevant image or driver.
STACK_TEXT: Shows the recorded execution stack.
FAILURE_BUCKET_ID: Provides a crash classification used during analysis.

These fields are diagnostic clues, not automatic proof of responsibility. For example, a Microsoft kernel module appearing in a crash analysis does not necessarily mean that the Microsoft component is defective. A third-party driver may have caused an earlier invalid operation.

4. Examine the Bug Check Parameters

Pay particular attention to Parameter 1.

Its value identifies the validity check that failed:

0 – Invalid feature mask or extended state not enabled.
1 – Extended-state operation attempted above the permitted IRQL.
2 – Invalid relationship between saved and current execution levels.
3 – Saved processor state belongs to a different thread.
4 – Saved processor state belongs to a different level.

The remaining parameters must be interpreted according to the applicable Parameter 1 value. They should not be treated as four interchangeable numeric fields.

5. Review the Driver Call Stack

Examine the stack trace to identify which kernel routines and drivers were involved in the failing execution path.

Look for:

Third-party driver names.
Recently updated driver modules.
Repeated appearances of the same driver across multiple crash dumps.
Unexpected execution paths involving processor-state operations.

Compare multiple dump files if the computer has experienced repeated crashes. Consistent evidence across several failures can help identify a common component.

For additional information, refer to Microsoft's WinDbg !analyze documentation and Advanced Troubleshooting for Stop Code Errors.

Using Driver Verifier for Advanced Driver Investigation

Driver Verifier is a Windows diagnostic utility that checks the behaviour of kernel-mode drivers against specified operating system requirements.

It can help identify certain driver violations that may otherwise be difficult to reproduce or diagnose.

However, Driver Verifier is an advanced diagnostic tool and should not be enabled casually on a business-critical or production computer.

Important Precautions

Driver Verifier can intentionally trigger additional blue screen errors.
It can significantly affect system performance.
Incorrect configuration can make Windows difficult to start.
It should not be enabled for every driver without a specific diagnostic reason.
Before using it, ensure that important data is backed up and that a recovery method is available.

Experienced technicians can use it to investigate suspicious third-party drivers identified through crash analysis.

If Driver Verifier causes startup problems, it may be possible to disable it through Safe Mode or Windows Recovery Environment, depending on the system configuration.

For complete instructions and limitations, consult Microsoft's Driver Verifier documentation.

When Should You Contact a Hardware or Software Manufacturer?

Professional support may be necessary when the error continues despite basic troubleshooting or when the available diagnostic evidence indicates a deeper kernel or platform problem.

Contact the appropriate manufacturer or technical support provider when:

The same stop code repeatedly occurs after driver updates and configuration checks.
Crash dumps consistently identify a particular third-party driver.
The error started after a BIOS, firmware or processor platform update.
Memory or hardware diagnostics report errors.
The computer cannot boot into Windows normally.
The problem affects business-critical systems or production workloads.

Provide the following information when requesting assistance:

Exact stop code: 0x00000131.
All four bug check parameters.
Windows version and build number.
Computer model and processor information.
Recently installed hardware and software.
Driver and firmware update history.
Relevant memory dump files.
Actions that consistently reproduce the error, if known.

Do not publicly upload complete memory dumps without reviewing their contents. Depending on the dump type, they may contain sensitive system information.

How to Prevent INVALID_EXTENDED_PROCESSOR_STATE Errors

Although this bug check cannot be prevented through a single setting, appropriate system maintenance and controlled configuration changes can reduce the likelihood of recurring system instability.

Install compatible drivers from official hardware manufacturers.
Keep Windows updated with applicable security and reliability updates.
Install BIOS and firmware updates only when appropriate for the hardware.
Avoid unsupported CPU overclocking and undervolting configurations.
Use manufacturer-supported processor and memory settings.
Investigate recurring crashes rather than repeatedly restarting the computer without diagnosis.
Maintain regular backups of important files.
Test new drivers and firmware changes before deploying them across business systems.
Monitor system stability after significant hardware or software modifications.

Frequently Asked Questions

1. What does stop code 0x00000131 mean?

Stop code 0x00000131, also known as INVALID_EXTENDED_PROCESSOR_STATE, means Windows detected an invalid condition while saving or restoring extended processor state. It is a kernel-level bug check involving processor-state management.

2. Is INVALID_EXTENDED_PROCESSOR_STATE a CPU hardware failure?

Not necessarily. The error indicates a violation of processor-state management rules, but it does not automatically mean that the physical CPU is defective. A driver or other kernel-mode component may be responsible. Hardware instability should be investigated when supported by additional diagnostic evidence.

3. Can a faulty driver cause error 0x00000131?

A faulty or incompatible kernel-mode driver is an important area to investigate because drivers can interact with Windows processor-state management. However, the specific responsible driver must be identified through crash dump analysis and other diagnostic evidence.

4. What does Parameter 1 mean in bug check 0x131?

Parameter 1 identifies the failed validity check. Values from 0 through 4 describe conditions involving invalid feature masks, IRQL restrictions, execution levels and thread ownership of previously saved processor state.

5. Can updating BIOS fix INVALID_EXTENDED_PROCESSOR_STATE?

A BIOS or UEFI update may help if the manufacturer has documented a relevant processor compatibility or platform stability issue. However, firmware updates are not a guaranteed solution for this bug check and should only be installed when appropriate for the system.

6. How do I identify the driver responsible for this BSOD?

Locate the crash dump in C:\Windows\Minidump or C:\Windows\MEMORY.DMP. Open it with WinDbg and execute !analyze -v. Review the bug check parameters, module information and execution stack. A qualified technician may need to perform additional kernel debugging.

7. Is it safe to use Driver Verifier to fix this error?

Driver Verifier is a diagnostic utility, not a repair tool. It can intentionally trigger crashes to expose driver violations. Use it only when investigating specific drivers and when a recovery method is available.

8. Will reinstalling Windows solve error 0x00000131?

Reinstalling Windows is not a guaranteed solution. If an incompatible driver, firmware issue or hardware instability is responsible, the problem may return after reinstallation. Investigate the crash dump and recent system changes before considering a clean installation.

9. Where can I find Windows blue screen dump files?

Small memory dumps are normally stored in C:\Windows\Minidump. Kernel, automatic and complete memory dumps are normally stored as C:\Windows\MEMORY.DMP, depending on the configured dump type.

10. What should I do if Windows repeatedly crashes with this stop code?

Start with Safe Mode if necessary, investigate recent driver and hardware changes, check processor settings and firmware, and collect the crash dump files. If the crashes continue, have the dump files analyzed by a qualified Windows kernel debugging technician or contact the relevant hardware or software manufacturer.

Key Takeaways

The 0x00000131 INVALID_EXTENDED_PROCESSOR_STATE blue screen error indicates that Windows detected an invalid operation involving extended processor state management.

The bug check parameters provide specific information about the failed validity check, including feature-mask validation, IRQL restrictions, saved execution levels and thread ownership.

For ordinary users, the most useful initial actions are to investigate recent driver changes, check Windows updates, review processor configuration and examine applicable firmware updates. For recurring failures, memory dump analysis with WinDbg provides a more reliable way to identify the underlying problem.

Because this is a kernel-level error, avoid assuming that the processor must be replaced or that reinstalling Windows will automatically resolve it. Identify the actual source of the invalid operation before making major hardware or software changes.

Official References

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.