1.

Solve : strange errors when driver wasn't not able to update properly?

Answer»

well i have a geforce 210. i recently tried to update the driver but a last step of updating the step said that the installation wasn't completed. now every time i start my computer there are two errors that come.
first-RunDLL32.exe-entry point not found
the procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll.
this error also come when i open my nvidia control panel and also whew i start a game with great graphics
please help me this error has slowed down my pc too.
i have a HCL pc with pentium 4 processor and 1 gb ram and 1 gb ram with graphics card. assuming a windows pc you're using,

use the System Restore to revert pc back to way it was before you did anything about driver updates.

well i tried that but there is no recovery point on the date when i updated thatCheck out these links.  And what Operation system are you running?

first-RunDLL32.exe-entry point not found

http://support.microsoft.com/kb/832323


the procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll.
 

 http://in.answers.yahoo.com/question/index?qid=20100320004848AAWKF5ri have windows XP proI just copied this answer from one of the links, however, both links indicate both errors might have to do with a service pack issue. When was the last time you updated your most current Win xp SP.    I am not entirely sure this will fix the problem.  I am just troubleshooting the errors right now.


The error is NOT caused by your application writing over MSVCRT.DLL, it is caused by the fact your game developer used either a newer or older library for that DLL when the game was created. Since this is a fairly new game I expect that your system is a little out of date.

Best solutions are to
a) ensure you have the most recent Service Pack installed for the O/S
b) if that doesn't fix it then check the support site for the game to see if they have a fix or patch available.
i have the latest service pack 3
and this error is also coming when demon TOOLS automatically starts after shut down Which version of Deamon tools do you have? Have you tried uninstalling it to see what effect it has on your computer. shaurya21, click start, then run. Type devmgmt.msc into the box and press enter. This will open device manager. In device manager, right click the video adapter and select properties. Click the driver tab, then click on Roll Back Driver and click OK. Quote from: IowaMrs on December 24, 2011, 08:47:37 PM

Which version of Deamon tools do you have? Have you tried uninstalling it to see what effect it has on your computer.

i have demon tools lite Quote from: JJ 3000 on December 24, 2011, 09:33:16 PM
shaurya21, click start, then run. Type devmgmt.msc into the box and press enter. This will open device manager. In device manager, right click the video adapter and select properties. Click the driver tab, then click on Roll Back Driver and click OK.

I can only see display adapters in device managers Quote from: shaurya21 on December 20, 2011, 01:26:26 AM
well i have a geforce 210. i recently tried to update the driver but a last step of updating the step said that the installation wasn't completed. now every time i start my computer there are two errors that come.
first-RunDLL32.exe-entry point not found
the procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll.
this error also come when i open my nvidia control panel and also whew i start a game with great graphics
please help me this error has slowed down my pc too.
i have a HCL pc with pentium 4 processor and 1 gb ram and 1 gb ram with graphics card.

This probably has nothing to do with anything. What antivirus are you using? I was wondering if something else might be causing the slow down of your computer. 

Ok, just to recap. You tried to update geforce210  drivers but were given message wasn't completed.  and got the errors you mentioned. So the problems started with updating driver and everything with your computer was working "perfectly" up to this point? Quote from: shaurya21 on December 25, 2011, 04:20:33 AM
I can only see display adapters in device managers

That's it. Click the plus sign next to that to expand the menu. You should see your graphics adapter there.

If that doesn't work for you, try installing a fresh copy of your video driver.

Daemon Tools...no matter what version will mess up hardware profiles...
If you are not currently using it ...get rid of it.well i roll back my driver but still error is coming. first it used to come after complete start up the windows but now it is coming in the starting screen and multiple time See Above...has it been suggested to try and uninstall drivers and then attempt reinstall to see if things would be properly installed this time around?On my Win7 System:

Code: [Select]C:\Windows\System32>dumpbin /exports msvcrt.dll | find /i "_except_handler4_common"
       
        346   159 00023E27 _except_handler4_common

File Version of the file is 7.0.7600.16385

running the same command on a fully patched XP SP3 system- I get nothing. No _except_handler4_common is exported in the XP version. (file version for that one is 7.0.2600.5701, btw).


I also tried installing the VC++ 2008 and 2010 redistributables but neither one updated the file.

However. The exception function being called CLEARLY marks it as a Exception handler; the number (4) and the fact that there are in fact similar exports for 3, 2, and 1 in the file led me to believe that it may be that the file msvcrt.dll isn't considered to be part of the c-runtime (in fact, most systems I've seen, it is only updated by the OS or service packs). So, those wouldn't be changed regardless. This leads me to think (further) that it's related to a compile-time option, whereby you can choose to either statically link the C Runtime, or dynamically link to it as a dll, in the latter case, most programs will link against msvcrt.dll- and thus the problem, since depending on the version of the C run-time .lib file that is being used, it will try to link against FUNCTIONS that don't exist in earlier versions of windows.



The answer, from what I can gather, is that the programs were compiled wrong. they aren't supposed to link against msvcrt.dll- they should be linking against msvcr80.dll (or the appropriate version for the compiler in use). msvcrt.dll is only to be linked against by window applets and components. Additionally, it should not be updated by anything other than service packs or KB hotfixes. (this includes things like the redistributables).

The problem therefore, has several causes- either the software is stupidly(not surprising given the software in question) linked against msvcrt.dll for no good reason, or, more likely, there is some other component or DLL copied from a Vista system onto the XP system, possibly in the hopes of "upgrading" it, and of course the Vista/7 file depends on the Vista/7 OS version of the dll.


Discussion

No Comment Found