Solved Possible BSOD'ing Virus

[JohnRB]

G'day,

I've been having a touch of trouble with a possible virus. What happens is, I boot up my laptop (Win7-64Bit), log in, and about 30 seconds later I get a BSOD.

Antiviral Software: None o)
OS: Windows 7 64Bit
BSOD Error: Not recorded
What am I doing: Logging in
Aproximate time from logging in to BSOD: 30s

What have I tried so far:

1. Booting up with a linux antivirus livecd to devirus windows
2. Entering Safe Mode and installing several anti virus software (then scanning with them, and booting up with them)

I've tried:

Kaspersky
Micro Trend
McAfee
Avira
AVG
(And a few others)

After logging in one of the times I got a small error popping up next to the clock saying that "VProtector.exe" was corrupted or something... However, on googling it, it seems that that itself is a virus, that's what makes me think it is one.

Thanks for your help,

John

 

[koolkat77]

Welcome to SevenForums.

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Perform a clean boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Uninstall all those antiviruses if you have them and make scans with the following:

-Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

-ESET online scanner

• Free Online Virus Scanner | ESET

MSE is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software:-

• 
  1. Microsoft Security Essentials - Free Antivirus for Windows
  2. Malwarebytes - Free
  3.http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

:warn: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Additionally, run the malicious software removal tool and WDO:

• http://www.sevenforums.com/tutorials/24076-malicious-software-removal-tool.html
• http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

Get into safe mode with networking by booting from http://www.sevenforums.com/tutorials/666-advanced-boot-options.html and post the files following http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[JohnRB]

Thanks for the reply

I am not able to use MSE because I can only log into safe mode. I've been doing all the work in safe mode. I've already tried Malwarebytes, and TDSSKiller. I'm also not able to run Windows Defender Offline because I'm in safe mode. And I'm not able to run MSRT because I am in safe mode.

I've attached some .zip files with the system information, along with a log made by the program outlined in the "How-To-Post-BSOD-Threads".

Thanks Again,

John

View attachment 244428
View attachment 244429

 

[JohnRB]

Hi, On crash I get the error:

0x000000000BE

(The number of 0's may not be right)

And it seems to have something to do with

bscsisda.sys

Thanks,

John

 

[JohnRB]

Fixed! It was a corrupted SD card, which had crashed it's driver while the driver was trying to boot.

 

[JohnRB]

I was not able to run scans while in safe mode, as I am not able to run MSE in safe mode. I have removed McAfee, however it was not the cause of the BSODs. Also, Maleware Bytes did run, however did not fix the issue (as it was not virus related).

Thanks for your help,

John