Problem heap memory with P3D v4

[chrislru]

Hi,

Since I switched to P3D v4 and FSUIPC5, on Windows 10, I have a crash problem.

I have 5 game controlers (2 pokeys, 1 Saitek combat Rudder, 2 Saitek Throttle Quadrant) on the same USB self-powered HUB. On P3D v3 and FSUIPC4 all was good.

I can install FSUIPC5 without problem, registration is ok, but when i start P3D v4 i have a CTD with error 0xc0000005 or 0xc0000374 Faulting application Prepar3d.exe Faulting module ntdll.dll

If I start again P3D v4 and FSUIPC5, just after the crash, no crash P3D start ok. But when I reboot my PC, same problem: CTD then Ok on second start.

Without FSUIPC, P3D v4 start all the time good and game controlers are logged.

It's the same with Windows 10 (fresh install and up to date) and P3D V4 (fresh install without addons) and memory changed.

I have done some tests and these are my conclusions.

If I plug only 1 of the 5 game controlers P3D v4 with FSUIPC5 start all the time. If I plug 2 game controlers on the same HUB crash (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0004).

If I plug 2 game controlers on HUB with differents ID (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0007) P3D v4 start without CTD.

Do you see a solution ?

Attached logs are after the install of FSUIPC5

Best regards.

 

FSUIPC5.ini

FSUIPC5.JoyScan.csv

FSUIPC5.log

[Pete Dowson]

49 minutes ago, chrislru said:

If I plug only 1 of the 5 game controlers P3D v4 with FSUIPC5 start all the time. If I plug 2 game controlers on the same HUB crash (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0004).

If I plug 2 game controlers on HUB with differents ID (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0007) P3D v4 start without CTD.

Sorry, things like port and hub numbers are no use to me. What actual devices can you plug in without the CTD?

This from your Log is worrying:

    18609 ***** HID USB device reconnected: re-initialising FSUIPC connections
    18609 ---------------------- Joystick Device Scan -----------------------

but then the same 5 devices are listed, in the same order. So something, possibly being eliminated, is re-connecting all by itself. 

Please add these lines to the [General] section of the FSUIPC5.INI file:

Debug=Please
LogExtras=x200000

then try again. I need to see the log, upto the CTD, with those lines added.

And please also test just without the PoKeys connected. Those seem to have three entries each in the Registry:

Y, x1E, x1DC3, x1001, Virtual Joystick, 0, 0, 3, {42D1F9E0-7AC6-11E7-8004-444553540000}, {42D1F9E0-7AC6-11E7-8004-444553540000}, {42D1F9E0-7AC6-11E7-8004-444553540000}, Y, Y
Y, x1E, x1DC3, x1001, Virtual Joystick, 3, 3, 5, {436EFD30-7AC6-11E7-800F-444553540000}, {436EFD30-7AC6-11E7-800F-444553540000}, {436EFD30-7AC6-11E7-800F-444553540000}, Y, Y
N, x11, x1DC3, x1001, Virtual Joystick, -1, -1, 0, {NULL}, {42D1F9E0-7AC6-11E7-8001-444553540000}, {NULL}, N, N
N, x11, x1DC3, x1001, Virtual Joystick, -1, -1, 1, {NULL}, {42D1F9E0-7AC6-11E7-8002-444553540000}, {NULL}, N, N
N, x11, x1DC3, x1001, Virtual Joystick, -1, -1, 2, {NULL}, {42D1F9E0-7AC6-11E7-8003-444553540000}, {NULL}, N, N
N, x11, x1DC3, x1001, Virtual Joystick, -1, -1, 4, {NULL}, {4320B620-7AC6-11E7-800A-444553540000}, {NULL}, N, N

59 minutes ago, chrislru said:

On P3D v3 and FSUIPC4 all was good

What version of FSUIPC4 was that with? The joystick scanning on current versions of FSUIPC4 and FSUIPC5 is identical.

Pete

 

[chrislru]

Hi, thanks for your answer.

I will test "debug" this evening.

During my tests i added this lines and i remember an error like 0000006 during scanning. I will post complet log.

For the fisrt question, I can plug each device on HUB USB without CTD, but only one at a time.

I will search version of FSUIPC4 i used.

Christophe

[Pete Dowson]

6 minutes ago, chrislru said:

