Posted 02 May 2009 - 09:45 AM
I completed a new build for my main home computer in March. Components are: Vista 64 Home Premium, Asus P6T6, i7 920, 6GB of Corsair Dominator 1600 RAM, ASUS Xonar DX, 2 RD3 WD 1 tbyte drives in RAID 0 (boot drive), 1 500GB WD drive for backup, Logitech Z6800 digital speakers, Pioneer DVD/CDR, LG BlueRay drive, EVGA GTX 285 SSC, Noctua CPU cooler, Revolution 85+ 950W, Planar 26" IPS. The processor is not overclocked and the bios configuration (updated to latest 0407) is default except the RAM, which is set to XMP profile 1600 8,8,8,24. The system ran without a hiccup from first build, and I am very happy with it except for this VERY annoying problem.
In the middle of a computer session, the monitor would go black and I would get an overclocking failed message (I have never overclocked this computer). This has happened sporadically approximately five times to this writing. When entering the BIOS after each occurance, the hard drive sequence under the boot menu was reversed from "Intel Raid" in the first position to my single 500GB drive used for backup. "Intel Raid" now occupied the second position. I would then replace "Intel Raid" back into it's proper first position in the sequence, save the changes and leave the BIOS. The computer would then boot normally. No other changes were noted throughout the BIOS. A new, related behavior has started since the beginning of April where again the screen would go black (with a few white lines flashing) in the middle of a session, and no error messages would appear. I would then shut down the computer, reboot, enter the BIOS and AGAIN the same reversal of the hard drive sequence had occured. I would then fix the problem as previously described and the machine would reboot normally. This sporadic behavior has also happened approximately five times. By the way, updating the BIOS from 0311 to 0407 did not help.
I'm getting tired of this. I have attempted to search the forums throughout the NET regarding these issues, and found a few similar (though not exact) references to this problem, but no fixes. Judging by the lack of information I can find about this problem, few users are experiencing it. Anybody out there have more definitive knowledge?