serbiaNem
12-02-2008, 02:50 AM
I was hoping one of the geniuses here could help me out with a problem I'm having.
I just built a new computer with the following specs:
Q6600
Asus P5Q Pro
1x Samsung 22x SATA on Intel Controller
1x WD Raptor 150 on Intel
2x Hitachi 1TB on Intel
2x Maxtor 250GB on Intel
1x Seagate 300GB on Marvell
AMD 4830
Antec 1kW PSU
Here is the issue.. When the SATA setting is set to IDE in the bios, all is well and windows installs perfectly and detects all of the drives, even on the Marvell controller after drivers are installed.
I want to keep my single raptor as my OS drive, but I want to raid 0 my two Hitachi drives like I had them before while also raid 0ing my Maxtors. So I go into the bios and set SATA to raid. I configure the Intel bios to raid 0 the hitachi drives and raid 1 the maxtors.
I go to install windows x64 sp1 (original disc) and i get a blue screen right at Setup is entering windows at the very beginning. The first stop error is 0x0000007B. I even went and put my floppy in to try and load the raid drivers, same issue after loading the drivers.
So I disconnect everything other than my DVD (sata, could this be a problem?).. still the blue screen. I try switching up which sata port it's on.. nothing. I try updating my bios to the latest... nothing... I check if 32-bit has the same problem.... it does.. I try disabling the Marvell controller... nothing. I try taking out one stick of ram... nothing. I try putting the 8-pin power connector instead of the 4-pin.... nothing
But changing the setting back to IDE fixes the problem immediately. What could possibly be going wrong with the RAID configuration?
I'm really at my wit's end here. Is this just some obscure windows glitch? Could slipstreaming a new service pack fix the problem? You have no idea the gratitude you will get from me if you can find me a solution.
QUICK UPDATE: A bootleg version of x64 with SP2 does the same thing.
I just built a new computer with the following specs:
Q6600
Asus P5Q Pro
1x Samsung 22x SATA on Intel Controller
1x WD Raptor 150 on Intel
2x Hitachi 1TB on Intel
2x Maxtor 250GB on Intel
1x Seagate 300GB on Marvell
AMD 4830
Antec 1kW PSU
Here is the issue.. When the SATA setting is set to IDE in the bios, all is well and windows installs perfectly and detects all of the drives, even on the Marvell controller after drivers are installed.
I want to keep my single raptor as my OS drive, but I want to raid 0 my two Hitachi drives like I had them before while also raid 0ing my Maxtors. So I go into the bios and set SATA to raid. I configure the Intel bios to raid 0 the hitachi drives and raid 1 the maxtors.
I go to install windows x64 sp1 (original disc) and i get a blue screen right at Setup is entering windows at the very beginning. The first stop error is 0x0000007B. I even went and put my floppy in to try and load the raid drivers, same issue after loading the drivers.
So I disconnect everything other than my DVD (sata, could this be a problem?).. still the blue screen. I try switching up which sata port it's on.. nothing. I try updating my bios to the latest... nothing... I check if 32-bit has the same problem.... it does.. I try disabling the Marvell controller... nothing. I try taking out one stick of ram... nothing. I try putting the 8-pin power connector instead of the 4-pin.... nothing
But changing the setting back to IDE fixes the problem immediately. What could possibly be going wrong with the RAID configuration?
I'm really at my wit's end here. Is this just some obscure windows glitch? Could slipstreaming a new service pack fix the problem? You have no idea the gratitude you will get from me if you can find me a solution.
QUICK UPDATE: A bootleg version of x64 with SP2 does the same thing.