WHEA_INTERNAL_ERROR (0x00000122) – Causes, Diagnosis and Troubleshooting Guide

Quick Answer

WHEA_INTERNAL_ERROR (0x00000122) is a Windows Stop error indicating that an internal failure occurred within the Windows Hardware Error Architecture (WHEA). WHEA is responsible for handling hardware error information reported by the processor, chipset, firmware and other platform components.

According to Microsoft, this bug check can occur because of problems in a vendor-provided Platform-Specific Hardware Error Driver (PSHED) plug-in, firmware handling of hardware error records, or firmware-based error injection.

Unlike some other hardware-related blue screen errors, WHEA_INTERNAL_ERROR does not automatically establish that a physical hardware component is defective. The actual failure must be investigated using the bug check parameters, Windows crash dump, firmware information and system diagnostic records.

The recommended approach is to preserve the crash dump, identify the failing WHEA initialization or error-handling operation, check firmware and vendor platform components, and investigate any recent hardware or configuration changes.

What Is WHEA_INTERNAL_ERROR (0x00000122)?

WHEA_INTERNAL_ERROR is a Windows bug check, also known as a Blue Screen of Death (BSOD) or Stop error. Its hexadecimal bug check value is 0x00000122.

WHEA stands for Windows Hardware Error Architecture. It is a Windows framework that collects, processes and reports hardware error information. It allows Windows and platform firmware to communicate about hardware failures through standardized error records and platform-specific interfaces.

The WHEA framework supports error reporting from several hardware sources, including:

• Processor machine check exceptions.
• Corrected and uncorrected processor errors.
• PCI Express hardware errors.
• Platform-reported hardware errors.
• Firmware-reported hardware conditions.
• Other hardware error sources supported by the platform.

WHEA_INTERNAL_ERROR specifically indicates an internal problem in the WHEA error-handling infrastructure. It is not simply another name for a CPU failure or faulty RAM.

Microsoft documents this stop code primarily for developers and platform manufacturers. Therefore, diagnosing it often requires Windows debugging tools and information from the computer manufacturer.

Understanding Windows Hardware Error Architecture (WHEA)

WHEA provides a common framework for Windows to receive and process hardware error information. It works with hardware, firmware and platform-specific software to make error information available to the operating system.

Main WHEA Components

• WHEA: The Windows framework responsible for managing hardware error reporting and processing.
• PSHED: The Platform-Specific Hardware Error Driver. It provides an interface between Windows and platform-specific hardware error handling implemented by the system manufacturer.
• Firmware: System firmware can provide hardware error information and implement platform-specific error reporting functionality.
• Hardware error sources: These include processors, PCI Express devices and other supported platform components that report hardware errors.
• Error records: Structured information describing an error, its source and other diagnostic details.

A problem in the interaction between these components can prevent WHEA from correctly initializing or processing hardware error information.

Symptoms of WHEA_INTERNAL_ERROR

When Windows encounters bug check 0x122, the system may display a blue screen and restart automatically, depending on its startup and recovery configuration.

Common observable symptoms include:

• A blue screen displaying the Stop code WHEA_INTERNAL_ERROR.
• The bug check value 0x00000122 in diagnostic information.
• Unexpected system restarts during Windows startup.
• Repeated crashes during hardware initialization or system operation.
• Crash dump files being generated after the failure.
• Hardware Error Architecture or WHEA-related events appearing in diagnostic logs.

These symptoms are not sufficient to identify the exact defective component. A WHEA_INTERNAL_ERROR crash must be investigated using its bug check parameters and available diagnostic evidence.

Possible Causes of WHEA_INTERNAL_ERROR

Microsoft identifies several specific implementation and initialization problems that can cause this bug check.

1. PSHED Plug-in Implementation Problems

A vendor-provided Platform-Specific Hardware Error Driver (PSHED) plug-in may contain an implementation defect or fail to initialize an error source correctly.

Because PSHED connects the Windows hardware error framework to platform-specific functionality, an issue in this component can interfere with hardware error reporting.

