[Error] - SATA-Raid0 Bluescreen

[Dookie]

Hello.

I got a problem withmy new SATA-RAID.

I get a bluescreen booting Windows XP.

I catched it with my digicam:

http://img354.imageshack.us/img354/9974/bild0019ln.jpg

It's a Stop: 0x00000024 Error => so an ntfs file system problem, but i dont know why.

Checked both harddrives with Samsung hutil.exe and both are completely okay!

Hardware:

- Mainboards is Elitegroup NFORCE4-A939

- HDDs are both Samsung SP1614C (SATA1)

What I tried yet:

- I tried several BIOS-Versions (e.g. 1.0b, 1.1a, 1.1c), atm I have the newest (1.1c) installed for my BIOS.

- I tried several nForce-drivers (6.53, 6.70), atm I have the newest (6.70 WHQL-certificated, I think Raid-driver is 5.52 here) installed.

- As said I checked both HDDs with a Samsung HDD Tool an they are working well.

- The RAID0 is working fine, and I finally used an nLite-created WinXP_SP2-CD including nForce RAID-drivers (so I dont have to use F6 at install every time), but the same problem here:

WHEN THE INSTALLATION IS FINISHED, WINDOWS LOADS UP TO THE WIN LOGO SCREEN AN 4 SECONDS LATER THERE IS THE BSOD (see link above).

- When I install Windows with the 6.53 drivers, it fails writing the first Windows-file.

- When I'm booting with a Windows Live CD (used Bart's PE including the RAID-drivers of course) then I can use every drive INCLUDING THE RAID!!!!!!! So possibly it has something to do with booting from the raid?! If it's not the boot-drive => it works!!

- I also tried to remove all other drives but the RAID => no change

Well, I'm finally confused and got no more ideas.

So I'm glad for any constructive inspiration!

Thank u a lot!!!

Title Edited - Please follow new posting rules from now on.

--Zxian

[InTheWayBoy]

Have you tried installing XP with just one drive, not in an Array. That should at least help pinpoint if it's a problem with the RAID or something else.

And I know they are better as of late, but I don't trust ECS at all...ECS = PCChips = PCSh*ts

[nmX.Memnoch]

Also try installing it with a regular (read: non-nLited) XP CD. As suggested, do this with and without the RAID.

but I don't trust ECS at all...ECS = PCChips = PCSh*ts

True that.

[Dookie]

I started to try different WinXP CDs because it wasn't working.

So the nLite was my second step, not the first.

And I buyed a second similar HDD around christmas to speed up my system, before it was working very well on only one drive.

Another ideas? Buy a new Mainboard? :-/

[cluberti]

The file system corruption is coming from somewhere - if the drives both check out fine on their own, install Windows one at a time on each drive, then try again on a new array. If it works on each drive but not the array, you'll know where your problem lies. There are no really good solutions to these types of issues - it's all trial and error, and wherever the error is, that's the problem location or configuration .

[Dookie]

I'm nearly sure that Windows-installation will work fine on each drive (I used one of the drives as main-drive for WinXP before without any issues).

Do you think it will work if I install Windows on each drive an then on the RAID again? These are 3 Win-Installation, costing nearly 3 hours of time, and I'm afraid that this won't work, resulting in a waste of time...

but I have to try if you and others are sure it could solve all my SATA-RAID problems...

what do you think?

++++++++++++++

UPDATE: I tried the nForce4 7.13 WHQL driver, which seems to include an earlier RAID-driver-version: 5.35 (instead of 5.52 in the 6.70 package) if I'm right... don't know why...?!

And I also used an unaltered version of WinXP (without SP2) for this by the way.

The results: A fresh installation on a fresh RAID threw a very early bluescreen with another error-message:

STOP 0x0000007B (meaning INACCESSIBLE_BOOT_DEVICE).

I ask myself if the guys are too stupid to code working drivers for the hardware, or if it's all my fault using them.

Any ideas?

Edited December 29, 2005 by Dookie

[InTheWayBoy]

If everything was working fine before the HD, then the first thing to verify is the new HD. First off, what make and model are your drives? Both original and new. Second, since you know that the original one works fine, disconnect that from the system and try to load windows on the new one. If the new HD is bad, it should display similar errors when opperating on its own. You could also try and run the manufacturers diagnostic tools.

[Dookie]

The hutil.exe (samsung diagnostic tool) went fine for both hdds (in hours of intensive testing) :-/

Now im trying to do a low level format with the same tool, possibly this will solve problems/rests of earlier installations (mbr stuff).

I read about that possibility.

Stay tuned

[Sonic]

nForce 7.xx are for Intel ... 6.xx are for AMD ...

And both version doesn't update in same time ...

Edited December 29, 2005 by sonic

[Dookie]

Oh ok, i c.

Thank u for that explanation, sonic!

I went to this page:

http://www.computerbase.de/downloads/treib...nforce-treiber/

to look for other versions of nForce drivers, and there is a 7.13 (nForce 4) and a 7.15 (nForce 4 Intel Edition).

So I thought 7.13 could be AMD, but I was only a mistake then.

Well, a low level format didn't heal my RAID yesterday

[nmX.Memnoch]

How long did you have the first drive before you bought the second drive? It could be an incompatibility of the firmware versions on the drives since you purchased them at seperate times. It's generally advised to purchase the same make and model of drives for RAID setups, and purchase them at the same time.