I’m having serious problems with the new AdWatch 2007 (I’m using AdAware 2007 version 7.0.2.3).

After starting up (it starts when Windows starts), AdWatch soon occupies about 50% of the CPU, and 750-800 MB RAM, thereby effectively blocking all other applications. (I have 2,16 GHz CPU and 3 GB RAM.)

I then close down and restart AdWatch, and initially it takes 0% CPU and about 2 MB RAM – but after a while it starts growing to several hundreds of MB RAM and slowing down the computer.

What is AdWatch actually doing? This never happened with the previous version of AdWatch. And recently it also caused a system crash with the infamous blue screen of death.

My only solution has been to permanently disable AdWatch. Is this how it is intended to be??

Hi Hans_N,

As posted in the Software Updates section, the latest version (7.0.2.3) greatly improves Ad-Watch performance and resource leaks have been fixed in various Ad-Watch modules.

Did you update to v.7.0.2.3 by downloading the Software Updates, or did you uninstall then download /re-install the new 7.0.2.3 executable from your License Account inside the Support Center?

Also, what is your OS (ie XP, Vista 32, Vista 64) and what other security software (eg: anti-virus, anti-malware, firewall etc) do you have installed/running on your system?

Regards,

Spike

I have exactly the same problem that Hans has with Ad-Watch. I am running AdAware 2007 version 7.0.2.3 also. It started on October 7, 2007 after I updated Ad-Aware from within the program. My first clue was getting a serious exception notice from Lavasoft on bootup and I sent the crash report as requested. I found the memory issue when I noticed Ad-Watch.exe was using 1.7 GB and bringing the the machine to its knees by all of the memory use and paging. I am running XP with Norton Internet Security 2007 and the Windows Defender Security Program. There never has been an issue until that last Lavasoft software update via Software Updates that I made about Oct 6th. I have a 2.8 MHz CPU with 2 GB of RAM. I have attached a screen shot of the exception window and shots of the Windows Task Manager showing how much memory the Ad-Watch.exe was using and the plot of the system performance before and after I terminated Ad-Watch. As Hans has said, the memory use plummets upon termination. Like Hans, I have had to disable Ad-Watch but before that I did not get the blue screen (so far). I did get some sort of a message from Windows saying that a Lavasoft program had terminated in a strange manner but not much else information.

It is clear that something has happend and that I cannot use Ad-Watch Do you have any suggestions on how to proceed? As I said, this all started after the latest Software Update that included program elements and not just new entries in the detection database.

Thanks,

ndk

Click to view attachment

Click to view attachment

Hi ndk,

As posted here - Software Update 7.0.2.3 September 26th, 2007 - that problem should have been fixed by the 7.0.2.3 software update - for me, the resources used by both AAW 2007 and Ad-Watch lessened considerably after the update

An initial suggestion - firstly, log into your license account at the Support Center and download/save the new (smaller) exectuable for AAW 2007 version 7.0.2.3.

Then uninstall your current version and install the updated AAW 2007 program and re-register it - there is an "E-mail Serial Number" link in case you need it.

(If you strike any uninstall error messages, go to "Start > Run" and type in services.msc - locate the Ad-Aware Service and click "Stop", then continue with uninstallation).

Please advise whether that helps.

Regards,

Spike

I updated by downloading the software updates. My OS is XP SP 2. I'm using Norton AntiVirus 2007, ZoneAlarm 7.0, AVG Anti-Spyware 7.5, Spyware Doctor 4.0. All of these have worked perfectly well with the previous version of AdAware and AdWatch.

Hi Hans,

Please see this post dated today from LS CalamityJane in Ad Watch Error Code


Given that the Devs have identified that particular problem, I would suggest following Janie's advice.


By the way, I have Spyware Doctor 5, which has real-time protection of it's own - therefore I turn off Ad-Watch before re-enabling/loading Spyware Doctor to scan. Having two programs with real-time protection running at the same time can cause problems of their own.

Regards,

Spike