2. Firmware Implementation Errors

System firmware is involved in reporting and describing certain hardware errors. Problems in the firmware implementation of hardware error records can cause WHEA to encounter internal failures.

BIOS or UEFI firmware problems should be investigated, particularly when the issue began after a firmware update, hardware replacement or platform configuration change.

3. Firmware Error Injection Problems

Hardware error injection is a platform capability used in testing and validation to simulate hardware errors. Microsoft identifies problems in firmware implementations of error injection as another possible source of this bug check.

This cause is particularly relevant to platform developers, hardware manufacturers and systems undergoing hardware error validation. It should not be assumed to be the cause on an ordinary desktop computer.

4. WHEA Initialization and Memory Allocation Failures

Several WHEA_INTERNAL_ERROR parameter combinations indicate that Windows could not allocate the memory required for WHEA initialization or error handling.

Examples include failures to allocate memory for:

• Hardware error source descriptors.
• WHEA information blocks for individual processors.
• Hardware error source tables.
• Individual error records.

These failures identify the operation that could not be completed. They do not necessarily establish that the installed RAM is physically defective.

5. Hardware Error Source Initialization Failures

WHEA may fail while initializing a particular error source or processing an error reported by a platform component.

The error source type and source ID in the bug check parameters can help narrow down the investigation.

WHEA_INTERNAL_ERROR Bug Check Parameters

Bug check 0x122 uses four parameters. Microsoft documents the following parameter combinations and their meanings.

Parameter 1	Parameter 2	Parameter 3	Parameter 4	Documented Meaning
0x1	Size of memory	Error source count	0	Insufficient memory allocation for all error sources in the hardware error source table.
0x2	Number of processors	0	0	Insufficient memory allocation for a WHEA information block for each processor.
0x5	Status	Initialization phase	0	Memory allocation failure for error sources or failure during error source enumeration.
0x6	Status	Initialization phase	Error source type	Failure to initialize the specified error source during the indicated phase.
0x7	Status	0	0	Memory allocation failure.
0x8	Number of error sources	0	0	Insufficient memory allocation for all error source descriptors.
0x9	Error source type	Source ID	0	WHEA received an uncorrected error from an invalid error source.
0xA	Error source type	Source ID	0	Failure to allocate an error record for an uncorrected error.
0xB	Error source type	Source ID	0	Failure to populate the error record for an uncorrected error.

Important: Parameter 1 identifies the documented failure category. The remaining parameters provide additional diagnostic information. Their interpretation should follow Microsoft's bug check documentation rather than assumptions based on their numerical values.

Understanding WHEA Error Source Types

When Parameter 1 is 0x6, 0x9, 0xA or 0xB, one of the other parameters contains an error source type.

Error Source Value	Description
0x00	Machine Check Exception
0x01	Corrected Machine Check
0x02	Corrected Platform Error
0x03	Non-Maskable Interrupt
0x04	PCI Express Error
0x05	Other Error Sources / Generic
0x06	IA64 INIT Error Source
0x07	BOOT Error Source
0x08	SCI-Based Generic Error Source
0x09	Itanium Machine Check Abort
0x0A	Itanium Machine Check
0x0B	Itanium Corrected Platform Error

These are documented error source identifiers, not a list of defective hardware components. For example, a PCI Express error source indicates the category of the reported source; it does not automatically prove that the graphics card is defective.

How to Diagnose WHEA_INTERNAL_ERROR

Because this stop code can originate from WHEA, firmware or platform-specific implementations, identifying the underlying failure is more important than applying generic blue screen fixes.

Step 1: Record the Complete Stop Error Information

Before changing the system configuration, record the following information:

• Exact stop code: WHEA_INTERNAL_ERROR.
• Bug check value: 0x00000122.
• All four bug check parameters.
• Windows version and build number.
• Computer manufacturer and model.
• Processor and motherboard model, where applicable.
• Recent BIOS, firmware, driver or hardware changes.

