Hi,
Your best option is just to wait until Lavasoft release a software update for these sort of bugs. If this doesn't fix it then contact Lavasoft again.
Casey
GMER log file contents:
GMER 1.0.15.15281 -
http://www.gmer.netRootkit scan 2010-03-03 15:30:25
Windows 6.0.6002 Service Pack 2
Running: gmer.exe; Driver: C:\Users\Mom\AppData\Local\Temp\awecrkow.sys
---- User code sections - GMER 1.0.15 ----
.text C:\Program Files\Windows Live\Family Safety\fsssvc.exe[1208] ADVAPI32.dll!RegOpenKeyExA 75DA7C42 5 Bytes JMP 0058237E C:\Program Files\Windows Live\Family Safety\fsssvc.exe (Windows Live Family Safety Service/Microsoft Corporation)
---- User IAT/EAT - GMER 1.0.15 ----
IAT C:\Windows\Explorer.EXE[2556] @ C:\Windows\system32\ole32.dll [msvcrt.dll!free] [6D46F3FB] C:\Windows\AppPatch\AcSpecfc.DLL (Windows Compatibility DLL/Microsoft Corporation)
---- Devices - GMER 1.0.15 ----
AttachedDevice \Driver\tdx \Device\Tcp Lbd.sys (Boot Driver/Lavasoft AB)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume1 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume2 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume3 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume4 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
---- EOF - GMER 1.0.15 ----