Most likely something went wrong during a (automatic) update while I was rendering a video-clip. During the rendering (I wasn’t watching the process), the computer crashed and when I came back there was the BSOD.
I ran above test/repair/ options several times, but it never got better : crash on aswRvrt.sys
I renamed aswBoot.exe to aswBoot.xxx to kinda prevent AVAST to start, but same result
So, my question is :
How can I stop AVAST to start (even in Safe Mode)
Please remember that I CAN NOT get into windows. So I’m looking for some kinda command line code, or even a manual Registry edit.
I’m using WIN7 Ultimate on a Gigabyte 99FX mobo with AMD 8-core. My bootdisk is a 60GB SSD
To everyone who tries to help me : THANKS IN ADVANCE !!!
Well, I learned alot since this problem happened (last week)
Yes of course I have ! but then I would have to reinstall all my progs, no ?
If like you say that aswRvrt is the last succesfully loaded file … then how do I find out wich one is the next file ?
Agree, maybe this is not the right place to ask … but still …
Oh and btw : Thanks ALOT for your concern and time !!!
to boot w/o avast
in recovery mode goto
in C:\Windows\Sysnative\drivers
and rename all files “asw*.sys” to “asw*.sys_”
that will prevent avast init it’s drivers
if you successfully boot to Windows afterward,
Please check for the corresponding minidump files (in C:\Windows\Minidump) and upload them to ftp://ftp.avast.com/incoming
this did it ! I already did an sfc scan before, but probably used the wrong syntax.
this one did it :
sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=d:\Windows
Now it said that it found corrupt files, but was unable to fix some of them …
You can guess what my next question is … :
How do I find wich files are corrupt ? I’ve been browsing in the CBS file, but I can’t find anything that kinda relates to unfixable files…
Nevertheless I rebooted, but no luck… So I started Startup repair again but “Windows cannot repair this computer automaticly”. I looked in the repair details, but I didn’t see anything else but 0x0’s. At the end, however, the repair details stopped abruptly. The last lines are:
[b]Test performed
Name : Boot status test
Result: Completely succesfully, Error code 0x0
Time taken = 0ms
OK. after renaming the asw*.sys files, Safe mode stopped at the one before … so it is definatly the “next” service that makes the computer stop and reboot …
How do I find this “next” service ?
You know thats an excellent question…I actually dont know where the log ends up when running from disc but judging from the dates on the log you posted its not that one.
Edit: I found one guy that said you can set the variable before running sfc like this: set WINDOWS_TRACING_LOGFILE=C:\TEMP\CBS.log