Arghh

 

Flying FSX KORD-KJFK default airports, default weather (thunderstorm) at cruise in NGX;  using UT2 and only scenery is FTX Global, and Vector. 1 hour into flight, hit the Q key, screen turns this semi transparent white with message fsx not responding. I had this at other times and it resolved itself in a couple of seconds. Now at 5 minute mark.

 

What causes this, and what's best course of action.

 

BTW using DX10, with Steve's fixer software. Most settings are balanced in fixer software and I applied highmem fix. Brand new high end PC.

 

Rob

You need to run AppCrashView to see what could have possibly caused this crash.  It could have been the NGX, UT2, FTX Global, Vector, FSX, or Steve's DX10 Fixer (less likely).  White screens could indicate memory starvation.  If you have your settings set too high and lots of Autogen, FSX is probably close to running out of Virtual Address Space (VAS) especially after flying for one hour or more.  The link to AppCrashView can be found in the AVSIM CTD Guide located to the right of this forum under Hot Spots plus tools to investigate your crash.

 

The fsuipc module has the capability of monitoring your VAS.  The freeware or registered versions of the FSUIPC utility will allow you to monitor the amount of VAS remaining during a flight session.  This might be valuable in troubleshooting Out-of-Memory (OOM’s).  Startup FSX and then enter the Addon Menu and select FSUIPC.  Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed.  The FS Window is for Full Screen sessions.  The FS Title Bar is for Windowed Mode.  AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then it logs usage throughout your flight.  You can then go to a website that converts KB's and determine how much VAS you had at the start of the flight and how much at the end or when FSX crashed.  I use http://www.whatsabyte.com/P1/byteconverter.htm.

 

Best regards,

You need to run AppCrashView to see what could have possibly caused this crash.  It could have been the NGX, UT2, FTX Global, Vector, FSX, or Steve's DX10 Fixer (less likely).  White screens could indicate memory starvation.  If you have your settings set too high and lots of Autogen, FSX is probably close to running out of Virtual Address Space (VAS) especially after flying for one hour or more.  The link to AppCrashView can be found in the AVSIM CTD Guide located to the right of this forum under Hot Spots plus tools to investigate your crash.

 

The fsuipc module has the capability of monitoring your VAS.  The freeware or registered versions of the FSUIPC utility will allow you to monitor the amount of VAS remaining during a flight session.  This might be valuable in troubleshooting Out-of-Memory (OOM’s).  Startup FSX and then enter the Addon Menu and select FSUIPC.  Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed.  The FS Window is for Full Screen sessions.  The FS Title Bar is for Windowed Mode.  AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then it logs usage throughout your flight.  You can then go to a website that converts KB's and determine how much VAS you had at the start of the flight and how much at the end or when FSX crashed.  I use http://www.whatsabyte.com/P1/byteconverter.htm.

 

Best regards,

 

Hello Firehawk 44:

 

You recommended looking at the "AVSIM CTD Guide located to the right of this forum under HOT SPots Plus Tools". Under "Hot Spots" I do not see any reference to "tools" or the "CTD Guide". Do you have any idea what I am doing wrong here or has that display changed since your reply? IGNORE THIS, I backed out of the CTD forum and see the hot spot now. Sorry!

 

The problem in this post sounds exactly like what I am seeing, although I may be running a little bit different system. My system specs are attached at the bottom of this reply. My fsx panel display also goes white, or somethat transparent and dim. When this happens, I cannot even shut down FSX, and task manager take forever to respond. I just restart the computer. This may happen immediately, or well into a flight.

 

Background:

I recently reformatted and reinstalled everything. Before doing this, for literally years I ran both FS9 and FSX with no problems, and all sliders with the exception of water effects and Land and sea traffic were maxed out with sliders full right. All hardware and installed software are exactly as the original which had no problem. That being said, many months ago when all was first installed, it seems I did see this problem, but this old memory cannot remember what my solution was then. I don't remember whether it just went away, or I found a solution.

 

Note: I have made backups of anything relevant before changing anything. If my change did not work, I replaced my change back to the original backup.

 

What I tried based on posts found by a google search by others claiming to have found a solution for their crashes to desktop:

 

1. First of all, I tried the old 3gbenabler/boot.ini/LARGEADDRESSAWARE patch that worked so well with XP. I tried implementing "4gb_patch.zip". I was quickly informed that this was already included in SP2. In spite of this I was able to make realtime 12 hour plus flights KJFKLLBG and LLBGKJFK flawlessly even with lengthy pauses and thought I had my problem solved. Unfortunately soon thereafter the crashes to desktop returned. I removed the resulting modified fsx.exe file and put my backup original back in.

 

