GeorgeMB

Hello, Having read through some fourm history here about the BEX CTD I was wondering if there's been any new ideas on how to fix it. This error seems to be a slippery one. But lucky for me it only happens when I close FSX and not during a flight so far anyway. And I'm kind of nervous about renaming my fsx.cfg file or deleting any Facilities,Scenery,Shader folders. Thanks for any help. My two CTD's from it: Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: StackHash_27eb Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 7524cb49 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 27eb Additional Information 2: 27eb358fe674a6f15dafe56d42bb9bf3 Additional Information 3: 2f06 Additional Information 4: 2f06c18113e6d7c00e6b91fa1fde84b6 #1 Log Name: Application Source: Application Error Date: 8/20/2014 2:35:38 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: 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: 0xc0000005 Fault offset: 0x7524cb49 Faulting process id: 0x16cc Faulting application start time: 0x01cfbc4079f2b398 Faulting application path: C:\FSX\fsx.exe Faulting module path: unknown Report Id: 327e514b-2834-11e4-8a5a-00038a000015 Event Xml: <Event xmlns= <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-08-20T06:35:38.000000000Z" /> <EventRecordID>4659</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>7524cb49</Data> <Data>16cc</Data> <Data>01cfbc4079f2b398</Data> <Data>C:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>327e514b-2834-11e4-8a5a-00038a000015</Data> </EventData> </Event> #2 Log Name: Application Source: Application Error Date: 8/20/2014 2:35:38 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: 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: 0xc0000005 Fault offset: 0x7524cb49 Faulting process id: 0x16cc Faulting application start time: 0x01cfbc4079f2b398 Faulting application path: C:\FSX\fsx.exe Faulting module path: unknown Report Id: 327e514b-2834-11e4-8a5a-00038a000015 Event Xml: <Event xmlns= <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-08-20T06:35:38.000000000Z" /> <EventRecordID>4659</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>7524cb49</Data> <Data>16cc</Data> <Data>01cfbc4079f2b398</Data> <Data>C:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>327e514b-2834-11e4-8a5a-00038a000015</Data> </EventData> </Event> My rig specs: HP bought in 2009 Model #: p6340f PCBRAND: Pavilion Processor: Intel® Core™2 Quad CPU Q8400 @ 2.66GHz 2.67GHz RAM: 8.00 GB Windows 7 64 bit OP Graphics Card: Nvidia GeForce GTX 770 Driver Version 340.52 FSX Add-ons I have installed in my rig: FSX Gold Sp 1 and 2 REX OD FSUIPC4 V934 EZdok 1.17 A2A Accu-Feel V2 PMDG MD-11 FS2Crew MD-11 QW 757 Service Pack 3 Navgragh FMS Manager

Sorry double post.

Having CTD's wouldn't be so bad to me if your flight hours still got recorded into FSX somehow. Or a option to add the hours if you were keeping track yourself. Maybe someday someone will create a new logbook addon that can be edited in case of CTD's. Losing 5 to 9 hours of flight time is a painful thought to me. Especially if your flying in normal mode and not 4 or 8x speed. My worst crash was during a 4 hour flight, was just about to enter the BYP6 Star into KDFW in a PMDG MD11 when she froze in midair. Could still hear her 3 beautiful engines running for several minutes but soon they faded. A urge to destroy everything in my room flamed through my mind. But soon the rage cooled into a inquisitive mind set. I found out from other FSX users here that shutting off my UAC settings and taking out all the FSX files that were listed in my anti viruses low restricted folder, could stabilize my game. They were right. I still have issues but it's much better. That's how I will cope with crashes from now more analytically. On payed FSUIPC, I'm not sure if that saves totally everything you have set and had to program into the jet. Like FMS info and what if you started the flight with engines off or a pre loaded panel state? Not sure if saving will help.

You must of had to use simconnect and WideFS right? Great idea but sounds very complex to set up.

Thanks for the replies, this all sounds terrible. I'll try the A2A update, hopefully that will stabilize one issue. The MD-11 issue is weird because all I was going to do was a few traffic patterns. I didn't need to put much FMS route data other then DEP and DEST airport ICAO info. I took off no issue but then went to turn the heading knob and CTD. I find it cool that you guys can dissect issues with FSX CTD messages, wish I understood it but it's Greek to me. I have some more questions. Does Memory_Access_Violation mean I have damaged RAM cards or motherboard slots? will running FSX.exe in Compatibility mode for Windows 7 help stabilize it? I was told by someone in a other forum to make sure that I'm ''running with UAC turned off and run FSX from the right click menu item "run as administrator" Any app you run that touches FSX should be run the same way. The error messages all indicate an access violation which is typical if you have FSX in the default directory'' as I do. Does this UAC settings change suggestion hold water? I also been told to consider uninstalling FSX and reinstalling it but to load it into a different folder example C:\FSX instead of C:\Program Files (x86) Is uninstalling FSX and reinstalling FSX into a different folder advisable? As you can see I'm not all that computer confident. Well thanks again, best regards.

