Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.
P3D CTD due to USB Hub Failure/Issues
Hello everyone,
Just a bit of knowledge share here. In November, I built a new i9900K ASUS ROG Z390-E computer. I was wanting to get ahead/ready for MSFS 2020 and run P3D with something more than 15 FPS in sparse scenery! I was hardly able (1 out 10 flights) to complete a P3D V4.5 flight with my new set up without a CTD. Very frustrating. I saw some issues in Event Viewer trying to fix them. One in particular keep occurring:
Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526
Exception code: 0xc0000374
Fault offset: 0x00000000000f9269
Faulting process id: 0x2da8
Faulting application start time: 0x01d5c023470d67bf
Faulting application path: H:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: f51a2e9f-bd62-480d-b112-19da7a358028
Faulting package full name:
Faulting package-relative application ID:
Exception code: 0xc0000374 is a "Stack Heap" error, whatever the heck that is. I posted this error on the LM PD3 Forum and on Avsim's Hardware Forum. On the AVSIM forum, Tony P lead me to an issue fellow simmer Ray Proudfoot experienced. Ray ran it to ground with the MS Engineers as described here:
https://answers.microsoft.com/en-us/windows/forum/all/directinput-causing-l-m-prepar3d-v4-to-crash/20c20b5d-4261-4b13-8a58-375c387b7b3e
This issue was a failed/failing Powered USB Hub or a USB hub that was not Win 10 compatible. I have a rather extensive GoFlight Hardware setup including a GF 166 five unit COMM/NAV/XPDR panel.
I have been noticing for the past few weeks following the new setup that on P3D start up and/or a preflight check with the GoFlight Configure software that not all of the units of the GF166 were operating. In fact, sometime none of them would work. I would unplug and replug in the USB. Sometimes it would work. Some time it would CTD, and always with the Exception code: 0xc0000374 error code. Ray's information pointed to the Powered USB hub.
I replaced my D-Link USB hub that came with the GF 166 that's about 4 years old with a new one from Best Buy. I flown two flights without a problem. Also restarted P3D with all five units on the GF 166 working each time. Strongly suspect that my old Powered USB Hub was failing or failed and not providing enough power to the USB Port. The signal drop outs, which could be heard over the computer speakers (chimes, dings, dongs, whatever), were usually followed by a CTD with the above error message.
I thought this was a software issue either with the Win 10 OS, P3D, or the GoFlight Config software. Instead, it looks like it was a hardware issue.
Passing this along so that others don't have to experience the frustration I had the last few weeks. Thanks to Ray Proudfoot on the AVSIM Forum for chasing this one to ground with MS. Hope it helps!
Happy New Year!
Rich Boll
Wichita KS
Just a bit of knowledge share here. In November, I built a new i9900K ASUS ROG Z390-E computer. I was wanting to get ahead/ready for MSFS 2020 and run P3D with something more than 15 FPS in sparse scenery! I was hardly able (1 out 10 flights) to complete a P3D V4.5 flight with my new set up without a CTD. Very frustrating. I saw some issues in Event Viewer trying to fix them. One in particular keep occurring:
Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526
Exception code: 0xc0000374
Fault offset: 0x00000000000f9269
Faulting process id: 0x2da8
Faulting application start time: 0x01d5c023470d67bf
Faulting application path: H:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: f51a2e9f-bd62-480d-b112-19da7a358028
Faulting package full name:
Faulting package-relative application ID:
Exception code: 0xc0000374 is a "Stack Heap" error, whatever the heck that is. I posted this error on the LM PD3 Forum and on Avsim's Hardware Forum. On the AVSIM forum, Tony P lead me to an issue fellow simmer Ray Proudfoot experienced. Ray ran it to ground with the MS Engineers as described here:
https://answers.microsoft.com/en-us/windows/forum/all/directinput-causing-l-m-prepar3d-v4-to-crash/20c20b5d-4261-4b13-8a58-375c387b7b3e
This issue was a failed/failing Powered USB Hub or a USB hub that was not Win 10 compatible. I have a rather extensive GoFlight Hardware setup including a GF 166 five unit COMM/NAV/XPDR panel.
I have been noticing for the past few weeks following the new setup that on P3D start up and/or a preflight check with the GoFlight Configure software that not all of the units of the GF166 were operating. In fact, sometime none of them would work. I would unplug and replug in the USB. Sometimes it would work. Some time it would CTD, and always with the Exception code: 0xc0000374 error code. Ray's information pointed to the Powered USB hub.
I replaced my D-Link USB hub that came with the GF 166 that's about 4 years old with a new one from Best Buy. I flown two flights without a problem. Also restarted P3D with all five units on the GF 166 working each time. Strongly suspect that my old Powered USB Hub was failing or failed and not providing enough power to the USB Port. The signal drop outs, which could be heard over the computer speakers (chimes, dings, dongs, whatever), were usually followed by a CTD with the above error message.
I thought this was a software issue either with the Win 10 OS, P3D, or the GoFlight Config software. Instead, it looks like it was a hardware issue.
Passing this along so that others don't have to experience the frustration I had the last few weeks. Thanks to Ray Proudfoot on the AVSIM Forum for chasing this one to ground with MS. Hope it helps!
Happy New Year!
Rich Boll
Wichita KS
Comments
Microsoft forum help were pretty useless it has to be said and appear to be based on a script-based service. They never once suggested taking the powered USB2 hub out of the equation.
Ray (Cheshire, England)