View Single Post
  #3 (permalink)  
Old September 5, 2011, 10:28 AM
AkG's Avatar
AkG AkG is online now
Hardware Canucks Reviewer
 
Join Date: Oct 2007
Posts: 4,305
Default

Without known the exact BSOD error code...no way of knowing if its SF related or not.
Honestly, running SF2281s in raid 0 only starts to pay for itself when you do 3 or more. You are running them in a degraded state, thus getting almost none of their full potential.

IF it was me I'd break the array, run one as your C the other as your D (with 2ndary apps installed on it).

Turn OFF hot plugging in the BIOS. See if the BSOD happens again. IF it does write it down. The "SF bug" is one of a couple things. Most likely its the partial sleep issue that they can enter (even though its part of the new Intel PCH and one of the advertised features), when they shouldnt then the OS tries to access the drive....and it errors out as the drive is sleeping. Reboot solves it as the system tells the drive to wake up on hard reboot.
__________________
"If you ever start taking things too seriously, just remember that we are talking monkeys on an organic spaceship flying through the universe." -JR

“if your opponent has a conscience, then follow Gandhi. But if you enemy has no conscience, like Hitler, then follow Bonhoeffer.” - Dr. MLK jr
Reply With Quote