Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
I just worked on a cutomer's computer with a BSD screen with an error message regarding "Bad Image Checksum" in Windows XP Professional. The file it had a problem with in this instance was the OLE32.DLL file.
This computer would not boot into normal or safe mode. I booted to the CD and went in to the recovery console, I found that all the directory structures and files seemed intact.
I then booted to the CD and reinstalled XP over itself. After the 20-30 install routine; XP booted fine, everything intact and working.
Most techs use the "install Windows over Windows" 'trick', but just so there is a record, this worked to resolve this problem for this problem, this time.
One of my favorite gripes is that people will spend days trying to fix some obscure problem when an hour spent reinstalling windows over itself will usually fix it.
0
Response Number 2
Name: Paul M Date: April 30, 2002 at 13:41:06 Pacific
Reply:
I couldn't agree more. I have always aved so much time just installing it again over itself. Why waste time looking for elusive currupt files!
Summary: At startup I get blue screen (bad image checksum) - image ole32.dll is possibly corrupt. The header checksum does not match the computed checksum. Any suggestions? thanks, vandal67...
Summary: When i turn on my pc i get a blue screen that says "stop: c000007b bad image. The application or dll \??\c:\windows\system32\sfcfiles.dll is not a valid windows image. Pleace check this against your i...
0 
