Troubleshooting Windows Servers
Useful Links
Get the
Google AdSense
widget and many other
great free widgets
at
Widgetbox
!
Search
Inside
G
o
o
g
l
e
Display results as :
Posts
Topics
Advanced Search
Latest topics
»
Order of Group Policy Processing
Tue Dec 30, 2008 4:05 pm by
nbhatt
»
Authentication Methods in IIS
Tue Dec 30, 2008 1:06 pm by
Admin
»
Event id 4004 DNS errors and external name resolution problems
Mon Dec 29, 2008 4:19 pm by
Admin
»
Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP
Mon Dec 29, 2008 1:43 pm by
Admin
»
Stop 0x7B or INACCESSIBLE_BOOT_DEVICE
Sat Dec 27, 2008 10:37 pm by
Anonymous
»
Stop 0x7A or KERNEL_DATA_INPAGE_ERROR
Fri Dec 26, 2008 9:42 pm by
Admin
»
Stop 0x79 or MISMATCHED_HAL
Fri Dec 26, 2008 9:36 pm by
Admin
»
Stop 0x77 or KERNEL_STACK_INPAGE_ERROR
Thu Dec 25, 2008 4:19 pm by
Admin
»
Stop 0x6B or PROCESS1_INITIALIZATION_FAILED
Thu Dec 25, 2008 4:09 pm by
Admin
Shopmotion
Navigation
Portal
Index
Memberlist
Profile
FAQ
Search
Forum
Create a free forum
Free forum support
Affiliates
Premade Website Designs
Server Unleashed
::
STOP Errors
::
Common Stop Messages
::
Stop 0x79 or MISMATCHED_HAL
::
Stop 0x79 or MISMATCHED_HAL
Post a reply
Username
Subject
Dark Red
Red
Orange
Brown
Yellow
Green
Olive
Cyan
Blue
Dark Blue
Indigo
Grey
White
Black
None (use implicit)
Message body
x
YouTube
Dailymotion
x
px
Tiny
Small
Normal
Large
Huge
Dark Red
Red
Orange
Brown
Yellow
Green
Olive
Cyan
Blue
Dark Blue
Indigo
Violet
White
Black
Arial
Arial Black
Comic Sans Ms
Courier New
Georgia
Impact
Times New Roman
Trebuchet MS
Verdana
Index
Exponent
Spoiler
Hidden
Horizontal scrolling
Vertical scrolling
Random
WoW
x
Ok
Ok
Ok
x
px
Ok
YouTube
Dailymotion
Ok
Tiny
Small
Normal
Large
Huge
Dark Red
Red
Orange
Brown
Yellow
Green
Olive
Cyan
Blue
Dark Blue
Indigo
Violet
White
Black
Arial
Arial Black
Comic Sans Ms
Courier New
Georgia
Impact
Times New Roman
Trebuchet MS
Verdana
Index
Exponent
Spoiler
Hidden
Horizontal scrolling
Vertical scrolling
Random
WoW
Close Tags
Options
Options
HTML is OFF
BBCode
is ON
Smilies are ON
Disable BBCode in this post
Disable Smilies in this post
Jump to:
Select a forum
|
|--Active Directory
| |--Migration
| |--Replication Issues
| |--Group Policy processing order
| |--Troubleshooting Unshared sysvol and netlogon.
| |--Metadata Cleanup after unsuccessful demotion of server
|
|--Exchange Issues and Articles
| |--Unable to run Forestprep for Exchange 2003 due to MSDTC errors
| |--Exchange Services not starting: Unexpected error There are no more endpoints available from the endpoint mapper
|
|--NTBackup Issues
| |--Error returned while creating the volume shadow copy: 0xfffffff
|
|--Service Pack Issues
| |--Unable to install SP2 for Windows server 2003
| |--Remote Desktop Fails after intalling SP2 for Server 2003
| |--How to uninstall Service Packs for Windows from recovery console
|
|--STOP Errors
| |--Stop Errors Overview
| |--Configuring Memory Dumps
| |--Using Memory Dump Files to analyze STOP Errors
| |--Being Prepared for Stop Errors
| |--Common Stop Messages
| |--Stop 0xA or IRQL_NOT_LESS_OR_EQUAL
| |--Stop 0x1E or KMODE_EXCEPTION_NOT_HANDLED
| |--Stop 0x24 or NTFS_FILE_SYSTEM
| |--Stop 0x2E or DATA_BUS_ERROR
| |--Stop 0x31 or PHASE0_INITIALIZATION_FAILED
| |--Stop 0x32 or PHASE1_INITIALIZATION_FAILED
| |--Stop 0x3F or NO_MORE_SYSTEM_PTES
| |--Stop 0x50 or PAGE_FAULT_IN_NONPAGED_AREA
| |--Stop 0x6B or PROCESS1_INITIALIZATION_FAILED
| |--Stop 0x77 or KERNEL_STACK_INPAGE_ERROR
| |--Stop 0x79 or MISMATCHED_HAL
| |--Stop 0x7A or KERNEL_DATA_INPAGE_ERROR
| |--Stop 0x7B or INACCESSIBLE_BOOT_DEVICE
| |--Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP
|
|--Networking
| |--No Internet after connecting through VPN
| |--Event ID 4004 DNS errors and external name resolution problems
|
|--IIS
|--AuthenticationMethods in IIS
Topic review
Author
Message
Admin
Fri Dec 26, 2008 9:36 pm
Topic: Stop 0x79 or MISMATCHED_HAL
The Stop 0x79 message indicates that the HAL and the kernel type for the computer do not match. This error generally results from one of the following circumstances:
• Either Ntoskrnl.exe or Hal.dll has been manually updated.
• ACPI firmware settings were changed after Windows Server 2003 was installed. For example, an administrator might have installed Windows Server 2003 on an x86-based computer with the firmware ACPI enable option enabled, and later decided to disable it.
• Mismatched single-processor and multiprocessor configuration files are copied to the system.
• The operating system loader is an older version than the operating system kernel; for example, the Windows 2000 Server loader is used to load the Windows Server 2003 kernel because Windows 2000 Server was installed after Windows Server 2003.
Interpreting the Stop 0x79 Message
When the value of parameter 1 is set to 0x00000002, the build type codes shown in Table 10.15 become effective for parameter 2 and parameter 3.
Build Type Code Description
0x00000000 Multiprocessor-enabled free build
0x00000001 Multiprocessor-enabled checked build
0x00000002 Single-processor free build
Troubleshooting the 0x79 Stop Error
The following sections list the most common sources for this Stop error and suggest some troubleshooting solutions.
Incorrect versions of Ntoskrnl.exe or Hal.dll files
A Stop 0x79 message occurs when the operating system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the operating system. This error also occurs when copying mismatched files, such as a multiprocessor HAL to an operating system that uses a single-processor kernel (or vice versa). The kernel and HAL files for single-processor and multiprocessor systems are stored on the Windows Server 2003 operating system CD by using two different file names: Ntoskrnl.exe and Ntkrnlmp.exe, respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your system as Ntoskrnl.exe.
In Recovery Console, it is possible to use the Copy command to copy the correct Ntldr, HAL, or kernel files from the operating system CD to the appropriate folder on the hard disk. For more information about Recovery Console, see “Recovery Console overview” in Help and Support Center for Windows Server 2003.
Incorrect firmware settings
If you experience Stop 0x79 messages after changing firmware settings, restore the original settings used during Windows Server 2003 Setup.