stephanev Posted June 5, 2019 Report Share Posted June 5, 2019 Hello, Since I installed a new PC with Windows 10 for my cockpit I have P3D crashing to desktop before splash screen at the first launch, whenever FSUIPC is enabled. I could narrow the problem down to USB devices connected. Whenever I have a device connected to any USB port and FSUIPC enabled, this crashes. If I launched P3D the 2nd time it doesn’t CTD. I did not have time to make a long flight to see if the CTD occurs during flight as well. But the CTD during 1st launch is happening 99% of the time wherever at the startup of PC or after a restart. Rarely this does not CTD at the 1st launch but I can’t understand why as no change is made. If I unplugged all my USB devices with FSUIPC enabled, there is no crash. If my USB devices are connected and FSUIPC is disabled in dll.xml or not installed this does not crash. This happens with a clean installation of P3D without any addon installed. No overclock on the system and default bios settings. My configuration is the following: Motherboard: MSI Z390 gaming Pro with latest firmware and latest drivers for Windows 10 installed CPU: Intel i7 9700k GPU: KFA2 Nvidia GTX2080 OC, 8GB with latest drivers installed RAM: Corsair Vengeance LPX 16Go (2x8Go) DDR4 3200Mhz XMP 2.0 FSUIPC registered version is 5.151 The error reported in the event viewer is related to ntdll.dll Attached the logs from FSUIPC (removed my personal info) and below the log from AppCrashview P3D is always launched as administrator USB devices are: 2x ACE yokes and 1 Revolution Sim product TQ. Windows OS is installed on its own SSD and P3D installed on its own SSD as well. I had the same USB devices running on another PC with Windows 7 before without any issue at all. Here is what I tried so far without any success: - Tried P3D 4.4 and 4.5 - Deleted P3D.cfg and shaders but as this was a clean install without any customization I figured it would not make any difference. - Tried to reinstall Windows 10 and P3D - Disabled USB Power management for all USB devices and hubs in Windows device manager - Disabled USB sleep in Windows Power management - Disabled Windows 10 fast startup - Performed tests of the RAM with memtestx86 and CPU with Prime95, no error to report - Tried with 1 USB device plugged only, whatever the device this CTD - Tried to plug one old USB joystick, this CTD - Tried to plug a single device directly to the PC or to powered USB hubs, tried different powered USB hubs with the same result - Tried to change the motherboard for a Gigabyte Z390 and reinstalled the all system with latest drivers with the same result - Tried to put my previous GPU which is a GTX680 with the same result - Ran DXdiag and it reported no error - Tried to disable sound cards (Nvidia and Realtek) before to launch P3D with the same result - Looked ad USBdevView but could not identify a culprit - Performed a clean install of Nvidia drivers using DDU I’m not sure FSUIPC is the culprit but this definitely does not CTD when it is disabled or not installed. I would really appreciate any help as I cannot figure out what is the issue after hours of tests and troubleshooting. Thanks. Stephane The Appcrashview log: ?Version=1 EventType=APPCRASH EventTime=132038752963112628 ReportType=2 Consent=1 UploadTime=132038752965585747 ReportStatus=268435456 ReportIdentifier=8497ad1e-6894-468c-b0da-7ace1540ac8b IntegratorReportIdentifier=b4c023af-fd0c-4eab-aa09-cbe69000abbd Wow64Host=34404 NsAppName=Prepar3D.exe OriginalFilename=Prepar3D.exe AppSessionGuid=00002110-0001-0005-8c41-89d18b18d501 TargetAppId=W:000062416ca643eea0c66683bf4bed7925bb00000904!0000f4a6d227777f5de7b2e85c3afb498a6b55cc49a0!Prepar3D.exe TargetAppVer=2018//11//27:21:46:29!2d2651!Prepar3D.exe BootId=4294967295 TargetAsId=185 UserImpactVector=318771984 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=db90e762e87703372887667f4d3b7a3d Response.BucketTable=4 Response.LegacyBucketId=1767494075708832317 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=4.4.16.27077 Sig[2].Name=Application Timestamp Sig[2].Value=5bfdbb35 Sig[3].Name=Fault Module Name Sig[3].Value=StackHash_8764 Sig[4].Name=Fault Module Version Sig[4].Value=10.0.17763.348 Sig[5].Name=Fault Module Timestamp Sig[5].Value=ca65c822 Sig[6].Name=Exception Code Sig[6].Value=c0000374 Sig[7].Name=Exception Offset Sig[7].Value=PCH_16_FROM_ntdll+0x00000000000A01C4 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.17763.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=8764 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=8764adce99867239694fe5ffad5b2b6c DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=6bba DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=6bba844f2bc9a482e9cdaefde49bcf0d UI[2]=P:\Prepar3D v4\Prepar3D.exe LoadedModule[0]=P:\Prepar3D v4\Prepar3D.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll LoadedModule[4]=C:\Windows\SYSTEM32\apphelp.dll LoadedModule[5]=C:\Windows\SYSTEM32\AcGenral.DLL LoadedModule[6]=C:\Windows\System32\msvcrt.dll LoadedModule[7]=C:\Windows\System32\sechost.dll LoadedModule[8]=C:\Windows\System32\RPCRT4.dll LoadedModule[9]=C:\Windows\System32\SHLWAPI.dll LoadedModule[10]=C:\Windows\System32\combase.dll LoadedModule[11]=C:\Windows\System32\ucrtbase.dll LoadedModule[12]=C:\Windows\System32\bcryptPrimitives.dll LoadedModule[13]=C:\Windows\System32\GDI32.dll LoadedModule[14]=C:\Windows\System32\gdi32full.dll LoadedModule[15]=C:\Windows\System32\msvcp_win.dll LoadedModule[16]=C:\Windows\System32\USER32.dll LoadedModule[17]=C:\Windows\System32\win32u.dll LoadedModule[18]=C:\Windows\System32\ole32.dll LoadedModule[19]=C:\Windows\System32\advapi32.dll LoadedModule[20]=C:\Windows\System32\SHELL32.dll LoadedModule[21]=C:\Windows\System32\cfgmgr32.dll LoadedModule[22]=C:\Windows\System32\shcore.dll LoadedModule[23]=C:\Windows\System32\windows.storage.dll LoadedModule[24]=C:\Windows\System32\profapi.dll LoadedModule[25]=C:\Windows\System32\powrprof.dll LoadedModule[26]=C:\Windows\System32\kernel.appcore.dll LoadedModule[27]=C:\Windows\System32\cryptsp.dll LoadedModule[28]=C:\Windows\SYSTEM32\USERENV.dll LoadedModule[29]=C:\Windows\SYSTEM32\MPR.dll LoadedModule[30]=C:\Windows\SYSTEM32\SspiCli.dll LoadedModule[31]=C:\Windows\System32\IMM32.DLL LoadedModule[32]=C:\Windows\SYSTEM32\VCRUNTIME140.dll LoadedModule[33]=C:\Windows\SYSTEM32\CRYPTBASE.DLL LoadedModule[34]=P:\Prepar3D v4\api.dll LoadedModule[35]=C:\Windows\System32\WS2_32.dll LoadedModule[36]=C:\Windows\SYSTEM32\Cabinet.dll LoadedModule[37]=C:\Windows\SYSTEM32\MSWSOCK.dll LoadedModule[38]=C:\Windows\System32\CRYPT32.dll LoadedModule[39]=C:\Windows\SYSTEM32\WINHTTP.dll LoadedModule[40]=C:\Windows\System32\MSASN1.dll LoadedModule[41]=C:\Windows\SYSTEM32\WINMM.dll LoadedModule[42]=C:\Windows\SYSTEM32\VERSION.dll LoadedModule[43]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.17763.379_none_10e5882c642d5588\COMCTL32.dll LoadedModule[44]=P:\Prepar3D v4\atc.dll LoadedModule[45]=P:\Prepar3D v4\acontain.dll LoadedModule[46]=P:\Prepar3D v4\ai_player.dll LoadedModule[47]=P:\Prepar3D v4\controls.dll LoadedModule[48]=C:\Windows\System32\SETUPAPI.dll LoadedModule[49]=C:\Windows\System32\bcrypt.dll LoadedModule[50]=C:\Windows\System32\OLEAUT32.dll LoadedModule[51]=P:\Prepar3D v4\facilities.dll LoadedModule[52]=P:\Prepar3D v4\demo.dll LoadedModule[53]=P:\Prepar3D v4\dis.dll LoadedModule[54]=P:\Prepar3D v4\flight.dll LoadedModule[55]=P:\Prepar3D v4\fe.dll LoadedModule[56]=P:\Prepar3D v4\gps.dll LoadedModule[57]=P:\Prepar3D v4\g3d.dll LoadedModule[58]=P:\Prepar3D v4\livingwater.dll LoadedModule[59]=P:\Prepar3D v4\g2d.dll LoadedModule[60]=C:\Windows\System32\WLDAP32.dll LoadedModule[61]=P:\Prepar3D v4\main.dll LoadedModule[62]=C:\Windows\System32\COMDLG32.dll LoadedModule[63]=P:\Prepar3D v4\menus.dll LoadedModule[64]=P:\Prepar3D v4\pdk.dll LoadedModule[65]=P:\Prepar3D v4\multiplayer.dll LoadedModule[66]=P:\Prepar3D v4\simscheduler.dll LoadedModule[67]=P:\Prepar3D v4\panels.dll LoadedModule[68]=P:\Prepar3D v4\sim1.dll LoadedModule[69]=P:\Prepar3D v4\simprop.dll LoadedModule[70]=P:\Prepar3D v4\symmap.dll LoadedModule[71]=P:\Prepar3D v4\terrain.dll LoadedModule[72]=P:\Prepar3D v4\fs-traffic.dll LoadedModule[73]=P:\Prepar3D v4\sound.dll LoadedModule[74]=P:\Prepar3D v4\util.dll LoadedModule[75]=C:\Windows\SYSTEM32\MSVCP140.dll LoadedModule[76]=P:\Prepar3D v4\visualfx.dll LoadedModule[77]=C:\Windows\SYSTEM32\WINMMBASE.dll LoadedModule[78]=P:\Prepar3D v4\weather.dll LoadedModule[79]=C:\Windows\SYSTEM32\CONCRT140.dll LoadedModule[80]=P:\Prepar3D v4\window.dll LoadedModule[81]=C:\Windows\SYSTEM32\HID.DLL LoadedModule[82]=C:\Windows\SYSTEM32\MFReadWrite.dll LoadedModule[83]=C:\Windows\SYSTEM32\MFPlat.DLL LoadedModule[84]=C:\Windows\SYSTEM32\dxgi.dll LoadedModule[85]=C:\Windows\SYSTEM32\DINPUT8.dll LoadedModule[86]=C:\Windows\SYSTEM32\d3d11.dll LoadedModule[87]=P:\Prepar3D v4\mplEasyBlendSDKDX1164.dll LoadedModule[88]=P:\Prepar3D v4\d3dx11_43.dll LoadedModule[89]=C:\Windows\SYSTEM32\OPENGL32.dll LoadedModule[90]=P:\Prepar3D v4\librti1516e.dll LoadedModule[91]=P:\Prepar3D v4\D3DCOMPILER_47.dll LoadedModule[92]=C:\Windows\SYSTEM32\GLU32.dll LoadedModule[93]=C:\Windows\SYSTEM32\MSIMG32.dll LoadedModule[94]=C:\Windows\SYSTEM32\DSOUND.dll LoadedModule[95]=C:\Windows\SYSTEM32\MSACM32.dll LoadedModule[96]=P:\Prepar3D v4\libfedtime1516e.dll LoadedModule[97]=P:\Prepar3D v4\d3dx9_43.dll LoadedModule[98]=P:\Prepar3D v4\audiere.dll LoadedModule[99]=P:\Prepar3D v4\D3DCOMPILER_43.dll LoadedModule[100]=P:\Prepar3D v4\OpenRTI.dll LoadedModule[101]=C:\Windows\SYSTEM32\RTWorkQ.DLL LoadedModule[102]=P:\Prepar3D v4\language.dll LoadedModule[103]=C:\Windows\SYSTEM32\inputhost.dll LoadedModule[104]=C:\Windows\SYSTEM32\CoreMessaging.dll LoadedModule[105]=C:\Windows\SYSTEM32\d2d1.dll LoadedModule[106]=C:\Windows\SYSTEM32\twinapi.appcore.dll LoadedModule[107]=C:\Windows\SYSTEM32\CoreUIComponents.dll LoadedModule[108]=C:\Windows\SYSTEM32\wintypes.dll LoadedModule[109]=C:\Windows\SYSTEM32\PROPSYS.dll LoadedModule[110]=C:\Windows\SYSTEM32\RMCLIENT.dll LoadedModule[111]=C:\Windows\SYSTEM32\ntmarta.dll LoadedModule[112]=C:\Windows\system32\uxtheme.dll LoadedModule[113]=C:\Windows\SYSTEM32\MSXML6.DLL LoadedModule[114]=P:\Prepar3D v4\uiInterface.dll LoadedModule[115]=C:\Windows\SYSTEM32\mscoree.dll LoadedModule[116]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll LoadedModule[117]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll LoadedModule[118]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[119]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\a4c029035a52b21a293c249a889b6925\mscorlib.ni.dll LoadedModule[120]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll LoadedModule[121]=C:\Windows\system32\rsaenh.dll LoadedModule[122]=C:\Windows\SYSTEM32\dwrite.dll LoadedModule[123]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[124]=C:\Windows\SYSTEM32\MSVCP120_CLR0400.dll LoadedModule[125]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[126]=C:\Windows\system32\dwmapi.dll LoadedModule[127]=C:\Windows\SYSTEM32\iphlpapi.dll LoadedModule[128]=C:\Windows\System32\NSI.dll LoadedModule[129]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL LoadedModule[130]=C:\Windows\SYSTEM32\dhcpcsvc.DLL LoadedModule[131]=C:\Windows\SYSTEM32\DNSAPI.dll LoadedModule[132]=C:\Windows\System32\MSCTF.dll LoadedModule[133]=C:\Windows\SYSTEM32\DEVOBJ.dll LoadedModule[134]=C:\Windows\System32\WINTRUST.dll LoadedModule[135]=C:\Windows\system32\nvapi64.dll LoadedModule[136]=C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_127f5d94e1abe12e\nvldumdx.dll LoadedModule[137]=C:\Windows\System32\imagehlp.dll LoadedModule[138]=C:\Windows\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_127f5d94e1abe12e\nvwgf2umx.dll LoadedModule[139]=C:\Windows\SYSTEM32\WTSAPI32.DLL LoadedModule[140]=C:\Windows\SYSTEM32\WINSTA.dll LoadedModule[141]=C:\Windows\System32\clbcatq.dll LoadedModule[142]=C:\Windows\SYSTEM32\CLDAPI.dll LoadedModule[143]=C:\Windows\SYSTEM32\FLTLIB.DLL LoadedModule[144]=C:\Windows\System32\Windows.StateRepositoryPS.dll LoadedModule[145]=C:\Windows\system32\ntshrui.dll LoadedModule[146]=C:\Windows\system32\srvcli.dll LoadedModule[147]=C:\Windows\SYSTEM32\cscapi.dll LoadedModule[148]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17763.379_none_05b83be8071c94a1\comctl32.dll LoadedModule[149]=C:\Windows\system32\netutils.dll LoadedModule[150]=C:\Windows\system32\mssprxy.dll LoadedModule[151]=C:\Windows\System32\coml2.dll LoadedModule[152]=C:\Windows\SYSTEM32\LINKINFO.dll LoadedModule[153]=C:\Windows\system32\NetworkExplorer.dll LoadedModule[154]=C:\Windows\System32\drprov.dll LoadedModule[155]=C:\Windows\System32\ntlanman.dll LoadedModule[156]=C:\Windows\System32\davclnt.dll LoadedModule[157]=C:\Windows\System32\DAVHLPR.dll LoadedModule[158]=C:\Windows\System32\MMDevApi.dll LoadedModule[159]=C:\Windows\SYSTEM32\AUDIOSES.DLL LoadedModule[160]=C:\Windows\SYSTEM32\AVRT.dll LoadedModule[161]=C:\Windows\SYSTEM32\resourcepolicyclient.dll LoadedModule[162]=C:\Windows\System32\Windows.UI.dll LoadedModule[163]=C:\Windows\System32\TextInputFramework.dll LoadedModule[164]=C:\Windows\SYSTEM32\XInput9_1_0.dll LoadedModule[165]=C:\Windows\SYSTEM32\wdmaud.drv LoadedModule[166]=C:\Windows\SYSTEM32\ksuser.dll LoadedModule[167]=C:\Windows\SYSTEM32\msacm32.drv LoadedModule[168]=C:\Windows\SYSTEM32\midimap.dll LoadedModule[169]=P:\Prepar3D v4\SimObjects\Modules\Utilities.dll LoadedModule[170]=P:\Prepar3D v4\CIGI.dll LoadedModule[171]=P:\Prepar3D v4\radar.dll LoadedModule[172]=P:\Prepar3D v4\VirtualReality.dll LoadedModule[173]=P:\Prepar3D v4\openvr_api.dll LoadedModule[174]=P:\Prepar3D v4\ControllableCamera.dll LoadedModule[175]=P:\Prepar3D v4\Gauges\TargetInfo.dll LoadedModule[176]=P:\Prepar3D v4\Gauges\Fury_1500.dll LoadedModule[177]=P:\Prepar3D v4\Gauges\F-16.dll LoadedModule[178]=P:\Prepar3D v4\SimObjects\Modules\Driver.dll LoadedModule[179]=P:\Prepar3D v4\SimObjects\Modules\Orion MPCV.dll LoadedModule[180]=P:\Prepar3D v4\SimObjects\Modules\SLS Block 1.dll LoadedModule[181]=P:\Prepar3D v4\SimObjects\Modules\Laser.dll LoadedModule[182]=P:\Prepar3D v4\SimObjects\Modules\Quadcopter.dll LoadedModule[183]=P:\Prepar3D v4\SimDirector.dll LoadedModule[184]=P:\Prepar3D v4\Modules\FSUIPC5.dll LoadedModule[185]=C:\Windows\System32\PSAPI.DLL LoadedModule[186]=C:\Windows\SYSTEM32\SHFolder.DLL State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=17763 OsInfo[3].Key=ubr OsInfo[3].Value=379 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=84 OsInfo[8].Key=sku OsInfo[8].Value=48 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=256 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=0 OsInfo[15].Key=osinsty OsInfo[15].Value=2 OsInfo[16].Key=iever OsInfo[16].Value=11.379.17763.0-11.0.115 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=16318 OsInfo[19].Key=svolsz OsInfo[19].Value=222 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=180914 OsInfo[22].Key=bldtm OsInfo[22].Value=1434 OsInfo[23].Key=bldbrch OsInfo[23].Value=rs5_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.17763.379.amd64fre.rs5_release.180914-1434 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=Professional OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[34].Key=containerid OsInfo[35].Key=containertype OsInfo[36].Key=edu OsInfo[36].Value=0 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Prepar3D exe AppPath=P:\Prepar3D v4\Prepar3D.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=00A3C5542DF9D2B5636A50F6624E0A49 MetadataHash=7054841 FSUIPC5.JoyScan.csv FSUIPC5.log FSUIPC5.ini Link to comment Share on other sites More sharing options...
stephanev Posted June 5, 2019 Author Report Share Posted June 5, 2019 I attached log from another crash as in fsuipc.log it does not always seem to crash at the same point. But we can see the same error: Error 6 [00000006] returned on HidD_GetPreparsedData: () FSUIPC5.log Link to comment Share on other sites More sharing options...
John Dowson Posted June 5, 2019 Report Share Posted June 5, 2019 Hi, looks like you have some serious USB problems...! If you run without FSUIPC, can you assign your joystick axis/buttons in P3D (or in any other program)? Can you try the HidScanner utility, available from Unplug your devices and reboot first before reconnecting them, then try the HidScanner to see if that recognises your devices correctly. I'm pretty sure you've done this already, but also check the device manager on your usb hubs/devices to see if any errors or conflicts are reported. Cheers, John Link to comment Share on other sites More sharing options...
John Dowson Posted June 6, 2019 Report Share Posted June 6, 2019 17 hours ago, stephanev said: If I launched P3D the 2nd time it doesn’t CTD Could you also provide the FSUIPC5.log file for this as well please. John Link to comment Share on other sites More sharing options...
John Dowson Posted June 6, 2019 Report Share Posted June 6, 2019 oh, and the FSUIPC5.JoyScan.csv after a successful start please. Link to comment Share on other sites More sharing options...
stephanev Posted June 6, 2019 Author Report Share Posted June 6, 2019 Hi John, thank you for your answer and your help. I will provide the information later on today. Stephane Link to comment Share on other sites More sharing options...
stephanev Posted June 6, 2019 Author Report Share Posted June 6, 2019 Hi, I made again a bunch of tests this afternoon and I found it seems that the CTD happens whenever I have the Revolution Sim product TQ plugged or an Opencockipts USB expansion cards in combination with a joystick USB device. I also have other cards from OC like servo, relay but they don't seem to be a problem. Note that the TQ only has 1 USB plug that connects the jostick part(axes and buttons) plus an OC DC motor board. If I plug on the expansion board, there is no issue. If I plug the expansion board and the ACE yoke, this CTD at first launch. If I plug only the TQ this CTD. If I disable FSUIPC this does not CTD. It seems the CTD is happening during the scanning part of the joystick as I can hear the Windows sound for USB connection just before the crash. I can confirm all device are recognized in Windows device manager. I attach here the logs from the crash with OC expansion and Ace yoke plugged in. Below the content of Hidscanner log as I'm not able to attach the file: ********* HidScanner, Version 2.00 by Pete Dowson ********* Device at "\\?\hid#vid_1d57&pid_f833&mi_01&col01#7&4d008ba&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Device is a mouse Usage Page: 1 Input Report Byte Length: 5 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 3 Number of InputData Indices: 8 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 5 at indices 0 -> 4 Value Wh at index 5, range -127 -> 127, using 8 bits Value Y at index 6, range -127 -> 127, using 8 bits Value X at index 7, range -127 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1d57&pid_f833&mi_01&col02#7&4d008ba&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Usage Page: C Input Report Byte Length: 3 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 573 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_0835&pid_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Product= Serial Number= Usage Page: 0 Input Report Byte Length: 19 Output Report Byte Length: 0 Feature Report Byte Length: 64496 Number of Link Collection Nodes: 39968 Number of Input Button Caps: 64 Number of InputValue Caps: 19 Number of InputData Indices: 0 Number of Output Button Caps: 39672 Number of Output Value Caps: 64 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 256 Number of Feature Data Indices: 0 Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits ************************************************************************** Device at "\\?\hid#vid_1d57&pid_f833&mi_01&col03#7&4d008ba&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Usage Page: 1 Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_16c0&pid_2786#6&142c2b04&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=16C0, Product=2786 (Version 1.35) Manufacturer= ACE Product= 737YOKE-LE by ACE Serial Number= B38195 Usage Page: 1 Input Report Byte Length: 10 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 3 Number of InputData Indices: 35 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 2 -> 33 Value Y at index 0, range 0 -> 4095, using 16 bits Value X at index 1, range 0 -> 4095, using 16 bits Value POV at index 34, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_0835&pid_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Product= Serial Number= Usage Page: 0 Input Report Byte Length: 19 Output Report Byte Length: 0 Feature Report Byte Length: 64496 Number of Link Collection Nodes: 39968 Number of Input Button Caps: 64 Number of InputValue Caps: 19 Number of InputData Indices: 0 Number of Output Button Caps: 39672 Number of Output Value Caps: 64 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 256 Number of Feature Data Indices: 0 Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits ************************************************************************** Device at "\\?\hid#vid_1d57&pid_f833&mi_00#7&2d3ab683&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Device is a keyboard Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 2 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 154 Number of Output Button Caps: 1 Number of Output Value Caps: 0 Number of Output Data Indices: 3 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** 1156: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 22141: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0000&PID_0000#7&393fe3de&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0000, Product=0000 (Version 0.0) Manufacturer= Product= Serial Number= Usage Page: FFA0 Input Report Byte Length: 9 Output Report Byte Length: 9 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 0 Number of InputValue Caps: 2 Number of InputData Indices: 2 Number of Output Button Caps: 0 Number of Output Value Caps: 2 Number of Output Data Indices: 2 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x04 at index 0, range -128 -> 127, using 8 bits Value 0x03 at index 1, range -128 -> 127, using 8 bits ************************************************************************** 22156: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 22156: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 22219: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 22281: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 59141: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 59203: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 59656: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 59719: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** FSUIPC5.JoyScan.csv FSUIPC5.log Link to comment Share on other sites More sharing options...
stephanev Posted June 6, 2019 Author Report Share Posted June 6, 2019 In this post I attach the logs from the 2nd launch which was successful and the Hidscanner log: ********* HidScanner, Version 2.00 by Pete Dowson ********* Device at "\\?\hid#vid_1d57&pid_f833&mi_01&col01#7&4d008ba&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Device is a mouse Usage Page: 1 Input Report Byte Length: 5 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 3 Number of InputData Indices: 8 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 5 at indices 0 -> 4 Value Wh at index 5, range -127 -> 127, using 8 bits Value Y at index 6, range -127 -> 127, using 8 bits Value X at index 7, range -127 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1d57&pid_f833&mi_01&col02#7&4d008ba&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Usage Page: C Input Report Byte Length: 3 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 573 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_0835&pid_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Product= Serial Number= Usage Page: 0 Input Report Byte Length: 19 Output Report Byte Length: 0 Feature Report Byte Length: 64496 Number of Link Collection Nodes: 39968 Number of Input Button Caps: 64 Number of InputValue Caps: 19 Number of InputData Indices: 0 Number of Output Button Caps: 39672 Number of Output Value Caps: 64 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 256 Number of Feature Data Indices: 0 Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits ************************************************************************** Device at "\\?\hid#vid_1d57&pid_f833&mi_01&col03#7&4d008ba&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Usage Page: 1 Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 3 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_16c0&pid_2786#6&142c2b04&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=16C0, Product=2786 (Version 1.35) Manufacturer= ACE Product= 737YOKE-LE by ACE Serial Number= B38195 Usage Page: 1 Input Report Byte Length: 10 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 3 Number of InputData Indices: 35 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 2 -> 33 Value Y at index 0, range 0 -> 4095, using 16 bits Value X at index 1, range 0 -> 4095, using 16 bits Value POV at index 34, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_0835&pid_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Product= Serial Number= Usage Page: 0 Input Report Byte Length: 19 Output Report Byte Length: 0 Feature Report Byte Length: 64496 Number of Link Collection Nodes: 39968 Number of Input Button Caps: 64 Number of InputValue Caps: 19 Number of InputData Indices: 0 Number of Output Button Caps: 39672 Number of Output Value Caps: 64 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 256 Number of Feature Data Indices: 0 Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits Value 0x00 at index 0, range 0 -> 0, using 0 bits ************************************************************************** Device at "\\?\hid#vid_1d57&pid_f833&mi_00#7&2d3ab683&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd" Vendor=1D57, Product=F833 (Version 1.16) Manufacturer= Product= Serial Number= Device is a keyboard Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 2 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 154 Number of Output Button Caps: 1 Number of Output Value Caps: 0 Number of Output Data Indices: 3 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** 1156: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 22141: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0000&PID_0000#7&393fe3de&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0000, Product=0000 (Version 0.0) Manufacturer= Product= Serial Number= Usage Page: FFA0 Input Report Byte Length: 9 Output Report Byte Length: 9 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 0 Number of InputValue Caps: 2 Number of InputData Indices: 2 Number of Output Button Caps: 0 Number of Output Value Caps: 2 Number of Output Data Indices: 2 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x04 at index 0, range -128 -> 127, using 8 bits Value 0x03 at index 1, range -128 -> 127, using 8 bits ************************************************************************** 22156: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 22156: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 22219: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 22281: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 59141: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 59203: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 59656: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 59719: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 220563: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 220625: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 221063: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 221125: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8501#7&1f9c35c5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8501 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** 227953: Device change detected ... ***** This device has been removed: Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 228016: Device change detected ... A device has been attached! Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0835, Product=8502 (Version 6.9) Manufacturer= Action Star Product= USB HID Serial Number= USB HID Usage Page: FF01 Input Report Byte Length: 8 Output Report Byte Length: 8 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 7 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x10 at index 0, range 0 -> 255, using 8 bits Value 0x11 at index 0, range 0 -> 255, using 8 bits Value 0x12 at index 0, range 0 -> 255, using 8 bits Value 0x13 at index 0, range 0 -> 255, using 8 bits Value 0x14 at index 0, range 0 -> 255, using 8 bits Value 0x15 at index 0, range 0 -> 255, using 8 bits Value 0x16 at index 0, range 0 -> 255, using 8 bits ************************************************************************** FSUIPC5.JoyScan.csv FSUIPC5.log Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 6, 2019 Report Share Posted June 6, 2019 Just a quick interjection (John will have to continue on this, because i'm off on holiday soon): The Hidcanner logs show devices connecting, disconnecting, and connecting again. This is very similar to problems experienced by Ray, another user here, which were eventually tracked down to a connected hub device which was incompatible with Win10. It too caused CTD the first time then not on restart, and the logs showed devices regularly connecting and disconnecting. Unfortunately, your FSUIPC log from the session where there was no CTD seems stopped after 10 seconds, so their may have been more if you let the session continue and provided a full log ... but even in those first 10 seconds I see: 7484 ***** A device has been attached! 7484 -------------------------------------------------------------------- and 8016 ***** This device has been removed: 8016 Device at "\\?\HID#VID_0835&PID_8502#8&1f938545&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 8047 ***** A device has been attached! So -- try with NO HUBS attached, whether used or not. If the problem still exists then it must be a motherboard hub problem. Pete Link to comment Share on other sites More sharing options...
Ray Proudfoot Posted June 6, 2019 Report Share Posted June 6, 2019 Pete, I agree it's a very similar problem to mine. One other thing I would mention is the increasing use of USB3 ports on new computers. Some (but not all) devices really do not like USB3 so it's important they are plugged into a USB2 port. Ignore the claims of backward compatibility. Some really do not like USB3. I'm thinking of GoFlight GF166 modules especially as they will just blank out if plugged into USB3. Other devices may be similarly affected. I bought this USB2 powered hub and it solved my problems. https://www.amazon.co.uk/gp/product/B0725WHBX6/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 6, 2019 Report Share Posted June 6, 2019 35 minutes ago, Ray Proudfoot said: Pete, I agree it's a very similar problem to mine. There was one other thing about your experience too. DXDIAG. Isn't that where you ran DXDIAG and it failed, but then, after doing that, P3D ran okay? EXCEPT you found, from the logs , the many USB disconnects/reconnects which actually weren't noticed whilst flying ... ? Pete Link to comment Share on other sites More sharing options...
Ray Proudfoot Posted June 6, 2019 Report Share Posted June 6, 2019 Hi Pete, yes, I mentioned that in my email reply to John which I copied you in on. Getting DXDIAG.EXE to run successfully (two attempts as the first always fails) is key to P3D not crashing but the disconnects / reconnects will still happen in the background. The MSE said it was such a fast computer that’s why you never noticed it when flying. Link to comment Share on other sites More sharing options...
stephanev Posted June 8, 2019 Author Report Share Posted June 8, 2019 Guys, I just want to let you know that thanks to your advices I think I identified the problem. This is indeed coming from USB hubs, I used another spare one from another brand and no disconnect/reconnect anymore and no CTD from P3D. Initially I also thought the TQ was directly plugged to the PC and today I realized that I also had another of this non compatible hubs hidden inside the pedestal where the TQ was plugged in 😯 after I removed it and plugged the TQ to another hub, P3D does not seem to CTD anymore. For info the "faulty" usb hub is a Dlink DUB-H7 and I had 3 of them in the cockpit. Thank you Ray for the info and provided the link to the hub I will get a similar one. I want to thank you for your support and time, really appreciate it. I will make more tests once I received the new hubs but I feel pretty confident Here is a pic of my cockpit Link to comment Share on other sites More sharing options...
Ray Proudfoot Posted June 8, 2019 Report Share Posted June 8, 2019 Hi Stephanev, Im very pleased for you. That’s a brilliant setup you have there. I’m pretty sure I also had the same model of hub. It was certainly a D-Link as mentioned in my post here. I can’t check because I was so disgusted with it I threw it in the bin after getting the new one. 😀 Windows 10 eh? Don’t you just love it? 😠 Link to comment Share on other sites More sharing options...
John Dowson Posted June 9, 2019 Report Share Posted June 9, 2019 Hi Stephanev, glad its working for you - and wow - that is a great set-up you have there! Link to comment Share on other sites More sharing options...
stephanev Posted June 9, 2019 Author Report Share Posted June 9, 2019 Thank you Ray ! 😄I had the same feeling. I tried to stay away from Win10 as long as possible but with the new PC, unfortunately, vendors don't provide drivers for Win7 anymore. Link to comment Share on other sites More sharing options...
Ray Proudfoot Posted June 9, 2019 Report Share Posted June 9, 2019 Hi Stephanev, yes, unfortunately even the BIOS on new PCs checks the OS and if not Win 10 won't boot up. To be fair I haven't had any real problem with W10. USB devices have been the worst and Windows updates will turn Power Management for USB back on so make sure you check those after any updates. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now