Hi. I couldn't find any technical contact for Ad-Aware so I'm writing here

An application that we have written seems to cause systems running Ad-Aware to crash with BSOD because of lbd.sys . I googled a bit and it seems we're not the only ones (which leads me to believe that the problem is more on Ad-Aware's side rather than ours). For the moment, we're advising our users to temporarily disable ad-aware's Ad-Watch Live! while they run our application.

Is there a known bug in lbd.sys ?
Who can we contact to talk about it ?

Hi there,

I'll report this as a bug and try and point an LS staff member in your direction.

GoddersUK

Hello
as far as I know was it a glitch in AAW08.
Plz run an update to AE.
Next is : disable or uninstall NIS/ZoneAlarm/Symantec(former Norton).
If it doesn't solve the problem, post back with more detailed information about the afflicted
machines
Regards
Raziel

Hello,

I can easily reproduce the bug on XP and Vista (both 32 bit).

LBD.SYS doesn't seem to be versioned (version info is 1.0.0.000).
File size : 64.160 bytes
PE Checksum: 0x13A60

The crash is always at offset base+0x2895:

base+0x2895: 8B 0E mov ecx, dword ptr [esi] ; C0000005, access violation, ESI points to invalid memory.
base+0x2897: FF 15 <...> call IofCallDriver

The bug appears when scanning with BitDefender QuickScan - http://qscan.bitdefender.com/
BitDefender QuickScan does not contain kernel mode code.

I'm assuming improper parameter validation in lbd.sys.

Please let me know if you need more info.

Cheers,
sysenter

Just found entries in ...
docs. and settings .... driver 32 / 64
Windows 32 driver
Programs

All Boot drivers
will test Bitdefender -- nope won't.
Read about the Cleaning-Behaviour of it

Is it false positive ?

Addendum:
just scanned all lbd.sys files with avast and MAM
no problem.

Raziel,

The problem is a CRASH (BSOD) in lbd.sys, like I said, possibly because of improper parameter validation.
The easiest way to reproduce the BSOD would be to run BitDefender QuickScan - http://qscan.bitdefender.com/

Like I said, since BitDefender QuickScan does not use kernel mode code, the crash is 100% because of LBD.SYS

Cheers,
sysenter

It's reported to the IT guys.
I close here

Hey guys,

Just heard from LS Staff that this should be fixed in the next update

Good to hear. Will LavaSoft customers receive it automatically or do they have to go through an extra step (manually downloading a patch or something similar) ?

So long as users have Ad-Aware set to automatically update they should not have to do anything to receive the update. If they do not have it set to auto-update they will manually need to press the "Web Update" button on the main screen of the program.

Hey guys. Did 2 updates (one on the 17th and one today) and the problem is still there. Do you have an estimate on when the fix including lbd.sys will be up ?

Thanks

Those updates were for definition files only, not program updates. This is all we have...



...so it should be put through in the next few days

Casey

Fixed today. Update 8.0.4

http://www.lavasoftsupport.com/index.php?showtopic=25141

Casey

Can confirm it's fixed now. Great stuff, guys ! Thanks !

Great news. Thanks for the confirmation. Will close this topic now then. If, for some reason, you need it reopening, then PM any moderator.

Casey