Question about Dell Computers & Internet

Open Question

Stop: c000021 (bad image checksum) image ntvdm.exe is possible corrupt.

Posted by Anonymous on

Ad

2 Suggested Answers

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
New users get 2 Free calls (no credit card required) and instant help on almost anything you can think of (from cars to computers, appliances, handyman, and even pets).
click here to download the app (for users in the US for now) and get all the help you need.
Goodluck!

Posted on Jan 02, 2017

Ad
  • 3940 Answers

SOURCE: bad image checksum

Boot to recovery console (Boot to Windows CD, Press R at 1st prompt) run CHKDSK /R

Posted on Aug 11, 2009

Ad

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

Compaq Presario 2500 stopped loading windows XP with a prompt STOP: c0000221 {bad Image Checksum} The image COMCTL32.dll is possibly corrupt. The header checksum does not match the computed checksum.


This error is not the same as a CMOS Checksum Error, which refers to corrupted values of the CMOS settings, the ones you set through the BIOS setup program. This error means the contents of the BIOS code itself are damaged.

During the boot process you will see on the screen to press delete to enter setup
Press and hold delete during the boot up process to enter BIOS you can load failsafe defaults or load optimized defaults ,press escape then press f10 to save to cmos to restart
click start control panel date and time you can make your adjustments to the date and time from there also right click on the date and time on the bottom toolbar (bottom of screen) you should see Adjust date and time tab
hope this helps you

Sep 09, 2011 | Compaq Presario 2100 and 2500 ,NX 9000...

1 Answer

Laptop: Toshiba Satellite NB200.Problems when restart after upadated antivirus (kaspersky 2010) this message appear: STOP:c0000221 [bad Image Checksum] The image urlmon.dll is possibly corrupt.the...


Yes it may be possible, installing and updating antivirus may have figured our corruption in urlmon.dll deleted the file or did some changes due to which you are getting the critical error

You can try 2 things,

1. Restore earlier settings, which may uninstall your antivirus and you need to install again. But if this works recommend you to first scan the system with free standalone antivirus availalable and then install your version of antivirus. Try following link

http://go.trendmicro.com/housecall7/HousecallLauncher.exe
http://www.trendmicro.com/ftp/products/rootkitbuster/RootkitBuster_2.80.1077.zip
2. Repair the URLMON.DLL file

1.Insert your Windows XP CD in your CD-ROM drive and boot your computer from the CD.
2.When the Welcome to Setup screen appears, press R to open the Recovery Console.
3.When prompted for an administrator password, type the password and then press Enter. In case no administrator password was set, just press Enter.
4.At the Command Prompt, type the following command and press Enter
cd %systemroot%\system32
5.Next, type the following command to rename the urlmon.dll file and press Enter.
ren urlmon.dll urlmon.old.dll
6.Now, to restore the original urlmon.dll, type the following command and press Enter.
expand [CD drive letter]:\i386\urlmon.dll %systemroot%\system32 /Y
7.Next, type exit and press Enter.
8.Restart your computer.

3. Repair complete OS. You will need XP CD
Boot from CD and follow the instructions to repair the OS

801b785.gif
d849da9.gif
2f0b982.gif

May 20, 2010 | Computers & Internet

1 Answer

My laptop wont load to Windows XP when it tries to I get the following message. STOP:c0000221 {Bad Image Checksum} The image shell32.dll is possibly corrucpt. The header checksum does not match the...


your windows is surely corrupted.. install your windows again... if you dont know how to install your windows...contact me....at (bharat_s@ymail.com)

please vote for me...im sure this will solve your problem...

Sep 26, 2009 | Compaq Presario 2100 and 2500 ,NX 9000...

1 Answer

Help


Greetings,

When you upgrade your computer to Windows XP, you may receive an error message that is similar to one of the following: C0000221 (Bad Image Checksum)
-or- STOP: C0000221 - Bad Image Checksum in ModuleName
-or- STOP: C0000221 - Bad Image Checksum. User32.dll is possibly corrupt. The header check sum does not match the computed check sum.

