"STOP: C0000221 unknown hard error" or "STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH" error message occurs
View products that this article applies to.
Article ID : 314474
Last Review : December 1, 2007
Revision : 3.2
This article was previously published under Q314474
SYMPTOMS
You may receive any one of the following Stop error messages:
STOP: C0000221 unknown hard error
Path\File_name
STOP: 0xC0000221 unknown hard error
C:\Winnt\System32\Ntdll.dll (or another specific file or driver)
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
Path\File_name
For additional symptom details, see the “More Information” section.
Back to the top
CAUSE
This problem may occur if the file that is described in the error message is corrupted. The following files are checked for integrity when Microsoft Windows XP starts: • All driver files (except those that are loaded by the system loader to start. the computer)
• All dynamic-link libraries (DLLs), including User, Graphics Device Interface (GDI), Shell, Kernel, Ntdll, Crtdll, and others.
This problem may occur if you install an inappropriate driver for your hardware. For example, you receive one of the error messages that are described in the "Summary" section if you install a millions of instructions per second (MIPS) driver on an X86-based computer.
This problem may occur if an Iomega Zip drive is on the same integrated device electronics (IDE) cable as the hard disk drive.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Back to the top
RESOLUTION
To resolve this problem, obtain a new copy of the corrupted file or reinstall Windows XP. If you continue to receive any one of the error messages that are described in the "Summary" section after you reinstall Windows XP, a hardware problem or a network problem may exist.
Back to the top
MORE INFORMATION
This error message may be displayed in many different formats, including an error message that is displayed on a blue screen or an error message that is displayed in a dialog box. The type of format that the error message is displayed in depends on how much of the operating system was loaded when the corrupted file was detected.
Back to the top
go google! but I figured you might had a currupted file, do you remember updating anything recently? any popups about drivers needed to be updated and things like that? well lets keep reinstalling windows xp to a last resort, first lets rollback all the drivers to a previous update. you can do this by going to control panal, system, click the tab that says hardware then select device manager. under each + tab is a device on the machine, click on the plus to open the catagory then right click on the thing inside and select properties. inside the properties select the driver tab and select rollback driver. Try this with at least the display, sound, network, processor drivers. If that doesn't work try all the drivers. and if that doesn't work then you might have to reinstall your operating system. I just hope its a driver and not a DLL file (DLL's cant be fixed, any changes to a DLL file could currupt the system)