After recently reinstalling FSX, I now get an error when trying to use FPS Limiter. The error is: (0xc0000005) "app was unable to start correctly click ok to close. Has anyone else had this problem, and if so, is there a way to fix it? I used FPS Limiter for the past year without ever encountering this problem. I made sure to save my old bat file to use with my reinstalled FSX. It now doesn't work nor does the new bat file I created to replace it. All I get now is the (0xc0000005) error message.

Any help or suggestions from the forum would be much appreciated.

 

Gil Ferreira

Does anyone have any suggestions? Should this have been posted to Tip and Tweaks instead?

Gil

Made a folder, C:\Games\FSLimiter, installed from there and don't move anything. Make a desktop icon for the bat file.

 

Dave

After recently reinstalling FSX

 

When you un-installed FSX, did you also manually remove all of the junk it leaves behind, including all the registry entries for both FSX and all/any addons?

The 0xc0000005 error indicates you had a Memory_Access_Violation. Quite common with all FSX crashes. It probably means FSX was calling for a file and could not find it. I would recommend reinstalling the FPS Limiter. When doing so, make sure you have User Access Controls disabled as I think that prevents FSX from writing to a file, say, for instance to the dll.xml. To disable, click on the start button, type User Access in the search box then look up in the menu and click on How to Change User Access Controls. Once there, pull the slider down to disable. Now reinstall your product.

 

Best regards,

Jim

Thanks all for the wonderful suggestions. I'll try them in order, though I do have the UAC already disabled as I find it annoying. As for FSX remnants left behind, I cleared those that I'm aware of, but I didn't go through the registry. Everything was working just find and then suddenly, this error started coming up. I'll double check again and see if your suggestions fix the problem.

Thanks all!

Gil Ferreira

c0000005 is a null pointer error - it means the program expected a variable to be at a specific memory address and when it went to access it, the variable wasn't there or wasn't initialized. The value it reads is "null" and it crashes.

 

Do you have an Nvidia GPU? If so there's no need to use external FPS limiters like what you're using - the Nvidia drivers have one built in that's accessible through Nvidia Inspector.