For the fisrt question, I can plug each device on HUB USB without CTD, but only one at a time.

What even all three without the PoKeys? The Pokeys are the only ones which have rather strange extra registry entries. There are lots of users with the other devices.

Pete

 

[chrislru]

Hi,

With P3D v3 i used FSUIPC4, Version 4.955c (14th June 2016) and FSUIPC4, Version 4.966c (17th April 2017).

Here is the log requested with only the 3 saitek.

Best regards.

Christophe

 

 

FSUIPC5.log

[Pete Dowson]

2 hours ago, chrislru said:

With P3D v3 i used FSUIPC4, Version 4.955c (14th June 2016) and FSUIPC4, Version 4.966c (17th April 2017).

Ah, in those there was not the same device checking at all. The system had to be changed since the older methods didn't work with devices like the Saitkey X-55 and x-56. And the new mehodes (4.969, 4.97 and 5.103 onwards) are far more logical and easier to sort out.

2 hours ago, chrislru said:

Here is the log requested with only the 3 saitek

That shows it hanging or crashing during a DirectInput operation to acquire the Saitek Pro Quadrant in order to check it is operating.

If this doesn't happen with, say, the quadrant only attached, then it points to a hardware problem. You say you are using a hub. A powered one? If you don't have another to try, can you test with the devices all connected directly to USB sockets on the PC itself?

If it's the same with more than one deive on the PC, then it sounds worse -- a motherboard problem.

Otherwise, if it is only related to one or two devices, rather than whether you have two or more attached, then I think something is screwed up with your device installations. Can you uninstall any Saitek software you have installed, then all the devices, completely (in Device Manager, find each device, right-click, uninstall, including drivers when the option arises), then re-boot. Windows will find them all and automatically set them up for use with standard DirectInput drivers.

Pete

 

 

[chrislru]

Hi,

My HUB is powered. I will try with all devices connected directly.

I don't understand what is different between the fisrt start of P3D (crash) and the second one that works.

If it was the motherboard it always crash...

Precision, when i say first and second start, it's with FSUIPC. If I start P3D without FSUIPC and that I restart it with FSUIPC == crash.

I have done a full install (Windows 10 + P3D V4 + FSUIPC5) two times. So I don't know where is the problem, perhaps Saitek drivers ???

2 hours ago, Pete Dowson said:

Otherwise, if it is only related to one or two devices, rather than whether you have two or more attached, then I think something is screwed up with your device installations. Can you uninstall any Saitek software you have installed, then all the devices, completely (in Device Manager, find each device, right-click, uninstall, including drivers when the option arises), then re-boot. Windows will find them all and automatically set them up for use with standard DirectInput drivers.

I will try to do that.

Thanks.

Christophe

Edited August 8, 2017 by chrislru

[Pete Dowson]

23 minutes ago, chrislru said:

I don't understand what is different between the fisrt start of P3D (crash) and the second one that works.

If it was the motherboard it always crash...

I don't understand either. It's as if the device was in a strange state which DirectInput didn't like, but which cleared itself -- or, since the actual device concerned seems to be irrelevant only whether there are two or more), something conflicting between them in the hub or mobo chippery which clears.

25 minutes ago, chrislru said:

i say first and second start, it's with FSUIPC.

Yes, i assumed so.

26 minutes ago, chrislru said:

I have done a full install (Windows 10 + P3D V4 + FSUIPC5) two times.

Ouch!

26 minutes ago, chrislru said:

So I don't know where is the problem, perhaps Saitek drivers ???

The Saitek software does seem to give more problems than solutions fo programs like FSUIPC which try to deal with the devices directly.

Pete

 

[chrislru]

Hi Pete,

I did what you suggested : uninstall saiteks drivers and devices, devices all connected directly to USB sockets on the PC.

After that i configured P3D for Direct input (No RAW) because I had a api.dll error.

And now it seems OK !!!! After 3 or 4 PC reboots P3D v4 with FSUIPC5 starts at the firs step. Now I can test LINDA and my Lua scripts.

No HID reconnected in the log. The USB HUB was a problem too.

My mistake was to think that what worked with P3D v3 + FSUIPC4 was good with P3D v4 + FSUIPC5.

Thank you for your work on FSUIPC, it's a fantastic tool.

Best regards,

Christophe