Announcement
Collapse
No announcement yet.
GIGABYTE Latest Beta BIOS
Collapse
This is a sticky topic.
X
X
-
Re: GIGABYTE Latest Beta BIOS
Originally posted by stasio View PostAll OK,from my side.i7 6700k @4.5 Ghz
Gigabyte Z170 Gaming 7
Gigabyte Xtreme GTX970
Kingston Fury 16GB DDR4
Be Quiet Dark Rock 3
Superflower 1000watt
Corsair K70 RGB
Corsair M65 RGB
Samaung EVO 850 SSD
Evolv ATX
Asus ROG Swift G-Sync 1440p 144hz
Windows 10 64bit
Comment
-
Re: GIGABYTE Latest Beta BIOS
Originally posted by berte View PostGA-Z170X-Gaming 7 - F6k still does not work memory slot 1 and 3 with Kingston HX426C15FBK2/16.
I'm not sure about this error however only slot 3 also not working
When i put memory to slots 2-4 or 1-3 to get dual channel i got post code 55 error.
( Bios F6K ) GA-Z170X-Gaming 7
Please Gigabyte add support for this type of memory Kingston HX426C15FBK2/16
Comment
-
Re: GIGABYTE Latest Beta BIOS
I had similar problems with the GA-Z170X-UD3/6700K in combination with the (QVL!) Kingston HX426C15FBK4/32 memory (thus 4x8GB @ 2666 MHz).
All individual modules worked find and every combination of dual channel memory worked fine as well, but as soon as I used slot 2 and 4 together I got error code 55 during boot.
I rechecked every individual component but each was properly installed and worked correctly (at the default 2666 MHz), just not the combined set of 4 memory modules.
After booting with at most 2 modules and reducing the memory frequency to 2133 MHz, I could boot with all 4 memory modules installed (but of course lower memory frequency).
Still I knew that default settings (thus 2666 MHz for this memory), e.g. after a CMOS reset or loading default, would require removing at least 2 memory modules and repeating the process.
This behavior was with both the official BIOS and the F5b beta.
However, I can report that after upgrading to beta BIOS F5c, now all 4 modules (32 GB) work flawlessly at 2666 MHz
Also the modules use the official settings from Kingston (according to CPU-Z), which were the defaults after flashing the new BIOS.
So it seems that Gigabyte identified the problem and resolved it in the latest BIOS for this board and I hope they put the solution in the next official BIOS.
However, it is strange that this memory was on the QVL list for this board but apparently was not properly tested.
This issue (error code 55 with specific slot combinations) is reported for more Z170X boards and often with this Kingston memory; sometimes also with other memory with a native frequency > 2133 MHz.
These memory problems were a real disappointment after I assembled my new PC, but I am happy it is now solved (at least with the beta BIOS).
And yes, I can confirm that after going from the official BIOS to the beta BIOS (in my case it was F5b) the activation of the upgraded Windows 10 was lost.
Strange because when I upgraded the official BIOS after I received the board, the activation was not lost.
I have used a new Windows 10 activation key, because I did not want to beg Microsoft for repairing the activation or repeat the upgrade process.
So be careful when using a beta BIOS on an upgraded Windows 10.Last edited by Flitzer; 12-20-2015, 02:38 AM.
Comment
-
Re: GIGABYTE Latest Beta BIOS
Originally posted by Flitzer View PostSo be careful when using a beta BIOS on an upgraded Windows 10.3i5-6600k 4.6 Ghz, Intel HD530, 16GB RAM
Gigabyte Z170 Gaming 3, 850 EVO m.2
Comment
-
Re: GIGABYTE Latest Beta BIOS
I have purchased a retail Windows Pro 10. I have just one Event Viewer error log after every boot.
I am normally quite good at identifying Event ID's but I cannot find any information regarding this one. I have formatted twice, installed just the drivers and I received this after both clean formats. How can I resolve this if it does not tell me anything? What is ACPI 5?
Everything is okay in Device manager, any assistance would be greatly appreciated. My motherboard is the Z170X Gaming 5.
The description for Event ID 56 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ACPI
5
the message resource is present but the message is not found in the string/message table
Event Xml:
Many people have this error, could you fix it?
Hi, I've just upgraded from a 7+ year old machine, so I may be a little rusty when it comes to trying to problem solve the following... When I'm in game (Alien Isolation, occasionally GTA V, so far not X-COM), I'm seeing the occasional system freeze. I have to do a hard reset to clear the error, wi...
Last edited by OiCkilL; 12-20-2015, 01:49 AM.
Comment
-
Re: GIGABYTE Latest Beta BIOS
I also have the exact same event listed in my Windows 10 logs and although I know what ACPI 5 is there is no place in the BIOS to disable/enable that revision of the ACPI spec so it's completely dependent on the hardware vendor (in this case, Gigabyte) to either fix it within the BIOS or give us the option to control it. Bottom line is, the error is probably never going to go away. I'd love to be wrong.
Comment
-
Re: GIGABYTE Latest Beta BIOS
Hi there again. Some good news!
For all those guys on z170 gaming 3/5/7 who are experiencing system freezes / instabiliy: Does that apply to you?
I recently mentioned that I get consistend hangs on win10 about 1x per day. That was with default BIOS setting and after NOT using the bigfoot 100 killer NIC driver. But instead just a regular plain old generic atheros driver 8161 (have disk --> forced install).
Still the thing hangs every few hours. But then I applied all my overclocking settings and pushed it up to 4.6 GHz. And it hasn't hanged yet :) It's not clear which specific setting solved my issue. But either it was disabling Turbo Boost, or else enabling the XMP Profile for the DDR4 sticks I have. (which is Corsair Vengance LPX Black C14 2400Mhz).
Here are my full OC settings (all were changed in 1 go, I have not isolated yet):
* Increase base clock multiplier --> 101.96 Mhz <----------
(bios default is 100Mhz)
* All cores base multiplier --> 45 (4.5 GHz)
(bios default is 39 for my i5-6600K)
* Turbo boost --> disabled (greyed out)
(bios default is 'auto' and enabled)
memory settings:
* XMP profile 1 --> (2400mhz, 14-16-16-31)
- depends on your installed DDR4 modules
(bios default is xmp disabled / intel defaults 2133Mhz and DDR4 spec timings).
Best of all, I don't need to go out and buy a new network card. The killer NIC can still work allright if used with old atheros 8161 generic chipset driver. Not widthstanding the situation while no driver is installed yet (e.g. fresh install) that the killer NIC will wreak havoc if left plugged in. Flooding LAN with bad packets and takes down my local router (crashing it completely) and also DDOSing nearby networked devices. Which (unlike random system freezes) is very simpler / straightforward problem / hardware bug to workaround.Last edited by dreamcat4; 12-21-2015, 10:08 AM.3i5-6600k 4.6 Ghz, Intel HD530, 16GB RAM
Gigabyte Z170 Gaming 3, 850 EVO m.2
Comment
Comment