Loading Profile...
Vista SP1 Blue Screens Scheduled Scans
My most recent scheduled scans have been resulting in Blue Screens - the last couple of times I watched the scan in progress, it started to fail a few minutes after it started while it was scanning for rootkits. I have Vista SP1 with the latest updates and latest updates of VIPRE installed as well.
I’m getting frustrated.
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thank you for you post. I am sorry to hear about the problem while scanning with Vipre. Please send an email to us here at Support@SunbeltSoftware.com with a brief description of this problem as well as your system info. Also please note if it is doing this only during deep, or quick scans, or both. Also please note if it is doing this with root-kit detection turned off, and if it is getting stuck on any one file in particular. Please make sure that you do not have any other AV security programs installed at the same time as Vipre, and that there are not any other programs running Active Protection at the same time Vipre AP is turned on. If you do have other Anti-Spyware security programs you may also try unchecking the option for scan within archives located under File>Settings>Scan Options Tab to see if this helps.
I’m happy
-
Inappropriate?Will email tomorrow...
It was happening during deep scans (which were the only kind I had scheduled.) I've always had root-kit detection turned on and the Blue Screens happen so fast, that I'm unable to tell if it happened on any one particular file.
As far as other AV security programs go, I don't have them, I solely use Sunbelt Software's stuff - nothing was pre-installed on this machine and Windows Defender has been disabled since I installed Vipre.
I’m undecided at this point.
-
Inappropriate?I am sorry to hear that the BSOD problem persists. This is usually caused by a conflicting driver. If you do not have any other security programs installed that may be conflicting please follow the instuctions below to create a crash dump so that we can better assist. Please reply to us via email at support@sunbeltsoftware.com with Vipre Ticket# 287185 in the subject line.
1. Install Debugging Tools for Windows 32-bit Version. This can be downloaded here:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.9.3.113.msi
2. Once you have the tools installed, open VIPRE and disable Active Protection. This is very important!
3. Now open a Command Prompt. Start > Run. Type in "cmd" and hit Ok.
4. Navigate to the install path of Debugging tools for windows. Type in "cd c:\Program Files\Debugging Tools for Windows (x86)" without the quotes.
5. Now type in "cscript ADPlus.vbs -crash -quiet -NoDumpOnFirst -pn SBAMSvc.exe -o c:\Vipretemp" without the quotes. This will hook the debugger into the service.
6. Now reproduce the error with VIPRE and wait for it to crash.
Once SBAMSvc.exe crashes the memory dump will be created in c:\Vipretemp.
7. Go into c:\Vipretemp, right click on the "Crash Mode" folder and select "Add to Zip"
8. To upload the files to our FTP server, go to Start > Run, then type in the below line.
ftp.sunbeltsoftware.com/supportlogs/consumer
A window should open up. Just drag and drop the “Crash Mode.zip” file into this window. It may take awhile to transfer as the file is going to be pretty large.
I’m confident
