Hello there,

 

I require help on finding what's caused FSX to crash after 2 hours and 12 minutes of flight. I am now steaming with anger in desperation to find a solution to this problem, because typically a piece of s**t called FSX made by the entirely awful Microsoft, managed unsurprisingly to crash yet again (sorry for either sarcasm or hate out of frustration). I have got some of the error details from the reporting tool of Windows 7 once FSX has crashed, the headings are in my native language, however I do hope you only need the figures and the info beside the titles - if not, I'll be happy to translate them for you ^_^

 

I was reading a bit on the latest CTD's and I haven't found the exact solution in the answers, however I can confirm that I have the UIAutomationCore.dll fix inside the FSX folder, and I have NVIDIA GTX560 GPU.

 

Hope you can help me, thank you in advance.

 

Nazwa zdarzenia problemu: BEX
Nazwa aplikacji: fsx.exe
Wersja aplikacji: 10.0.61637.0
Sygnatura czasowa aplikacji: 46fadb14
Nazwa modułu z błędem: FSUIPC4.dll
Wersja modułu z błędem: 4.8.2.7
Sygnatura czasowa modułu z błędem: 4f993421
Przesunięcie wyjątku: 00087375
Kod wyjątku: c0000417
Dane wyjątku: 00000000
Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.1
Identyfikator ustawień regionalnych: 2057
Dodatkowe informacje 1: 719b
Dodatkowe informacje 2: 719bb1fc3f1abd658fdcc1d79733d6f5
Dodatkowe informacje 3: 0408
Dodatkowe informacje 4: 0408537b5b6f07b8061fdb60db923ee4

The exception code c0000417 indicates you had a "STATUS_INVALID_CRUNTIME_PARAMETER", which indicates some sort of problem in the MS Visual C++ RunTime libraries. The fact you have the "uiautomationcore.dll fix" inside the FSX folder could be the problem. The uiautomationcore.dll is part of the Microsoft.net framework. You should have Versions 1 thru 4 installed. Version 4 comes with Windows 7. Dotnet is used by developers to run their software. None of the versions are backward compatible so, if a developer used Version 1.1 of dotnet, that's what FSX is looking for. Although they are not backward compatible there isn't any known drastic changes so a later version might work for a while with FSX but may eventually crash your system. The uiautomationcore.dll installed in your FSX folder should be the one that came with Vista. I works for some and doesn't for many.

 

Look in your Add/Remove Programs and see that your have all of the Microsoft Visuals C++ Redistributables 2005, 2008, and 2010 installed. These are runtime libraries that are used by developers to install a product on your computer. If not properly installed, it will not function properly.

 

Problem event BEX indicates a Buffer Overflow Exception. Your virtual memory (page file) setting should be set as "system managed mode". I read somewhere that Windows 7 handles virtual memory better than previous OS's. It has fixed a lot of problems here.

 

In regards to the FSUIPC.dll as the faulting module, you appear to have the latest version installed. A conflict could occur if you have your joystick settings set up through the FSUIPC module and your joystick caused the crash. That's a long shot though. the FSUIPC.dll is very good and it probably was called up as the faulting module as that was the module being called by FSX at the time you had CTD.

 

I think FSX works well for being over 5 years old without a patch but I understand your frustrations. Hope this bit of info helps you resolve your problem.

 

Best regards,

Jim

Thank you for your reply Jim,

 

It seems I have all the redistributables installed, 2005, 2008 and 2010 are present...

 

 

Could you tell me more about the uiautomationcore.dll please? I just dropped in a single file that I downloaded from the internet, supposedly a Vista version of the file, and it is present in the FSX folder. And how can I set the Virtual Memory inside Windows 7 to be "system managed mode"? Regarding the joystick and FSUIPC, yes, I do have a joystick, however it is configured through FSX.

 

I have also rolled back on the GPU driver, uninstalling 301.42 and installing the older 270.84. I'll see how that works and I'll report back. I have also decided to use an autosave software in case it crashes again.

 

Thank you.

You are missing SP1 to the 2005 Redistributable which was released after Acceleration was released - http://archive.msdn.microsoft.com/KB961894/Release/ProjectReleases.aspx?ReleaseId=2067. The 2005 Redistributable was included in the Acceleration program but SP1 was released afterwards and should be installed if you have Acceleration installed.

 

