TotalMounter caused BSOD
Posted: Thu Dec 09, 2010 5:49 am
Hi, I dunno if you're still developing this product, but I hope you are, because I really need something like it.
I have Win XP SP3, fully updated, running OEM on a netbook. When I tried to install v 1.33, I got a BSOD shortly after the "unsigned driver" alert. I tried several times to re-install (after uninstalling, of course, each time) but always got the same BSOD, which flashed by too quickly for me to get the error code (although I believe it referred to, or happened shortly after, the installation of the driver file k(something)bus.sys?)
I just saw that there is a 1.40 b version out, and I will test it out, although I am not too hopeful.
Is this a known bug?
I have Win XP SP3, fully updated, running OEM on a netbook. When I tried to install v 1.33, I got a BSOD shortly after the "unsigned driver" alert. I tried several times to re-install (after uninstalling, of course, each time) but always got the same BSOD, which flashed by too quickly for me to get the error code (although I believe it referred to, or happened shortly after, the installation of the driver file k(something)bus.sys?)
I just saw that there is a 1.40 b version out, and I will test it out, although I am not too hopeful.
Is this a known bug?