Hi! Welcome to Sysnative, thanks for taking the time to register and letting us know about your issue. First off, you have uninstalled LogMeIn Hamachi and the crashes have ceased, yes? Onto contributions, the best way to do so is to install LogMeIn Hamachi, set your system to generate kernel-dumps (
Enabling a Kernel-Mode Dump File (Windows Debuggers)), let it crash, and then post it here for Harry and I to take a look at to check for consistency. At this point, we have seen consistency, but more people providing kernel-dumps just to further prove it only helps!
I have *not* yet uninstalled Hamachi (currently I need it constantly since most of my work is on remote servers accessible only via a Hamachi gateway network), and am living with the BSOD. Only one more occurrence since my original post. :/
I do have a zip, am attaching it here.
If it helps, I am also on a paid Hamachi subscription, not a free one.... so in case we need volume in our voice to logmein you can count me in
I will report back once I can actually uninstall Hamachi and see if the BSOD crashes cease.
Thanks again.
Understood! Yes, as Harry said, we've analyzed about as much as we know we can and found a consistency enough to confidently label it a bug in the actual driver itself. Other than that, it's up to LogMeIn now to go ahead on their end and fix the bug in their driver. Since we cannot do that as we did not program this driver, all we as volunteers can do is recommend removal until LogMeIn fixes it.
Also, before you uninstall LogMeIn Hamachi, as I said, if you'd like to assist, setting a kernel-dump up and having it crash and providing that to us would be great. This is optional, but it helps us as research wise, and as I noted to further prove consistency. The .ZIP you provided contains a minidump, which although still good, we cannot unfortunately run a wide variety of extensions in to get valuable information.
Final note, which I am going to add to the top of my blog post because I need to make a huge edit to it today, I would go ahead and make a support ticket -
https://secure.logmein.com/support/submitaticket/
I am going to start adding that link to every one of my 0x44 posts. Eventually LogMeIn will get so many tickets this way, they have to look into it if they are not already. I'd also like to go ahead and research whether or not there has been official word from a developer or LogMeIn employee regarding this bug.
I just checked and my system settings were set to "Automatic Memory Dump" ... so the attached zip from my previous post was with that setting. Not sure if that is helpful for you or not. I have changed it to "Kernel memory dump" now.... that is better for you, correct?
Correct! When the system crashes, it will generate a MEMORY.DMP file within the directory C:\Windows
Once that happens, it'll be too large to attach here, so you'd then go ahead and upload it to a website like Skydrive, Mediafire, Google Drive, whatever works best for you and whatever can get a link to Harry & I.