Hi everyone

 

I am currently getting this black screen issue ever since formating to Window 7 Ultimate 64 bit . I have tried all the fixes in avsim forum one of them is adding a window vista uiautomationcore.dll to my main fsx folder. That didn't work but it helps when moving to some menu items like switching views or something . The problem is every time am flying for a long period of time when it comes to existing let say for example fspassengerx like tring to save the flight i just did my screen goes black an i can still here the sound the engines in the back ground . I have try reinstalling fspassengerx but the problems keeps happening . An i notice is not with fspassenger because when i click to view the map or something after a long flight i also got the black screen isuee. I have try adding vSync FIX but that doesn't solve the issue. I was searching on google for the error number i got from even viewer. An some one said this can fix this issue but am not sure if its right please help me out here . This is the fix someone suggested

 

 

 

FIX

 

 

I tried completely deleting the uiautomationcore.dll file from both the syswow64 and system 32 folders. Now I am playing FSX with graphics and traffic settings set to custom and turned all the way up while I have aircraft, scenery and weather settings turned to ultra high and no crashes for two days!!!! I can click in and out of any menu such as the MAP or virtual flight path or change aircraft mid-flight or change weather mid-flight with no crashing. I have tried every which way to get FSX to crash and I just cannot get it to!

FSX really is awesome when it works.

HERE IS THE FIX: You may have to take ownership of the files if windows stops you from deleting the file. Open CMD prompt and right click to run as administrator and then type in exactly as below substituting your windows login username where it says username:

takeown /f C:\Windows\System32\uiautomationcore.dll

cacls C:\Windows\System32\uiautomationcore.dll /G username:F

takeown /f C:\Windows\Syswow64\uiautomationcore.dll

cacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F

Now you can just navigate to your syswow64 and system32 folders in windows explorer and after backing up the UIautomationcore.dll files just delete them from your computer. (Remember to delete the Uiatomationcore.dll file in ure FSX folder also if you installed it as the fix in other posts.)

 

-------------------------------------------------------------------------------------------------

 

I don't think this is right , or i don't even know if will damage my system so i haven't try it. I just want someone to confirm that his is safe an that it actually works . Here is the error message i got when when my screen went black .

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc000041d

Fault offset: 0x732c4f0d

Faulting process id: 0x12c4

Faulting application start time: 0x01cd7af345afce7c

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: ef9ce4a8-e706-11e1-9de4-8c89a564bab2

 

 

Can someone help me solve this issue i am kind of new to window 7 64bit?

I definitely would not try that uiautomationcore.dll 'solution'. For one thing, deleting any system file from Windows 7 could create even more problems, not just with FSX but with other software on your computer. The dll is part of the Windows.net framework package. The first one was released when FSX was developed and it should be located in your C:\Windows\Microsoft.net\Framework folder. You should have Versions 1 through 4 installed.

 

There are many solutions (found by others) for your black screen problem and with FS Passengers. Just go to Google.com and do a search for fs passengers black screen. Most likely it is a problem with your video card driver and settings. When you search, there will be many fellow flight simmers from the whole FS community that have produced solutions to this problem but it's not the same for everyone. That's why I'm directing you to Google so you can read the 'solutions' yourself. There have been a lot of people in this forum who have problems with FS Passengers. Make sure it is up-to-date and you check out their FAQ for potential solutions. You are not the only one.

 

Best regards,

Jim

I definitely would not try that uiautomationcore.dll 'solution'. For one thing, deleting any system file from Windows 7 could create even more problems, not just with FSX but with other software on your computer. The dll is part of the Windows.net framework package. The first one was released when FSX was developed and it should be located in your C:\Windows\Microsoft.net\Framework folder. You should have Versions 1 through 4 installed.

 

There are many solutions (found by others) for your black screen problem and with FS Passengers. Just go to Google.com and do a search for fs passengers black screen. Most likely it is a problem with your video card driver and settings. When you search, there will be many fellow flight simmers from the whole FS community that have produced solutions to this problem but it's not the same for everyone. That's why I'm directing you to Google so you can read the 'solutions' yourself. There have been a lot of people in this forum who have problems with FS Passengers. Make sure it is up-to-date and you check out their FAQ for potential solutions. You are not the only one.

 

Best regards,