The four bug check parameters are particularly important because they identify the documented WHEA failure category.

Step 2: Check Windows Event Viewer

Event Viewer can provide additional information about hardware errors and system failures recorded before or around the time of the crash.

1. Press Windows + R.
2. Type eventvwr.msc and press Enter.
3. Expand Windows Logs.
4. Select System.
5. Look for critical and error events around the time of the crash.
6. Check for relevant WHEA-Logger, Kernel-Power and other hardware-related entries.
7. Open relevant events and examine their General and Details information.

WHEA-Logger events may contain useful hardware error information. However, the presence of a Kernel-Power event, such as Event ID 41, generally records an unexpected shutdown and does not by itself identify the original cause.

Step 3: Locate the Windows Crash Dump

Windows may generate a crash dump when a bug check occurs. This file can contain information needed to investigate the failure.

Check these standard locations:

• C:\Windows\Minidump\ – Small memory dump files, if configured and successfully generated.
• C:\Windows\MEMORY.DMP – A kernel or complete memory dump, depending on the configured dump type.

If no dump file exists, check the Windows startup and recovery settings and ensure that the system drive has an appropriately configured paging file and sufficient free space. Some crashes may prevent dump generation.

Step 4: Analyze the Dump Using WinDbg

WinDbg is Microsoft's debugging tool for analyzing Windows crash dumps. It is particularly useful for examining bug check information and kernel-level failures.

1. Install WinDbg using Microsoft's official documentation.
2. Launch WinDbg.
3. Open the relevant crash dump using the File menu.
4. Allow symbols and debugging information to load.
5. Run the following command in the debugger command window:

!analyze -v

This command requests a detailed analysis of the crash dump. Review the bug check code, parameters, stack information and any additional diagnostic output.

For the specific bug check, Microsoft's debugger documentation also supports examining the code and parameters using:

!analyze -show 0x122

If the four parameters are available, they can also be supplied for a more specific description:

!analyze -show 0x122 Arg1 Arg2 Arg3 Arg4

Replace Arg1, Arg2, Arg3 and Arg4 with the actual hexadecimal values from the crash.

Important: The output of !analyze -v is diagnostic evidence, not an automatic confirmation that the module named in the report is defective. A kernel component may appear in a stack trace because it was handling an error originating elsewhere.

Step 5: Review Recent System Changes

Determine whether the crash started after any of the following:

• BIOS or UEFI firmware updates.
• Motherboard replacement or hardware upgrades.
• CPU or memory configuration changes.
• Installation of platform-specific drivers.
• Windows updates.
• Changes to virtualization or hardware error injection settings.
• Changes to overclocking, undervolting or memory profiles.

Correlating the first crash with a recent change can help narrow the investigation. Do not automatically roll back firmware or drivers without checking compatibility and the manufacturer's recovery procedure.

How to Fix WHEA_INTERNAL_ERROR (0x00000122)

There is no single guaranteed repair for WHEA_INTERNAL_ERROR. The appropriate corrective action depends on the failing parameter, firmware implementation, error source and system configuration.

Follow the steps below in order, beginning with low-risk checks.

Solution 1: Restart and Check Whether the Error Repeats

If the error occurred only once, restart Windows and observe whether the system operates normally.

• Record the crash information before restarting if possible.
• Check Event Viewer for related errors.
• Observe whether the crash happens during startup, under load or during normal operation.
• Do not assume that a successful restart means the underlying issue has been resolved.

If the system repeatedly crashes, preserve the available dump files and proceed with further diagnosis.

Solution 2: Install Manufacturer-Approved Platform Drivers

Check the computer or motherboard manufacturer's support website for the correct drivers for the exact model and Windows version.

Depending on the platform, relevant components may include:

• Chipset drivers.
• Platform management or system interface drivers.
• Processor-related platform drivers, where supplied by the manufacturer.
• Storage controller drivers.
• PCI Express device drivers.

