The configuration listed here is causing parity errors and system lockups on this machine.
Board and drives pass all tests and seem to work OK in IDE mode, but configuring the Intel Raid controller for RAID mode causes the drives to eventually fail when running benchmarks or performing large file copies between drives. This has occured with multple Intel driver versions and board BIOS versions.
Anyone else reporting this issue or know any resolutions?
MOBO = ASUS P5E3 Premium WiFi
BIOS used = 0401 or 0505
CPU = Intel Quad QX9770
Memory = OCZ Platinum-1600 2x2GB
OS = Vista x64 SP1
Drives = 2x raid 0 arrays 4 x 300gb WD velociraptors
Intel Storage Matrix Controller ver 8.2.0.1001 (June 2008)

Errors reported in windows log files include
a) parity error on device 0 (iastor.sys raid driver)
b) iastor.sys has failed to respond in the time allocated

The intel raid monitoring app will eventually report that one of the drives in each array is failing.
After drive corruption, wiping the drives (writing zero to ALL sectors), allows them to be reinitialized and reformatted.

Running IDE mode now with no problems.
Any suggestions appreciated.
Wait for new drivers? Give up on MOBO raid and buy a dedicated controller?

I have also problems here with my velociraptors on the ASUS P5E3 Premium Wifi. I am running 2 velociraptors in raid0 as a windows bootdevice.

I cant say anything about parity errors or log files, because i have no understanding of them.
Anyway, after some time of use (1 week after fresh install) my system will sometimes become unresponsive and i need to reboot. After this has happend a few times one of my drives will give a error on the raid status screen at bootup. The system keeps booting from de raid-device but the next week or sometime later the system wont boot anymore as the array seems to have fallen appart and the system doesnt recognize the drives as being a raid device. (no bootdevice found)

My thoughts about what could cause the problems:
-Memory issures
-One bad diskdrive, (badblocks or something (parity erros??))
-Bad raid controller (Saw a intel report about some controllers with bad ram, will check bacjk to that)
-Bad mobo some how runs drives in IDE mode at bootup (One time the array showed broken at the raid status screen at bootup and the system gave mesage "no bootdevice found". Somehow after a second reboot the raid status screen showed the proper raid setup again, and booted again. Aint the weird???)
-Bad serial interface cables. These things are realy crapy some times and get loose quiet easily. Have change them a couple of times but the error status keep comming back.

I have not that good computer understanding so the things that can cause these problems my be impossible, anyhow i just dont know realy....

Does someone know a program to check if a disk is bad?


Lian Li PC-V2100BplusII
Enermax Galaxy 1000W
ASUS P5E3 Premium Wifi-AP @n
Intel Q9450
Corsair TWINX4096-1600C7DHXIN ver3.1
MSI NX8800GTS 320MB DDR3
2x WD VelociRaptor Riad 0
Vista Ultimate 64bit OEM