Jim

 

Wawo wish i had seen your post before trying this but i went ahead an try it out . The once i deleted was in window system 32 an 64 folder . I have run fsx an no menu crashes so far for some reason the computer loads program way faster. System seems to be stable . I also back up the same file as the current user stated to do in his instruction . I am still testing . To be honest i really didn't want to delete these files as many posted these files to be a solution to menu crashes . The problem is that the black screen issue is not with fs passenger x only but more than that. Its like when you are on a 2 hour flight an decide to minimize the screen or even go to a flight plan , maps an then is when i get those black screen crashes . I won't really called it crashes because fsx do not crash right away. It is only when i press ALT + Enter to minimize is when i get the crashes. I look up the error code in the event viewer , an by looking up the code in google is where i was lead to this solution .

i deleted was in window system 32 an 64 folder . I have run fsx an no menu crashes so far for some reason the computer loads program way faster. System seems to be stable .

 

Interesting. Glad you got FSX running again. Even though it looks like your system is running better and your problem is fixed, I still wont recommend this procedure but I hope it works for everyone who has a similar problem. The 64 bit version of the uiautomationcore.dll would never be used by FSX as FSX is a 32 bit program. Thanks for posting the fix(es) for your problem. It could help others.

 

Best regards,

Jim

Interesting. Glad you got FSX running again. Even though it looks like your system is running better and your problem is fixed, I still wont recommend this procedure but I hope it works for everyone who has a similar problem. The 64 bit version of the uiautomationcore.dll would never be used by FSX as FSX is a 32 bit program. Thanks for posting the fix(es) for your problem. It could help others.

 

Best regards,

Jim

 

Thanks Jim for your help . I just have one question dow an i wonder if this was the cause of my problem . The uiautomationcore.dll that i was using in my fsx main folder came from a window vista version uiautomationcore.dll . Most simmers consider this to be the actual fix for menu errors. But i always ask myself doesn't this affects the computer or something running uiautomationcore.dll from a window vista version in my main fsx folder ?

FSX reads every .dll placed in the FSX main folder and that would trump any similar system dll. FSX was developed when the Vista OS was first released so this could be the reason the Vista dll works and the Windows 7 version does not. Still, I have never had this problem with the menus and I do not have the Vista version of the uiautomationcore.dll in my FSX folder. There are thousands of other users who do not have this problem (or at least they never reported it). It's strange why some have this menu error and others do not. I have done everything I possibly can do to replicate the error like opening and closing the menu but no crash 20 or 30 times but FSX continues to work like a charm. It's nice that placing the uiautomationcore.dll from Vista in the main FSX folder works for many but I don't think it's the 'magic bullet'. Many people who take long flights in FSX report this error often and I rarely use flightplans that are longer than 1 hour so maybe a reason I don't (and others) don't get the CTD. I'm thinking of renaming my 32 bit versions of the uiautomationcore.dll on my system and see if I see any improvements like you (and others) have indicated. However, it seems to me the Windows System File Checker (SFC /scannow Command) would fix it and download and reinstall the dll. Microsoft just released a newer version of Microsoft.net (4.5) but I see it did not update this system dll. It's possible Microsoft.net is no longer required on computers as I read that Windows 8 does not have it and, if someone upgrades from Windows 7 to Windows 8, you must uninstall Microsoft.net for Windows 8 to work properly.

 

Best regards,

Jim

FSX reads every .dll placed in the FSX main folder and that would trump any similar system dll. FSX was developed when the Vista OS was first released so this could be the reason the Vista dll works and the Windows 7 version does not. Still, I have never had this problem with the menus and I do not have the Vista version of the uiautomationcore.dll in my FSX folder. There are thousands of other users who do not have this problem (or at least they never reported it). It's strange why some have this menu error and others do not. I have done everything I possibly can do to replicate the error like opening and closing the menu but no crash 20 or 30 times but FSX continues to work like a charm. It's nice that placing the uiautomationcore.dll from Vista in the main FSX folder works for many but I don't think it's the 'magic bullet'. Many people who take long flights in FSX report this error often and I rarely use flightplans that are longer than 1 hour so maybe a reason I don't (and others) don't get the CTD. I'm thinking of renaming my 32 bit versions of the uiautomationcore.dll on my system and see if I see any improvements like you (and others) have indicated. However, it seems to me the Windows System File Checker (SFC /scannow Command) would fix it and download and reinstall the dll. Microsoft just released a newer version of Microsoft.net (4.5) but I see it did not update this system dll. It's possible Microsoft.net is no longer required on computers as I read that Windows 8 does not have it and, if someone upgrades from Windows 7 to Windows 8, you must uninstall Microsoft.net for Windows 8 to work properly.

 

