Frequent BSOD with same memory-related stop code ...F...05

Nathaniel · 05 Oct 2014

Thank you in advance for any help. I'm attaching the zip files created by the two tools listed in the How to Post thread. I'm not clear on whether they contain the same information. I forgot to write the stop code down to put in the title but the next time it happens I'll try updating it if I can. I know it has F and ends in 05 but forget how many 0s go where.

I have a PC that I put together myself and it has always had occasional BSOD that I've no idea how to fix. For a while they were IRQ NOT LESS THAN but I found my CD drive was bad and replaced it. After that I started getting the memory-related errors.

Recently they have become more frequent to the point of happening almost every day. I'm not sure where to begin with updating drivers and checking for BIOS updates; I'm hoping that someone can use the dump info to point me in the right direction. I probably should just replace the RAM but I've run MemTest86 a few times and it's never identified a problem.

Arc · 05 Oct 2014

Hi Nathaniel.

You use the Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64 which is teh cause of the BSOD.

Code:

BugCheck 3B, {c0000005, fffff80002eb9ac5, fffff88009d39ba0, 0}

*** WARNING: Unable to verify timestamp for acsock64.sys
*** ERROR: Module load completed but symbols could not be loaded for acsock64.sys
Probably caused by : acsock64.sys ( acsock64+b5a6 )

Followup: MachineOwner
---------

And it is somehow old.

Code:

    Image name: acsock64.sys
    Timestamp:        Tue Jan 24 21:37:18 2012 (4F1ED736)

Update it from Cisco Systems ... let us know the result.

Nathaniel · 06 Oct 2014

Thanks! I've uninstalled the Cisco Adapter for now. It's a work thing for connecting from home and I've submitted a ticket to MIS asking about the newer version but that's all I can do for now. I sure hope they have a solution or I'll have to give up my work from home day. Or install it on Friday morning and uninstall that night. I'm going to leave this thread open for a few days to see if I get any more BSOD but so far none since your reply.

Nathaniel · 09 Oct 2014

Unfortunately corporate MIS didn't have any suggestion other than re-installing the Cisco software and waiting to see what happened. My computer blue screened again over night but I wasn't able to grab the dump file before leaving for work this morning. I'll post it this evening to confirm that the same error is manifesting again and then uninstall.

Everyone I work with has the same version of the Cisco software installed and many of them have the same Windows version but none are getting the BSOD. This suggests to me that perhaps my computer has some other problem that is triggering the acsock64.sys error so maybe if I can get a BSOD and dump after uninstalling the Cisco software, more information will emerge. I hope it's ok to continue keeping this thread open.