MDFMike

I am using P3D - not FSX. I just isolated this problem by disabling the following in dll.xml - it is for Active Sky Next for P3D V2,2 - which has been working fine until now. <Launch.Addon> <Name>as_connect</Name> <Disabled>True</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> Information from ASNext web site documents requirement to either run P3D as administrator, or, change ownership or permissions to update the C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\as_srv directory. There are two files in this directory which need to be updated during execution: 1) btstrp.txt 2) log.txt I updated permissions and re-enabled the entry in dll.xml - no more CTD - and it doesn't require being run as admin.

I was using P3D 2.2 latest version over the past few days - including today - without issue, and just exited P3D after completing a flight. I have not installed any addons since Sunday Morning. Current addons are Airbusx, GSX, various FSDT Sceneries, ASNEXT, Megascenery Earth, FSUIPC 4.929, all installed and tested without incident Saturday and Sunday. Starting a few minutes ago - Upon restart of P3D, I get immediate CTD during initialization. I decided to then try loading P3D as an administrator, and it started without incident. I never had to start it as an administrator before. Now, it CTDs every time I start it, unless I start it as an administrator. I even tried this after applying the latest hot fix - same results. RESOLVED: ASNext needs to update two files in C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\as_srv 1) btstrp.txt 2) log.txt I updated user permissions to allow updates to C:\Program Files (x86)\Lockheed Martin\ and all sub-directories. <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> Michael DelFranco Log Name: Application Source: Application Error Date: 4/15/2014 1:39:14 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: MDF-XPS-L702X Description: Faulting application name: Prepar3D.exe, version: 2.2.10438.0, time stamp: 0x53468776 Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7 Exception code: 0xc0000005 Fault offset: 0x000222d2 Faulting process id: 0x21c0 Faulting application start time: 0x01cf586cfe8c2e23 Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 4712c81f-c460-11e3-a0db-88532e1c5a83 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-04-15T05:39:14.000000000Z" /> <EventRecordID>755331</EventRecordID> <Channel>Application</Channel> <Computer>MDF-XPS-L702X</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>2.2.10438.0</Data> <Data>53468776</Data> <Data>ntdll.dll</Data> <Data>6.1.7601.18247</Data> <Data>521ea8e7</Data> <Data>c0000005</Data> <Data>000222d2</Data> <Data>21c0</Data> <Data>01cf586cfe8c2e23</Data> <Data>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe</Data> <Data>C:\Windows\SysWOW64\ntdll.dll</Data> <Data>4712c81f-c460-11e3-a0db-88532e1c5a83</Data> </EventData> </Event>

*** Resolved*** - I uninstalled my DisplayLink software and drivers and P3D was able to initialize and detect my nVidia GT555M.

Right click on P3D V2 presents nothing from P3D. Just the standard windows icon properties pop-up. Sent from my iPad using Tapatalk

I just purchased P3D for 1st time, at V2. Unable to launch P3D due to rendering engine error message indicating I either don't have DirectX 11 video card or drivers not current. Is anyone using P3D V2 with NVidia GT555M DELL L702X? I have posted in the LM P3D hardware forum, but, I am curious if anyone has had success with same hardware, or, if anyone else has same issue. I made sure I have the latest drivers, and there is no second video adapter to be found on this laptop to confuse the p3D renderer. I even tested with no external monitor connected. Dxdiag indicates I have DirectX 11 and only the nVidia GT555M Display adapter is detected. Thanks, in advance. Sent from my iPad using Tapatalk

I think I've found root cause of my issues with the range of NVidia drivers between 314.07 and higher. To recap, I had two symptoms at these driver levels, 1) FSX crashed to desktop at startup, and 2), DWM.exe crashed. I neglected to consider that I also have a Targus Display Link USB 2.0 adapter with a third monitor enabled via its video port. So, I decided to try a test by installing the latest NVidia driver, 320.18, which just released a few days ago. I then noticed that the NVidia control panel was unable to display any monitor information (other than 3d settings) when the monitor attached to the Targus USB Display Link adapter was active. Also, dwm.exe crashed as soon as I tried to run the refresh to update my Windows Experience Index. I then decided to disable the video connected via the Targus Display Link and try again. - The Windows Experience index refresh was then successful - no more dwm.exe crash - The NVidia control panel was able to display all sections of video information. - FSX started and ran with no issues on NVidia driver level 320.18. So, I think something may have been fixed in Nvidia driver level 320.18 to allow FSX to startup without crashing. There is still an issue involving video connected via the Targus USB 2.0 and the NVidia levels higher than 314.07. Update: - I no longer experience the DWM.EXE crashes with the Targus video adapter active after upgrading the Targus DisplayLink USB 2.0 drivers to the following levels: - DisplayLink Core Software - version 7.2.47873.0 - DisplayLink Graphics - version 7.0.43577.0 Hardware: Dell XPS L702X- Processor: Intel i7-2820QM CPU - 2.3 GHz Memory: 8GB RAM OS: Windows 7 Ultimate - 64 bit. Video Card: GT555M with NVidia 3D Vision Targus Display Link USB adapter Model ACP51USZ