Hello, Been having FSX problems, all CTD crashes. My rig specs: HP bought in 2009 Model #: p6340f PCBRAND: Pavilion Processor: Intel® Core2 Quad CPU Q8400 @ 2.66GHz 2.67GHz RAM: 8.00 GB Windows 7 64 bit OP Graphics Card: Nvidia GeForce GTX 770 Driver Version 332.21 FSX Add-ons I have installed in my rig: FSX Sp 1 and 2 FSUIPC4 + FSUIPC490 update EZdok 1.17 A2A Accu-Feel V2 PMDG MD-11 FS2Crew MD-11 QW 757 Navgragh FMS Manager Here are the 6 CTD messages I have in just 2 days: #1 Log Name: Application Source: Application Error Date: 2/15/2014 8:38:41 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: PMDG_MD11.DLL, version: 10.0.61355.62, time stamp: 0x49b7c81d Exception code: 0xc0000005 Fault offset: 0x00118301 Faulting process id: 0xea4 Faulting application start time: 0x01cf2a4db4bbc1d6 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLL Report Id: 7b2fb04f-9646-11e3-99d7-00038a000015 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-02-15T13:38:41.000000000Z" /> <EventRecordID>3763</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>PMDG_MD11.DLL</Data> <Data>10.0.61355.62</Data> <Data>49b7c81d</Data> <Data>c0000005</Data> <Data>00118301</Data> <Data>ea4</Data> <Data>01cf2a4db4bbc1d6</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLL</Data> <Data>7b2fb04f-9646-11e3-99d7-00038a000015</Data> </EventData> </Event> #2 Log Name: Application Source: Application Error Date: 2/14/2014 3:47:02 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: A2A_Feel.dll, version: 0.0.0.0, time stamp: 0x50dc6814 Exception code: 0xc0000005 Fault offset: 0x0002af92 Faulting process id: 0x1764 Faulting application start time: 0x01cf2960ce5389b4 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll Report Id: 91fdf46b-9554-11e3-8d65-00038a000015 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-02-14T08:47:02.000000000Z" /> <EventRecordID>3525</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>A2A_Feel.dll</Data> <Data>0.0.0.0</Data> <Data>50dc6814</Data> <Data>c0000005</Data> <Data>0002af92</Data> <Data>1764</Data> <Data>01cf2960ce5389b4</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll</Data> <Data>91fdf46b-9554-11e3-8d65-00038a000015</Data> </EventData> </Event> #3 Log Name: Application Source: Application Error Date: 2/14/2014 3:42:10 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: A2A_Feel.dll, version: 0.0.0.0, time stamp: 0x50dc6814 Exception code: 0xc0000005 Fault offset: 0x0002af92 Faulting process id: 0x120c Faulting application start time: 0x01cf295df4175d35 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll Report Id: e3fa2cf8-9553-11e3-8d65-00038a000015 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-02-14T08:42:10.000000000Z" /> <EventRecordID>3519</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>A2A_Feel.dll</Data> <Data>0.0.0.0</Data> <Data>50dc6814</Data> <Data>c0000005</Data> <Data>0002af92</Data> <Data>120c</Data> <Data>01cf295df4175d35</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll</Data> <Data>e3fa2cf8-9553-11e3-8d65-00038a000015</Data> </EventData> </Event> #4 Log Name: Application Source: Application Error Date: 2/13/2014 9:54:31 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: 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: 0xc0000005 Fault offset: 0x751ec9f5 Faulting process id: 0x178c Faulting application start time: 0x01cf293005a44772 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: unknown Report Id: 537ebe0d-9523-11e3-8bec-00038a000015 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-02-14T02:54:31.000000000Z" /> <EventRecordID>3394</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>751ec9f5</Data> <Data>178c</Data> <Data>01cf293005a44772</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>unknown</Data> <Data>537ebe0d-9523-11e3-8bec-00038a000015</Data> </EventData> </Event> #5 Log Name: Application Source: Application Error Date: 2/13/2014 9:22:22 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: 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: 0xc0000005 Fault offset: 0x751ec9f5 Faulting process id: 0x1444 Faulting application start time: 0x01cf292b7b35f399 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: unknown Report Id: d589cd2f-951e-11e3-8bec-00038a000015 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-02-14T02:22:22.000000000Z" /> <EventRecordID>3360</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>751ec9f5</Data> <Data>1444</Data> <Data>01cf292b7b35f399</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>unknown</Data> <Data>d589cd2f-951e-11e3-8bec-00038a000015</Data> </EventData> </Event> #6 Log Name: Application Source: Application Error Date: 2/13/2014 9:20:32 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GeorgeMB-PC Description: 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: 0xc0000005 Fault offset: 0x751ec9f5 Faulting process id: 0x14d0 Faulting application start time: 0x01cf292b1ee63bce Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: unknown Report Id: 93bc8328-951e-11e3-8bec-00038a000015 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-02-14T02:20:32.000000000Z" /> <EventRecordID>3356</EventRecordID> <Channel>Application</Channel> <Computer>GeorgeMB-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>751ec9f5</Data> <Data>14d0</Data> <Data>01cf292b1ee63bce</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>unknown</Data> <Data>93bc8328-951e-11e3-8bec-00038a000015</Data> </EventData> </Event> I reinstalled everything on my computer 7 days ago with the hope that it would stabilize FSX, no such luck. The GeForce GTX 770 is a month old and I'm not touching it's settings at all. I do have all graphics sliders in FSX maxed out but a few settings unchecked and AI planes and airport vehicles set to zero. it was handling it so well the first few weeks I didn't see that being a issue. I didn't change anything in my FSX config file. I have made changes in the simobjects airplane folder to shut off some panels to clean up the aircraft select menu. The crashes happen at different times, like today I was just changing the heading selector on the MD-11 with the mouse wheel and it crashed. Other times just flying the default Cessna 172 it crashed. Thanks for any help.