VRDB freezes the computer

Hello, I’m using avast 4.8 home edition, OS Windows xp pro.
VRDB was set as default to start when the computer is inactive, I’ve only once started it immediately after the first and onlyone installation more than one year ago.
A few days ago I’ve left the computer for a while, later on I waked it up and I tried to do some activity. I’ve seen the VRDB icon turning, but I haven’t been able to do anything: no answer to any command, no way to open any application, not even possible to open task manager, ctrl-alt-del not working, no way to turn off the computer if not by brute force turning off the current.
Restarting the behaviour was the same, after a while VRBD starts working and again freezes the computer. I’ve been ought to turn off the current again and as soon as rebooted I’ve deactivated VRDB.
I have done some other attempts, but I’ve realized I cannot leave VRDB on: always the same pronlem.
Any suggestion? VRDB is not the only but one the best competitive edge of Avast versus competitors, but if I cannot use it…

Disable it. It’s outdated technology. Doesn’t work at all on Vista and Win 7
and will not be used any more when the avast! 5 is released.

Ok, I will, but it’s a pity, so far I’ve never been obliged to use it, anyhow having a safety shield behind was positive.
Is there a similar tool coming with the new version, as far as you know?

Me its work fine on Vista with default config of the Avast!

It isn’t that it doesn’t work, it’s that the system already protects your system files. VRDB isn’t needed in Vista or Windows 7.

So it can be safely turned off on my Vista Home Basic SP1?

I’ll answer it this way:
I have it running on my Windows XP system but shut off on the
two systems running Windows 7. :slight_smile:

Well, I do have Windows XP and I do not want to leave it, and I cannot use VRDB. So far, the only suggestion is to disable it and it is exactly what I have been obliged to do in order to keep Avast and the PC running.

It stores the necessary info to restore executables (*.exe, *.com) files.
VRDB is not a backup system, the stored information is very small (not the whole files).
Besides, only Win32 executables are processed.
VRDB is a generic method, storing file parts that are often target of virus infections. Actually, VRDB scans all the local hard disks for executable files and stores some info about them. VRDB is not a backup system, the stored information is very small (not the whole files). Besides, only Win32 executables are processed. The VRDB data are stored in \Data\Integ\avast.int

Those 8 seconds mean VRDB will start generating when mouse is not moved(and keyboard not pressed) for 8 seconds. If you give any input to your PC within these 8 sec VRDB will NOT start generating. On Vista, it can be manually build… But I’m using avast for 6 years and I never used VRDB for nothing…

Are the freeze momentary or it “crashes” the computer and you need to force boot?

well i can say its on when i got the screen turned on and its didnt freeze so i will let it on. Also i know what its needed or what its not so :slight_smile:

Sometimes, while waking up the computer from the screen saver, the VRDB is processing a file and needs some time to finish the job… the icon disappears after some seconds. On Vista, it runs on system account and the processing could happen even when the screen saver is off. See the picture…

Yes, it crashes the computer and yes, I need to force boot. Last attempt: I forced VRDB to “start now”, then I’ve left it working, leaving the computer. After more than two hours, the VRBD icon was still rotating, even if I didn’t see any activity of the CPU (the Process Explorer of Sysinternal was open) or whatever else service. The computer was in crash, the onlyone working items were the rotation of VRBD icon and the mouse arrow. End of story.

Sorry to say, but probably the programmers won’t give this that much attention as they’re on avast 5 development and, as said, this technology will be dropped. I just suggest you leave it disabled.
I had run VRDB on Vista, it finished, no problems.

It’s a somewhat unusual problem, but, as said, relatively unimportant.
The reason the problem is present might be worth looking into.
What other security programs run on this computer, and what was your last AV?

I have definetely disabled VRDB.
Security programs:

  • Zone Alarm free edition.
  • Spybot Search&Destroy and Ad-Aware free edition, both not active, only scanning on demand about once a month.
  • Windows Defender - always active.

What do you mean for last AV? If AV scanning, last one has been done about 15 days ago.

Anyhow, the problem arose suddenly after more than one year of good behaviour, and without any change of the OS and/or related applications.

What I mean by “last AV” is what type of antivirus was installed prior to Avast.
Sometimes the remnants of old AV’s can have an affect several months after they were uninstalled, if (and this is the case with a few of them) the uninstaller doesn’t clean up well.

I never heard about a problem with VRDB and these programs…
Just to be safe, add this to the Exclusion lists:
?:\System Volume Information\tracking.log

Before moving to Avast the AV I was using was AVG free edition, nevertheless I’m used to clean the registry every now and then with CC Cleaner, and always after any uninstallation of software.

I’m going to follow your suggestion, but I’m in doubt if activating again VRDB, if it doesn’t work again I have to close the computer via brute force, that’s not healty for it, I believe…