virus possibly related to svchost.exe

Thanks for providing the report.

Must let you know that reading device driver logs is definitely not my thing.

With that said, there appears to be a group of Hardware Initiated calls on the setupapi.dev.log related to
some drivers.

You may want to post your concerns and the setupapi.dev.log in the Drivers forum:
Drivers - Windows 7 Help Forums

Someone there may be able to provide some guidance on this issue.

Hold off for a day or so!

After posting, thought of an advisor who is well qualified to deal with these types of issues (I think), and asked for him to take a look at the log posted.

He is in England, so there is a time difference involved.

Hopefully, he will be here sometime tomorrow.

Hi guys,

These driver installation logs aren't really my forte, but I've had to deal with them in the past so have a little experience with them. The good news is that I can't see any unrepaired errors in your log, but the bad news is that the problem must lie elsewhere. Let's get an up to date FRST log and see what things look like there:

Farbar Recovery Scan Tool (FRST)

1. Run FRST.
2. Click Scan to start FRST.
3. When FRST finishes scanning, a log, FRST.txt, will open.
4. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this log into your next post please.

Also, whilst we review this, I would like you to follow these instructions:

How to perform a clean boot in Windows 8.1, Windows 8, Windows 7, or Windows Vista

Click on this to expand the instructions:

How to determine what is causing the problem by performing a clean boot

Then click on:

Windows 7 and Windows Vista

Then, when you have finished narrowing down the culprit (if you do find one), revert your startup files to their normal values by following the instructions under:

How to reset the computer to start as usual after clean boot troubleshooting

Tom

What are your thoughts on these cottonball/Jacee? I'm not allowed to remove any malware yet, but these don't look very good to me:

S3 Asynrsrvbfr;
S1 aleglkvm; \??\C:\Windows\system32\drivers\aleglkvm.sys [x]
S1 bhszzscg; \??\C:\Windows\system32\drivers\bhszzscg.sys [x]
S1 fbbhzhmo; \??\C:\Windows\system32\drivers\fbbhzhmo.sys [x]
S1 fizrehbq; \??\C:\Windows\system32\drivers\fizrehbq.sys [x]
S1 tgefigxr; \??\C:\Windows\system32\drivers\tgefigxr.sys [x]
S1 vtizivqe; \??\C:\Windows\system32\drivers\vtizivqe.sys [x]
S1 yoyloawn; \??\C:\Windows\system32\drivers\yoyloawn.sys [x]

Tom

Let's nuke those drivers/service in Post #37, and see if it makes any difference...

Please open notepad (Start > All Programs > Accessories > Notepad)
Copy the entire contents inside the code box below (Do not copy the word 'code') to Notepad.
Save it to the Desktop, and name it: fixlist.txt

Code:

start
S3 Asynrsrvbfr; 
S1 aleglkvm; \??\C:\Windows\system32\drivers\aleglkvm.sys [x]
S1 bhszzscg; \??\C:\Windows\system32\drivers\bhszzscg.sys [x]
S1 fbbhzhmo; \??\C:\Windows\system32\drivers\fbbhzhmo.sys [x]
S1 fizrehbq; \??\C:\Windows\system32\drivers\fizrehbq.sys [x]
S1 tgefigxr; \??\C:\Windows\system32\drivers\tgefigxr.sys [x]
S1 vtizivqe; \??\C:\Windows\system32\drivers\vtizivqe.sys [x]
S1 yoyloawn; \??\C:\Windows\system32\drivers\yoyloawn.sys [x]
C:\Users\Steve\AppData\Local\Temp\NVI2_29.DLL
end

NOTICE: This script is written specifically for this computer!!!
Running this on another computer may cause damage to the Operating System.

Now, please run FRST, and press the Fix button, just once, and wait.

When done, the tool creates a report on the Desktop called: Fixlog.txt
Please post the Fixlog.txt in your reply.