Hi Bryan,
 
I have just updated to FS2Crew v1.7 with my PMDG 777 in P3D v3.1
 
Whenever I press the button on joystick assigned to show the FS2Crew main panel I get crash to desktop with the following error:
 
Faulting application name: Prepar3D.exe, version: 3.1.2.15831, time stamp: 0x5672b60a
Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x55636317
Exception code: 0xc0000374
Fault offset: 0x000cea5f
Faulting process id: 0x4a4
Faulting application start time: 0x01d15124b5a09171
Faulting application path: F:\Prepar3D\Prepar3D.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 65e06101-bd18-11e5-a26d-f46d04665fab
 
and, then:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
 
Problem signature:
P1: Prepar3D.exe
P2: 3.1.2.15831
P3: 5672b60a
P4: StackHash_c3ef
P5: 6.1.7601.18869
P6: 55636317
P7: c0000374
P8: 000cea5f
P9: 
P10: 
 
Attached files:
C:\Users\UN8GC\AppData\Local\Temp\WEREB1D.tmp.WERInternalMetadata.xml
 
These files may be available here:
C:\Users\UN8GC\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_b4c1a14e51653c2f9d25fa21f851c770b8c88a_06ebf912
 
Analysis symbol: 
Rechecking for solution: 0
Report Id: 65e06101-bd18-11e5-a26d-f46d04665fab
 

Any idea how to fix this?
 
Thanks.

Once the gauge is initialized, I get the crash. This is the last thing I am seeing:

 

https://www.dropbox.com/s/d8msxokhxiux0ed/Capture.JPG?dl=0

Hi,

 

The link to your screenshot on dropbox returns a 404 erro, could you please check?

What happens if you use a keyboard assignment instead of a joystick button?

 

https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#newwindow=1&q=ntdll.dll+p3d+v3

Bryan,

 

here's the updated link with the screenshot once the CTD occurs:

 

https://www.dropbox.com/s/d8msxokhxiux0ed/Capture.JPG?dl=0

 

As for key assignment, I will test it and will get back to you shortly.

Ok. I have tried assigning a keyboard combination for toggling the main panel. No luck. Here's what I got:

 

https://www.dropbox.com/s/rt5sn1m6jz90ann/ButtonAssigned.JPG?dl=0

Please re-install the 777 aircraft cleanly.

 

Manually delete any leftover 777 folders in the SimObjects folder prior to re-installing.

 

Do several test flights without having FS2Crew enabled to try to isolate the problem.

 

Best,

Bryan,

 

I don't get it: I am not trying to troubleshoot PMDG 777. I have recently updated it and I don't seem to have any issues with it. It works until I actually invoke the FS2Crew in it. Please explain me how will doing the test flights in 777 without FS2Crew will help me isolate the problem?

 

Thanks.

Re-installing often cures weird gremlins.

 

We have a very large 777 user base, I'm afraid I haven't heard of this one before.

 

Have you tried updating all your audio/video drivers?

 

Are you running at average monitor resolutions?  Or do you have a unique setup?

Bryan,

 

I have average monitor resolution. It runs at 1920x1080 (GF780GTX here). 

 

All video drivers are up to date. Nothing unique about my setup, really.

 

I will reinstall FS2Crew and will report if the issue is gone or not.

Bryan,

 

LOL: this whole thing was gone after I reinstalled FS2Crew! Ain't it funny?

 

Ok. The issue is solved (looks like). Next time I know what to do.

 

Thanks.

 

 

LOL: this whole thing was gone after I reinstalled FS2Crew! Ain't it funny?
 
Ok. The issue is solved (looks like). Next time I know what to do.

 

Great!

 

Re-installs often cure weird issues!

 

Cheers,