Anybody had CTD yet?

[Brenchen 51]

I have!

 

I was trying to run graphics on everything high, and loaded F35, but it gave me an error saying "Runtime Error!  Program: P:\xxx\Prepar3D.exe  R6025 - pure virtual function call".

 

The second time, program just stopped functioning when I tried to load the full graphics (to see how my system handles it).

 

Anyone seen these or any CTDs in general?  If you could also provide the steps you took to solve the problem,, that'd be really helpful too!

 

Cheers,

[styckx 1,871]

Yup.. I'm about to refund this.. I've bit my tongue. When it's running, it's running great but..  DON"T TOUCH IT...

 

Guess what all these are from? Yep. Prepar3D...   Remember in FSX when accessing the menus too much would crash FSX?

 

Every single one of these is when I tried going into the menus or leaving the menus.. Doesn't matter the plane or scenery...  

 

 

[HughesMDflyer4 470]

Yup.. I'm about to refund this.. I've bit my tongue. When it's running, it's running great but..  DON"T TOUCH IT...

 

Guess what all these are from? Yep. Prepar3D...   Remember in FSX when accessing the menus too much would crash FSX?

 

Every single one of these is when I tried going into the menus.. Doesn't matter the plane or scenery... 

 

Report the issue on LM's forums then. They tend to fix problems when they hear about them. Since they can now do updates without including the full program, it is likely that an update will be pushed out in a short amount of time.

[styckx 1,871]

I just did. And their forums are painfully slow

[Syonco 13]

I've had a crapload of CTD's today. Mostly OOM Errors, and quite a few Fatal Errors aswell. This is with default scenery/aircraft. Wonder what's going to happen when the more advanced planes become available?  :blink:

[Mochi 82]

Same crash as OP. Also gets stuck at 83% loading traffic at EGLL - default scenery, added AI traffic from FSX. 

[Brenchen 51]

Yea I'm running defaults as well.  About posting to LM, I'm sure I'm not the only one, I'll give them 60 days to get it sorted

[styckx 1,871]

Yea I'm running defaults as well.  About posting to LM, I'm sure I'm not the only one, I'll give them 60 days to get it sorted

 

Check your event log.. See what the fault module is it.  I don't even get an error message.. v2 just closes to the desktop without a error dialog

[Manny 1,293]

I got a couple..when I switched aircrafts...

[Jim Young 2,356]

This is a common Microsoft Visual C++ error and your error report shows the API.dll as the faulting module.  Whenever the API.dll pops up in FSX, it means you are close to running out of memory or your settings are set too high and the program cannot handle the demands.  Probably need to lower a couple of sliders.  Make sure you have Microsoft Visual C++ 2005, 2008, and 2010, 32 bit versions installed on your computer.  Also, included with your runtime errors in the Event Viewer are several errors with Microsoft.net.  You need to have Microsoft.net Framework versions 1.1 through the latest on your computer.  The P3DV2 program should have installed the proper dotnet if not found on your system but you need to make sure.  I don't know if you tried to install other addons, like those from Carenado, FTX/Orbx, but they require an even different version of Microsoft.net and MSV's.  Whoever provided the F35 might have used another set of MSV's and dotnets.

 

Best regards,

Jim

[styckx 1,871]

This is a common Microsoft Visual C++ error and your error report shows the API.dll as the faulting module.  Whenever the API.dll pops up in FSX, it means you are close to running out of memory or your settings are set too high and the program cannot handle the demands.  Probably need to lower a couple of sliders.  Make sure you have Microsoft Visual C++ 2005, 2008, and 2010, 32 bit versions installed on your computer.  Also, included with your runtime errors in the Event Viewer are several errors with Microsoft.net.  You need to have Microsoft.net Framework versions 1.1 through the latest on your computer.  The P3DV2 program should have installed the proper dotnet if not found on your system but you need to make sure.  I don't know if you tried to install other addons, like those from Carenado, FTX/Orbx, but they require an even different version of Microsoft.net and MSV's.  Whoever provided the F35 might have used another set of MSV's and dotnets.

 

Best regards,

Jim

 

OMM with default scenery and planes?   No thanks..  I'll just refund it..  I left FSX to Prepar3D a over a year ago to stick a fork in the constantly "fiddling" with crap to get it stable. 1.3 ran beautiful and 1.4 despite some teething incompatibility issues with Windows 8 ran beautiful. This is not beautiful.. Well ok, the eye candy and new stuff is but it runs like a broken watch. Why have options at all if they'll just fubar stability? I need a stable flight training tool not at home IT training kit. I have zero time for any of this. 

[Jim Young 2,356]

OMM with default scenery and planes?   No thanks..  I'll just refund it..  I left FSX to Prepar3D a over a year ago to stick a fork in the constantly "fiddling" with crap to get it stable. 1.3 ran beautiful and 1.4 despite some teething incompatibility issues with Windows 8 ran beautiful. This is not beautiful.. Well ok, the eye candy and new stuff is but it runs like a broken watch. Why have options at all if they'll just fubar stability? I need a stable flight training tool not at home IT training kit. I have zero time for any of this. 

Here are some suggestions.  Most are already in compliance with the information below but I thought I would post it so you could check for yourself.  The first recommendation below is particularly directed toward you as you have Windows 8.1 and Lockheed Martin has stated in their installation instructions that you should make sure your hardware drivers are up-to-date at all times.  Windows 8.1 is a new OS and hardware developers are still developing drivers that will be compatible with the new OS.

 

Actions to take to prevent crashes -

 

