Alright Hello Everyone 

 

So I got p3d recently and when i launch it straight away it crashes to desktop everything is up to date.

when I check event viewer it shows this : 

 

Faulting application name: dxdiag.exe, version: 10.0.10240.16384, time stamp: 0x559f3b96

Faulting module name: nvwgf2um.dll_unloaded, version: 10.18.13.5582, time stamp: 0x55dc6e32

Exception code: 0xc0000005

Fault offset: 0x0085e250

Faulting process ID: 0x1c8c

Faulting application start time: 0x01d0ed93ce3b65c8

Faulting application path: C:\Windows\SysWOW64\dxdiag.exe

Faulting module path: nvwgf2um.dll

Report ID: 6fa00e9e-72a0-4055-980a-8b39e8aaba73

Faulting package full name: 

Faulting package-relative application ID: 

 

 

And : 

 

Fault bucket 116011770037, type 5

Event Name: BEX

Response: Not available

Cab Id: 0

 

Problem signature:

P1: dxdiag.exe

P2: 10.0.10240.16384

P3: 559f3b96

P4: nvwgf2um.dll_unloaded

P5: 10.18.13.5582

P6: 55dc6e32

P7: 0085e250

P8: c0000005

P9: 00000008

P10: 

 

Attached files:

C:\Users\mrbreenhd\AppData\Local\Temp\WER5E7A.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dxdiag.exe_ff53dcd1d3b139852758fb945ee94a3e6b28b_932f07b2_0b8d609d

 

Analysis symbol: 

Rechecking for solution: 0

Report ID: 6fa00e9e-72a0-4055-980a-8b39e8aaba73

Report Status: 0

Hashed bucket: 9d891e0a4cd85c2b791059ebb67db259

 

if anyone has any idea how to fix it would be amazing thanks

 

Video card and/or its drivers. Try reinstalling your drivers... preferably using the display driver uninstall utility first.

That's strange that dxdiag would cause this type of crash but then dxdiag is run to see if there are any problems with your video and sound drivers.  I suspect there are problems.  Make sure you use admin privileges to reinstall them.  Make sure any anti-virus program is temporarily disabled too during the installation.

 

Best regards,

Alright so after reinstalling the drivers it fixed the directx issue but now i have hit another one .net runtime Application: Prepar3D.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address 00000000

Stack:

 

Application Error 

Faulting application name: Prepar3D.exe, version: 2.5.12946.0, time stamp: 0x555f2e54

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00000000

Faulting process ID: 0x1750

Faulting application start time: 0x01d0edb5baefc3f1

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe

Faulting module path: unknown

Report ID: d60e8e23-17fb-4726-a892-36c1bf402bf6

Faulting package full name: 

Faulting package-relative application ID: 

 

I cannot catch a break thanks guys for the reply sadly for me with p3d its 1 step forward and 2 back  

 

 

Alright so after reinstalling the drivers it fixed the directx issue but now i have hit another one .net runtime Application: Prepar3D.exe
Framework Version: v4.0.30319

 

This is an easy fix (I think).  P3D is actually the FSX engine with some modifications.  FSX requires Microsoft.net 2.0 to run properly so make sure it is installed.  A lot of members have FSX and P3D installed so the reason why not everyone gets this dotnet error as the old dotnets and Microsoft Visuals are already installed.  Dotnets are not backward compatible.  You should also make sure you are running P3D as an Administrator.  You can right click P3D.exe and select properties.  Under the compatibility tab, look all the way down and make sure it shows that it was always run as an administrator.

 

Best regards,

In addition to Jim's advice, also reinstall P3D outside of the program files folder. Try simply C:\Prepar3D.

This is an easy fix (I think).  P3D is actually the FSX engine with some modifications.  FSX requires Microsoft.net 2.0 to run properly so make sure it is installed.  A lot of members have FSX and P3D installed so the reason why not everyone gets this dotnet error as the old dotnets and Microsoft Visuals are already installed.  Dotnets are not backward compatible.  You should also make sure you are running P3D as an Administrator.  You can right click P3D.exe and select properties.  Under the compatibility tab, look all the way down and make sure it shows that it was always run as an administrator.

 

Best regards,

i always run fsx or p3d in administrator mode and it has no baring if i run it in admin mode or not im running windows 10 which installed some .net framework 4.5 i think 

In addition to Jim's advice, also reinstall P3D outside of the program files folder. Try simply C:\Prepar3D.

No luck with that either 

As stated in the AVSIM CTD Guide, you should try the Microsoft.net repair tool whenever you have a Microsoft.net error - https://support.microsoft.com/en-us/kb/2698555. One thing we know for a fact is that it is not the fault of P3D. P3D, v2.5 runs perfectly for thousands of users. The problem for most individuals is a bad installation of the product. They have too much security turned on and we recommend everyone make sure UserAccessControls (UAC) is disabled before installing any software product.  The Anti-virus program must be disabled too.  These two programs can do a lot to damage any installation of a product.  The AVSIM CTD Guide shows you how to disable UAC.  Now, if you install P3D in the non-default folder like gmoneyprs recommended above, then UAC does not have to be disabled as the program will not try to protect you from evil people when an application goes into a non-default folder.

 

We also have no idea what your system looks like. It could be an old Pentium. 

 

There was no faulting module in your error report AFTER you ran P3D.  It was an unknown module and these are very difficult to diagnose.  The c000005 exception code indicates a Memory_Access_Violation which is common in every crash for freeze.  It is obvious, with the Microsoft.net error that you have a bad installation of P3D.  Now you have to figure out what you did wrong when you installed the product.  You must have Microsoft Visual C++ 2005 w/SP1 installed.  I would also recommend 2008 w/SP1.  Lockheed Martin used Microsoft Visual C++ 2010 to make sure P3D is installed correctly in the way they intended.  The P3D program will install this first.  I am not sure whether it also installs Microsoft.net 2.0 or which Microsoft.net program they are using as I have FSX installed too.  Microsoft.net's are used by the developers to make sure the program runs in the way they intended, including memory management.   The AVSIM CTD Guide provides a link to the Microsoft Visuals and Microsoft.net programs required.

 

I have seen "unhandled exceptions" fixed by simply removing all of your startup programs.  You go to the start button, type msconfig in the search box and then, when the program starts up, look under Startup tab.  Disable all of the startup programs.  They are not needed.

 

Lastly, you may have to run a scan of your system for any missing or corrupted files - https://support.microsoft.com/en-us/kb/929833

 

Best regards,

Did you install Prepar3D using setup.exe and not Prepar3d.msi? If so, uninstall and  re-install using setup.exe.

so after downgrading from windows 10 back to 7 i ran it first time CTD no error for some reason and the second time it ran find yay I closed it and restarted p3d again and boom back to the desktop and now another issue my specs are a I5 3330 3.0GHZ 6GB RAM GT 640 1TB HHD 

 

 Fault bucket 45730045, type 30

Event Name: AppHangXProcB1

Response: Not available

Cab Id: 0

 

Problem signature:

P1: Prepar3D.exe

P2: 2.5.12946.0

P3: 555f2e54

P4: 1b5a

P5: 32768

P6: dxdiag.exe

P7: 6.1.7600.16385

P8: 

P9: 

P10: 

 

Attached files:

C:\Users\MrBreenHD\AppData\Local\Temp\WERD806.tmp.appcompat.txt

C:\Users\MrBreenHD\AppData\Local\Temp\WER343A.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Prepar3D.exe_ceb1d1fccfda8293ed19a3d7b9679d082c87ffc_0b474e5d

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: e3125be8-5a52-11e5-beea-d4bed9fcd810

Report Status: 0

 

and again dxdiag is invloved ive updated everything i installed p3d to C:\Prepar3D i disabled UAC 

 

also this was there aswell 

 

The program Prepar3D.exe version 2.5.12946.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

 Process ID: dc4

 Start Time: 01d0ee5f6297003c

 Termination Time: 130

 Application Path: C:\Prepar3D\Prepar3D.exe

 Report Id: e3125be8-5a52-11e5-beea-d4bed9fcd810

 

Edited September 13, 201510 yr by MrBreenHD

It appears P3D is crashing when it attempts to run dxdiag to see if your system is capable of running P3D.  Go to the Start menu, click on Search and type dxdiag.  See if it starts up okay and, if it does, see if there are any problems with your graphics card drivers and sound card drivers.  If so, repair.
 
Your GT640 video card is extremely bad. It is not liked by any of the experts who review video cards. I have a feeling it does not meet the specification for P3D and that's why P3D is crashing when it runs dxdiag - http://www.engadget.com/2012/06/20/nvidia-geforce-gt-640-review-roundup/. Best to upgrade the video card.  I have no idea what the minimum specs are for running P3D but you must be close to the minimum.  Running dxdiag will determine if there are any problems with the video card.  You might want to check with Lockheed Martin and see if your video card is capable of running P3D.  P3D uses a lot of computer resources.  You want to make sure you do not have an old p3d.cfg loading that has high settings.
 
Best regards,

It appears P3D is crashing when it attempts to run dxdiag to see if your system is capable of running P3D.  Go to the Start menu, click on Search and type dxdiag.  See if it starts up okay and, if it does, see if there are any problems with your graphics card drivers and sound card drivers.  If so, repair.

 

Your GT640 video card is extremely bad. It is not liked by any of the experts who review video cards. I have a feeling it does not meet the specification for P3D and that's why P3D is crashing when it runs dxdiag - http://www.engadget.com/2012/06/20/nvidia-geforce-gt-640-review-roundup/. Best to upgrade the video card.  I have no idea what the minimum specs are for running P3D but you must be close to the minimum.  Running dxdiag will determine if there are any problems with the video card.  You might want to check with Lockheed Martin and see if your video card is capable of running P3D.  P3D uses a lot of computer resources.  You want to make sure you do not have an old p3d.cfg loading that has high settings.

 

Best regards,

well its safe to say I am over the recommended specs i am running win 7 64 bit ive a quad core @ 3 ghz ive 6 gb ram recommended it 4 ive 4 gb of GDDR5 recommended is  2 ive Direct X 11 and the rest so? everything shows its working fine ive dropped everything to the minimum disabled the uac and installed outside of the Programs Files so now at this stage i need a new gpu  

I wish there was a simple solution to your problem.  Most crashes have to be investigated at the scene of the crime.  It's my understanding you have a virgin install of P3DV2.5.  No addons whatsoever.  And, when you launch P3D you get the dotnet error showing unhandled exception and the error was caused by dxdiag.exe (not P3d).  DX Diagnostics is used to determine whether there are any problems with your video card and/or sound card.  If there's a problem, dxdiag.exe will tell you.  But I understand you cannot open up dxdiag.exe w/o getting the error (or at least I suggested that and you have not provided the results of that test).  You are correct that your computer meets the minimum specs for P3Dv2.5 but, if you have somehow put a new parameter in the p3d.cfg which is a tweak, or raised your settings too high (above the default), then P3D may not start up correctly.

 

Best regards,

I wish there was a simple solution to your problem.  Most crashes have to be investigated at the scene of the crime.  It's my understanding you have a virgin install of P3DV2.5.  No addons whatsoever.  And, when you launch P3D you get the dotnet error showing unhandled exception and the error was caused by dxdiag.exe (not P3d).  DX Diagnostics is used to determine whether there are any problems with your video card and/or sound card.  If there's a problem, dxdiag.exe will tell you.  But I understand you cannot open up dxdiag.exe w/o getting the error (or at least I suggested that and you have not provided the results of that test).  You are correct that your computer meets the minimum specs for P3Dv2.5 but, if you have somehow put a new parameter in the p3d.cfg which is a tweak, or raised your settings too high (above the default), then P3D may not start up correctly.

 

Best regards,

since i have gone back to windows 7 64 bit i have not got a dotnet error only the Application Hang. yes it is a virgin p3d no addons i can load open the dxdiag on its own. once i launch into the game when it goes from the loading screen to the game if i press pause quick enough i am able to mess around in the menus i can look around the cockpit and what ever else but once i unpause it bam dead. no p3d.cfg tweaks are made