Please go through the below mentioned link:

http://support.microsoft.com/kb/326687

Sep 20, 2009 | Microsoft Windows XP Professional for PC

1 Answer

Bad image checksum


Boot to recovery console (Boot to Windows CD, Press R at 1st prompt) run CHKDSK /R

Aug 09, 2009 | Dell Computers & Internet

1 Answer

STOP: c0000221 {bad image checksum}


You most likely have bad RAM. If you have two chips, pull one out and run the laptop on a single stick. You may need to alternate the sticks just incase the non-working one is the one you left in the laptop.

May 19, 2009 | Computers & Internet

1 Answer

The ntvdm cpu has encountered an illegal instruction


I took this from another web site:
Michael Chiew said:
What did you do before this happened? What were your last deeds on the machine before the pop-up appeared?

I think what you're referring to is NTVDM CPU, not NTDVM CPU. Am I correct?

What do you know about 16-bit and 32-bit applications? Well, 16-bit applications are those that must work within the DOS (Disk Operating System) environment, a real-mode arena. NTVDM stands for NT Virtual Dos Machine.

In Windows XP, as in Windows 2000, or Windows 98, there are 16-bit and 32-bit environments (real mode and protected mode respectively).

Windows XP can only operate in 32-bit mode. All 16-bit applications must work within its own theatre of operation, typically, the first MB of physical memory (ram). Conversely, 32-bit applications must function above the first MB memory line. If either of these applications happens to slip into "alien" territory, you get an error message like "something" has encounter an illegal instruction. In other words, the wayward application is trying to slip by the immigration checkpoint.

In your case, updatemgr.exe (I suspect updatemgr.exe is a 32-bit application) has in all likelihood wondered into the 16-bit arena. Hence, NTVDM CPU issues that warning. 

Why do you continue to get the message. It's because updatemgr.exe incessantly misbehaves itself on start-up, always trying to load itself into a particular memory address where it is not welcome. Why the persistence? Updatemgr.exe has gone bonkers. It is either corrupted or damaged.

On the other hand, one cannot discount the possibility that NTVDM (NTVDM.EXE) is corrupted or damaged. So your problem lies with either updatemgr.exe or NTVDM.EXE, or both.

There are 2 things you could do.

First, establish who owns updatemgr.exe, Microsoft or some third-party owner. Second, rename updatemgr.exe and see whether the message goes away.

To establish ownership (and the function of updatemgr.exe), do a search for the file. 

Click START, select FIND. In the FIND dialog box, type: updatemgr.exe. See the directory in which the file has lodged. In Windows Explorer, get to the file, right-click on it, select PROPERTIES. Who owns it? Is there an indication of its function.

Next, rename the file. Right-click it, select RENAME and rename it to, say, updatemgr.old. RESTART your computer. Do you still get the error message. Not likely.

To clean things up a bit, perhaps it is a good idea for you to replace the current NTVDM.EXE with a new copy. Find out where NTVDM.EXE is. Then, click START, select RUN. Type in the RUN dialog box SFC to run the System File Checker. Insert your OS CD, follow the prompts, extract a copy of NTVDM.EXE and send it to its place of residence. Of course, you should also replace a copy of updatemgr.exe.

That should eliminate your problem for good.


Dec 25, 2008 | Microsoft Windows XP Home Edition

3 Answers

Bad image checksum and not reading a hard drive


Please give more info about this.

Try to reformat your Hard Drive and install it againg freshly. This might do the work.

Mar 03, 2008 | Microsoft Windows XP Professional for PC

Not finding what you are looking for?
Computers & Internet Logo

Related Topics:

67 people viewed this question

Ask a Question

Usually answered in minutes!

Top Dell Computers & Internet Experts

Les Dickinson
Les Dickinson

Level 3 Expert

18402 Answers

Doctor PC
Doctor PC

Level 3 Expert

7733 Answers

mukhtar21 shaikh
mukhtar21 shaikh

Level 3 Expert

2017 Answers

Are you a Dell Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...