C0000221 Bad Image checksum

[goombawaho]

Getting this error on a customer's PC on NTVDM.EXE I understand that it might mean the file is corrupt and that I could try to extract the file from the XP cd and see if that fixes the problem.

But what about checking the hard drive first to rule out a bad drive (thus causing general file system corruption) and/or a memory test to see if good files are being read in but garbage is output???

Anyone think either of my suggestions could be the root cause and the corrupted file just the symptom?? There's not much to go on out there based on a google search.

 

[linney]

314474 - "STOP: C0000221 unknown hard error" or "STOP: C0000221

http://support.microsoft.com/?kbid=314474

What program is using NtVdm.exe, is it some old Ms-Dos program, that you could try running in a different compatibility mode, or use the RunAs command to run it as an Administrator?

292533 - HOW TO: Use Windows Program Compatibility Mode in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;292533&FR=1&PA=1&SD=HSCH

314106 - Troubleshooting MS-DOS-Based Programs in Windows

http://support.microsoft.com/default.aspx?scid=kb;en-us;314106&FR=1&PA=1&SD=HSCH

Entries in Config.nt or Autoexec.nt May Cause NTVDM Errors (Q156687)

http://support.microsoft.com/support/kb/articles/q156/6/87.asp

To check your RAM.

http://www.memtest86.com/

http://oca.microsoft.com/en/windiag.asp

http://www.simmtester.com/PAGE/products/doc/docinfo.asp

To check your Hard Drive.

The drive manufacturer will have free diagnostic software to check your drive for problems.

Try running ChkDsk to check your drive for errors. Right-click your Drive icon/ Properties/ Tools/ Error Checking. Select both boxes.

Run the System File Checker program from the Run Box by typing.....Sfc /Scannow in it and have your XP CD handy.

 

[goombawaho]

I haven't been to visit the client yet so I have no idea what they're doing with the PC.

I wasn't asking for the "how to" part of this as I know how to diagnose bad hard drives and test for bad memory. I was asking if anyone thought the root cause could be on the hardware side as opposed to "a windows file just got corrupted spontaneously". So I'll rephrase my question:

Is it likely a hardware root cause (HDD or memory) vs. a software root cause (Windows just being Windows).

Thanks for the links about NTVDM - I will review those in case the client is doing something weird.

 

[linney]

By default I am "guessing" it is more likely to be software related than hardware.

If it was a hardware problem you would think that more processes would be showing problems rather than just NtVdm.exe?

The overall health of any machine can often be determined by visiting the Event Viewer and looking for any Red "X" errors.

 

[goombawaho]

System won't even boot - it's in an infinite loop of checkdisk then blue screen then reboot and repeat. I'll report back after seeing the machine today.

 

[linney]

If you can get to the Safe Mode options screen, you have the option to turn off any automatic restart and to halt at the blue screen so that you can see what the error is, and whether it also references NtVdm.exe.

Chkdsk Runs Each Time That You Start Your Computer

http://support.microsoft.com/?kbid=316506#kb1

CHKNTFS.EXE: What You Can Use It For

http://support.microsoft.com/default.aspx?scid=kb;EN-US;160963#kb1

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000 and Later (Q218461)

http://support.microsoft.com/support/kb/articles/q218/4/61.asp

Chkdsk runs everytime on start up?
thread779-958348

 

[goombawaho]

Laptop resumed a parallel installation of Windows XP Pro when I turned it on. Unfortunately for the client, his license was for XP Home, so we had to cancel that.

Ran a chkdsk from Bart PE and found lots of errors. Ran second - no errors. On reboot still blue screened with a 0X0000007B. Ran HDD diagnostic test and found no problems. Ran memory test and found no problems. Tried to do an XP Home repair install and it failed in a very strange way (keyboard and mouse stopped working after "failed to load installer for tape controller" error) during setup.

Client wanted to give up at that point. Would need to run further diagnostic tests to determine what hardware problem is happening. Some bad juju in that laptop. Case closed for now - no love from the laptop gods.

 

[BadBigBen]

0X0000007B

this indicates that the install can not find a certain DRIVE, happens usually with SATA drives, due to missing drivers, during install...

check the laptops BIOS for the SATA setting as IDE or IDE LEGACY MODE... if it does not have those two, then you will need to supply the XP Setup (F6 prompt at the very beginning) with the appropriate drivers


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[goombawaho]

I highly doubt that a mainstream Dell laptop would require a SATA driver loaded via F6, but it's possible. Anyway, I'm done with this question because the user doesn't want to pay me for any more troubleshooting. Good luck to him!!