MSVCR80.DLL and constant CTD

[Guest SuperFortress]

Last week I posted a question about getting a FATAL ERROR in FSX every time I switch from the VC to the external view and then back to the VC. This time I looked at the details of the error and it seems that a particular DLL is the cause of the problem. The MSVCR80.DLL. I have already read the existing thread here about this DLL problem. I've tried everything suggested in the thread but nothing seems to help. I'm so frustrated from reinstalling and reinstalling. I havent been able to use FSX at all and all I've done is experiment and experiment to alleviate this problem but absolutely nothing seems to help:(Does anyone have any kind of advice or suggestions please?Thank you.

[Guest PhilC]

Hi SF.Not sure what all you have done but it can really screw things up if you move the file around on your PC. It would have to be registered in the registry again.Do you have Microsoft Defender installed? From what I've read the only solution to this problem on most systems is to uinstall Microsoft Defender.Type MSVCR80.DLL in Google search and you may find some answers.Don't know if this is of any help. Good luck!

[Guest SuperFortress]

>Hi SF.>>Not sure what all you have done but it can really screw things>up if you move the file around on your PC. It would have to be>registered in the registry again.>>Do you have Microsoft Defender installed? From what I've read>the only solution to this problem on most systems is to>uinstall Microsoft Defender.>>Type MSVCR80.DLL in Google search and you may find some>answers.>>Don't know if this is of any help. Good luck!I think you're referring to Vista users. I did read about that in various google searches but this scenario does not apply to me since I am using WIN XP PRO SP2.However after spending more hours on this problem today I managed to narrow it down to anti-aliasing. If I completely disable AA in the Nvidia control panel and delete the AntiAliasing line from the FSX.CFG the problem finally stops BUT now I'm left with jagged lines everywhere since I'm not using AA. This is absolutely so annoying! Thank you for the tip though.

[moss1 11]

This is very interesting. Being that you did something related to your video card settings, and the problem seems to go away. Maybe it is a driver related issue of some sort. Did you change your video card drivers before this problem first appeared? Also, have you tried installing new drivers just to see. The other thing you can do, is uninstall the exsisting drivers, then reinstall them again if you don't want to go with newer ones. (newer is not always better). One quick note too, there is a program called Driver Cleaner Pro that is free. This ensures all remnants of the old drivers are out of your system before installing new ones, to avoid conflicts and other issues, If you do go down that road, be very carefull to follow the directions so you do not remove the wrong thing like MB drivers etc... I do hope this helps in some way or another. Keep us posted.

[Vox-tm 0]

I share your pain SuperFortress. I too am plagued with this problem, although not when switching views but when loading certain aircraft. Sad to say, I have tried *everything* to fix this, including emailing both Microsoft and NVidia. But as usual... silence. There doesn't seem to be a fix right now, even rolling drivers back to the original version that first supported my card.Word from Microsoft seems to be that you need to upgrade to Vista and a better NVidia card (check the CTD section for threads discussing this problem).Sorry, but MS/NVidia just don't care about us.Vox

[Guest SuperFortress]

>This is very interesting. Being that you did something>related to your video card settings, and the problem seems to>go away. Maybe it is a driver related issue of some sort. Did>you change your video card drivers before this problem first>appeared? Also, have you tried installing new drivers just to>see. The other thing you can do, is uninstall the exsisting>drivers, then reinstall them again if you don't want to go>with newer ones. (newer is not always better). One quick note>too, there is a program called Driver Cleaner Pro that is>free. This ensures all remnants of the old drivers are out of>your system before installing new ones, to avoid conflicts and>other issues, If you do go down that road, be very carefull to>follow the directions so you do not remove the wrong thing>like MB drivers etc... I do hope this helps in some way or>another. Keep us posted.This problem seems to be directly related to the SP1 update for FSX. Each time I did a complete reinstall I made sure to test FSX before installing SP1 and the crash never happened. It started immediately after installing SP1. It was only at this point that I began playing with various Nvidia drivers. Currently I'm using the 162.18 Beta drivers and before that I was using the 158.45 Beta driver. I guess I can try using the non-beta 94.24 driver again. And yes I always use Driver Cleaner anytime I install new video drivers. Thank you.

[Guest SuperFortress]

>I share your pain SuperFortress. I too am plagued with this>problem, although not when switching views but when loading>certain aircraft. Sad to say, I have tried *everything* to fix>this, including emailing both Microsoft and NVidia. But as>usual... silence. There doesn't seem to be a fix right now,>even rolling drivers back to the original version that first>supported my card.>>Word from Microsoft seems to be that you need to upgrade to>Vista and a better NVidia card (check the CTD section for>threads discussing this problem).>>Sorry, but MS/NVidia just don't care about us.>>Vox

[PhilTaylor 45]

Is this happening only with add-on aircraft?

[Guest SuperFortress]

>Is this happening only with add-on aircraft?Unfortunately this happens with any aircraft that I try, whether it's default aircraft or add-on. Thank you.

[PhilTaylor 45]

And any add-on utility?Did you try downloading the VS 2005 SP1 redist? It has a new msvcr80.dll, and if you have any add-on permanently loaded that requires it, and that add-on didnt install it for you; that could be a problem.

[Guest SuperFortress]

>And any add-on utility?>>Did you try downloading the VS 2005 SP1 redist? It has a new>msvcr80.dll, and if you have any add-on permanently loaded>that requires it, and that add-on didnt install it for you;>that could be a problem.The only add-ons I have for FSX are Flight1 Cessna 172, Active Sky X and X-Graphics however I've tried FSX without any of these add-ons and still manage to get the same problem. I know I did not have this problem prior to SP1. I did try the VS 2005 SP! redist yesterday but that made no difference. So far the only thing that works is disabling AA in the Nvidia control panel and deleting the AntiAliasing line from FSX.CFG. Thank you.

[PhilTaylor 45]

That would indicate a driver problem.

[Guest SuperFortress]

>That would indicate a driver problem.I agree but is there a particular Nvidia driver that I should be using instead of my current beta 162.18 driver? Thank you.

[Vox-tm 0]

Hi Phil and thank you for replying.At the moment, I don't seem to have the problem with default aircraft, only with add-on aircraft. However, I can generally get default aircraft to CTD by ALT-TAB task switching out of FSX and back again.I can concur with SuperFortress that switching off all AA seems to fix the problem and that despite trying all available driver versions for my nVidia card none of them solve the problem. I too also only experienced the problem after installing SP1. I have also tried installing the VS 2005 SP1 downloadable with the new msvcr80.dll, but that didn't work either :(I understand that it may well be an nVidia driver problem, but can I say that you at least have had the decency to respond to our problem and that is much appreciated... nVidia haven't even acknowledged my contact with them over this issue and may not even have made themselves aware of it.I guess something changed in SP1 that might well have exposed a video driver bug/shortcoming - is that possible?Vox

[PhilTaylor 45]

unfortunately the only advice I can give is to start walking back thru the versions until you find one that works.when you crash, do you get to send a report?