The best way to help us resolve the problem quickly is to send us stack trace by using a microsoft debugging tool - windbg. We need the 32-bit msi package for windbg.

You can download the package here directly.
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi

Or you can go to the page here.
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx#b

Go down to 'Previous Versions of Debugging Tools for Windows' section and download
Previous Release version 6.11.1.404 - March 27, 2009
Install 32-bit version 6.11.1.404 [16.9 MB]


Once you install the msi package, please set it up as a postmortem debugger:
(1) Open a Command Prompt (If on Vista, open the command prompt with Admin right)
(2) cd to the directory where the debugger is installed, normally it is at C:\Program Files\Debugging Tools for Windows (x86)
cd "C:\Program Files\Debugging Tools for Windows (x86)"
(3) type:
windbg -I

this will install windbg as the postmortem debugger.

When Gladinet crashes again, it will crash into debugger.

In windbg command prompt:
Type 'kb' to generate the stack trace.
Type 'r' to get the registry info related.
Type '.dump /ma c:\temp\gladinet.dmp' to create mini dump.

Copy and email the stack trace to us at support@gladinet.com, with your Gladinet version number and OS information. Please keep the mini dump, in case we need to dump file to analyze it.

Thanks!

jerryh attached the following image(s):