General discussion

  • Creator
    Topic
  • #2321562

    Stop error message in W2K

    Locked

    by casemaker ·

    Hi,
    I get this stop message when I boot.
    Stop: c0000221 (bad image checksum)
    The image olesvr32.dll is possibly corrupt. The header checksum does not match the computed hecksum.
    To my knowledge, Lotus 123 was recently loaded on this machine.
    How can I correct this.

All Comments

  • Author
    Replies
    • #3415875

      Stop error message in W2K

      by casemaker ·

      In reply to Stop error message in W2K

      I BOOTED INTO START OPTIONS AND TRIED TO GO INTO SAFE MODE, I GOT THE SAME ERROR MESSAGE

    • #3415825

      Stop error message in W2K

      by saihib ·

      In reply to Stop error message in W2K

      The following STOP message appears when a critical system file or other file needed to load Windows is corrupted:

      In Windows 2000 the error reads as follows:
      STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH \
      This error can appear in many different formats, ranging from a blue system error screen to a dialog box. The type of format depends on how much of the operating system was loaded when the corrupted file was detected.

      CAUSE
      If you receive this error message, the file listed in the error message is corrupted.

      RESOLUTION
      To resolve this issue, you need to either obtain a new copy of the file or reinstall Windows. If reinstallation fails to solve the problem, a hardware or network problem mayexist.

    • #3415750

      Stop error message in W2K

      by curlergirl ·

      In reply to Stop error message in W2K

      It sounds like someone tried to load a version of Lotus that’s not compatible with Win2K and this file got corrupted. Usually Win2K is pretty good about being self-healing on these things, but someone probably selected the wrong option at the wrongtime and hosed it. You should be able to replace this file with a newly extracted one using the Win2K Recovery Console. If you’ve never used it, you might want to read up on it a bit before trying it – but it works great. Basically what it does is provide you with a boot environment to a command-line interface that allows you to manage files within the system folders. You need the administrator password and then boot your system with a Win2K CD or, if you have the recovery console pre-loaded on your machine, select it when booting. You’ll also need any manufacturer’s IDE or SCSI controller driver diskettes, if you have a 3rd party storage system. Then, you’ll need the Win2K CD also to get a fresh copy of the olesvr32.dll file to replace the damaged one. Hope this helps!

    • #3415722

      Stop error message in W2K

      by casemaker ·

      In reply to Stop error message in W2K

      This question was closed by the author

Viewing 3 reply threads