Machine Won't Boot -- Usual Problem With aswRvrt.sys

Viruses and worms
1

This problem has come up before, and been discussed extensively, namely, the machine won’t boot into normal or safe mode, but hangs up on aswRvrt.sys, and then restarts the bios boot strap process.

However, the fix appears to be individualized. Per the instructions on another thread, I’ve booted the machine using a reatogo boot CD, and ran FRST.exe from the flash drive. Attached are the results of that scan.

Please advise on what to do next. Thanks for the help.

2

Lets try this first

Download the attached fixlist.txt to the same location as FRST
Run FRST as before and press fix
On completion try a reboot

3

Thanks for the rapid response, Essexboy. I did what you said to do, but it didn’t work; same results.

However, I might have inadvertently damaged the repair process. You said to reboot, but didn’t say how to reboot; I tried “last good configuration”–could that have undone the fix from FRST.exe? I then tried “Safe Mode”, where it again snagged on aswRvrt.sys, and then went back to the bootstrap loader.

Should I re-apply the fixlist.txt, and then do a normal boot up?

4

Yes re-run the fix and try a normal boot… If it fails could you run FRST again please and attach the log. I will then see what other options are available

5

Essexboy, your advice and assistance appears to have fixed this problem. http://forum.avast.com/Smileys/default/smiley.gif You really know your stuff!

However, I do have a few questions, if you don’t mind:

  1. So, what was the problem, and how did that FRST fix correct it? How do you know what FRST fix to recommend? It there a secret manual for FRST?
  2. I set the computer to do a boot scan to check for more/other viruses. I rebooted, and it is doing that scan now. Do you see any problems doing this boot scan? What is the difference between a full scan and a boot scan?
  3. From some of the other threads dealing with this problem, I thought it might be a virus, so I decided to do a full scan on my desktop computer; Avast found some viruses on that one, and recommended that I do a boot scan, which I did, and it found more (or the same ones?). In the boot scan, I deleted some, put some in the chest, and ignored some. Afterward, I did an individual scan of the ignored files, and Avast reported no threat found! Why do some scans indicate there are threats, and others don’t?

After the boot scan, I’ll try a Safe Mode boot and test the other user accounts, etc.; but I’m expecting for all that to work. If not, I’ll let you know.

Thanks again for the help. Do you have a tip jar or something?

6
  1. HKU\Thomas E. Sandidge.…\CurrentVersion\Windows: [Load] C:\TCWIN45\PIPELINE\remind.exe
  2. 2013-11-19 17:45 - 2013-11-19 17:45 - 00000000 ____D C:\Documents and Settings\Thomas E. Sandidge\Application Data\aartemis

The one I believe was causing the problem is 1. as winload is only used in XP and is a known hijack point, that if incorrectly set will stop windows from fully loading
The second element is just a browser hijacker

There is a basic tutorial here http://www.geekstogo.com/forum/topic/335081-frst-tutorial-how-to-use-farbar-recovery-scan-tool/ but it should be used with caution as this tool does not mess about :slight_smile:

A boot scan automatically checks for unwanted programmes like adware whereas a standard scan will not, unless you tell it to

7

Thanks for the rapid response. What you identify as the problem is interesting; the Turbo C remind program has been there for years without creating a problem.

Should I be concerned about what you identify as a browser hijacker?

The computer is still running the boot scan–it’s old and slow!

I’ll take a look at that tutorial.

Keep this up and you’ll graduate from being Essexboy to Essexman. http://forum.avast.com/Smileys/default/wink.gif

8

If you are experiencing no browsing problems then you should be OK

Had you recently updated the TurboC programme

9

Firefox 21 would often crash, and require a restart. I think I have Firefox 25*, and have not had any problems.

No upgrade to Turbo C. That’s Borland’s “home version” C compiler from Window 3.1.

  • I know I updated one machine, and I think both, but have to verify.
10

I wonder if Avast tried to fix the winload entry and failed to do it properly, intriguing

11

Essexboy, some good news, some bad news, and some (hopefully) better news. The bad news is the problem re-occurred. The good news is the same FRST fix you previously gave me corrected the the problem.

The better news is I think I’ve discovered the cause. Stepping back for a moment, shortly after buying the computer, one of the two built-in USB ports broke–probably cheap plastic. So, for years, I’ve used the one good port, and a USB hub. Apparently, when recently operating without the hub, I accidentally plugged a USB device (mouse or flash drive) into the broken port–and that “did something”. I don’t know why “the something” did this, or how it could be consistent in results, nor did this damage the USB device, but that appears to be the case. (I’ve taped over the bad port to make sure I don’t inadvertently plug into the wrong port again.)

Sorry for the long post, but I’m telling you this in the hope that this might help you to help others with this same problem. It might not be a problem with Avast, or a virus; it might be an odd hardware glitch. An FRST fix may still be necessary, but you could alert them to be careful with USB devices and ports to prevent a repeat.

Thanks again for all your help.

12

Thank you very much for the additional info, it may come in useful as another area to check

13

You’re welcome for the information, and thanks for all your help.

I guess that takes care of things, so no need for you to reply further.