aswRvrt.sys boot problem.

[essexboy]

No it is just that the last driver loaded was one of Avasts...  Google mup.sys for systems without Avast  and you will find that it affects all system from XP on

[REDACTED]

Can you maybe help me understand what happened here then, one day everything was fine and next day my pc wont boot and requires a reinstall. Im not looking to place blame im just trying to understand what happened, like i said in my op a google search brought me here so i assumed it was an issue with avast, am i wrong in assuming so?

[davexnet]

Could that CHKDSK above be in the wrong partition?  It's only 30GB, 15 files.

I'm just trying to understand... If that is the OS partition, where are all the files?

[essexboy]

The file locations are recorded on the MFT http://ntfs.com/ntfs-mft.htm

Each file on an NTFS volume is represented by a record in a special file called the master file table (MFT). NTFS reserves the first 16 records of the table for special information.

The first record of this table describes the master file table itself, followed by a MFT mirror record.

If the first MFT record is corrupted, NTFS reads the second record to find the MFT mirror file, whose first record is identical to the first record of the MFT. The locations of the data segments for both the MFT and MFT mirror file are recorded in the boot sector.

If that is corrupt then there is no location information for the location on the disc of the boot files
Chkdsk if it finds the MFT corrupt will try to find the mirror (backup) copy and use that, if that is corrupt then it might as well be an empty disc

Disk: 0 (Size: 29.8 GB) (Disk ID: 5268F47E)
Partition 1: (Active) - (Size=29.8 GB) - (Type=07 NTFS)

This is the only disc that FRST can see

Can you maybe help me understand what happened here then, one day everything was fine and next day my pc wont boot and requires a reinstall. Im not looking to place blame im just trying to understand what happened, like i said in my op a google search brought me here so i assumed it was an issue with avast, am i wrong in assuming so?

Not even MS has been able to determine what causes this error.  There are many different ways of fixing this from resetting the BIOS to read from SATA or IDE (dependant on the current setting) To removing any low level installed programmes via chkdsk.  But, the MS answer is always re-install 

[REDACTED]

ok np. thanks for trying to help. my friend did a reinstall and im back up and running again.

[essexboy]

Sorry we could not resolve this any other way

[davexnet]

The file locations are recorded on the MFT http://ntfs.com/ntfs-mft.htm

Each file on an NTFS volume is represented by a record in a special file called the master file table (MFT). NTFS reserves the first 16 records of the table for special information.

The first record of this table describes the master file table itself, followed by a MFT mirror record.

If the first MFT record is corrupted, NTFS reads the second record to find the MFT mirror file, whose first record is identical to the first record of the MFT. The locations of the data segments for both the MFT and MFT mirror file are recorded in the boot sector.

If that is corrupt then there is no location information for the location on the disc of the boot files
Chkdsk if it finds the MFT corrupt will try to find the mirror (backup) copy and use that, if that is corrupt then it might as well be an empty disc

Disk: 0 (Size: 29.8 GB) (Disk ID: 5268F47E)
Partition 1: (Active) - (Size=29.8 GB) - (Type=07 NTFS)

This is the only disc that FRST can see

Can you maybe help me understand what happened here then, one day everything was fine and next day my pc wont boot and requires a reinstall. Im not looking to place blame im just trying to understand what happened, like i said in my op a google search brought me here so i assumed it was an issue with avast, am i wrong in assuming so?

Not even MS has been able to determine what causes this error.  There are many different ways of fixing this from resetting the BIOS to read from SATA or IDE (dependant on the current setting) To removing any low level installed programmes via chkdsk.  But, the MS answer is always re-install

Thanks for the info.  The thing that bothers me though is that CHKDSK says it "found no problems"