Hi,
No matter what option I choose to boot, I always get a BSoD with ex code 0x0000007B (0xBA4D3528,0xC0000034,0x00000000,0x00000000), and it stops at aswRvrt.sys.
Can anybody please help?
Thanks
STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICEBasically you have a hard drive/boot sector problem
Do you have the recovery console on the computer ?
Hi,
Via Windows XP installation CD, yes, I can access to recovery console. (If it is what I’m thinking)
The error in the blue screen starts with that code, but it doesn’t say “INACCESSIBLE_BOOT_DEVICE”.
I forgot to tell, some virus appeared, and after clean it, Avast requested to reboot. After the reboot, it never booted again.
The computer belongs to my brother. So I can’t really have more details about the cause.
OK download the following programme to a USB
Then reboot to the recovery console command prompt and insert the USB
At the command prompt type the following :
notepad and press Enter.
The notepad opens. Under File menu select Open.
Select “Computer” and find your flash drive letter and close the notepad.
In the command window type e:\frst.exe and press Enter
Note: Replace letter e with the drive letter of your flash drive.
The tool will start to run.
When the tool opens click Yes to disclaimer.
https://dl.dropbox.com/u/73555776/FRST%20Start%20scan.gif
Press Scan button.
It will make a log (FRST.txt) on the flash drive. Please copy and paste it to your reply.
The recovery console is command line. I try do execute it by typing FRST.exe but it says “the command is not recognised” 
For the run command you need to put the drive location of the USB first i.e. e:\frst.exe if you do not put the drive letter first it will look on the C drive for it
Yes, I know how DOS commands.
I’m not used to work with the Windows XP recovery console, but I’m guessing it not capable to execute that .EXE file.
By the way, just to explain what I did, I booted with the Windows XP installation CD, then I choose “repair” in the menu I’m allowed also to choose to install.
A new CLI session is open and I have to choose the installation to repair from a list. In this case, it’s only one: 1 C:\windows
I choose “1”, than it asks for the administrator password, and after that I have a prompt.
I confirmed the path of the USB key with the file frst.exe, in this case, D:
I checked by typing “d:” and “dir”, it shows the file in list.
The FRST.exe is a windows 32bit executable file. I’m wondering if the recovery console only accept “old” DOS .EXE files.
Do you have any clue, or an alternative ?
Thanks again
No it works perfectly well from the windows recovery console
The alternative would be to run it from a PE environment
If you go to this thread http://forum.avast.com/index.php?topic=53253.0 and then scroll down to If you cannot Boot the computer
That will give instructions and links for how to download a PE environment
Definitely we were not talking about the same thing 
But I followed the instructions in the link, and here is the log.
By the way, that link is an excellent topic.
OK initially I will try a restore point
Download the attached fixlist.txt to the same location as FRST
Run FRST as before and press fix
On completion reboot to normal windows
It’s still the same
Attached is the fixlog generated after click on Fix
And another FRST.txt I ran again after tried to boot without success.
This will disable avast, although I do not believe it to be the problem
Download the attached fixlist.txt to the same location as FRST
Run FRST as before and press fix
Try a normal boot
Should I click on Scan prior to choose Fix ?
No go direct to the fix button
Nice, thanks. But it still rebooting after a blue screen
Now when I try to boot in safe mode, it stops at btkrnl.sys.
Again, is attached the Fixlog.txt and a new FRST.txt after trying to boot.
Any guess?
Only one thing left to try
From the reatogo desktop run a command prompt and type the following command :
chkdsk c: /r
I did that previously by plugging the HDD to another computer. But I will do as you say.
Still don’t boot
Unfortunately all that remains is a re-install of windows sorry
That happened right after a reboot required by Avast after running the steps to clear some virus.
Are you sure there isn’t anything else to try ?