What does BSOD 0x79 (MISMATCHED_HAL) mean?

 
Could be also:
ConstantTypeOS
ERROR_SEM_TIMEOUTWin32 errorWindows
EREMOTEIOerrnoLinux
ESOCKTNOSUPPORTerrnoSolaris
ENOLINKerrnoWindows
Previous Next
PHASE0_EXCEPTION KERNEL_DATA_INPAGE_ERROR

MISMATCHED_HAL

The MISMATCHED_HAL bug check has a value of 0x00000079. This bug check indicates that the Hardware Abstraction Layer (HAL) revision level or configuration does not match that of the kernel or the computer.

MISMATCHED_HAL Parameters

Parameter 1 indicates the type of mismatch.

Parameter 1 Parameter 2 Parameter 3 Parameter 4 Cause.

0x1

The major processor control block (PRCB) level of Ntoskrnl.exe.

The major PRCB level of Hal.dll.

Reserved

The PRCB release levels are mismatched. (Something is out of date.)

0x2

The build type of Ntoskrnl.exe.

The build type of Hal.dll.

Reserved

The build types are mismatched.

0x3

The size of the loader parameter extension.

The major version of the loader parameter extension.

The minor version of the loader parameter extension.

The loader (ntldr) and HAL versions are mismatched.

When Parameter 1 equals 0x2, the following build type codes are used:

  • 0: Multiprocessor-enabled free build

  • 1: Multiprocessor-enabled checked build

  • 2: Single-processor free build

  • 3: Single-processor checked build

Cause

This stop code means that the kernel, HAL, or loader data came from incompatible build or configuration sets. Parameter 1 identifies whether the mismatch is in PRCB revision levels, checked/free or uniprocessor/multiprocessor build type, or the loader parameter extension.

Diagnostic approach

Start with Parameter 1 and compare the kernel, HAL, and loader versions from the same boot. A 0x1 or 0x2 mismatch points to kernel/HAL components from different builds or build types; a 0x3 mismatch points to loader data that does not match the running kernel/HAL set.

Preserve the dump and the exact OS image provenance before replacing files. Verify that boot files, servicing state, deployment image, and any offline repair source belong to the same Windows build. Manual file copying from unrelated installation media can create the mismatch that this bug check reports.

References


Looking for a different code? Search another status or error code.