Hi, first of all thank you very much for developing this patch! I enjoy cockpitshadows and watereffects very much. But...

 

After a while my screen becomes black and Win7-64 brings this message:

 

 

In engish: the graficcard-driver has been recovered after a failure.

 

Unfortunatly this happens every time after about 10 or 15 minutes flying and the monitor is black after this message. FSX is not down, I hear the engines and can stop simulation with ESC. After that the start menu is visible, but the preview window with the chosen airplane is black. Restarting FSX and everything is okay, until the next breakdown after a few minutes of flying - no metter, where I am (Orbx or default FSX, all the same).

 

All about my pc-system you can find here.

 

Thanks a lot for any help!

Markus I have ati and cannot help you but I remember that somewhere here in this forum I saw a post about nvidia driver versions. Someone went to previous versions because of problems that he had. If you have the time do a search in this forum or wait the nvidia folks to answer you.

Thanks for your answer. Search inside Avsim-forums is a bit strange since they use Google and a search is over all forums... I've tried it with an older driver version (285.62) but got the same result...

Thanks for your answer. Search inside Avsim-forums is a bit strange since they use Google and a search is over all forums... I've tried it with an older driver version (285.62) but got the same result...

 

Hi Marcus,

 

I had to revert to Nvidia 304.48 drivers. I've had no trouble since. I have the same card as you have.

 

Jim

Sometimes just cleaning your card (if dusty) can take care of the problem.

Only a couple of problems will cause a hang, with or without the black screen - to happen after a flight has been in progress for a while, Markus:

 

1). If the OS is Windows 7 - then the culprit is likely the version of UIAtomationCore.dll in the system's root folder, and the answer is to put the compatible Vista 32-bit version into the flight sim's root folder. It's a common problem, and well documented. BUT - 2). the fact that you have an error message concerning the GPU tells me that it has had a failure which is caused by overheating - possibly, as Alain has said - due to dust buildup and/or poor cooling - bad air circulation. Investigate this as the number one cause, - you might check the temperature of the GPU (Nvidia Inspector gives this on its first page) and the case itself, too, but get back to us - tell us what you've found.

Thanks a lot for your answers.

 

The card is clean and water-cooled, even with very heavy games not more than 50°C, mostly mid forties using FSX.

I'll try to go back to driver version 304.48.

UIAtomationCore.dll is version 6.0.6001.18000 in FSX root and newer versions (6.1.xxx) in system32 and SysWOW64. I found this in Microsoft Community forum. Is it a solution to delete the DLL?

Hi Markus: No - do not ever delete the system .dll's!!! I know of that post, and whoever posted that should have his tongue and his fingers cut off! :lol:

 

The correct version to place in the FSX root folder is this one: download it, do as it's name suggests, and then rename it to its' proper name - UIAtomationCore.dll. It's version should be 6.0.5840.16386. The one you have does work for a while, but it does crash from time-to-time. This one has no issues at all. OK?

 

The version # for the Windows 7 OS is 6.1.7600.16385

 

That post in the Microsoft Community should be pulled. What does that person expect will happen if he/she has a new application running - that was compiled using the functions within version 6.1.7600.16385 (default) - and it has been changed it for an older version? Right - those new functions aren't there and the application will crash - the same way that FSX does when it tries to use the newer default one. FSX was "End of Life" when Windows 7 came out - so it was never tested to run on Windows 7. We are very lucky that it does - especially on the 64-bit version.

Thanks a lot for your answers.

 

The card is clean and water-cooled,

 

 

Is the card plugged on the red or blue faucet...... :Big Grin:

Hi Paul,

 

I read your post with interest, and although I've not had problems, curiousity made me look at my FSX root folder.

 

I don't have UIAtomationCore.dll. I do have ui.dll. Am I lucky not to have it? OR Lucky to have got away without having it? :unsure:

 

Jim

Just plain luck, Jim. There is a ui.dll in the stock FSX root folder.

 

The hang usually happens when you are running a commercial flight - say an NGX at O'Hare, weather, clouds, ATC, AI, 2D & VC and and FMC, and you access the Menu Bar (the normal "Flight - Aircraft - World - Display bar at the top of the screen) a goodly number of times, changing views, using the overhead - lots of mouse clicks, etc., Some, any, many of those clicks will be calling Active Sky, RC4, FSUIPC, Aircraft, World - and so on, and for FSX to interface with any, one, all of those programs - it uses an API - an Application Programming Interface, which contains a goodly number of functions which are used - called from within the dll - during any of that connectivity: --> Programs talking to other programs via an API. <--

If the version of that particular API is the wrong one - then one, some, many of the needed API functions may not be in the dll. Simple as that, and obviously the latest Windows 7 version is not backwardly compatible with our old FSX. When one accesses that menu Bar to initiate a connection to another program and needs a function from within a dll - it looks first for that dll in it's own root folder - so this is the place to put it.

 

Definitely not in the main Operating Systems - Systems32 and SysWOW64 folders!! :Thinking:

Thanks, once again for the explanation, Paul.

 

I hope I'm learning, but I'm definitely having to swim hard to keep afloat of all that's going on.

 

I mostly do short flights VFR, and I've got a real lean towards choppers, but I do like a longer IFR flight when I have time. I use Active Sky 2012, and Pro Flight Emulator, for those, but have not tried an IFR flight since I started tweaking, here, tweaking there, tweaking nearly everywhere, for DX10. :rolleyes:

 

Maybe I should put your Win7 version of UIAutomationCore.dll into my FSX, just in case a problem develops. I do have Win7-64.

 

Regards, Jim

Can't hurt anything, Jim. I put that one in a couple or three years ago, and she hasn't frozen since. Used to happen on every flight with the Maddog, just going from Seattle to Portland.

UIAtomationCore.dll

 

Just to clarify is it UiAtomationCore or UiAutomationCore? I went throught the process a long time ago, but I noticed that I have the latter in my root folder. Other threads reference uiautomationcore as well.

UIAutomationCore.dll.... Mat: good catch..(my wife wasn't watching my spelling...) :lol: