P3D CTD

[Connor Anderson 0]

Hello,

 

I am experiencing Fatal Errors within P3D v3 running Windows 10 and while connected to VATSIM via VPilot.

 

I don't know how to interpret this error which is listed under .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 6035D500

 

Any help would be appreciated.

 

Thanks,

 

Connor

Additionally here is some more info:

 

Faulting application name: Prepar3D.exe, version: 3.4.14.18870, time stamp: 0x581239e2

Faulting module name: nvwgf2um.dll, version: 21.21.13.7595, time stamp: 0x582cfb8f

Exception code: 0xc0000005

Fault offset: 0x00c3d500

Faulting process id: 0x1ef4

Faulting application start time: 0x01d25ef90bddfb0e

Faulting application path: C:\Prepar3D\Prepar3D.exe

Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_410e5247be0e5f00\nvwgf2um.dll

Report Id: 5290046b-2a82-42f4-bd05-b3913a730ddc

Faulting package full name: 

Faulting package-relative application ID: 

And a little more:

 

Fault bucket 108646278503, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: Prepar3D.exe

P2: 3.4.14.18870

P3: 581239e2

P4: nvwgf2um.dll

P5: 21.21.13.7595

P6: 582cfb8f

P7: c0000005

P8: 00c3d500

P9: 

P10: 

 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA93.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_b1455b4185bea9b844f8f536251db5799657ab1_b7731188_14cec00f

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: 5290046b-2a82-42f4-bd05-b3913a730ddc

Report Status: 0

Hashed bucket: 56d75acb6a9f2578ea048c7b1c24b651

 

I apologize, I simply don't know how to interpret any of this.

[Jim Young 2,356]

A video card driver was the cause of the crash.  Recommend you reinstall your video card drivers with Admin privileges.  The latest drivers are 376.48 (I think.  They keep finding bugs).  Your driver is 375.95

 

One member fixed this by uninstalling GEForce Experience.

 

Best regards,

Jim

[Connor Anderson 0]

Jim,

 

Thank you. I know I don't have GeForce Experience installed. I will remove my old driver and install the latest.

 

Thanks again!

 

Connor

[Jim Young 2,356]

 

 

I know I don't have GeForce Experience installed

 

That may be the problem.  NVidia gets very upset when you do not install their spyware! 

 

Best regards,

Jim

[Connor Anderson 0]

That may be the problem.  NVidia gets very upset when you do not install their spyware! 

 

Best regards,

Jim

 

In that case, I will install it and give it a shot both installed and uninstalled.

 

Thanks!

[Luke 782]

 

 

NVidia gets very upset when you do not install their spyware!

 

Given how many hundreds of people run nVidia hardware and drivers without the GF Experience, I imagine we would have seen lots of reports of that by now.

 

Cheers!

 

Luke

[Connor Anderson 0]

An update: I found the nvwgf2um CTD was being caused by the TFDi 717. They've listed it as something they are working on fixing here: http://forums.tfdidesign.com/index.php?/topic/436-the-immediate-to-do-list/

 

Thanks for the helpful responses.

 

Connor

[Jim Young 2,356]

Interesting as many others have had this same BSOD/CTD and it was fixed by reinstalling their drivers (and did not have the FTDi 717 installed).  So, is everyone who installed the FTDi 717 having a BSOD with the nvwgf2um.dll as the faulting module?

 

Best regards,

Jim

[Connor Anderson 0]

I spoke with a gentleman who was experiencing the exact same issue with the 717. On the other hand another user was experiencing it only upon night flights. I can't find the consistency, but they claim to be working on it.