Totalcmd crashes directly when started in RDP-Session

[Grendelbox]

Following problem:

I have a brand new PC running fresh installed
Win7 SP1 x64 Ultimate (fully patched).

Hardware is:
- AMD 890GX Chipset motherboard (MINIX 890GX USB3)
- AMD Phenom X4 905e
- 2x4 GB DDR3-1333 S0DIMM Trancend
- OCZ Vertex2E 120GB SSD

Totalcmd starts up & running normally so far
but it crashes directly when I was working
in a Remote Desktop Session on this PC.
A Totalcmd Instance opened locally before running RDP
this instance is still working in RDP (no problems here),
but I'm NOT able to start any new TCMD in RDP Sessions later.



We use TCMD at our company too,
but I never saw this kind of problem
on ANY other PCs in my life before.

My System is a brandnew installation
with latest drivers und M$ Patches.
I really don't have any more ideas why it crashes,
because I have no other software or
hardware issues on this system.

Errormsg....

Problemereignisname: APPCRASH
Anwendungsname: TOTALCMD.EXE
Anwendungsversion: 7.5.6.1
Anwendungszeitstempel: 2a425e19
Fehlermodulname: ntdll.dll
Fehlermodulversion: 6.1.7601.17514
Fehlermodulzeitstempel: 4ce7ba58
Ausnahmecode: c0000005
Ausnahmeoffset: 00038da9
Betriebsystemversion: 6.1.7601.2.1.0.256.1
Gebietsschema-ID: 1031



Any ideas why this happens ???

[karlchen]

Hello, Grendelbox.

Though I cannot simply tell you why you experience this problem, it may be helpful to know that Total Commander v7.56a works fine when started inside an RDP session on a machine running Windows 7 Enterprise SP1, 32-bit. (Sorry, no 64-bit workstations here.)

Have you tried launching Total Commander inside the RDP session using an empty wincmd.ini?

Code: Select all

\full\path\to\totalcmd.exe /N /I="%temp%\fresh.ini"

Does this T.C. instance crash immediately as well?

Kind regards,
Karl

[Grendelbox]

1)

It still crashes with fresh clean .INI file


2)

I have no other PC with the same problem
starting TCmd in RDP.
(32 or 64Bit Win7, XP or any Windows Server Edition we use
makes no difference)
Only this PC described above.
Very strange thing...I know.

[Grendelbox]

btw....sometimes the AppCrash-Info gives 4 extra info-lines like this here:


Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: TOTALCMD.EXE
Anwendungsversion: 7.5.6.1
Anwendungszeitstempel: 2a425e19
Fehlermodulname: ntdll.dll
Fehlermodulversion: 6.1.7601.17514
Fehlermodulzeitstempel: 4ce7ba58
Ausnahmecode: c0000005
Ausnahmeoffset: 00038da9
Betriebsystemversion: 6.1.7601.2.1.0.256.1
Gebietsschema-ID: 1031
Zusatzinformation 1: ec73
Zusatzinformation 2: ec73724fe3c1758d41646152a339965b
Zusatzinformation 3: 5569
Zusatzinformation 4: 5569b04a9e470c1e3da87ff82b4e5450

[karlchen]

Hello, Grendelbox.

Too bad that I cannot test T.C. launched in an RDP session started on Windows 7 64-bit SP1, because the only 64-bit Windows machines which we have got are Windows servers, e.g. Windows Server 2008 R2.
So, currently I have not got a helpful idea what to check or try out next.

Karl

[Grendelbox]

Big thanks Karl,

I know this problem is a hard to find problem.
I meanwhile checked RAM Modules with MEMTEST86
no errors found.

Thanks and best regards...

[ghisler(Author)]

When you get this error, don't click it away. Instead, go to the TEMP folder and look for the most recent subfolder. It should have a files of type .dmp inside (a crash dump). Please send me this file by e-mail to support at ghisler dot com, zipped if possible.

[Grendelbox]

Crashdump is on it's way...

big thanks for help

[Grendelbox]

Problem App found:

It was the "1&1 Upload Manager", Fileversion 2.0.628.0
a Tool which is mapping the 1&1 Online HDD to a networkdrive
with a special icon in Windows Explorer.

I deinstalled the tool and TCMD is now starting
normally again in RDP Sessions.

Very strange effect...

----------------

Die schuldige Installation an dem Schlamassel
ist der "1&1 Upload-Manager" --> Dateiversion 2.0.628.0
der sich mit eigenen Icons in den Explorer als Netzwerklaufwerk einklinkt
um den direkten Zugriff auf die 1&1 Online-Festplatte bereitzustellen.

Nach dem ich das Tool deinstalliert hatte ging das Aufstarten des Totalcommanders in der RDP Session sofort - ohne Reboot - wieder.
Der Hinweis mit der Explorererweiterung hat mich dazu veranlasst da mal näher hinzuschauen.

Bleibt jetzt nur noch die Frage was dieses 1&1 Programm überhaupt mit dem Totalcommander zu tun hat und wo genau es sich mit dem TCMD beißt...
Wäre blöd wenn ich das Tool nur deswegen nicht mehr nutzen kann.

Danke und Gruß