dogrokket

Thanks again Jim. I deleted the automationcore.dll. I also deleted my fsx config and let fsx build a new one. That seemed to fix things! Now I can alt enter and back without a crash. Now I can move on with my life :rolleyes: .

Jim, could you please point me to the topic you are refering to? Also, according to app crash view, I am getting a d3d9.dll error; but by far, it's the ntdll.dll that shows up most often. Thanks

Thanks for the reply. I haven't done anything to the bios, however, windows just updated itself recently. I'm running a Lenovo Y50 and so far, I have been very pleased with its performance; its a good travel companion (as I spend half my life in hotels). I will dive into the guide and report back; however, it's curious that it was working quite well before. I will have to back track and figure out what changed. FSX is like the Airbus. It's all about the voltage.

I need to add some info... It does not seem to be related to RCV4. If I alt tab and click on the REX weather window, it crashes instantly as well. I tried a clean boot. No difference. Here's an event log: Log Name: Application Source: Application Error Date: 2/11/2015 6:28:34 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: BigMool Description: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: ntdll.dll, version: 6.3.9600.17630, time stamp: 0x54b0d74f Exception code: 0xc0000008 Fault offset: 0x0007d730 Faulting process id: 0x1d98 Faulting application start time: 0x01d04651dad93c70 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: b21b0a56-b245-11e4-8278-303a64afbfa8 Faulting package full name: Faulting package-relative application ID: 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="2015-02-11T23:28:34.000000000Z" /> <EventRecordID>30556</EventRecordID> <Channel>Application</Channel> <Computer>BigMool</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>ntdll.dll</Data> <Data>6.3.9600.17630</Data> <Data>54b0d74f</Data> <Data>c0000008</Data> <Data>0007d730</Data> <Data>1d98</Data> <Data>01d04651dad93c70</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data> <Data>b21b0a56-b245-11e4-8278-303a64afbfa8</Data> <Data> </Data> <Data> </Data> </EventData> </Event> If that's not the right log, please let me know! Thanks <<<EDIT>>> Even if nothing else is running (re: RCV4, REX), if I alt tab and even click anywhere on the desktop, I get the crash. Wierd! Frame rates are great!

This just started happening: it doesn't matter what a/c I have loaded. I load a flight plan into RCV4, start FSX. After pressing fly now, I press alt+enter to window fsx. As soon as I so much as click on the RCV4 window, FSX crashes. It doesn't seem to crash at other times. I have updated REX Essentials Plus WoAi traffic files Several add on airport sceneries Updated nvidia graphics driver Automationcore.dll A machine with 16g of RAM quad core Intel processor 2.5 ghz nvidia gt870 graphics. I just wondered if anyone had any thoughts before I dive into the CTD guide?? Forgot to mention optimized .cfg file with venetubo.

I bought the A330 because I wanted a longhaul airbus in my collection. As some of the previous comments go, they are accurate. The VC textures are not up to the photo real level of the aerosoft A320 product. The exterior model is very nice. Definitely a work in progress (I hope!) and I now regret buying an unfinished product, because there are no gaurantees on what the finished product will be, or when it will be. I fly the A320 for a living and I noticed some immediate deficiencies in the MCDU and the ND. For instance, when you select the DIR button and LSK the waypoint you wish to fly to, the page closes without giving you the option of verification or erasing your selection. Also, on the ND (nav display screen, the green route line extends beyond the compass azimuth on the top of the screen as well as beyond the tail of the virtual aircraft on the bottom of the screen. These are pretty big gaffs. There are also no descent point indicators (a short horizontal line with a downward arrow) displayed indicating that you need to begin your descent to meet a crossing restriction, nor is there an indication of where you will level off in a climb. These are very important indicators. Also, the magenta ball (which we refer to as the speed bump) is missing as well. All I can hope is that these items are forthcoming. This is an adequate sim if you just want a basic experience of flying the 330. However, if you are looking for a level of realism that the aerosoft product offers, I would not recommend it, especially at the current price point.

FIXED after reinstall.... disregard.

I just started getting a runtime error 62 'RadarContact.rcv4module.read_atcnames' error on start up while running as administrator. This comes up on the splash screen, so I can't get any further in to rebuild databases, etc. Any idea as to where to start on this? I'm running win 8 and FSX. While wracking my brain, the only things that I have done recently is download REX (which I believe operates outside of the FSX folder) and I downloaded a little freeware flight planner Plan-G.