My Tech2Win keeps crashing.

I've updated the licenses, and uninstalled and reinstalled the 3 apps in All Scanner (pasthru, GM GDS2, SGM RDS).

I'm trying to flush the ABS system, each time I try to initiate a flush Tech2 crashes.

Anybody got an idea.., Hey @Dano523 got any ideas?

Thanks,

Dave

 

FYI, I do see there is an upgrade in AllScanner

I'm at 1.8.4, current is 1.9.1.2

Is this update safe?

 

Update is safe, but may have to go into defender to allow the latest VX manger to load/not be blocked.
Just watch when loading the latest VX manager, if you you get any pop up of either defender or other software programs trying to block it's install.

Also, when you get VX manager updated, update the nano firmware, then licensees, then do a quick uninstall and reinstall of the three apps in VX manager diagnostics, instead of just updating them.

If you still get disconnects afterwards, then suspect that the factory USB cable that comes with the machine is having problems.

Myself, since I have a few Nano's, just switch over to using these cables, and don't have to play the tape the cable to the nano to keep a good connection.

 

Bumping this thread because I found it helpful but I still have an issue.

I have Tech2Win running, the device firmware updated, all drivers installed, etc.

I can run Tech2Win and connect to the Nano, but I can't stay connected to the car.

I followed the reinstallation order Dano laid out in this thread and others. I uninstalled the GM MDI app, re-ran the Tech2Win Auto install.exe, then opened VXDiag and uninstalled/reinstalled Passthru, GDS2, SGM/RDS, the licenses, and confirmed the firmware of the device as 19.4.2.

I can connect to the car, but Tech2Win always crashes once I have it start to read from the car. It might crash instantly, it might take 5-10 seconds, but the crash always happens.

I took a video to describe it and show my software settings. I tried both 2013 (generically but recommended) and 2011 (my car's year) and the crash happens in both. You can see it crash when I try to read the skip shift and loop status special functions. You can tell it's reading from the car before it crashes.

I have tried multiple USB cables and ports on my PC, which is Win7 SP1 32bit.


​​​​​
Any other ideas for me to try?

Sending out the bat signal to @Dano523

 

Close VX manager before you use tech2 win, and do a complete computer reboot if you get a Tech2win crash/do not open VX manager again when you do use t2w again.

The reason for a computer shut down and restart and. not to open VX manager again when you use T2w ,is often there is something going on in the computers back ground that is causing the crash to begin with.

So if fresh computer shut down and restart, not opening up VX manager after the reboot does not solve the crash problems, then need you to click on your start button, type in msconfig in our search bar, click on MS config.exe to open it, click on the service tab, the list what services the computer is showing and if they are running or stopped. Also, need to click on the start up tab as well, click on the open task manager, then give me that list and if they are set to enable or disable, then lastly processes and that list and any that are using showing a CPU percentage use at the same time T2w in being used as well.

Hence the reason that T2w is crashing, is either connector problem at the obdII port, or the BCM down line that cleaning them up with contact cleaner will resolve,
Or on the computer side, with another programming trying to use/monitor the Nano com's port at the same time it using it, and why that is causing the crash.

With luck, it just leaving VX manager closed from the system start up, that solves the crashing problems with Tech2win in the first place, and don't have to go down the rabbit hole of what other program on the computer is causing the crash instead.

P.S, if you do not have CC cleaner on your machine, now would be a good time to install it. Hence install it, do a custom clean to clean up any cookies on the machine that could be causing problems, then click on the register button to do a clean up of that next. From there, the tools button, start with start up, to go through the list to see what is loading at start up and it need to or not at start up. The click on the uninstall button to really see what is loaded on the machine, to weed out any programs that may have been installed that you did not intend to install/where back door installed, or just garage programs that are know to cause problems ,and uninstall them as well.

Hence the CC cleaner uninstall is good about showing all the programs that have been installed on the machine, verse the normal windows computer uninstall list, that some installed programs may be hidden on isntead.

 

Thanks Dano - I had VX Manager open the whole time so I will try closing that and looking at other programs that may be running conflicting processes with Tech2Win.

 

Well you can't make this stuff up.

​​​​​​The laptop died just as I was about to plug the Nano into it after work today to keep testing.

It's totally dead, not responsive. Won't power up at all.

I'm returning the Nano and will keep an eye out for a used laptop that I can start fresh with and set it up for the Nano and an MPVI3 one day.

 

Not sure if this will be helpful to anyone else (as my situation is probably fairly unique), but for reference:

I just ran into this myself - Tech2Win install (that previously worked fine) would crash within a few seconds of attempting to communicate with the car (regardless of whether or not the device was plugged into the OBD-II port when attempting to communicate). There were no error messages on the screen or in the logs after a crash, other than generic "Application Error" and "APPCRASH" messages in the Windows "Application" Event Log (showing that emulator.exec crashed with "Exception code: 0xc0000005" and "Fault offset: 0x00092998"). I updated all the firmware and licenses, reinstalled everything, tried upgrading and downgrading Windows, tried different USB cables, tried cleaning contacts, etc but still hit the same crash every time.

Eventually I managed to figure out that the problem was my CPU model. I'm running Tech2Win in a QEMU VM, and I was using "host passthrough" mode for the VM's CPU. Since the last time I successfully used Tech2Win, I upgraded to new hardware with an Intel Xeon CPU, and Tech2Win apparently doesn't like something about Xeon CPUs. Configuring the VM to either pass through a real Xeon CPU or emulate any Xeon CPU (Cascadelake-Server*, Skylake-Server*, etc) causes Tech2Win to crash when attempting to communicate; Configuring the VM to emulate an Intel Core CPU (eg. Skylake-Client-noTSX-IBRS) works fine.

(For anyone who isn't familiar with CPUs: "Xeon" is Intel's enterprise-grade CPU line, "Core" is Intel's consumer-grade CPU line. While the CPUs are somewhat similar across those two lines and are generally compatible in the OS and software, there are some significant differences between their feature sets that could potentially affect things like the hardware emulator used internally by Tech2Win. Xeon CPUs are far more expensive than Core CPUs, and most consumers wouldn't care about the added features, so I doubt anyone other than me is running Tech2Win on a Xeon CPU. However, it might be helpful for others to know that these Tech2Win crashes could potentially be caused by CPU compatibility issues and could potentially be fixed by running Tech2Win in a VM that emulates a different CPU.)

 

Yep, kind of luck of the draw if you can get Tech2win to work in VM shell with different chips,and the reason that I just run it in native, with the only thing run in a shell being Tis2000 running under windows 7 32 bit with 16 bit driver suport tuned on (win 64 bit versions does not have 16 bit driver support, and win 7 32 bit is about the latest version that tis2000 cracked load on without problems).

So vx manager, GDS2, TDS all run in navtive,
and only TIS2000 in shell under windows 7 32 in shell,with VX manager, usb cable driver if going to use hand held type tech II.

And to add to the mess, there are some other units like the table type with different notebooks, that will not work with Tech2win as well.

Hence the Tech2win install will load the needed software, but you run into problems with the T2Configurator.exe not working correctly, and instead of getting the pop up windows to select the north america, mdi1, usb Nano to make is the pass through device, loads tech2win up directly, with nano not connects as the pass through device instead..