Solved BSOD keycrypt64

[boweasel]

This more of a curiousity. I couldn't figure out the problem, and since everything had been backed up, I simply did a factory restore, but I'm wondering if there's anything I could have done.

HP Pavilion dv6-2150us Entertainment Notebook. I actually don't know if it's a 32 or 64 bit OS.

Got the Blue Screen on every boot - safe, safe with networking, with command prompt, directory services restore. etc. I've never seen the keycrypt64 BSOD.

Startup repair took me into HP set of diagnostic screens. I tested everything with their tools and everything passed, hard drive, memory, startup, etc. I tried to do a restore, but was told that no restore points had been set.

Any thoughts on what I COULD have done instead of a complete reinstall?

 

[Dsprague]

There may have been it doesn't seem it was hardware causing the problem Keycrypt64 is a driver used by Zemana Antilogger it is more likely that the driver was doing something that is shouldn't have been and needed to be updated or uninstalled and then re-installed.

 

[boweasel]

There may have been it doesn't seem it was hardware causing the problem Keycrypt64 is a driver used by Zemana Antilogger it is more likely that the driver was doing something that is shouldn't have been and needed to be updated or uninstalled and then re-installed.

Is there a way to update this driver in a PC that blue screens? AIAS the 'repair' option from Windows gives me a half-second's worth of 'Windows could no repair this computer' before flipping me into HP diagnostics. Even if I could get this updated driver on a flash drive, and could, somehow, get to the command prompt by using a DVD, would I have been able to access the flash drive through recovery? Or the file with the driver?

 

[Dsprague]

from the sounds of things likely not I'm not sure if the recovery console even loads the drivers needed to use the usb ports, but then I'm not expert on the subject. Too it sounds like it could have been simple file corruption which the SFC /scan now command may have been able to fix. worst case scenario it may have been malware and there are a number of bootable antiviruses you could have tried, but again all of this is just speculation as I have nothing other than your description of the problem to go off of.

 

[Layback Bear]

Do you by chance use ComCast.

keycrypt64.sys - Microsoft Community

 

[boweasel]

Thanks.

 

[boweasel]

Do you by chance use ComCast.

keycrypt64.sys - Microsoft Community

Yes

 

[Layback Bear]

Did the web site Microsoft help you?

 

[boweasel]

Did the web site Microsoft help you?

Kind of....

In the start of this thread I said that I'd already done a full restore. I only wanted to know if there was anything else I could have done instead.

I don't own a USB keyboard with a USB port for the mouse, so the solution proposed wouldn't have worked for me, but it's a moot point since I reformatted and reinstalled. What I did take from it was to not reinstall Constant Guard from Comcast. Shame on them for their shoddy software.

 

[Layback Bear]

Thank you for the information. Not installing Constant Guard from Comcast is the answer. That answer may help many others.
Happy computing.