Best regards,

Jim

 

Wawo Jim thanks this is really helpful thank you thank you so very much . When i first remove uiautomationcore.dl from my computer i thought it would act funny or something . But everything seem find desktop items starts up really quick.An fsx seem smooth up to now . Wawo judging from what you said i think there was never a reason for me to add uiautomationcore.dl to my fsx main folder . It is just that since i have done the same thing in my window vista 64 bit i figure i would have to do the same for Window 7 64 Bit. But i think is like you said maybe window 7 don't need uiautomationcore.dl that much . I think that is why my system behaves normal . What i will do now is search on google to see how many app uses uiautomationcore.dl to run well on window 7 . Because i don't have many programs on my computer just Cubase 5 music production software an FSX that is it . So i will have to test the result installing other software that our fellow simmers may have that doesn't involve fsx but could affect the computer performance with other software just like you said JIm .

 

Thanks Again

Goodday,

I would like to try to eliminate the ui files but sofar I cannot type in prompt.

it comes with C:/users/doeke which is my name

I went to prompt for administrators rights and i have full rights but I think i have to do more to get

the full ownership

because after typing the sentences it ignored what i did.

so first i have to get off C;/users/ and my name it comes automaticaly

any idea what i can do now.

Goodday,

I would like to try to eliminate the ui files but sofar I cannot type in prompt.

it comes with C:/users/doeke which is my name

I went to prompt for administrators rights and i have full rights but I think i have to do more to get

the full ownership

because after typing the sentences it ignored what i did.

so first i have to get off C;/users/ and my name it comes automaticaly

any idea what i can do now.

 

It is very difficult to understand what you are trying to do. Are you trying to get full ownership of uiautomationcore.dll so that you can delete it? You right click on the file (uiautomationcore.dll) and select Properties. Open the Security tab and go down to Permissions for Users. Click advanced then open the Owner tab. Under 'Change Owner to" click on Edit. Current owner should be trustedInstaller. Click on your userid, then okay. Close all open Windows. Right click uiautomationcore.dll and select Properties. Open the Security tab and under Group or User Names, click on your userid (C:/users/doeke) then click on Edit (to change permissions). Make sure you userid is highlighted then click on Full control and then click on OK and close. You now have full control (as well as the TrustedInstaller).

 

I would not delete any system file including the uiautomationcore.dll. If you want to see if the fix above works, just rename it to uiautomationcore.old or uiautomationcore.dll.orig.

 

Best regards,

Jim

 

Perhaps the following link will explain it better.... http://www.techrepublic.com/blog/window-on-windows/quick-tip-take-ownership-of-files-and-folders-in-windows/3688

thank you Sir, that was very helpfull.

I have followed your suggestion to put .old behind the ui files.

now i could switch easer from one to another within fsx

the only one which is still there is : when I have done switching i.e from missions to Mp and going to free flight and exit.

during exit i got the message fsx is not working anymore.

that one I cannot get rid of it.

during exit i got the message fsx is not working anymore.

that one I cannot get rid of it.

 

If you are getting the CTD when you exit FSX, that shouldn't be a problem. You need to provide us with info from your Event Viewer. For every crash, an 'event' is created. To learn more about the Event Viewer, click on the Start button and, then click on Help and Support. Once open, type Event Viewer in the search box. You'll receive several links about the event viewer and a link directly to your system event viewer. Once you open up Event Viewer, open up Windows Logs. Click on Application. In the middle column you'll see all the Events that occurred with Applications on your system. In the right hand column, click on Find... then type FSX. This should bring up the first FSX crash, click next and it will show you the next FSX crash. You want the latest crash. Once you find it, look in the right hand column and click on Copy and select Copy Details as Text. Then come back over here to this forum and paste the information into a new post here.

 

Best regards,

Jim