Originally posted by grzegorz
View Post
Announcement
Collapse
No announcement yet.
GIGABYTE Latest Beta BIOS
Collapse
This is a sticky topic.
X
X
-
Good afternoon, I'm new to the forum.
If possible, please answer questions. I apologize in advance for the quality of my knowledge of English.
I ordered the Z390 Master motherboard. waiting for when he arrives.
1) F11m bios have a same a Me and microcode De version like a L version?
2) will there be more updates for this board in the future?, Release f11?
3) what is the best method for flashing beta versions?, Qflash- intact, fpt or efiflash, dos?
I have not had a gigabyte board for a long time and I see on the forums that sometimes people have damaged firmware when updating via qflash on the Z390 models, although the process runs normally and ends successfully and the PC power is connected to Ups.
But after restarting the board does not behave correctly.
What is the reason for this behavior ?, not all the conditions for the firmware are met?
Is it worth clearing cmos before flashing and doing load deafaults on this board?, Qflash bugs? Or is it better to choose the fast flashing method, without the Me region?
Comment
-
Hello,
looks like f12b is an improvement fo me. I've updated from f11 and also, reinstalled windows and didn't have a WHEA or BSOD yet ,48h soon, even with OC RAM. (Crossing REEALLY hard my fingers)
My settings are:
Vsoc 1.1
RAM manual 16 18 18 38 58 38 6 9 and DRAM to 1.37. (3600)
Infinity Fabric to 1800
CPU bus to 100, disabled auto and forced manually this value (was the same in auto)
PCIe gen forced to 3.0 in all PCIe.
PBO auto
Precission Boost also to enabled, default settings.
I did notice that my VIDcores min has gone from 9.44 to 9.50 and also power deviation now sits at 114% min. Before it even reached 84% having also red colours in HWinfo64
This is the first time I am not getting BSODs with Memory OC after less than 24h. The only strange thing that happened to me is that my backplate Jack audio stoped woring after a memtest86. I use now the frontal one.
Comment
-
Originally posted by LuftManu View PostWell, spoke too soon. WHEA error 18 a few minutes ago. Will there be an ending to this madness?
I'll end up RMAing the CPU. But not just yet, too few stock and I can't have my PC offline for months.
Have any of you guys thought about just running stock optimized defaults until GB releases new Final bios versions for these boards. Don't know why ppl keep beating themselves up trying to OC when they know these bios are Beta versions. Can't blame the hardware for not doing what it ain't set up to do yet.
Comment
-
So you do memory OC and complain about instability? So where is your point?
Do you get WHEA errors with default settings?
edit: how can you post pictures? I always get "file doesnt exist or is not writeable" sth like that :(
my 18h stable karhu settings (just starting OC)
Comment
-
Originally posted by bad_sign View PostSo you do memory OC and complain about instability? So where is your point?
Do you get WHEA errors with default settings?
edit: how can you post pictures? I always get "file doesnt exist or is not writeable" sth like that :(
my 18h stable karhu settings (just starting OC)
My memory is on the QVL with the XMP and even if that's not 100% accurate, I think I found the reason of some random reboots.
I will now try to increase LLC.
There are a lot of people with issues, you can see them in this post: https://www.overclock.net/threads/re...boots.1774627/
For pictures, try to get the link and use the right upper corner, that picture thing.
Comment
-
My B550I Aorus Pro AX and 5600x would WHEA instead of boot windows every time on BIOS 11n or 11p. F10,11j,11k worked.
Some more testing and I got things working with BIOS F11p. I set the BIOS defaults and disabled core performance boost. This allowed windows to boot and seemed stable. I then defaulted bios again and set PBO advanced mode, with the only change being the curve optimizer positive +10 on all cores. My system now booted. In addition, previously my single core boost would not go above 4300MHz (any version of BIOS I tried). Now it is getting up to 4550-4600Mhz. However, my multicore boost values still never get above 4000MHz. I'm using cinebench and HWINFO to monitor.
One other note, when I enabled XMP in my BIOS (3600MHz RAM), windows booted but WHEA immediately. Adjusting the PBO curve optimizer to positive +20 seemed to get me stable again.
Hopefully one day AMD/Gigabyte will get a bios that works. I haven't tested my above settings extensively (a run or 2 of cinebench), so not sure how stable it is long term. I never planned to overclock my system, but I've been spending a lot of time with typically overclocking area settings just to try and get my CPU to run at its advertised boost rate.
Comment
-
Originally posted by BagoBones View Post
Have any of you guys thought about just running stock optimized defaults until GB releases new Final bios versions for these boards. Don't know why ppl keep beating themselves up trying to OC when they know these bios are Beta versions. Can't blame the hardware for not doing what it ain't set up to do yet.
Sorry if your post was pointing the other direction - i just felt the need to explain my needs :) merry x-mas
Comment
-
I had to go back to F10. F11p ran cinebench multiple times and the computer ran for a few hours ok. But once I started talking on Discord, it WHEA. After reboot and reloading Discord, it WHEA again. I'll wait for a F11 final that hopefully will work.
Also, I don't think that increasing the voltage a bit in the PBO curve optimizer gave me so much more performance. It was more likely the new BIOS. Increasing voltage a bit was just a way for it to even boot with my CPU.
Comment
-
Originally posted by stasio View Post
Just spoken with GB HQ.
Official BIOS F31 and F11 is stopped to be posted on GB web page last moment, due to unexpected shutdown issue reported to R&D and investigation of disconnection of Realtek 2.5GbE LAN chip and some other minor issue.
So,they decide to continue with Beta BIOS, till issues will be solved.
Are you staff at GB stasio ?
This should be stickied to stop repeat questions on this topic.
Clearly Realtek are expecting GB to do the work here.
Originally posted by stasio View Post
Yes, ALL vendors got same problem.
Realtek need to solve........
If we wait for Realtek we might be waiting for a long time for this fix.
Comment
-
Originally posted by Mordecai View Post
Are you staff at GB stasio ?
This should be stickied to stop repeat questions on this topic.
Clearly Realtek are expecting GB to do the work here.
Realtek are saying the opposite. They're saying to contact GB. Realtek have passed their lab tests and it's up to the manufacturer to follow the design rules.
If we wait for Realtek we might be waiting for a long time for this fix.
The reaction from Realtek is weird to be honest, According to Realtek they only sell the chips, which is true, but since multiple manufactures have the same problem(Asus, Asrock, MSI, Gigabyte) which all use those Realtek RTL8125 chips, and according to Realtek they all didn't follow their design rules, at least let's see how Gigabyte is gonna fix it because the drivers come officially from realtek
Comment
Comment