Site and content now available for sale - $1950 Contact Us
Includes 80,000+ pages content, Windows app, database, admin, graphics, and more.
spacer spacer spacer
  arrow Description
  arrow Sample Screen
  arrow Key Facts
  arrow Solutions
  arrow Forum Help
  arrow Technical Details
  arrow Vendor Summary
  arrow Research this Issue
  help Solutions Help
Fatal Error Solutions

Mismatched kernel and hal image.

STOP: 0x00000079


Key system files are mismatched. Windows requires key files to all be the same version. This can occur if you manually copy files such as hal.dll, ntoskrnl.sys or ntldr from the wrong media.

Some older versions of Windows will show the description as "MISMATCHED_HAL".

This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.

  Sample Screen  

A problem has been detected and Windows has been shut down to prevent damage to your computer.

Mismatched kernel and hal image.

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical Information:

*** STOP: 0x00000079

Beginning dump of physical memory
Physical memory dump complete.

Contact your system administrator or technical support group for further

Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown.
  Key Facts  
Full Title
  Mismatched kernel and hal image. 

Stop Code


occurance meter
  2000, XP, Vista, 2008, 7, 8

  Microsoft Corporation
  Solutions and Fixes  
  Date Votes ratings
Fix File Consistency
    Add    Flag
solution icon
Ensure the key system files are the same version and match the Windows version you have installed. Assuming the C drive is the system drive, the files are typically located at:

c: tldr (note this file is set to hidden, read-only)
c:WindowsSystem32 toskrnl.sys

Also note that the CD/DVD media has different versions of these files. For example, Ntoskrnl.exe is for single processor systems, while Ntkrnlmp.exe is the Multi-Processor version, which is renamed to Ntoskrnl.exe when installed. Debug versions of the operating system only used by developers (commonly called the Checked version) must also use only files from the Checked version.

solves it indicator
risk indicator
effort indicator
  FaultWire Staff
Posted: 2-Sep-2009
Repair Damaged or Missing OS Files
    Add    Flag
solution icon

Use the Windows RE (Repair Environment) under Window 7/Vista to repair and replace missing or damaged files. For XP users, you can re-install XP without erasing applications or settings, or use the XP Recovery Console to fix some problems. Pick the OS solution below.

Using Windows RE for Windows 7/Vista/Server 2008

For detailed instructions with screen shots, go to Using System Restore 7/Vista/2008, or use the brief summary here:

You'll need the Windows installation DVD. Note that many OEM manufactures leave out the installation DVD, which has to be purchased separately, or they only include a limited restore DVD that just erases the system and starts over (often a poor choice). All retail copies of Windows include this bootable DVD.

Insert the Windows DVD and reboot the system. Assuming the BIOS defaults to booting from the DVD (usually the default) then select the language. Next click on Repair your computer. A list of Windows installations should appear. Select your installation (typically there will only be one).

A list of recovery options will appear including an automatic repair function, restore from a previous system restore point, restore the computer from a backup (assuming one is available), run the memory diagnostic tool, or go to a command prompt (for advanced users).

Using Windows Recovery for XP

For detailed instructions with screen shots, go to Using System Restore XP.

solves it indicator
risk indicator
effort indicator
  FaultWire Staff
Posted: 5-Oct-2008

Also see our list of common Fatal Error Solutions.

  Forum Help  
Forums on topic

Check out what others say about this issue and review or add your own comments and solutions!

Go to Forums on topic.
  Technical Details  
  technical details

The Hardware Abstraction Layer (HAL) revision level or configuration does not match that of the kernel or the computer.

After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.

Parameter 1 specifies cause of the error (other Parameters will depend upon the type).

0x01 - The PRCB (Processor Control Block) release levels are mismatched and out of date.
0x02 - The build types are mismatched.
0x03 - The loader (ntldr) and HAL versions are mismatched.

  Vendor Summary  
  Microsoft Corporation (more info...)

Microsoft Corporation Logo



    While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by non-Microsoft applications, drivers and hardware issues.  
  Research this Issue  
Getting search results...
  While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at so we can correct it.