I do not recommend the uiautomationcore.dll fix. It works successfully for some but, like you, it doesn't work for others. I would remove the dll from your FSX directory. The uiautomationcore.dll was first included in Microsoft.net framework packages starting with Microsoft.net 3.0. Here's more info about the dll - http://en.wikipedia.org/wiki/Microsoft_UI_Automation. If you have all of your Microsoft.net packages installed from version 1 to version 4, you should be fully updated. Microsoft.net framework has many functions for developers including managing memory for the programs they developed. The important thing to know is that it is not backwards compatible. So, if you just have version 4 that came with Windows and FSX developers developed their product using a lessor version such as Version 2.0, then you could have an issue. You can look in your C:\Windows\Microsoft.net\Framework to see what versions you have installed. Most developers will install the proper version if not seen when you install a FSX product so you most likely have all versions installed. You just need to check.

 

To check your Virtual Memory, click on the Start button and in the search box type Virtual Memory then look up and click on How to Change Virtual Memory.

 

I doubt you have a video card driver issue but worth a try. Do you have UAC enabled or disabled. See if the problem continues with UAC disabled. To get to the UAC, click on the Start button, type UAC in the search box then look up and click on How to change the User Access Controls setting (or something like that).

 

If you ever get another CTD involving the FSUIPC.dll, immediately check the FSUIPC log in the FSX\Modules directory. A log is created everytime you run FSX and provides valuable information about what is happening inside FSX. Pete Dowson, the creator, would need to see this log should it be determined his dll is at fault.

 

The Event Viewer is another excellent Source for investigating your crash. It reports every event that occurred on your system and especially every CTD. Looking at the events just before your crash might provide a clue as to what caused your crash.

 

Best regards,

Jim

 Nazwa zdarzenia problemu: BEX
Nazwa aplikacji: fsx.exe
Wersja aplikacji: 10.0.61637.0
Sygnatura czasowa aplikacji: 46fadb14
Nazwa modułu z błędem: StackHash_927f
Wersja modułu z błędem: 0.0.0.0
Sygnatura czasowa modułu z błędem: 00000000
Przesunięcie wyjątku: 00000000
Kod wyjątku: c0000005
Dane wyjątku: 00000008
Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.1
Identyfikator ustawień regionalnych: 2057
Dodatkowe informacje 1: 927f
Dodatkowe informacje 2: 927fc7cbcb688a30214507594464a4ed
Dodatkowe informacje 3: cdf7
Dodatkowe informacje 4: cdf7e507a6696bab85b93c6748c41ff7

 

And again... It's hysterical. This time I was taxiing after a 2h 30min-ish flight, and it crashed. Seems that the video card drivers weren't the issue, and I have UAC disabled. FSX is ran as administrator. The thing that annoys me about that is I have to keep re-doing the same flight, because I use a PIREP software to report the flight back to a VA.

 

Also, forgot to mention that my system and found this: http://www.sevenforu...-c0000005.html. Third or fourth post talks about upping voltage on the CPU. My system is overclocked at 4.5GhZ and the voltage is 1.3V and the system seems quite stable after testing, and has been for a week or two now. Would it be good practice to increase the voltage?

 

And this: http://forum.avsim.net/topic/372170-stackhash-0a9e/. I've changed "Virtual Memory" to be managed by system and rebooted. I'll see how I'll go, but I probably won't be flying today, simply fed up with FSX :lol: - wish you could just get in and fly, but FSX requires a lot of optimization. But I'm keen to fly on this rig without any problems

1.3V is very low for an overclocked system. I overclocked my system to 4.4 and set my V Core to 1.4000. Once I lowered it to something like 1.34000 and my system started crashing so moved it back up to 1.40000. It's an easy fix worth exploring. The last link you referenced about Virtual Memory was from me and the recommendation to change to System Managed Size worked for this individual. I should have asked whether you were overclocked or not as that causes a lot of crashes and simply changing CPU voltages or memory frequencies/voltages/timings fixes most systems. Your PC specs do not indicate you are overclocked.

 

Srjan Word Not Allowed has an excellent guide pinned over in the hardware forum that might help too.

 

Hope you can get back to flying.

 

Best regards,

Jim

Hey Jim,

 

I think the Virtual Memory setting was the solution, I managed to complete the flight in 02h35min. I'll do however further testing, just in case it happens on longer flights, and if that fix doesn't work or something, then I guess I'll need to dig down further.

 

Thank you.

Glad it worked Kamil. I would still look seriously at your CPU voltage too. Look over in the hardware forum for settings others use with a similar system.

 

Best regards,

Jim