As a follow up, my FSX is stabilized on NVidia driver 306.97 since April 1. Last week, I finally took the leap to turn on DX10 (after following the excellent forum posts on DX10 pre-requisites) and I am quite pleased with the results.

And the winner is...... NVidia 306.97. Highest WHQL driver I was able to install on my DELL XPS L702X laptop and maintain stability. There were two quirks at this 306.97 version though - which I easily circumvented: 1) Resolution and Refresh Rates were all empty - I was initially unable to view or set the screen refresh rates for my three attached displays from NVidia Control Panel "-> Display -> Change Resolution" because the values were all empty in the resolution box. The drop down boxes for refresh rate and color depth were also empty. I then went to "-> Display -> Set up multiple displays" and unchecked one monitor at a time. For some reason, NVidia control panel (regardless of driver version) only shows 2 of my 3 active displays. When I went back to the "Change Resolution" page - the values were all populated again. I noticed even after re-booting, these fields all show up empty again when revisiting the "Change Resolution" page to view the values. 2) 3D Vision was not initially activating correctly with FSX - I had to disable both external monitors to get the NVidia 3D Vision to function properly for FSX. Once I re-executed the "Set up stereoscopic 3D" process with my external monitors disabled, all worked as designed even after reboots. Regards, Mike DelFranco.

Ok - so far rolled back to 310.61 and still getting error. FSX is a victim, I am getting the error in DWM.EXE. Diagnostics point to: Problem signature: P1: fsx.exe P2: 10.0.61472.0 P3: 475e17d3 P4: nvwgf2um.dll P5: 9.18.13.1061 P6: 50a8c203 P7: c0000005 P8: 000f59ad P9: P10: There is some activity from other gamers on the web about issues starting with the 310. and higher series drivers. Still Digging. Next Stop: Will try 309.xx series drivers - once I find some Regards, Michael DelFranco Flight Sim enthusiast since 1985.

I'll try a controlled test tonight, progressing forward with the NVidia driver updates until I hit the first driver version which breaks when I start FSX.

Thanks, I'm aware of that warning, perhaps I finally ran out of luck . I was just curious if anyone else had the issue, or just folks like myself who occasionally explore and test the newer driver versions despite the OEM notebook warning.

Since your configuration isn't mentioned here, I'll explain how I do it. I have a Dell laptop, so, there are two screens available via the built in display and the external video connector. I added a Targus USB port replicator which also contains an external video connector which allows me to connect the 3rd monitor. If you have a desktop, you will need a video card which supports two monitors. I am not certain, but, perhaps the Targus port replicator would provide the third monitor if it is supported on a desktop. Hope this provides a starting point. Mike.

I've tried running with NVidia Driver versions between 314.07 and 314.22, and on each version, I get an immediate crash to desktop when launching FSX. It crashes before the FSX menu screen can open. It is also accompanied with a crash to the Windows dwm.exe module. Each time I tried a different version of the 314.xx NVidia drivers, I chose the option for full clean reinstall. Currently I am backed off to 301.42. Is anyone else experiencing anything similar? Thanks, in advance. Hardware: Dell XPS L702X- Processor: Intel i7-2820QM CPU - 2.3 GHz Memory: 8GB RAM OS: Windows 7 Ultimate - 64 bit. Video Card: GT555M with NVidia 3D Vision

