Latest SecureRemote from Checkpoint crashed my XP Pro

Hello all,
My XP Pro crashed everytime after the installation of the latest SecuRemote.
How can I fix this problem ?
Here is the bugcheck analysis :

Microsoft (R) Windows Debugger Version 6.2.0007.4
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini073003-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\Program Files\Debugging Tools for
Windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp2.030516-0318
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543fb0
Debug session time: Wed Jul 30 19:45:35 2003
System Uptime: 0 days 0:01:19.590
Loading Kernel Symbols
............................................................................
..................................................................
Loading unloaded module list
.......
Loading User Symbols
****************************************************************************
***
* *
* Bugcheck Analysis *
* *
****************************************************************************
***
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 804ea218, b292e9a0, 0}
*** WARNING: Unable to verify timestamp for tmtdi.sys
*** ERROR: Module load completed but symbols could not be loaded for
tmtdi.sys
Probably caused by : tmtdi.sys ( tmtdi+14e1 )
Followup: MachineOwner
---------
kd> !analyze -v
****************************************************************************
***
* *
* Bugcheck Analysis *
* *
****************************************************************************
***
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804ea218, The address that the exception occurred at
Arg3: b292e9a0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
Database SolnDb not connected
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!IopfCallDriver+28
804ea218 8b7108 mov esi,[ecx+0x8]
TRAP_FRAME: b292e9a0 -- (.trap ffffffffb292e9a0)
Unable to read trap frame at b292e9a0
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from b287f4e1 to 804ea218
STACK_TEXT:
b292ea14 b287f4e1 864847c8 b287fcff 864e0030 nt!IopfCallDriver+0x28
WARNING: Stack unwind information not available. Following frames may be
wrong.
b292ea5c 804ea221 864e0030 864e00e8 86484758 tmtdi+0x14e1
b292ea6c 80561107 864e0018 863335d4 b292ec18 nt!IopfCallDriver+0x31
b292eb50 8059ae9a 864e0030 00000000 86333530 nt!IopParseDevice+0xa4d
b292ebd8 805977fb 00000000 b292ec18 00000040 nt!ObpLookupObjectName+0x56a
b292ec2c 80554a0b 00000000 00000000 c0503601 nt!ObOpenObjectByName+0xe9
b292eca8 80555186 00bcfc58 00100080 00bcfbf8 nt!IopCreateFile+0x407
b292ecf0 8055763a 00bcfc58 00100080 00bcfbf8 nt!IoCreateFile+0x36
b292ed30 8052df31 00bcfc58 00100080 00bcfbf8 nt!NtCreateFile+0x2e
b292ed30 7ffe0304 00bcfc58 00100080 00bcfbf8 nt!KiSystemService+0xc4
00bcfc50 00000000 00000000 00000000 00000000
SharedUserData!SystemCallStub+0x4

FOLLOWUP_IP:
tmtdi+14e1
b287f4e1 ?? ???
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: tmtdi+14e1
MODULE_NAME: tmtdi
IMAGE_NAME: tmtdi.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3ea8f4cd
STACK_COMMAND: .trap ffffffffb292e9a0 ; kb
BUCKET_ID: 0x8E_tmtdi+14e1
Followup: MachineOwner
---------

Start Free Trial