Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Stoutjack on February 03, 2011, 07:56:29 pm
-
Hi,
Been running my new system with this MB and a 2500K for the last 2 weeks or so. I purchased a CPU/MB pack from an online retailer, and to date all has been just fine.
However, over the last 2 days I'm getting a very odd issue when booting. I have 2 HDs, and older WD Velociraptor used for Win 7, and a newer Samsung Spinpoint for applications etc.
Problem is that the MB has stopped recognising the Win boot disk, and I get an error at startup (cannot find bootmgr.exe, followed by restart which often triggers the dreaded loop of restarts that can only be solved by switching everything off for a few minutes). When I go into the BIOS to fix the HD boot order, the WD HD isn't there, but the Samsung is.....
The really odd thing is if I press F12 to select the first boot drive during POST, I can select the correct drive and everyhting is fine, Win loads and happy days.....
Any advice?. First time posting here, so if you need any more info, please let me know and I'll stick it up.
Cheers!
SJ
-
Hi and welcome to the Gigabyte forum.
I am presuming that you know the problem that Intel has had to recall all the Cougar Point chips due to a flaw in hte silicon manufacture. This of course was causing a SATA2 burnout. The SATA3 ports are supposedly ok so if you are trying to use the SATA2 ports that could be your problem.
If you are already using the SATA3 ports then try putting a HDD delay of about 5 seconds in the BIOS. It maybe that tha drive is just taking a little too long to initialize and that is why when you press F12 it is ready by the time you select it.
-
Hi and thanks for your reply ;D
Yeah, am aware of the Sandy Bridge issues, just thought it was a bit too coincidental that this issue appeared the same day it was announced to the public!
I'll give the HD delay a try in the BIOS and report back.
-
Yes I can't think of anything but those two reasons for that problem to happen.
-
Yep, that seems to have sorted the issue.
Thanks for your help!
;D
-
You are very welcome and glad to see it was a nice easy fix. ;)