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[b]aswRvrt.sys[/b]
C:\Windows\System32\Drivers\aswSnx.sys
C:\Windows\System32\Drivers\aswSP.sys
C:\Windows\System32\Drivers\aswTdi.sys
C:\Windows\System32\Drivers[b]aswVmm.sys[/b]

…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 ??.