Let me summarize the problem, because I don't think everyone understands what happens...and what I have done to fix it.
The system, in both Safe and Normal mode, loads part of the way, then starts thrashing the hard drive.
I loaded to a Bootlog system.
When I inspect the Bootlog file, the system loads normally in both modes until it encounters the following commands, after which it stops loading drivers, then it loads a driver, then it stops loading drivers, ad nauseum in a loop:
Loaded driver aswVmm.sys
Loaded driver aswRvrt.sys
Loaded driver \??\C:\WINDOWS\system32\drivers\aswFW.sys
Avast has been uninstalled and the default Windows registry files were copied from the Repair folder. I also did a manual search for all ASW files and there are none remaining on the drive.
Therefore, it's clearly not a registry problem, as the system does the same thing when a fresh registry is installed.
ChkDsk has been run, repairs have been run from the original Windows CD, the system has been restored to four different backup points, and the same drivers still try to load.
I am baffled as to exactly where these loading instructions are coming from. A fresh registry from the initial Windows installation should not allow this to happen. What other file(s) instruct Windows as to which drivers should be loaded? And why should these drivers be loading during Safe Mode at all?
OK....so clearly Avast is still trying to "load" something and there are remnants of the install. How & What did you use to uninstall if you can't boot to Safe Mode or Windows ?
I think the next steps should be for Essexboy to step you thru using FRST. He'll show you how to create bootable USB or CD with it and he can blow away all remainders of Avast. Also, just reaching for items but in
http://forum.avast.com/index.php?topic=144233.0 the guy mentions
"to get a reboot I renamed the file aswSP.sys (eg to aswSP.sys.bak) that is in the folder windows/system32/drivers". Seems you can get to command prompt somehow since you said you have looked for Avast files ? If so, check for this one.
Also, hopefully Essexboy will chime in on FRST but looking at one of his "example" FRST logs here are some other locations of Avast files he was getting rid of in FRST. I only post them for you to see the path to look for..........if you find any I would rename, with .bak, not delete.
Note, you can see the
drivers below you outline in your boot log......
C:\Program Files\AVAST Software\Avast\AvastSvc.exe
C:\Windows\System32\Drivers\aswFsBlk.sys
C:\Windows\system32\drivers\aswMonFlt.sys
C:\Windows\System32\Drivers\aswrdr2.sys
C:\Windows\System32\Drivers\
aswRvrt.sysC:\Windows\System32\Drivers\aswSnx.sys
C:\Windows\System32\Drivers\aswSP.sys
C:\Windows\System32\Drivers\aswTdi.sys
C:\Windows\System32\Drivers\
aswVmm.sys ...............for the below statement from..........
Loaded driver \??\C:\WINDOWS\system32\drivers\aswFW.sys
..........obviously look for the aswFW.sys as well.
FYI, you mention about "partition" but I'm only guessing that Avast uses a "hidden/virtual" partition to accomplish things.
Obviously, I am not expert nor have any official insight on how/what Avast does but just a guess on why you see the \??\.