[SOLVED] After upgrading Avast error c000021a

After upgrading Avast I reboot and the PC crash at logon with error
STOP: c000021a (Fatal System Error). The Windows Logon
Process System process terminated unexpectedly with a
status of 0xc00000080 (0x0000000 0x00000000). The system
has been shut down
I can’t go also in safe mode (a similar error) wath can I do ?
Maybe Avast installed some driver in the last release ?

yours

Alberto

Are you using XP, if so do a search on the code
Seems to be a known problem and not dependent on your AV

Yes I use XP,
but I did a search, the rare people that received this error
(complete with 0xc00000080) seems to solve with a reistallation,
I think it depend from the AV because the error appeared at reboot after
upgrading the AV, and I saw that the upgrading downloaded a SYS file.
I don’t do anything else in this session.

yours

Alberto

Or repair
From the look of the Microsoft KB’s on the subject it isn’t so rare
Have you search Technet

I tried from the CD recovery console, but the LAST KNOWN GOOD CONFIGURATION
don’t work, I can try the recovery of the registry as explained in he technet,
wayh do you think ?

Alberto

What version of XP are you running, especially the SP
XP dosn’t back up all of the hives, so whilst it shouldn’t make things worse…

please follow these instructions

please upload Your minidump to so Avast staff can analyze it
to
ftp.avast.com/incoming

(files are usually located in C:\Windows\Minidump
it’s .dmp file from time of the BSOD

Dwarden
The OP can’t get past logon

he should try boot into safe mode / safe mode with networking and uninstall Avast there then

and ofcourse upload the dumps if any present

(i dont think renaming the avast asw*.sys files to e.g. asw*.sys_disabled in Windows XP will work w/o issue)

That won’t exactly work either:

Use a live CD and copy the file to another medium
It may help, but…

or usage of last known working configuration tho that might be tricky

thanks for replay but in recovery console the last working configuration don’t
do anything, I already try it

another thing is the asw*.sys the only file loaded by the registry ?

yours

Alberto

up

another thing is the asw*.sys the only file loaded by the registry ?

I think I am losing it :-[
I do not understand the quoted above
If you cannot get access to Windows - no logon, no safe mode etc how can you ‘see’ what is loaded by registry

I have a utility (ERD Commander)
that permits to runa live version of windows and permit to access to the registry,

alberto

he can disable the files from loading by renaming then (but to be fair i don’t remember if it works well enough in XP)

e.g. using the recovery mode or booting into other OS etc.

the answer about is asw*.sys
there are multiple files not one, * means any text so you need disable these
if someone has WindowsXP by hand You may help by telling what all drivers are loaded on boot by Avast v6

I use the v5 last update

yours

Alberto

no suggestion ?

digging in internet I found that some virus (ex. bagle) disabled the Safe Mode !
So it is possible that a virus crashes avast and as conseguence crash also the logo ?

Alberto