Just tried the comp again and it came up with a blue screen saying STOP: c0000221(bad image checksum) The image shell32.dll is possibly corrupt. any ideas

Dani AI

Generated

Following 's BSOD that points at shell32.dll, the fastest targeted fix is to restore a known-good copy of that DLL from the original Windows CD. That keeps repairs low-risk and avoids a full reinstall right away. Match the copy to the same Windows build/service pack; a wrong version can make things worse.

Boot the machine from the Windows XP CD, press R for the Recovery Console, pick the Windows install number and supply the Administrator password. Then back up the existing file and expand the CD copy (adjust the CD drive letter if it is not D:):

copy c:\windows\system32\shell32.dll c:\shell32.bak
ren c:\windows\system32\shell32.dll shell32.bad
expand d:\i386\shell32.dl_ c:\windows\system32\shell32.dll
attrib -r -h -s c:\windows\system32\shell32.dll

After reboot, run a full check of hardware and offline malware scanners before trusting the system. Faulty RAM or a failing disk can corrupt system files repeatedly; run a memory tester (memtest86+) and check the drive's health/SMART from a bootable utility. If the replacement does not clear the stop code, gather user files with a rescue/live CD and consider a more complete repair path. This note builds on the earlier replies from and by showing a practical, step-by-step recovery action that often fixes a single corrupted system DLL.

Recommended Answers

All 2 Replies

Run ChkDsk on it and go to windows update and update windows.

Do a windows repair. It might as well overwrite the corrupt File.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.