Error messages are funny creatures. Generally, they'll tell you what file that the error occurred in - but not the file that caused the error.
It's sorta like the engine in a car dying - that's where the error occured (in your case in kernel32). But it could have been bad gas, it could have been sugar in the gas tank, it could have been that you ran out of gas.
IMO - telling you to reinstall the OS is a very premature assessment of the issue (and is most likely incorrect). The benefit of this approach is that you'll come out of it with a squeaky clean system - and since you'll have to update all your drivers and programs, the program will probably disappear.
It's been my experience that the majority of problems of this sort are caused by corrupt files. And, recently I've seen at least one other problem of this sort that was caused by the software.
Have you used the "Clear" utility when uninstalling the EasyShare software? If not, here's a link to it: http://www.kodak.com/global/en/service/dow...=go&idhbx=clear
When software is removed from your system, only the stuff that's got a certain permission level is removed. This leaves stuff on your system (in case you reinstall in the future, etc). Unfortunately, if an error occurs in one of the files/registry entries that is left, your attempts to reinstall won't overwrite this file and it still won't work. (This happened to me way back with Windows 95 - and I spent weeks on the phone with Packard-Bell trying to fix it!).
I'm willing to bet that the Clear utility doesn't remove everything. But the fact that they have developed it indicates a need to remove more than just what's removed through the Add or Remove Programs dialog.
Anywhooooo, enough of the gabbing!
Download the latest version of the EasyShare software from the Kodak site
Uninstall the software using the Add or Remove Programs dialog
Run the Clear utility according to the instructions
Install the latest version of EasyShare and see if this fixes it!
(FWIW - there are other things that could cause this, but the above technique is by far the most likely solution)
BTW - when you ran SFC.EXE /SCANNOW - did it ask for your installation CD? If it did, I'd recommend that you visit Windows Update to make sure that it didn't replace one of your updated files with the version from the CD.
Edited by usasma, 03 December 2005 - 07:50 PM.