Install only drivers applicable to the hardware and operating system. Avoid third-party driver-updater utilities that cannot establish the correct manufacturer-supported package.

If the error began immediately after a driver installation, investigate that specific change and consider the manufacturer's supported rollback procedure.

Solution 3: Check for BIOS or UEFI Firmware Updates

Firmware can be involved in hardware error source initialization and the creation of hardware error records. Therefore, a manufacturer-approved firmware update may be relevant when the failure is linked to a firmware implementation problem.

1. Identify the exact computer or motherboard model.
2. Visit the manufacturer's official support website.
3. Check the BIOS or UEFI release notes for relevant hardware, WHEA, stability or compatibility fixes.
4. Read the update instructions and prerequisites carefully.
5. Back up important data before proceeding.
6. Ensure that the computer has reliable power during the update.
7. Install the firmware only through the manufacturer's approved method.

Warning: An interrupted or incorrect firmware update can make a system unbootable. Do not install firmware intended for another motherboard revision or computer model. If the computer is business-critical or has firmware recovery restrictions, consult the manufacturer or qualified technician before updating.

Solution 4: Restore Unsupported CPU and Memory Overclocking

Although Microsoft identifies firmware and PSHED implementation problems as documented causes of this particular bug check, unstable hardware configurations should also be investigated when the crash began after tuning changes.

Where applicable:

1. Enter BIOS or UEFI setup using the manufacturer's instructions.
2. Identify any manually configured CPU overclocking or undervolting settings.
3. Check whether an XMP, EXPO or other memory performance profile was enabled.
4. Restore manufacturer-supported default operating settings for diagnostic testing.
5. Save the changes and test Windows stability.

Changing these settings can affect performance and may alter other firmware configuration options. Record the original settings before making changes.

Do not assume that enabling or disabling a memory profile is a universal solution for WHEA_INTERNAL_ERROR. Use crash evidence to determine whether the configuration is relevant.

Solution 5: Run Windows System File Checker

System File Checker (SFC) checks protected Windows system files and attempts to repair corrupted files using the Windows servicing mechanisms.

Run the following commands from an elevated Command Prompt or Windows Terminal:

DISM.exe /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

sfc /scannow

Restart Windows if repairs are completed and required.

Limitation: DISM and SFC address Windows image and protected system file integrity. They do not repair defective motherboard firmware, a broken PSHED implementation or a physical hardware fault. These commands are general integrity checks, not a confirmed fix for bug check 0x122.

Solution 6: Check Windows Updates

Check whether Microsoft has released applicable Windows updates that address system stability or platform compatibility.

1. Open Settings.
2. Navigate to Windows Update.
3. Select Check for updates.
4. Review available updates and their applicability.
5. Install relevant updates according to your organization's change-management requirements.
6. Restart the system if required.

For managed business computers, coordinate updates with the IT administrator before changing production configurations.

Solution 7: Perform Manufacturer Hardware Diagnostics

If crash analysis or related hardware error events point toward a hardware subsystem, run the appropriate diagnostic tests supplied by the computer or component manufacturer.

Depending on the suspected component, diagnostics may include:

• Processor and system-board diagnostics.
• Memory tests.
• PCI Express device diagnostics.
• Storage health checks.
• Power and thermal monitoring.

For systems that cannot boot reliably, use the manufacturer's supported preboot diagnostic environment if available.

Do not replace the CPU, motherboard, RAM or graphics card solely because the error name contains the word hardware. Base replacement decisions on repeatable test results, diagnostic records and manufacturer guidance.

Solution 8: Contact the Computer or Platform Manufacturer

If the error persists after basic diagnostics, the manufacturer may need to investigate the platform-specific WHEA implementation.

Provide the support team with:

• Computer or motherboard model and revision.
• BIOS or UEFI version.
• Windows edition and build.
• Complete bug check parameters.
• Crash dump files, where permitted.
• Relevant WHEA-Logger event details.
• Recent firmware, driver and hardware changes.
• Results of manufacturer diagnostic tests.