I've been simulator flying since 1988, over those years I have used all versions of MS FS, Sublogic ATP, and Fly!, and have purchased a significant number of add-ons for aircraft, weather, traffic, and scenery. Back in those "late 1980's" days, I occasionally wondered how far simulated flying would evolve, and how advanced the experience would get by the time I was in my 50's. My first PMDG purchase was for a Boing 757 addon to FLY!, and I remember how impressed I was in the realism at that time. PMDG's NGX product has blown me away, and triggered the recollection of those times in the past when I wondered, with optimistic anticipation, how far the simulated flight experience would evolve. What PMDG has done with the 737 NGX product has raised the bar tremendously on all aspects of the aircraft simulation realism experience and quality, which I expect will be quite a challenge to meet for others in the commercial add-on business. "Raising the bar" is a great thing. It improves the experience providings satisfied customers, and it raises our expectations of quality from the vendors in the commercial add-on business, which helps accelerate the evolution of the flight simulation experience. Michael DelFrancoFlying the sims since 1988.

I have a new DELL XPS L702X laptop (Intel i7-2820QM 8GB RAM Win 7 64) with NVidia 3D, and the 737 NGX looks awesome in 3D - especially the interior cockpit lighting.When I purchased the laptop, I didn't even anticipate 3D being able to work with FSX, but it was a pleasant surprise when it did. The only issue is the "well-documented" runway lighting placement problem in FSX.

After hotfix 3 - I can only get it the Brake Temp page to work by changing the aircraft's DisplayType from EFIS/MAP to PFD/ND. I am flying the United 900 WX. Go into PMDG Setup, Aircraft, Displays and change the DisplayType - you will get the Brake Temp page on the lower display the next time you click the "SYS" button. Michael DelFranco

btw - you just installed one of the two soundcards I've been using - the Soundblaster x-Fi Gamer. The other I have is a PCI-424 for MOTU hard disk recording - not used for FSX at all - but I did temporarily config FSX to use it as a test - to eliminate Soundblaster or it's drivers as being an issue.

I had many of the same issues - the one thing that made the difference and solved my FSX frame rate issues: always make sure you install the current Directx from Microsoft after you've re-isntalled FSX. This will refresh even the Directx 9 modules that FSX depends on. I used dxwebsetup.exe from the Microsoft Direct X site.I had serious issues where frame rates gradually dropped to 2 or 3 fps after a period of 20 minutes- and then went up to 30 FPS when I muted the sound via "Q" or clicked on another non-FSX window. It wasn't sound card drivers - as I have two different vendor sound cards (one for general sound, the other for recording software) as the problem followed each sound card when I switched between using them as the active default.Regards,Mike.Dell XPS 720 Quad Core 6600 with 4MB Windows 7 Ultimate - 32bitNVidia 8800 GTX 768MB - Driver 196.21

Yes, it was successful - did a 3.5 hr flight with flight plan and VATSIM weather enabled.I replied via email. I also reported the obsolete "support forum" link to the old avsim forum - which I hear is on the list to be fixed as well.Thanks,Mike D.

Yes, I am. Thanks.

My apologies for adding confusion by echoing that I am experiencing the same failure. I do not know if a recent Windows Vista update can be tied to this issue as I've been on VISTA SP1 for months without any major upgrades other than what typically comes in. Perhaps opening another thread will add confusion elsewhere.

I just started getting the same problem, since Dec 7th. I've been using Active Sky X for about 1 year, this started a few days ago. The triggering event seems to be when setting the flight plan destination in the briefing. In my case KCMH to KEWR without importing a flight plan. Within a minute it fails. It seems to stay up as long as I do not set a departure or destination in the Briefing. I always load ASX and fully load a flight plan before starting FSX. To circumvent the error, I am avoiding setting the flight plan departure and destination.Windows Vista logs the following error: Problem Event Name: CLR20r3Problem Signature 01: xengine.exeProblem Signature 02: 1.0.0.332Problem Signature 03: 481f3d57Problem Signature 04: mscorlibProblem Signature 05: 2.0.0.0Problem Signature 06: 47577b16Problem Signature 07: 15cProblem Signature 08: 6cProblem Signature 09: System.ArgumentOutOfRangeOS Version: 6.0.6001.2.1.0.256.1Locale ID: 1033Regards,Mike.

I still had various avionics (radios atc etc...) problems despite trying the recommendations on the PMDG website. The following works for me:From the FS2004 (FS9) Menu Bar:Select Options -> Controls -> Assignments, and assign a keystroke (I chose CTRL + SHIFT + A) to the "Avionics master switch on/off" command. This command can be found under the "Radio Commands" dropdown in the Event Category dialog box. Regards,Michael DelFranco