2.

Someone recommended replacing the UIAutomaticCore.dll in the FSX root directory with one from Vista (I am running Windows 7 Home Premium). That dll was not present in my fsx folder, but I downloaded and tried the Vista version anyway. When it solved nothing, I removed it.

 

3. Another source recommended removing this same dll from both the System32 and SysWOW64 directories. I renamed both for a try. I thought I had it made again with successful flights, but soon the crashes again returned.

 

Now I am wading through the 1,509 posts relative to this problem in this forum seeking a solution. I will try your recommendations as soon as I can find the guide you reference, and can hopefully understand.

 

Your help is greatly appreciated:

RTH

 

System Specs:

Intel Core i7-2700K CPU

Corsair H80 Liquid CPU Cooler

SDRAM 1600 Memory

 

Windows 7 Home Premium 64Bit Operating System

EVGA SuperClocked GTX 580 Video card

EVGA GTX 285 1GB 512 bigt DDR3 Video Video Card

Latest Nvidia version Drivers

 

3 24" LCD Monitors

 

WD Velco/Raptor 200GB System Harddrive

WD Velco/Raptor 200GB fSX Harddrive

Seagate 320GB SATA FS9 Harddrive

Seagate 320GB SATA Backup Harddrive

 

2 each CDRW/DVDRW Drives

 

Knnica Minolta 2400W Laser Printer

HP Offricejet 4315V FAX/Printer/Copier

CH Pro USB Pedals

CH USB FlightSim Yoke

Microsoft FFB2 USB Joystick

Logitech cordless Keyboard

Logitech cordless mouse

High Speed Cable Internet/email Service with Router

 

Thermaltake Toughpower Grand TPG-1200 W v2.92 SLI Power Supply

 

SuperPower ATX Full Tower Case with Large side Fans

Customized for more ventilation (Seven Fans total)

Sorry for the misinterpretation.  I stated "The link to AppCrashView can be found in the AVSIM CTD Guide located to the right of this forum under Hot Spots plus tools to investigate your crash."  I should have stated "the link to the AppCrashView can be found in the AVSIM CTD Guide to the right of this forum under Hot Spots. The guide also has tools to investigate your crash."  I suspect I could have placed a comma after Hot Spots too.  I should have also stated FS9, FSX, P3D CTD Guide.  If you do not see it then you might need to clear your browser cache but it has been there for a long time.  You can also get access to the guide via the pinned topic at the top of this forum or under the AVSIM Publications tab at the top of this website.

 

The uiautomationcore.dll is part of the Microsoft.net (dotnet) packages that are installed when you install FSX/Acceleration and any addon.  IMHO, the uiautomationcore.dll in the main fsx folder is a placebo.  I have hundreds of CTD's in this forum where the individual had the uiautomationcore.dll in their main fsx folder and it did not stop their crash.  When I recommended they remove the dll, their crashes stopped.  Go figure!  The uiautomationcore.dll's in your main system folders should never be deleted or changed.  They are system dll's and they run other functions on your computer (but most likely not FSX).  The dotnet versions that run fsx are located in C:\Windows\Microsoft.net\Framework (x86) (then the various versions).  I guess these versions work in conjunction with the latest versions in your system folder.  You should have versions 2.2 through the latest in this folder.

 

If you are running Windows 7 Home Premium (like me) make sure it is the 64 bit version.  If it is the 32 bit version you will have less virtual address space (VAS) for FSX and your system programs to operate.  For 32 bit OS's, you get about 3GB's with a switch like the /3GB switch.  With the 64 bit version you get the whole maximum 4GB's of VAS.  With the newer systems, people are turning up the sliders and the settings.  They are modifying their fsx.cfg with additional tweaks like LOD_Radius=6.5 (max default is 4.5) and Texture_Max_Load=4096 (default is 1024).  This requires more VAS and it depletes pretty fast when you crank up the settings and throw in some other tweaks like BufferPools and Affinity Mask (which AVSIM does not recommend).  So that's what is happening.  You are getting memory starvation and it almost brings your system to its knees (well, in your case, it did bring it to its knees as you had to shutdown your system and restart to get it working again). 

 

