Windows 10: BSOD when using Cisco VPN - Driver Corrupted Expool (0x000000C5)

Whenever I connect to work network using Cisco VPN 4.2, I get BSOD almost all the time. Sometimes after an hour and sometimes immediately after I'm connected and using RDP.

:)

 

BSOD in Windows 10

Dear all,

I got several times the blues screen of death in Windows 10 telling me that there was a SYSTEM_SERVICE_EXCEPTION.

The error happens only when I use Cisco VPN Client v3.

Googling this, I read that this is a common issue with that program, but I need Cisco VPN to connect to my pc at work, and I cannot unistall it.

Is there any other way to keep using Cisco VPN without having other BSODs?

thanks

**Post moved by the moderator to the appropriate forum category.**

 

BSOD Driver Corrupted EXPOOL

Hi,

BugCheck C5, {760e0002, 2, 0, fffff80400a58850}

Probably caused by : memory_corruption

There was a lot of other information that was not clear.

1. So check with Lenovo Support, their on-line documentation and drivers, and check in their forums for any known issues. Update the BIOS, chipset drivers, and ALL the major on-board and separate device drivers - especially the ATI/AMD video
drivers. See driver update methods below.

BiosVersion = A2CN43WW(V2.11)

BiosReleaseDate = 01/09/2016

SystemManufacturer = LENOVO

SystemProductName = 80E3

SystemFamily = IDEAPAD

SystemVersion = Lenovo G50-45

SystemSKU = LENOVO_MT_80E3_BU_idea_FM_Lenovo G50-45

BaseBoardManufacturer = LENOVO

BaseBoardProduct = Lancer 5B2

Lenovo Support and downloads

Home Global Support

Lenovo Forums

English Community - Lenovo Community

Get the Catalyst Drivers here

Gaming Technologies and Products | AMD

ATI - Forums

Support Forums | Community

ATI - Support and Drivers

http://support.amd.com/us/Pages/AMDSupportHub.aspx

2. As needed use ALL the methods in troubleshooters below.

3. If needed run Driver Verifier to see if it can indicate a CAUSE (see Driver Verifier

methods below).

======================

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors




====================================================

Bug_Check : C5 0x000000C5 <-- read this link

http://www.faultwire.com/solutions-fatal_error/A-device-driver-has-pool-0x000000C5-*1198.html

Bug_Check : C5 0x000000C5 <-- read this link

https://msdn.microsoft.com/en-us/li...192(v=vs.85).aspx?f=255&MSPPError=-2147217396

==================================================

This utility makes it easy to see which versions are loaded :

Run DriverView - set VIEW to Hide Microsoft drivers - update those without

Dump in their names (and update BIOS and chipset).

DriverView - Free - utility displays the list of all device drivers currently loaded

on your system. For each driver in the list, additional useful information is

displayed: load address of the driver, description, version, product name,

company that created the driver, and more.

http://www.nirsoft.net/utils/driverview.html



For Drivers check System Maker as fallbacks and Device Maker's which are the

most current. Control Panel - Device Manager - Display Adapter - write down

the make and complete model of your video adapter - double click - Driver's

tab - write down the version info. Now click UPdate Driver (this may not do

anything as MS is far behind certifying drivers) - then Right Click - Uninstall -

REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard

if 3rd party with their own software and drivers and any other major device drivers

you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and

then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their

latest versions. (Look for BIOS, Chipset, and software updates at System Maker's

site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -

REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are

installing actually shows up. This is because some drivers rollback before the

latest is installed (sound drivers particularly do this) so install a driver - reboot

- check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER -

heck manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

====================================================

Memory tests do not catch all errors such as mismatched memory (possible even

for sticks that appear to be identical) and when faster memory is placed in system

behind slower memory. So it is best to also swap sticks in and out to check for

those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so. <-- best method

www.memtest.org

MemTestX86 - Test RAM With

https://www.windowsphoneinfo.com/threads/memtest86-test-ram.2010/

For the Windows Memory Diagnostic Tool.

Type in Cortana's search box -> Windows Memory Diagnostics

at top of list - click it. in Windows 8/8.1/10 the name is "Windows Memory

Diagnostic".



================================================

After doing ALL the updates you can, and if the issue continues, then run

DriverVerifier. (Remember to use the Windows 10 methods posted at the

top of the original reply above.)

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users

http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

are essentially the same).

http://www.winvistaclub.com/t79.html

Using Driver Verifier

https://msdn.microsoft.com/en-us/li...448(v=vs.85).aspx?f=255&MSPPError=-2147217396

WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

Use BlueScreenView to see if there is a driver specified in the error message.

Also check with MyEventViewer at the time of the BlueScreen.

If DriverVerifier creates a minidump upload it and post the link here so we can

analyze it.

Hope this helps.

--------------------------------------------------------------------------------------------

Rob Brown -
Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

 

Both dumpfiles are

acsock64 Thu Oct 08 17:12:56 2015
Also in your unloaded driver modules is vpnva64_6 Wed Feb 26 17:46:48 2014

Both drivers belong to
vpnva64-6.sys
acsock64.sys

Driver Description: Cisco AnyConnect Secure Mobility Client
Driver Description: Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter Driver
Driver Update Site: Security - Cisco AnyConnect Secure Mobility Client - Cisco

Update to a newer version and hopefully this stops the BSOD.

 

Thanks lifetec. Cisco VPN installation is provided by our company (I can't install any updates). I have a desktop (Windows 10 home). It works fine there. Only in my laptop this happens. I have had more BSODs since my last post. I have attached latest file now. (with more BSOD failures)

 

All the dumpfiles from 10,11 and 12 again blames Cisco VPN client.

Does the desktop has the same windows O.S version and build, are the same windows updates installed, are the same programs installed etc.?
Is the installed Cisco version exactly the same?
The installed version on your laptop might be corrupted?

Normally no system is exactly the same.


If you also cannot reinstall the program on your laptop (it might be corrupted) yourself, i would contact the ict-support of your company.

 

I understand no two systems are same (Just provided a reference as both are same OS version. Both have windows update turned on) Same version of Cisco VPN 4.2.

In fact, I tried uninstalling and reinstalling Cisco VPN 4.2. I still got BSOD. One or two failures from previous post is after this reinstallation.

Thanks for your assistance so far. I will contact my company. I have a feeling recent driver updates made to several components could be a cause (No errors in Device manager). I couldn't pin point which update might be causing this.