Recently the Cisco VPN client stopped working - version 4.8.01.0300-k9 (Windows XP2, Athlon XP, Asus nforce2 A7N8X motherboard). Actually rather more than that - firing it up caused the PC to reset.
I tried to uninstall/reinstall but even doing this caused the PC to reset itself midway through the process. Used System Restore to go back in time but no difference.
Then it got worse after further fiddling (trying to uninstall/install in Safe mode - also resets PC) as the connection to the internet and the internal network went down - eventually I traced these to the deterministic drivers (which you have to remove manually as they dont allow deletion, even in safe mode - see
formatting link
for details of manual removal) and got rid of them to get the network & internet working again.
Then I tried to install the VPN again but again it crashed the PC - but at least this time it left the network & internet intact.
So now the PC works but the VPN is only partially installed. Any ideas how to get it installed and working?
do you have vpn clients by other manufacturers installed ? - I had a similar problem after trying to install the cisco vpn client "on top" of checkpoint secure remote.
it was simply not possible. don't ask me which versions those were, though.
Nope, no other VPNs installed. And it was working a few weeks ago. Have managed to install the Cisco VPN after using EndItAll to kill everything else (Avast and ZoneAlarm in particular), but on running it resets the PC immediately after establishing the connection.
In the event log it lists Save Dump with the following text;
The computer has rebooted from a bugcheck. The bugcheck was:
0x100000d1 (0x00894fdd, 0x00000002, 0x00000000, 0x88bfc024). A dump was saved in: C:\\WINDOWS\\Minidump\\Mini010407-01.dmp. For more information, see Help and Support Center at
formatting link
the 0x100000d1 error number is always the same, the others vary.
Ok I've tried earlier versions of the VPN with the same reset effect. Have also tried different removing & reseating memory just in case there was a hardware error, and disabling virtual memory in case of HD error. Havent tried different nic yet because the existing one is built into the nforce2 motherboard (Asus a7n8x) and anyway this was working all working fine a few weeks ago. No hardware has changed, and Ive tried uninstalling any recent software but to no effect.
Have managed to get it to stop at BSOD now with either a 0x00000D1 error saying 'DRIVER_IRQL_NOT_LESS OR EQUAL' or a 0x00000BE error 'An attempt was made to write to read-only memory'
Have tried Windbg on the minidumps; here is an example of what I get: (hmmm I wonder if the problem is zonelarm which has the vsdatant driver
- will try clean reinstall and see what happens)
-------------------------- Microsoft (R) Windows Debugger Version 6.6.0007.5 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\\WINDOWS\\Minidump\\Mini010407-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV**
formatting link
search path is: Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_gdr.050301-1519 Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Thu Jan 4 00:00:53.062 2007 (GMT+0) System Uptime: 0 days 0:10:51.669 Loading Kernel Symbols ........................................................................................................................................................ Loading User Symbols Loading unloaded module list ............
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {894fdd, 2, 0, 88bfc024}
Unable to load image vsdatant.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys Probably caused by : vsdatant.sys ( vsdatant+44741 )
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00894fdd, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 88bfc024, address which referenced memory
OK Ive completely removed Zonealarm (and replaced it with Comodo) and the VPN works now. Dont know why Zonealarm kept resetting the machine but dont care any more!
snipped-for-privacy@hem> Forgot to say - WinXP SP2 all patches installed as far as I know... >
Hi it's me again I've got problem with Comodo. My system is configured to allow simultaneous remote desktop access by two people. But if there are two concurrent logins, Comodo is disabled (I think it clashes with itself). So I can't use it unless anyone knows a fix. Have tried other Firewalls too, eg Outpost & Kerio but havent managed to configure to allow all of the following:
Internet Connection Sharing Remote Desktop Cisco VPN.
So back to Z> snipped-for-privacy@hem> > OK Ive completely removed Zonealarm (and replaced it with Comodo) and
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.