This information is especially important for systems that use vendor-specific PSHED plug-ins or custom firmware error-reporting implementations.

Advanced Troubleshooting for IT Professionals

On enterprise systems, engineering workstations and computers that repeatedly encounter WHEA_INTERNAL_ERROR, the investigation may require platform-level debugging rather than routine Windows repair procedures.

1. Interpret Parameter 1 Before Changing the System

Start with the documented meaning of Parameter 1.

• 0x1, 0x2, 0x7 or 0x8: Investigate the documented memory allocation or error-source enumeration failure.
• 0x5: Examine the reported status and initialization phase.
• 0x6: Investigate the error source type and the initialization phase in which it failed.
• 0x9: Investigate the invalid error source and its source ID.
• 0xA: Investigate the failure to allocate an error record.
• 0xB: Investigate the failure to populate an error record.

This classification helps determine whether the investigation should focus on initialization, memory allocation, source enumeration or error-record handling.

2. Investigate the Platform-Specific Error Source

For Parameter 1 values that identify an error source, correlate the reported source type and source ID with the platform's hardware and firmware documentation.

For example, a PCI Express error source may require investigation of the associated PCI Express device, root port, firmware reporting path and relevant platform drivers.

Use manufacturer documentation and platform debugging facilities where available. Do not infer the exact physical component from the error source type alone.

3. Review PSHED Plug-in Compatibility

On systems using a vendor-supplied PSHED plug-in, check whether the component is supported for the installed Windows version, hardware platform and firmware revision.

Platform developers should validate the plug-in implementation against Microsoft's WHEA and PSHED development documentation.

4. Examine Firmware Error Records and Initialization

When the bug check parameters indicate failure during error source initialization or error-record processing, investigate the platform firmware implementation.

For system manufacturers and firmware developers, the investigation may involve:

• Error source enumeration.
• Firmware-reported hardware error records.
• Correctness of platform-specific error information.
• Firmware initialization phases.
• Error injection implementation and validation, where applicable.

These activities generally require platform-specific debugging knowledge and should not be attempted by changing undocumented firmware settings on a production computer.

Difference Between WHEA_INTERNAL_ERROR (0x122) and WHEA_UNCORRECTABLE_ERROR (0x124)

Both stop codes belong to the Windows Hardware Error Architecture, but they describe different types of failure.

Feature	WHEA_INTERNAL_ERROR	WHEA_UNCORRECTABLE_ERROR
Bug check code	0x00000122	0x00000124
Meaning	An internal WHEA failure.	A fatal hardware error was reported through WHEA.
Typical investigation	PSHED, firmware error handling, initialization and error-record processing.	Hardware error records and the reported hardware error source.
Hardware replacement	Not justified by the stop code alone.	Not justified by the stop code alone; diagnostic evidence is required.
Useful diagnostic information	Four bug check parameters and crash dump analysis.	Bug check parameters, WHEA error records and hardware diagnostics.

These errors should not be treated as interchangeable. Use the correct Microsoft documentation for the actual bug check displayed by Windows.

How to Prevent WHEA_INTERNAL_ERROR

Although firmware and platform implementation problems cannot always be prevented by end users, the following practices can reduce configuration-related risks and make future diagnosis easier.

• Keep BIOS and UEFI firmware at manufacturer-supported versions.
• Install chipset and platform drivers from trusted manufacturer sources.
• Avoid unsupported CPU overclocking and undervolting configurations.
• Use supported memory configurations and compatible hardware.
• Maintain a record of firmware and driver changes.
• Monitor relevant WHEA-Logger events on systems where hardware error reporting is important.
• Configure appropriate Windows crash dump settings on systems requiring failure analysis.
• Validate firmware and platform changes before deploying them across business-critical systems.
• Maintain regular backups of important business data.

Frequently Asked Questions (FAQs)

1. What does WHEA_INTERNAL_ERROR 0x00000122 mean?

