Cisco VPN client blue screens xp

Uninstall the VPN Client....

Start>run>CMD.exe

netsh int ip reset reset.log
netsh firewall reset
netsh winsock reset

Then remove ALL NIC's from the device manager..
In the Device Manager, select View>Show Hidden Devices

(If the Show Hidden devices is not present, do the following command from a command prompt..)

start>run>cmd
set devmgr_show_nonpresent_devices=1

More information on that command here....
Device Manager does not display devices that are not connected to the Windows XP-based computer
http://support.microsoft.com/kb/315539

Go back to Network Adapters, and make sure your adapters are all gone, including any older ones. (there will be several ' miniport' devices that are not able to be uninstalled....)
Once they are all gone, reboot and let Windows reinstall them...

Then, go ahead and reinstall the client and see if it still bsods....

I have tried John's suggestion of uninstalling all network adapters and netsh commands and reinstalling VPN client with same result.  I have uploaded the minidump file as requested.  I have also tried to back the VPN client from 4.8.01 down to 4.0.3f.  I am still getting same result.  I don't think this can be hardware due to the very specific and consistant nature of the blue screen.  Again, if you do not authenticate it does not blue screen, only when you authenticate correctly.

Might even try renaming the ipsec.sys from c:\windows\system32\drivers, and replacing with another one from the same level of SP from another machine.

Or, reinstall SP2...

Or...Start>run>cmd

netsh int ip reset reset.log
netsh winsock reset
netsh firewall reset

Then reboot disable the SP2 firewall, and retry...

2 other IPSec related links

Delete and re-build IPSec Local Policy.
http://www.howtonetworking.com/VPN/rebuildipsec.htm

Actually, just 1.....Cant count today...   :^)

Do you happen to be running McAfee HIPS on the laptop?

I uninstalled the antivirus software as part of my troubleshooting.  None of these suggestions have improved anything.  I am going to reload the whole OS and close this ticket please.  Thank you.

I forgot to come back and post the output of the dump...I apologize I missed this one... It shows as memory corrutpion, but I find that hard to believe.....

Just for giggles, have you tried a RAM test?

I split the points because the problem does seem to be related to memory.  When I move the memory chip to the slot B I stop getting the blue screen.  When I reinstall antivirus the blue screen comes back so I moved the memory back to slot A and it is gone again.  I am not sure what exactly the problem is but it works for now.  Thanks for you help.

We are having this problem as well. It does not happen all the time but when it happens the blue screen comes immediately after the VPN connected. It is intermittent problem for us. Anyone have idea on this?

Error code 1000007e, parameter1 c0000005, parameter2 00000000, parameter3 a4e0eb64, parameter4 a4e0e860.

I believe it is related to Antivirus software. We are using Sophos client 7.1.1.1.

istadmin, can I know what anti-virus software are you using? Thanks for your help.

We use Panda.

Hi

We use Trend Micro OfficeScan version 8 on a mix of Dell and Lenovo PC's. Some of our computeres experience the BSOD when we use the cisco vpn client. This problem started with version 4 (v 3 was fine) and has continued in version 5. It has happend more on the Lenovo T 61 than our Dell Latitudes (D 600, D 610, D 620 and D 630).

It is intermittent but fairly insistent for the users I have installed via an image. I don't have the problem myself on my own laptop, but 20-some users experience this.

Hi again

In another forum one user seems to get rid of the error by uninstalling VPN client and all antivirus AV, then re-installing VPN client BEFORE antivirus.

Some1 pls try it out...

Mvh,

TD

Hi Tomdane,

Thanks for your comment. We are using Dell Latitudes D series (D620 and D630) and it happened intermittently on VPN V4 and V5.

I will try to uninstall VPN Client and AV and put them back in order. Will post it again if it works. Many thanks.

Cheers,
Will

just make sure you delete the reference to csgina.dll in the registry (HKLM\sw\ms\win nt\currentversion\winlogon) before you restart after removing the Cisco VPN client. Otherwise you may get an interface error.

I have done this now on 2 machines and I am waiting for response from my users.

IMHO it is a fight over who starts first - AV or VPN - and it must be related to the GUI startup procedure. But that is just speculation on my part.

Hi tomdane,

You may right, this problem seems only happened on those computer with VPN re-installed. I am also re-installing a couple of laptops and see what's happened.

Keep me posted. Many thanks for your advise.


Kind Regards,
Will

From my experience, the issue is related to McAfee HIPS.  Before we had HIPS installed, we did not have a problem with blue screens after logging into the VPN client.  Funny thing is, McAfee blames the firewall software that is "built in" to the Cisco VPN client.  I still haven't found a resolution for these random bluescreens, however, it seems to only happen when the client is connecting to a wireless network.

Hi again

I think this is related to antivirus programs as a class, as we don't have any McAfee.

Finally some good news: On 2 machines I asked the users to remove the tick in "enable start before logon" in "windows logon properties" under "options". Then the machines worked without any problems!!

Of course this means their login scrips is not run, but that can be done manually by adding a simple shortcut to their desktop.

Br, Thomas

Hi again, again

No luck - still problems even without "enable start before logon". But I have a new theory: I think the problem is related to the official Lenovo "Vista to XP downgrade kit".

I am therefore creating a brand new machine from scratch, using my own select XP disc and manually installing all drivers. I will report back.

Br, Thomas

tomdane,

I think your thought is correct. I removed both AV (Sophos) and VPN client on a laptop. then reinstall them in the order - install VPN client before installing Sophos. I have been testing for that computer for more than a month and all good so far. Thank you very much!

Anyone else tested out this and how it goes?


Cheers,
Will

Hi all
Well, all my ideas have been shot down. My manual xp installation has helped somewhat but we still get blue screen.

Next idea: I know of a company who have downgraded to 4.6.00.0049 and that has solved their problems. Does anyone have this version? Because I would desperately like to get a copy to try it out...

Br, Thomas

!!!!!!!!!!  Success  !!!!!!!!!!!!!

I have downgraded clients to version 4.6.00.0049 and the first (and worst) user has reporte it works without any problems at all. The tricky part was to find a copy of the client that old, but I managed. Holla if you need a copy (you can reach me at a_tomdane@yahoo.com).

Br, Thomas

hmmm, success is relative....

Most users work fine now. Funny enough my own machine never had a problem, but started to bluescreen after i downgraded to 4r6. After upgrade to 4r8 my machine is fine again.....

Some users have problems, but I suspect it is because of residual keys in regedit. Remember to remove the csgina.dll reference in winlogon.
I will try again where I remove ALL cisco references after restart, then re-install 4r6.

Hi tomdane,

Just let you know that the problem came back after I reinstalled VPN & Sophos in order (I didn't delete the csgina.dll file, will try it again).

Let us know how it goes with 4r6

Thanks,
Will

Hello, this same problem showed up on the same machine again a year later.  After trying several things I uninstalled the antivirus (Panda file secure), uninstalled the VPN client, rebooted, installed VPN client 5.03 then pushed out the Panda from the server again and everything works perfect.  This also magically fixed the issue of this tablet blue screening as soon as it was docked.  The OS is XP tablet.

Hi istadmin/tomdane,

Even the problem came back after re-install VPN before anti-virus software, i have to say it helps lots on this problem since it happens only a couple of times since re-installation (much lesser than before). Thanks for your words.

Cheers,
Will