"Señor Apellido" <> wrote in message
news:FTmKa.25087$. ..
> Nom wrote:
> > "Señor Apellido" <> wrote in message
> > news:g5bKa.23698$...
> >
> >>Señor Apellido wrote:
> >>
> >>>Hardware: ASUS A7N8X Motherboard (1004 Bios), Seagate 80GB SATA Hard
> >>>Drive, high quality ram, case, ps.
> >>>
> >>>OS: Windows XP Pro (1.0.0.22 SiI3112A SATA drivers)
> >>>
> >>>Problem: Hard drive data corruption (NTFS boot drive).
> >>>
> >>>Symptoms: Windows XP Pro reboots during bootup sequence. Drive will
> >>>cause any computer that attempts to read from partition to crash.
> >>>Recovery Console BSOD with a STOP 0x00000024.
> >>>
> >>>My Theory: Bad SATA drivers or bad SATA controller (SiI3112A).
> >>>
> >>>Solution: Swap motherboard and SATA drive with IDE drive. The
> >>>motherboard (except for SATA drivers) might have been fine, but ASUS
> >>>does not provide enough information to determine this.
> >>>
> >>>Notes: Corrupt (primary) partition was lost. Seagate's bootable
utility
> >>>cd exits to a DOS prompt after loading SATA drivers, so you can delete
> >>>the bad partition using fdisk. Do not try to get partition information
> >>>of bad parition using fdisk (http://www.23cc.com/free-fdisk/). After
> >>>bad partition was deleted, drive was recognized and accessible as a
> >>>second disk.
> >>>
> >>>NTFSDOS can be used to access an NTFS partition from DOS
> >>>(http://www.sysinternals.com/ntw2k/fr...NTFSDOS.shtml).
> >>>
> >>>Conclusion: This is the first problem I have had with ASUS, and I might
> >>>buy another motherboard from them. I would never purchase another
> >>>product that includes hardware or software from Silicon Image.
> >>>
> >>
> >>For what it's worth, Silicon Image claims that the problem is with the
> >>ASUS BIOS.
> >
> >
> > It is, and the latest BIOS fixes it.
> >
> >
> >>I should not have been able to purchase a new motherboard
> >>with a known bug this severe.
> >
> >
> > Er, the bug is fixed.
> >
> >
> The corruption didn't crash the system until two weeks ago. The latest
> BIOS wasn't available when I purchased the motherboard almost a month ago.
Same situation here.
But now the problem is fixed, so don't worry about it