![]() ![]()
Well, I have done several scans last week, all of them in full: with CureIt! to begin with, of course, and it turned out to be that my system was infected with that Backdoor.Tdss.565 rootkit then. Why don't you make a scan with live CD and post results here. #Dr.web cureit 6.00.2.05140 free download windows#Perhaps some Windows settings do prevent all of this?Īre we sure you are not infected? Have you done a complete scan on your system with security softwares or online scanners? The Dump file field stayed blank, even when this had been run as Administrator by me, and even after the system had been rebooted. But for security (or even emergency) and back-up reasons, burning it to a CD is a good idea, of course. Remember that I still am able to run CureIt! in Windows 7's Safe Mode, and without problems. iso, and maybe I will burn this to a CD, if needed. #Dr.web cureit 6.00.2.05140 free download windows 7#That was exactly what I expected to happen, because a couple of days ago, I already ran a memory test with the built-in facility of Windows 7 for this purpose, and also there there turned out to be no memory errors. "***** Pass complete, no errors, press Esc to exit *****". 4.10: latest version), and this was what it exited with: ![]() I have run the memory test of Memtest 86 (v. Perhaps some Windows settings do prevent all of this? *.dmp file still is not there (nor anywhere) at my system I had even tried to set the settings for this in Startup and Recovery earlier this day, in the same screen picture as you forwarded to this thread in your latest posting.īut then, and just now, when I was trying to set Startup and Recovery the way that you have advised me to, this just would not succeed, and the Dump file field stayed blank, even when this had been run as Administrator by me, and even after the system had been rebooted.Maybe, CureIt! could be adjusted in future releases to tackle this specific problem? I tend to give up, things are becoming too complicated to me now. As a result, I had to use Windows 7's Setup DVD to recover the system by means of its latest System Recovery Point. ![]() At (normal) shutdown of the system, last evening, nothing was or went wrong. Or even, but I am not sure whether this was caused by this CureIt!/Online Armor conflict, system crashing all the time after new start ups after about ten hours (this morning), though the system itself could be started up. To add to this problem, also the system would crash sometimes if CureIt! had been running with Online Armor disabled (then CureIt! would run without a problem, in both of its modes), but then would crash as yet at the moment I would try to enable this firewall again. But, in every combination of settings and CureIt! modes, system crash occurred, at least once. So, I have tried several combinations of the above, and, most of the times the system still would crash and sometimes it would not, and within both of CureIt!'s modes. In the Protection section: ticked the Protect from termination and Protect from suspend settings. In the Permissions section: set to Allowed/set to Ask and vice versa all of these settings and ![]() In the Security section: ticked/unticked Installer Regretfully this was of no avail either, after this having set, system crashes kept coming up with Online Armor have read and watched the Online Armor document and videos, and, after having created a Program rule for it, in Advanced Options I have changed/unchanged and ticked/unticked several settings for the CureIt! file: Can also try to add exception for C:\Users\UserNameAppData\Local\Temp\ folder in online armor settings, temporarily. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |