mechasus

I think these are a growing problem that deserve a forum of their own; not CTDs, but the dreaded fatal freeze where the sound continues to loop but the sim quits responding. What's even worse is that these are not traced in the event log, so the problem requires more guesswork. This happens occasionally in FS2004 due to a number of different triggers, such as switching windows or using the menus too much, however the Project Airbus A320 is one aircraft that is unusable as it triggers a fatal freeze about 5 minutes into a flight. I've tested a few different JetBlue variations. The IFDG model worked with no problem. I'd like some help, I really want to get N606JB and some of the newer JetBlue liveries that IFDG doesn't have.

This worked. It got rid of the uiautomationcore.dll crash, but now igdumdim32.dll is causing crashes. I already said: Would rolling back an update be a possibility or switching to DX10? I hear some people saying they don't have the problem with DX10.

I did try a solution posted on other sites to download a fresh copy of "uiautomationcore.dll" and paste it to the FSX folder. It seemed to work under the circumstances that triggered this crash, however another DLL (igdumdim32.dll) is causing crashes that trigger when exiting the menu back to the sim. Updating the video driver will not work in this case, it is up to date. Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: igdumdim32.dll, version: 10.18.10.3355, time stamp: 0x52839a84 Exception code: 0xc0000005 Fault offset: 0x000c25c1 Faulting process id: 0x11dc Faulting application start time: 0x01d07700e3e3e2e4 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Windows\SYSTEM32\igdumdim32.dll Report Id: ce3f6eca-e2f9-11e4-82a0-f80f41c84939 Faulting package full name: Faulting package-relative application ID: fsx.exe 10.0.61472.0 475e17d3 igdumdim32.dll 10.18.10.3355 52839a84 c0000005 000c25c1 11dc 01d07700e3e3e2e4 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe C:\Windows\SYSTEM32\igdumdim32.dll ce3f6eca-e2f9-11e4-82a0-f80f41c84939

FSX crashed about 20-30 minutes into an IAD-EWR flight on the default CRJ-700, days after I had done the outbound EWR-DCA with no problems. Running in compatibility mode for Vista SP2. Addons running were Traffic X and various World of AI packs. Here are the results from the event log: Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Windows\SYSTEM32\uiautomationcore.dll Report Id: 79a363f1-e2c5-11e4-82a0-f80f41c84939 Faulting package full name: Faulting package-relative application ID: - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2015-04-14T16:44:11.000000000Z EventRecordID 48072 Channel Application Computer family-pc Security - EventData fsx.exe 10.0.61472.0 475e17d3 uiautomationcore.dll 7.2.9600.17415 54503bf7 c0000005 00004ec8 1d44 01d076ce5471accc C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe C:\Windows\SYSTEM32\uiautomationcore.dll 79a363f1-e2c5-11e4-82a0-f80f41c84939

3 Delta MD-88s (number unknown), 1 American Super 80 (number unknown), 2000, LGA-DFW-SAT Continental 757-300 (number unknown), Continental 737-900 N37409, 2008, EWR-MCO jetBlue A320s "Sacre Bleu", "A Friend Like Blue", 2009, EWR-MCO Continental 737-800s N16234, N76517, 2010, EWR-MCO Continental 737-700 N14731, ExpressJet ERJ-145XR N21130, 2011, EWR-CLT Mesa CRJ-900 N926LR, US Airways 737-400 N441US, 2011, EWR-CLT jetBlue A320s "Real Blue" (Real Salt Lake special), "It Had to Be Blue", 2011, EWR-MCO American Flyers Cessna Cutlass, N9851B, 2011, MMU Delta A319 N343NB, MD-88 N915DE, 757-200 N634DL, DC-9-50 N787NC, 2012, EWR-ATL-DAB United 737-800 N12216, 737-500 N19623, 2012, EWR-CLE Southwest 737-700 N556WN, 737-800 N8315C, 737-700 N786SW, 737-700 N402WN, 2013, EWR-MDW-LAS-HOU-EWR