• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Asus A8N-E & SATA Corruption

blurp

Member
I found that when I increase the FSB in the BIOS to ONLY 201 from 200, I always get ERRORS in the 'eventviewer' when transfering a file from my SATA drive to another driver and most often, my computer freezes. It does not matter if I choose to lock the PCI Bus.

What is more surprising is those ERRORS do not append when i overclock in Windows either with Clockgen or nTune. Then I can reach a Prime and Memtest stable overclock of FSB 226. I don't want to go higher because the PCI lock doesn't work when I have to leave the FSB to 200 in the BIOS...

This appends all the time no mather what BIOS version I use. I tried to Clear the BIOS, to update the BIOS in Windows, DOS and with the built-in BIOS Updater. I tried multiple versions of nForce drivers and also without drivers. I changed the SATA ports and cables: No GO.

Does anybody have a clue ? Do I have a faulty Motherboard ?


Asus A8N-E 3500 + Venice
eVGA 6800GT

 
Specifically - have you tried uninstalling the nvidia ATA disk controllers and replacing them with Microsoft?

That fixed my SATA errors in the event log.

Actually even better was ditching the ASUS A8N-SLI and getting a DFI UltraD last week, but that is another story....
 
I did completly remove the nVidia ATA drivers without results. I have a seagate and disabled the NCQ. Didn't help.

I know the DFI would be a better Mobo... It was my first pick but then I switched to Asus because it was my very first build and DFI-Street forums did not recommend this board as a first build. Wrong move I guess.
 
I received a new Asus A8N-E MoBo. Installed ... Works fine for far. So I guess my board was defective. More testing is needed though.
 
Back
Top