Installshield errors after overclock

Grease Monk

Grease Monk

Intertoob Ninja & Hamster Hunter Extraordinaire
Explorer
I recently tried my hand at overclocking, and I'm pretty sure i managed to corrupt some files on my hdd. Whenever i try to run some installations (those using installshield) i get the following error:

Unhandled Exception
Error Number : 0x80040706
Description : Object Reference Not Set
Setup Will Now Terminate

Nokia Phone Suite and the text message editor will not run any more. Any Free Download Manager doesnt start to auto download anymore. It says "free dwonload manager was not properly installed. Reinstall" Although it worked perfectly earlier.

Another odd thing is that my windows/system folder seems to only have 31 files in it. Is that normal or very low?

Even though these errors seem unrelated, i think they have a common cause.
 
assuming you are using xp or 2k, you can run sfc /scannow to check for corruption, as for applications just reinstall them.

also run chkdsk /f.
 
thanks for the info dips, however, when i run sfc, it keeps asking me for the xp disc (and i insert it) it doesnt detect it.

As for reinstallation, lol, thats the exact thing i cant do without installshield working.

will run chkdsk when i restart.
 
greasemonk, in that case try this, what you have to do is manually set the path of your xp installation, as the files req be sfc are not present in your dllcache folder or are corrupted, that's why it's asking for xp cd.

1. try to change the path of your xp installation, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ double click SourcePath & change the path to x:\ where x is your odd. reboot & run sfc.

or

2. copy the i386 folder from your xp cd to the harddisk say c: & change the path of xp install to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SourcePath - c:\ reboot & run sfc.
 
neither of the above steps worked. Just resorted to reinstalling xp. All is fine now. Thanks anyway.
 
ohh, cool then, but next time you overclock do it in small increments & run memtest after every o/c, followed be prime95.

p.s - as for the above steps not workin' there were additional steps to be followed in case they did not work ;) but anyways all's well that end's well :D
 
did exactly that (small increments followed by stability tests). Am starting to wonder if it was something else that triggered it off. But corruption of system files seems to be a characteristic of OCing.
 
Back
Top