Tech2Win crashes when connecting to vehicle - OBDXPro GT

[cobra30689]

I've owned an OBDXPro GT for quite a while, and it has worked fine with T2W.....until I upgraded the laptop I use from Win 7 to Win 10. Now T2W will crash out when it attempts to comm with the vehicle. I also have an MDI clone, but that connects just fine. Uninstalled and reinstalled T2W, as well as uninstalled and re-installed the NEW D-PDU driver. Still no joy. Any known issues pop up lately?

[antus]

Have you got an exact error message when it crashes to work from?

[cobra30689]

Unfortunately no. It hangs on "Establishing Communications" for awhile, then the T2W screen disappears.

[Tazzi]

Sounds like something has not installed correctly or is possible corrupted.

Make sure you have:

1) You have the .net framework installed: https://dotnet.microsoft.com/en-us/down ... -framework

2) You have installed the OBDX Pro GT Tech2win DPDU API

3) Verify that the OBDX Pro GT appears as a comport under device manager.

[cobra30689]

Sounds like something has not installed correctly or is possible corrupted.

Make sure you have:

1) You have the .net framework installed: https://dotnet.microsoft.com/en-us/down ... -framework

2) You have installed the OBDX Pro GT Tech2win DPDU API

3) Verify that the OBDX Pro GT appears as a comport under device manager.

Installed the .net framework this morning.....no change.

Reinstalled the API.

The GT is definitely shown as a COM port. T2W has no problem seeing it during the VCI selection screen, and as the emulator starts up "CANdI Module Detected" appears in the splash screen.....so it's communicating with it. Where it bugs out is when it attempts to comm with the vehicle.

It's been working fine since the day I got it, until I upgraded from Win 7 to Win 10. MDI works fine, it's just the GT that crashes it. T2W version 2.302, NAO 33.004 .bin.

[ironduke]

There should be a tech2win log stored somewhere.. not at a computer at the moment but poke around a little in the tech2win folders..

Logs I am thinking of is located at C:\Users\Public\General Motors\Tech2Win\Logs

[Tazzi]

Installed the .net framework this morning.....no change.

Reinstalled the API.

The GT is definitely shown as a COM port. T2W has no problem seeing it during the VCI selection screen, and as the emulator starts up "CANdI Module Detected" appears in the splash screen.....so it's communicating with it. Where it bugs out is when it attempts to comm with the vehicle.

It's been working fine since the day I got it, until I upgraded from Win 7 to Win 10. MDI works fine, it's just the GT that crashes it. T2W version 2.302, NAO 33.004 .bin.

Install and run the OBDX Pro firmware updater, and see if this helps at all as well

[04colyZQ8]

I have the same issue with mongoose pro and windows 11 laptop! It works fine on my desktop with windows 10. It also initially worked on my laptop until I installed the gds2 with sps and then it stopped!

[cobra30689]

Welp.....updated the firmware, still no joy. Crashes T2W after about 20 seconds at "Establishing Communications". I installed the drivers, the T2W API and T2W itself on my other Windows 11 laptop that has barely anything on it.

Same thing.

Could it be a hardware problem?

[antus]

Im thinking more likely a windows 11 problem. It changed a lot with memory protection and that 04colyZQ8 has the same prob on mongoose. You could try disabling the security option memory integrity and see if it makes a difference. Ive found a number of these types of tools which that feature breaks.