Stop: 0xC000012F - Image File Did Not Have the Correct Format.

This article was previously published under Q173518
This article has been archived. It is offered "as is" and will no longer be updated.
You may receive the following error message as your computer restarts:


The specified image file did not have the correct format, it did not have an initial MZ.

This error may also occur following installation of new drivers to thesystem, such as adding a new video driver, or is often seen during eitheran upgrade or new installation of Windows NT.
This error is caused by the system being unable to load a needed filebecause of the file being corrupted. This usually occurs during the filecopy process, and is often because of a hardware malfunction. It may be aone-time occurrence, but often is a signal for the user to do a throughexamination of system hardware to determine what is causing the corruption.

NOTE: The parameter 0xc000012f may also be seen in conjunction with otherTrap Codes such as 0x0000006b and is usually shown as the first parameterfollowing the trap:
STOP 0x0000006b (0xc000012f, 0xxxxxxxxx, 0xxxxxxxxx,0xxxxxxxxx)
Because this trap code is caused by a corrupted file required to loadWindows NT, and the trap screen does not always reference which specificfile caused the problem, the best solution is usually basic troubleshooting.

It is recommended to have a good back up of anything on the computer thatthe user considers valuable before proceeding with the differentprocedures.

Windows NT was Already Installed and Running

If the stop error occurred following a change in hardware drivers, pressthe space bar to select the Last Known Good option during startup, and thenchange the necessary components when the computer comes up.

Try selecting [VGA MODE] option from the boot menu, this will display theWindows NT system files on the screen as they are loaded and may give you aclue about which file is corrupt.

Use the Emergency Repair Disk to replace the missing or damaged driverfile on the partition by following the procedure outlined in thefollowing Microsoft Knowledge Base articles:

ARTICLE-ID: 103280
TITLE : Using an Emergency Repair Disk Created by Windows NT

ARTICLE-ID: 164471
TITLE : Replacing System Files Using a Modified Emergency Repair Disk

This will allow you to perform a system repair to replace the corruptedWindows NT system file.

If Performing an Initial Windows NT Installation or Upgrade

If the computer has MS-DOS or another operating system installed, copy thei386 directory from the Windows NT installation CD to C:\i386, and at acommand prompt carry out the following command:

This often allows the installation to proceed, but if Windows NT will notinstall in this manner, you may want to consider the following options:

  • When installing on a new computer with little or nothing else on it, reformat the hard drive and install using the three setup disks, or booting with DOS, copying the i386 directory, and carry out a WINNT /b command as above. If you are using the three setup disks, consider making a new set using the WINNT /ox switch to help eliminate the possibility of a bad floppy disk.
  • Disable caching options and BIOS shadowing.
  • Removing all possible hardware to take the computer down to a bare box with only one hard drive and controller in order to eliminate possible hardware conflicts.
  • Ask the computers' manufacturer if a newer System BIOS is available, if so, flash the BIOS using the manufacturers instructions.
Because this error is usually associated with hardware, it is recommendedto troubleshoot the computer from that stand point, including themotherboard, controller, memory, hard drive, and CD-ROM drive.
file corruption

Article ID: 173518 - Last Review: 12/04/2015 17:47:28 - Revision: 2.1

Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbprb kbsetup KB173518