Update Drivers – Microsoft does an excellent job providing updates for Windows and some drivers, such as for your keyboard, mouse, and video card.  But they do not find updates for drivers required for computer system stability.  Usually, the manufacturer of your computer, like Dell or Hewlett Packard will provide you updates for some of the hardware installed on your computer.  You should also download and run a program that will scan your computer for updated drivers.  These drivers will be updates for your CPU, your motherboard, USB ports, SSD’s, HDD’s, printers, etc.  There are several commercial developers who have programs that will scan your system.  Just Google or Bing Drivers or Driver Updates and you will get a list of programs you can download and run.  The programs are freeware but, when drivers are found to be out-of-date, they will ask you to pay a small registration fee to download and install the updates for you.  You can either pay or you can get the name of the out-of-date driver from the list provided by the driver scanner program and then go to Google/Bing and search for the updated driver. Once found, you can download and install the driver yourself.  Manufacturers constantly update drivers when they find issues with previous versions and it is one of the best things you can do to help maintain system stability.

 

Update Your Motherboard BIOS – Make sure the Motherboard BIOS is up-to-date.  The latest can usually be found on the Motherboard developer’s website, like ASUS, Gigabyte, Intel, Dell, or Hewlett Packard.  Do not automatically update the BIOS.  Look at what the update will provide.  If it says it increases system stability, you should definitely install it.

 

Update Microsoft Visuals - Make sure your Microsoft Visuals are installed properly and up-to-date. Microsoft Visuals are used by developers to make sure their software is installed properly and as intended.  FSX/P3D/FS9 and most commercial add-ons will install the appropriate version when you first install the product if it is not already found on your system.  For FSX/Acceleration (and most likely P3D), you will need to have the latest Microsoft Visual 2005 with SP1. SP1 was to be included with Acceleration but did not make it before the product was released.  For FSX commercial add-ons you will need the latest version of Microsoft Visual 2008 and Microsoft Visual 2010.  Microsoft has set up a website where you can download and install the latest versions - http://support.microsoft.com/kb/2019667. It is important to note that Microsoft Visuals are not, for the most part, backward compatible.  Only the 32-bit version is required as FSX and P3D are 32 bit applications.  Microsoft Update or a 64 bit application may install the 64 bit versions but they will not be used by FSX/P3D.  FS9 users will have the latest Microsoft Visual runtime version installed when FS9 is first installed.  However, FS9 add-ons may require later versions so we recommend you install the above Microsoft Visuals to ensure compatibility.

 

Make sure required Microsoft.net Framework Packages are installed and up-to-date - The appropriate Microsoft.net Framework packages are normally installed when you first install FSX/Acceleration/P3D and commercial add-on programs if the appropriate package is not found.  You will need versions 1.1 through the latest. You can see what versions are installed by going to Windows/Microsoft.net/Framework/(then the versions installed). Once the packages are installed, Windows Update will periodically update the packages.  You can verify whether your versions are properly installed and up-to-date by using the .Net Framework Setup Verification Tool User's Guide.  Microsoft.net packages are used by developers to make sure the program runs in the way they intended, including memory management. The packages are, for the most part, not backward compatible.

 

Best regards,

Jim

[styckx 1,871]

Thanks for that Jim.. I know you're trying to help.. I'm overly OCD about keeping my Operating Systems  up to date.  Especially my bios.. I'm surprised how many people don't realize that an outdated BIOS w/ a new OS can cause major problems.  

 

Anyway.. Yeah..  On Nvidia drivers 331.82 (I needed them for an SLI profile for an unrelated game), Windows update it set to automatic and is indeed up to date.  WBard asked if xmlms6 is installed and DX11 libraries which.. Of course they are.. So.  That's about it for me..  1.3/1.4 had no such issues with. No DX11 game or benchmark I have any issues with..  My OS runs like a expensive watch and P3D v2 has been the first monkey wrench since.. Well.. FSX to be honest..  

 

10/18/2013  01:15 AM    <DIR>          v1.0.3705
10/18/2013  01:15 AM    <DIR>          v1.1.4322
11/19/2013  08:04 AM    <DIR>          v2.0.50727
10/17/2013  03:32 PM    <DIR>          v3.0
10/17/2013  03:32 PM    <DIR>          v3.5
11/25/2013  06:38 AM    <DIR>          v4.0.30319
0 File(s)              0 bytes
6 Dir(s)  1,301,888,462,848 bytes free

Command prompt!  A sign of my age..

[styckx 1,871]

  At the recommendation of Beau I disabled SLI in Nvidia Control Panel as it may be possible even though P3D doesn't use SLI it could be conflicting... After my first go around with SunSkyJet KPHL and Carenado 182T and a bunch of in and out of menus, in and out of fullscreen etc.. No CTD yet *touch wood*.

 

From Beau 

 

Many settings changes trigger a display device reset in our rendering system. We cancel rendering of the current frame when we do this but perhaps the SLI drivers still trying to move resources around to render alternate frames on each GP

 

[ErichB 3,643]

OMM with default scenery and planes? No thanks.. I'll just refund it.. I left FSX to Prepar3D a over a year ago to stick a fork in the constantly "fiddling" with crap to get it stable. 1.3 ran beautiful and 1.4 despite some teething incompatibility issues with Windows 8 ran beautiful. This is not beautiful.. Well ok, the eye candy and new stuff is but it runs like a broken watch. Why have options at all if they'll just fubar stability? I need a stable flight training tool not at home IT training kit. I have zero time for any of this.

It's been less than 24 hours. Why don't you consider this 'teething problems' and give them 60 days to sort out the issues. Let's give them the benefit of the doubt.