The AVSIM CTD Guide explains VAS.  The PMDG 777 Intro Guide, starting around page 21, provides even more layman type information.  Many think they have a fast system that is overclocked to the max and they cannot understand why fsx still freezes or crashes.  It's most likely depletion of VAS.  There is a tool to test your VAS during a flight.  It can be configured with the fsuipc.dll module:

 

Monitoring VAS in FSX or P3DV2 – The freeware or registered versions of the FSUIPC utility will allow you to monitor the amount of VAS remaining during a flight session.  This might be valuable in troubleshooting Out-of-Memory (OOM’s).  Startup FSX/P3D and then enter the Addon Menu and select FSUIPC.  Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed.  The FS Window is for Full Screen sessions.  The FS Title Bar is for Windowed Mode.  AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then it logs usage throughout your flight. 

 

I use a program I found on the Internet to convert the KB's to GB's to see how much VAS I had at the beginning of the flight and how much left when I finished the flight - http://www.thebyteconverter.com/ .  When it gets low and into the MB's, you will start seeing massive slowdowns of everything on your PC as VAS is shared with your whole computer system.  In most cases your system will still continue to operate but you will have to close something or your whole system will lockup and crash.

 

As I stated above, the AVSIM CTD Guide has other suggestions for troubleshooting and fixing your fsx installation.

 

Hope this helps and apologize for any confusion I caused in my earlier post.  Being almost 70 my wordsmithing sometimes comes into question.  I just want you to know I share your frustrations when FSX does not work right.  This is why AVSIM created the excellent CTD Guide to help us get through our frustrations.

 

Best regards,

Jim, in all honesty, you don't look a day older than 50 in that photo of yours. (the next dick clark?) :-)

Wow!  Thanks for the compliment (I guess)!  My last name is Young so I'll always be young (but maybe not young-looking).  :lol:  That photo is about 2 years old (June 2012) and maybe I did a little photoshopping but Tom, the CEO here, photoshopped his too! :He He:

 

Best regards, 

I don't know if my problem (and the solution) is unique or not, but the following was my result:

 

I believe I tried all of the recommendations in the AVSIM CTD Guide, most multiple times with no positive results. Strangely, I never got an FSX error message in the AppCrashView unless it was something I tried and pretty well knew what I had done to cause it. After many transparent white screens with a lockup, I never saw any entry thereafter in AppCrashView. On at least one flight, after it locked up I went and did something else for a prolonged time, came back, and the flight had resumed. However, other related programs like FSC had given up indicating that they had lost contact with the flight when it locked up.

 

Fortunately I periodically backup everything with SyncBack. Obviously my system drive is the "C" drive. FSX is on a separate drive, "E". FS9 is on another separate drive, "F". My SyncBack backups are on a third drive, "H".

 

As a final attempt to find a solution, I did the following.

 

1. Renamed "E:\Program Files (x86)" to be "CDD Program Files (x86) 5-4-14"

2. Renamed "C:\Users\Roger\AppData\Roaming\Microsoft\FSX" to be "FSX 5-4-14

3. Copied "H:\E Harddrive FSX Backup\Program Files (x86)" to my "E" Drive

4. Copied "H:\C Harddrive backup:\Users\Roger\AppData\Roaming\Microsoft\FSX" to my "C" Drive.

 

So far after nine days and several flights, including duplicates of the former trouble flights, everything has been flawless. One odd thing that surprised me. In examining my FSX root directory, I see that the 6.0.6001.18000 version of the UIAutomationcord.dll is present. When I tried my new installation this dll was never seen in my folder, but was included in my backup which I am now using. I don't know from where it came, but everything seems to be working.

 

The value of backing up everything I think is obvious.

 

Happy flying:

RTH

 

One odd thing that surprised me. In examining my FSX root directory, I see that the 6.0.6001.18000 version of the UIAutomationcord.dll is present. When I tried my new installation this dll was never seen in my folder, but was included in my backup which I am now using. I don't know from where it came, but everything seems to be working.

Sometime late last year I discovered this issue as I don't believe in the uiautomationcore.dll fix but, whenever I looked in my main fsx folder, there it was. I said, now wait a minute.... I had removed this module several times already. I rightly determined that a commercial developer was placing the uiautomationcore.dll in the main FSX directory and the FSDT developer (Virtuali) admitted it was included in all of his airport scenery installers. He thought he had removed it but it was still there. He had it removed from all of his programs so, if you use an old installer of any of that scenery, it will install the uiautomationcore.dll.

 

Best regards,