It means Windows encountered an internal error in the Windows Hardware Error Architecture. Microsoft identifies possible causes involving a vendor PSHED plug-in, firmware error-record implementation or firmware error injection.

2. Does WHEA_INTERNAL_ERROR mean my CPU is damaged?

No. The stop code alone does not confirm CPU damage. It can result from failures in WHEA initialization, firmware implementation or platform-specific hardware error handling. The crash parameters and diagnostic records must be examined.

3. Can faulty RAM cause WHEA_INTERNAL_ERROR?

The documented bug check includes memory allocation failures, but these do not automatically indicate defective physical RAM. If there is independent evidence of memory instability, run appropriate manufacturer or memory diagnostics.

4. Is WHEA_INTERNAL_ERROR related to BIOS or UEFI?

Yes. Microsoft explicitly identifies firmware implementation problems as one possible cause. An investigation should consider the BIOS or UEFI version and the platform manufacturer's firmware support information.

5. What is the difference between WHEA_INTERNAL_ERROR and WHEA_UNCORRECTABLE_ERROR?

WHEA_INTERNAL_ERROR is bug check 0x122 and identifies an internal failure in the WHEA framework. WHEA_UNCORRECTABLE_ERROR is bug check 0x124 and indicates that an uncorrectable hardware error was reported through WHEA.

6. Where can I find the crash dump file?

Check C:\Windows\Minidump\ for small memory dumps and C:\Windows\MEMORY.DMP for a configured kernel or complete memory dump. File availability depends on the system's dump configuration and whether Windows successfully generated the dump.

7. Can updating BIOS fix WHEA_INTERNAL_ERROR?

It may help if the manufacturer has identified and corrected a relevant firmware issue. However, a BIOS update is not a guaranteed solution. Check the exact system model, release notes and supported update procedure before proceeding.

8. Can SFC and DISM repair this error?

They can repair certain Windows image and system file integrity problems. However, they do not directly repair firmware implementation defects or defective hardware error reporting components. Use them as general integrity checks rather than a guaranteed fix for 0x122.

9. Why does WHEA_INTERNAL_ERROR occur during Windows startup?

A startup crash may be associated with a failure during hardware error source enumeration or initialization. Examine Parameter 1, the initialization phase where applicable, firmware version and relevant crash dump information to narrow down the cause.

10. Should I reinstall Windows to fix WHEA_INTERNAL_ERROR?

Not as an initial troubleshooting step. The documented causes include platform-specific firmware and PSHED implementation problems, which may remain even after reinstalling Windows. Diagnose the crash before considering an operating system reinstall.

Key Takeaways

• WHEA_INTERNAL_ERROR (0x00000122) indicates an internal failure in the Windows Hardware Error Architecture.
• Microsoft identifies PSHED plug-in defects, firmware error-record implementation problems and firmware error injection issues as possible causes.
• The four bug check parameters provide important information about the failure category.
• Crash dump analysis using WinDbg and examination of relevant Event Viewer records can help identify the underlying issue.
• Firmware, chipset drivers and platform compatibility should be investigated when supported by diagnostic evidence.
• The error does not automatically mean that the CPU, RAM or motherboard must be replaced.
• Preserve diagnostic information and consult the system manufacturer when platform-specific investigation is required.

Official References

1. Microsoft Learn – Bug Check 0x122: WHEA_INTERNAL_ERROR – Official description, bug check parameters and error source types.
2. Microsoft Learn – Bug Check Code Reference – Reference for Windows stop codes and debugging information.
3. Microsoft Learn – Windows Debugging – Documentation for WinDbg and Windows crash debugging.
4. Microsoft Learn – Analyze a Kernel-Mode Dump File with WinDbg – Guidance for analyzing Windows crash dump files.
5. Microsoft Support – Troubleshoot Blue Screen Errors – General guidance for investigating Windows stop errors.
6. Microsoft Learn – Windows Hardware Error Architecture (WHEA) – Technical documentation for WHEA and hardware error reporting.