Some users are reporting that the TurboActivate window is never opening upon clicking “activate” in my application. Other users have no issue at all.
I've worked with one of the users to try and track down why TurboActivate.exe will not open for them. it won't open from my application, or if you click on TurboActivate.
It looks like it's crashing instantly on opening. In windows crash logs we see the following:
Faulting application name: TurboActivate.exe, version: 4.4.1.0, time stamp: 0x5fd90cd2
Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x27bfa5f0
Exception code: 0xc0000374
Fault offset: 0x00000000000ff0f9
Faulting process id: 0x5d0c
Faulting application start time: 0x01d6df96dae2f038
Faulting application path: C:\Users\devmi\Desktop\CLS_MSFS\bin\Release\TurboActivate.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 43c56a73-2ad5-48f8-9615-f9790103db8b
Faulting package full name:
Faulting package-relative application ID:
ntdll.dll is installed.
This is occurring with about 2% of my customers
In addition, my application was based on the C# sample. I am compiling using 64 bit only, including the 64 bit versions of TurboActivate.exe and dll. This works on most customers systems.
Can you provide more information for the computers on which this crash is happening?
OS? OS version? In a VM? If so, details about the VM? Can you reproduce this?
This happened with a number of users. I even decided to try not using TurboActivate.exe in my program and use the Inno installer example, and the installer would crash after clicking to submit the license key.
I was able to work closely with one user. They were using windows 10 on a Ryzen system. Actually a fairly new install. Both ways resulted in crashes. This is not in a VM.
I ended up having to resort to listening for the exit code of TurboActivate.exe when opening my software and bypassing the need to activate if it crashed. I was starting to have to refund customers.
OK, what version of Windows 10?
Can you reproduce this?
Is this only happening on AMD processors?
What function call with what parameters are causing the crash?
We haven't been able to reproduce this on any of our many, many test machines. So we need more information so we can track this down and fix it.
I can reproduce it on my Microsoft Surface Book 2
Windows 10 20H2 (OS Build 19042.685), Intel i7-8650U
TurboActivate.exe (64 bit) crashes with a Heap Corruption error (c0000374)
Please check the https://www.gtopala.com/img/other/WinDbg-TurboActivate.png image.
I have created a “.dmp” file using Sysinternal's procdump64 : https://www.gtopala.com/download/temp/TurboActivateCrash.zip
TurboActivate.exe doesn't crash if it is started via procdump64, but it shows the exception:
[12:18:33] Exception: 80000003.BREAKPOINT
[12:18:33] Exception: C0000374
[12:18:33] Unhandled: C0000374
It might be the same crash we reported here:
https://wyday.com/forum/t/4905/ta_usetrial-v4-4-on-windows-crashes/
If you need TurboActivate.exe, use the previous version. For the LM library, you may write some workaround for TA_UseTrial.
Thanks, Gabriel, we're digging into it now.
TA, TF 4.4.2 are out for Windows. This should fix these crashing bugs. Let us know if you have any other problems.