There is a known issue with the Logmein driver dated 1/24/2014 causing BSOD'S with the 0x44 error code and the titile of " MULTIPLE-IRP-COMPLETE-REQUESTS"
*
We recommend removing it or contacting the developer for a patch, update, work around, etc.
Failing that I would revert to an older version until a non buggy driver is released.
*
LogMeIn Hamachi Virtual Miniport Driver. Driver Update Site: https://secure.logmein.com/products/ios/
If you get an error message " "The feature you are trying to use is on a network resource that is unavailable."
Try this
http://community.logmein.com/t5/Free-Pro-User-to-User-Support/cannot-add-computer-to-computer-list/m-p/9474?query.id=96340#M5545
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff803`bea18000 PsLoadedModuleList = 0xfffff803`becdc990
Debug session time: Sat Feb 1 11:56:16.163 2014 (UTC - 5:00)
System Uptime: 0 days 4:03:54.947
Loading Kernel Symbols
*** WARNING: Unable to verify timestamp for Hamdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for Hamdrv.sys
Probably caused by : Hamdrv.sys ( Hamdrv+1f0a )
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 0000000000126feb, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: Steam.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff803beba5cce to fffff803beb65ca0
STACK_TEXT:
ffffd000`235d9738 fffff803`beba5cce : 00000000`0000004e 00000000`00000007 00000000`00126feb 00000000`00000001 : nt!KeBugCheckEx
ffffd000`235d9740 fffff803`beac3888 : ffffd000`235d98c9 ffffd000`207e4180 00000000`00000000 fffff6e8`0010f290 : nt! ?? ::FNODOBFM::`string'+0x2fb2e
ffffd000`235d9780 fffff803`beabfffc : ffffd000`00000001 fffff803`bed06180 00000000`00000000 00000000`00000002 : nt!MmUnlockPages+0x648
ffffd000`235d9820 fffff800`01ee4f0a : 00000000`00000000 ffffd000`21e52100 ffffe000`048476c0 ffffe000`048476c0 : nt!IopfCompleteRequest+0x52c
ffffd000`235d9930 00000000`00000000 : ffffd000`21e52100 ffffe000`048476c0 ffffe000`048476c0 ffffd000`00000020 : Hamdrv+0x1f0a
STACK_COMMAND: kb
FOLLOWUP_IP:
Hamdrv+1f0a
fffff800`01ee4f0a ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: Hamdrv+1f0a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Hamdrv
IMAGE_NAME: Hamdrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52e10c23
FAILURE_BUCKET_ID: 0x4E_7_Hamdrv+1f0a
BUCKET_ID: 0x4E_7_Hamdrv+1f0a
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x4e_7_hamdrv+1f0a
FAILURE_ID_HASH: {e0b22f77-01c2-a39c-d789-3fefdc512645}
Followup: MachineOwner
---------