System Freeze

Topics: Developer Forum
Sep 28, 2012 at 3:54 PM

I've been using Terminals for about 10 months strictly for RDP session management.  A few months ago I encountered a situation where my Lenovo T410 laptop would freeze up.  That is, moving the mouse would not cause the on-screen pointer to move, keystrokes would not appear and control-key sequences would not be recognized (such as control-alt-delete).  My only option was to perform a hard shutdown via the power button.

This scenario has occured 7 times over the past 2 months.  Performing a cold restart of your laptop in the middle of the day is incredibly inconvenient - especially when you're just about to host a conference call.

This morning I went to access a Terminals session that had been started the night before.  I clicked on the Terminals icon in my systray but there was no response.  Everything else on my laptop was responding just fine.  After repeated attempts to access Terminals in this manner I decided to shoot the terminals.exe process via Task Manager.  The moment I killed the process my laptop froze in the manner previously described.  No reaction to mouse movement, mouse clicks, keystrokes or control-key combinations.  My only recourse was a hard shutdown and restart.

This situation occured at 9:51AM on 9/28/2012.  The logs don't show anything relevant to that time period.

Some additional details:

OS Name:  Microsoft Windows 7 Enterprise
Version:  6.1.7600 Build 7600
System Manufacturer:  LENOVO
System Model:  25184JU
System Type:  x64-based PC
Processor:  Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz, 2400 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date: LENOVO 6IET74WW (1.34 ), 10/25/2010
Hardware Abstraction Layer:  Version = "6.1.7600.16385"
Installed Physical Memory (RAM):  8.00 GB
Total Physical Memory:  7.86 GB

Terminals About dialog extract:

This version of terminals was build for you on Tuesday, March 06, 2012 at 5:26:21 PM

CommandLine:"C:\Program Files (x86)\Terminals\Terminals.exe"
CurrentDirectory:C:\Program Files (x86)\Terminals
OSVersion:Microsoft Windows NT 6.1.7600.0
Framework Version:2.0.50727.4971



Sep 30, 2012 at 9:50 PM

Try to clear the history by deleting the history.xml in application directory. It may happen, that the file is large and creates problem to the file system. But in such case you should notice continuous slowdown of the application startup.

Oct 5, 2012 at 12:44 AM

Sorry jirkapok, no change.  Gotta bail - this bug is killing me. 

I tried.  I really did...


Oct 7, 2012 at 5:32 PM

Than, you have to provide log file, may be there we can find something.

Oct 16, 2012 at 5:53 PM

OK.  Here are the only errors I have in about 3 months of log files.  I have definetly encountered the problem I reported several times during those 3 months.

INFO  2012-10-11 11:38:33,616 162327272ms Terminals              Disconnect         - Error on Disconnect RDP
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
   at MSTSCLib.IMsRdpClient6.Disconnect()
   at AxMSTSCLib.AxMsRdpClient6.Disconnect()
   at Terminals.Connections.RDPConnection.Disconnect()

ERROR 2012-10-10 08:50:47,616 65861272ms Terminals              lient_OnLogonError - There was a logon error returned from the RDP Connection, details:

Logon Code:-2

Logon Description:Winlogon is continuing with the logon process.

ERROR 2012-10-08 12:40:38,496 76336492ms Terminals              lient_OnLogonError - There was a logon error returned from the RDP Connection, details:

Logon Code:-5

Logon Description:Winlogon is displaying the Session Contention dialog box.

Hope this helps.  Thanks for looking into this.


Oct 16, 2012 at 10:55 PM

Sorry, i have no idea.
Error "Logon Code" is general error in RDP connection library, which isn't related to your issue.