Me, Raid 0, and OCing is a bad combination

Balex99

Senior member
Sep 3, 2000
356
0
0
Just put in my new Abit NF7-S(thanks fuelrod) and put in two 80gb WDs on the SATA raid with the adapters(PATA to SATA). Installation went fine and Windows went fine. OCing went good till I finally hit the limit on my FSB. Machine shut down and when I restarted I can't load into windows no matter what fsb I am on. This is like the 3rd time this has happened. Previous times I thought were something else. Has anyone had troubles with windows being fouled up after testing their OC? Haven't had this problem when windows was on a single drive.
 

Falloutboy

Diamond Member
Jan 2, 2003
5,916
0
76
its fairly common if you pushing you computer too hard to corupt a drive. thats why I don't keep anything importand on my boot drive.
 

Shimmishim

Elite Member
Feb 19, 2001
7,504
0
76
Originally posted by: Balex99
Just put in my new Abit NF7-S(thanks fuelrod) and put in two 80gb WDs on the SATA raid with the adapters(PATA to SATA). Installation went fine and Windows went fine. OCing went good till I finally hit the limit on my FSB. Machine shut down and when I restarted I can't load into windows no matter what fsb I am on. This is like the 3rd time this has happened. Previous times I thought were something else. Has anyone had troubles with windows being fouled up after testing their OC? Haven't had this problem when windows was on a single drive.

NF7-S... are you using the SATA ports on the board or a separate card?

if you're using the board ports you're in trouble...

seems that you'll get corrupted files while using these ports...

if you REALLY want to use them, then you need to go download a beta bios...
 

MDE

Lifer
Jul 17, 2003
13,199
1
81
Originally posted by: Shimmishim
Originally posted by: Balex99
Just put in my new Abit NF7-S(thanks fuelrod) and put in two 80gb WDs on the SATA raid with the adapters(PATA to SATA). Installation went fine and Windows went fine. OCing went good till I finally hit the limit on my FSB. Machine shut down and when I restarted I can't load into windows no matter what fsb I am on. This is like the 3rd time this has happened. Previous times I thought were something else. Has anyone had troubles with windows being fouled up after testing their OC? Haven't had this problem when windows was on a single drive.

NF7-S... are you using the SATA ports on the board or a separate card?

if you're using the board ports you're in trouble...

seems that you'll get corrupted files while using these ports...

if you REALLY want to use them, then you need to go download a beta bios...
I'm using my NF7-S's onboard SATA (in a RAID 0 with two Raptors) without a problem. Pushing the FSB too high will cause corruption no matter what hard drive controller you're using.
 

pelikan

Diamond Member
Dec 28, 2002
3,118
0
76
While raising the FSB, you can boot into memtest86 and run test 5. If it passes that its safe to go into windows.
 

Balex99

Senior member
Sep 3, 2000
356
0
0
Thanks for the replies. I am using the onboard SATA. I started using Memtest and I will continue to use it to keep this from happening. After messing with it some more it seems that windows is not corrupted. I booted off a linux CD and while I was looking at my files, a friend adjusted my fan controller on my thermaltake PSU (which btw is plugged into my cpu port of the MB fan header). As soon as he did this my machine shut down and I wasnt even in windows. We turned it back all the way up and was able to get into windows. I think I've got something looking at that rpm and it was taking me out. I will be moving that rpm plug to the PWR port on the fan header asap just to eliminate that possibility. But for now all is working great. Thanks for the help.
 

Shimmishim

Elite Member
Feb 19, 2001
7,504
0
76
Originally posted by: MDE
Originally posted by: Shimmishim
Originally posted by: Balex99
Just put in my new Abit NF7-S(thanks fuelrod) and put in two 80gb WDs on the SATA raid with the adapters(PATA to SATA). Installation went fine and Windows went fine. OCing went good till I finally hit the limit on my FSB. Machine shut down and when I restarted I can't load into windows no matter what fsb I am on. This is like the 3rd time this has happened. Previous times I thought were something else. Has anyone had troubles with windows being fouled up after testing their OC? Haven't had this problem when windows was on a single drive.

NF7-S... are you using the SATA ports on the board or a separate card?

if you're using the board ports you're in trouble...

seems that you'll get corrupted files while using these ports...

if you REALLY want to use them, then you need to go download a beta bios...
I'm using my NF7-S's onboard SATA (in a RAID 0 with two Raptors) without a problem. Pushing the FSB too high will cause corruption no matter what hard drive controller you're using.

yes, if you use the onboard ones....
but i don't so getting high fsb's is no problem at all...
 

MDE

Lifer
Jul 17, 2003
13,199
1
81
Shim, I don't get what you're trying to say. Using a PCI SATA card should be no different, as the onboard SATA is on the PCI bus already. How exactly does the onboard SATA limit overclocking?
 

Shimmishim

Elite Member
Feb 19, 2001
7,504
0
76
Originally posted by: MDE
Shim, I don't get what you're trying to say. Using a PCI SATA card should be no different, as the onboard SATA is on the PCI bus already. How exactly does the onboard SATA limit overclocking?

well at least with the nforce3 boards with pci lock it does.

as with the nforce2 and him getting corrupt windows with higher fsb's.. i'm not quite sure...

either way, the Silicon image drivers and such on these boards suck big time.

but anyway with my pci card, i'm not limited on my fsb for o/c... in this case, only my board limits me (nf7-s sucks for really high fsb's).