VS2008 - Users experiencing "Faulting module name: MSVCR90.dll"

Question

_{Tuesday, December 24, 2019 8:10 AM}

Just to note, I am not a programmer by trade. Hobbiest at a stretch. 

We are forced to use VS2008 as our code is from early 2000s.

Many users of our application are getting the following error in Event Log.

Faulting module name: MSVCR90.dll, version: 9.0.30729.9619, time stamp: 0x5c4bd872
Exception code: 0xc0000417 
Fault offset: 0x000532cd
Faulting process ID: 0x47d0
Faulting application start time: 0x01d5ba26ae5225eb
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\game\game. exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft .vc90. crt_1fc8b3b9a1e18e3b_9. 0. 30729. 9619_none_508d9c7abcbd32b6\MSVCR90. dll
Report ID: 7f76a236-78fd-4c15-adaf-9df03438f5dd
Faulting package full name: 
Faulting package-relative application ID: 

They have "Microsoft Visual C++ 2008 Redistributable Package (x86)" installed. 

Any ideas?

All replies (4)

_{Wednesday, December 25, 2019 3:06 AM}

Hi JOGARA,

Welcome to MSDN forum.

This error message is more related to the corruption of the dll files. Also, other updates may affect it too.

You could refer to suggestions below to troubleshoot.

#1. If possible, please try to update your windows system to the latest version.

#2. Try to uninstall and re-install “Microsoft Visual C++ 2008 Redistributable Package (x86)”.

#3. Please try to repair VS 2008 from control panel -> find VS 2008 -> right-click -> change -> repair.

#4. Maybe, re-install the application will fix this error.

In addition, you could refer to this link: unable to open game, and I hope this could help you.

BTW, I’m not sure if this issue is caused by the compatibilities between the application(maybe steam) and the windows system. (Maybe, you could try to update the application)

Hope all above could help you.

Best Regards,

Tianyu

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

_{Wednesday, December 25, 2019 7:35 AM}

I know seeing the Microsoft CRT file name there makes you think, "aha, there is a bug in the CRT".

However this is one of those situations where a bug somewhere else can cause the crash to appear in another location. What's more, this crash seems to be a perfect example of this happening.

The second line, the Exception code, has a value of 0xC0000417. This is an NTSTATUS value and is documented. This value is documented as:

STATUS_INVALID_CRUNTIME_PARAMETER

"An invalid parameter was passed to a C runtime function."

So your code is calling a CRT function with a bad parameter, and instead of allowing something bad to happen, like writing to a block of memory too small for the data that you are trying to copy into it, the CRT is taking down the entire application.

So unfortunately this is a bug in your code that is showing up by the CRT reporting the error. You would have to debug the code to figure out where it is occurring and fix it.

This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.

_{Thursday, December 26, 2019 10:42 AM}

But this only happens with a small % of users.

And the dump file is not being created on their systems when the crash happens.

SmartAssembly is not even reporting the issue.

_{Friday, December 27, 2019 11:41 AM}

I don't know what you expect me to write in response to this post. Why do you think that this happening with a small percentage of users means anything different?

This is especially true when the functions that validate the parameters for the CRT explicitly states that it terminates the process with this exception code.

This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.