Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: rossb on October 28, 2016, 02:43:56 pm
-
I just upgraded my BIOS from F6 to F20b and my dual boot PC booted Windows 10 normally but it kept getting a BSOD error when attempting to boot Win 7. I used all of the BIOS defaults except I turned on RAID. I re-flashed BIOS F6 and everything now boots properly.
I also tried an OC with F20b and Win 10 and I noticed that F20b would not allow my system to hit my 1-Core clock speed. It seemed as though more than 1 core was always active no matter what I was doing. In addition, when the PC was at idle F20b would not throttle down as far as F6 does. F6 goes down to 8x100, while F20b would only go down to 9x100.
-
Why did you update the bios in the first place? That is a beta bios F20b for the new CPU and that is it. The other thing you can do is email support to tell them the problem you are having.
Because it is a beta bios they are looking for problems with it so they can fix it. That way when they do come out with it as a official bios they might have those things fix. This is just a user to user forum not support.
-
Why did you update the bios in the first place
Because it uses a new GUI, I wanted to play with it, and Gigabyte showed it as available for my mobo. FWIW, the new CPUs use a new socket type and will not fit my mobo.
-
Why did you update the bios in the first place
Because it uses a new GUI, I wanted to play with it, and Gigabyte showed it as available for my mobo. FWIW, the new CPUs use a new socket type and will not fit my mobo.
No one here has any problem with people who like to experiment "play with" or test new BIOS'. But because this can lead to downtime or other complications, we do not recommend using a production system or primary PC for this type of experimentation. Users choice of course. Sometimes flashing up means you can't go back. Something to be mindful of. I know dmdilks feels the same about this as I do.
Cheers