CryptoMonitor causing blue screen

After installing CryptoMonitor on my XP Pro machine, I get a blue screen on shut down. The computer logs off, saves settings and then gets to Shutting Down. After a bit, I'm presented with a blue screen.
MULTIPLE_IRP_COMPLETE_REQUESTS
.
.
.
STOP 0x00000044 (8ac53008, 00000D64, 00000000, 00000000)
The first set of numbers in the parenthesis changes.

Then on boot, I get an EasySync CryptoMonitor window saying

I uninstalled CrytoMonitor and all was good again. No messages on Shut Down or Boot. Reinstalled CryptoMonitor and the error messages came back on Shut Down and Boot.

Note: When I uninstalled CryptoMonitor, it said another application has exclusive access to C\Program Files\EasySync Solutions\Easy Sync CryptoMonitor
Proc.3sdb. I used unlocker to unlock the file and then the Crypto Monitor uninstaller continued properly.
I’ll have to see if they have a forum for issues. I see they’re talking about issues with CryptoMonitor at BleepingComputer, but I don’t know if that’s the proper forum for this.

 

I would try Bleeping Computer, Tony. Pete was one of the malware experts that did the beta testing and worked with the developer.

 

Hi Tony,

I'll let Nathan know about this.
The info may be helpful to him.

 

Thanks Pete, Let me know if I can be of any help.

 

Ok, will do.
I have given Nathan the link to this thread.

 

I just noticed I had incorrectly written that the error was 0x00000033. It should have been 0x00000044. I edited the original post to reflect the correction.

 

Thanks for letting me know Tony

 

Nathan found the cause of the reboot error and will correct this in the next update.
He's looking into the Blue Screen error now.

 

Cool and that was fast!

 

Hi Tony,

CM has now been updated to rectify the problems.
Could you let us know if you still get any errors now.
Many thanks for your input.

 

Good news and some not-so-good news. The update fixed the boot problem with the

I'm still getting the shut down blue screen ....
MULTIPLE_IRP_COMPLETE_REQUESTS
.
.
.
STOP 0x00000044 (8ac53008, 00000D64, 00000000, 00000000)

I don't know that it's due to CryptoMonitor, but it is a coincidence. A bit of searching says it has something to do with drivers. Now, even uninstalling CM doesn't fix the problem. I've even done a System Restore to before CM was installed and the problem persists. That's why I'm not sure it was caused by CM. I'll deal with it later.

 

I noted that CryptoPrevent has prevented my CPU/RAM monitor gadget from working. I told it that I was good with gadgets on my computer. These programs are helping. I think they just need a bit of fine tuning. There are so many users with so many various configurations and then a variety of Windows OSs running, it's almost impossible to create a perfect application.

 

I have past your comments on to Nathan.

 

Starbuck - please note that my last comment was on CryptoPrevent, not CM.

However, the problem facing Nathan and other app developers is the variety of configurations out there. It's has to be quite difficult creating applications for unknown scenarios.

 

Yes I did notice that the last comment was about CP..... so I left that out from my reply to Nathan.
I do agree about the problems facing these developers.
It can't be easy.