Dr.web Scanner Errors / Corruptions
#1
Отправлено 17 Август 2009 - 15:15
I started to have following problems with Dr.Web:
1. The complete scan doesn't scan my computer 100%, it stops in the beginning of my OS partition(E:). It checks a few files from E: and then says "done!". It should scan over 150.000 files, but now it says that complete scan is done after 60.000 files.
2. When scanner is running, I start to get error messages from windows that some of my files that exist in E: are corrupted.
3. Chkdsk starts to run after rebooting.
I don't get any errors if I don't use scanner, and chkdsk doesn't run if I haven't scanned anything.
I have used Dr.Web since 2007 and this is the first time I have some major problem with it. No problems with Avast and no errors if Dr.Web is uninstalled.
#2
Отправлено 17 Август 2009 - 17:14
#3
Отправлено 17 Август 2009 - 19:14
#4
Отправлено 17 Август 2009 - 20:40
Now I got this.. I made a fresh install in default directory. I used to have Dr.Web in C:/programs/drweb but now installed in E:/program files/drweb that is the OS partition. The scanner was running OK, no errors and it was about 87% and 150.000 files until it suddenly again was "Done!". Then I restarted the scanner. Then it said virus databases failed.
#5
Отправлено 18 Август 2009 - 00:17
I tried CureIt but I still got the same "corrupted" message.
#6
Отправлено 18 Август 2009 - 23:09
#7
Отправлено 19 Август 2009 - 16:19
#8
Отправлено 19 Август 2009 - 17:07
Then I just decided that this was enough, had a virus or not. I didn't notice anything suspicious with gmer, rootkit unhooker, hijackthis, and eset sys inspector. I believe it was some kind of driver conflict / other conflict with probable remnants of other security software.
Everything works now with the fresh OS. If problems re-appear then I might consider buying a new HDD.
#9
Отправлено 03 Сентябрь 2009 - 23:01
First Dr.Web crashed when scanning, the error from Windows event viewer:
20:19:00 Application Error
"Faulting application drweb32w.exe, version 5.0.6.8180, faulting module , version 0.0.0.0, fault address 0x00000000."
After this I re-started the scan and got:
20:27:51 ntfs
"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:."
My OS is installed on D:, not C:
Does anyone from the staff have any ideas / could help me? I attached the chkdsk log from C:
Прикрепленные файлы:
#10
Отправлено 05 Сентябрь 2009 - 16:17
He told me there is some weird problem with Dr.Web anti-rootkit module, is there anything I can do?
#11
Отправлено 05 Сентябрь 2009 - 16:42
I was helped by format_c at wilderssecurity and he told me to use "not_drop_shield" command when scanning and it worked. I was capable of making a full scan without any errors.
He told me there is some weird problem with Dr.Web anti-rootkit module, is there anything I can do?
please attach here, in a reply to me, your ntfs.sys driver. we want to see it
#12
Отправлено 05 Сентябрь 2009 - 17:39
#13
Отправлено 05 Сентябрь 2009 - 18:36
PM'd
thanx! the staff will see it soon
#14
Отправлено 05 Сентябрь 2009 - 23:41
#15 Guest_Artem Baranov_*
Отправлено 08 Сентябрь 2009 - 10:20
Great! If you need anything else, just ask.
Can you make logs of GMER & Rku tools?
#16
Отправлено 08 Сентябрь 2009 - 14:46
Great! If you need anything else, just ask.
Can you make logs of GMER & Rku tools?
Attached.
I tried the complete scan now without the not_drop_shield and it went through without problems. After this I restarted the scanner and then I got the "vdb failed". I did an update and after that the vdb was OK. I am now making another full scan to see if the ntfs problem/corruption appears.
Прикрепленные файлы:
#17
Отправлено 20 Октябрь 2009 - 19:35
However, Neoava Guard isn't developed anymore so this doesn't require any fixing or probably cannot be fixed. Case closed.
#18
Отправлено 01 Ноябрь 2009 - 19:01
I started the full scan today and yes .. here it goes again: ntfs errors with The file system structure on the disk is corrupt and unusable.. on both C: and D: drives.
I have used drw since september of 2007 but now had to switch for avast until this problem somehow "magically" gets fixed.
Читают тему: 0
0 пользователей, 0 гостей, 0 скрытых