Your problem is that's a question aimed at AMD, their AGESA implementation and the limitations of the IMC. The boards are largely similar on this one I think.
Personally I would leave it if you're able to hit 3000 ish at CL16 as gains will be minimal beyond that
Ok, and how come I am able to run my Corsair vengeance lpx at 3200mhz easily on my MSI gaming pro carbon by just enabling their A-Xmp feature and stable, however on my Gigabyte Gaming K5, nothing I do either manually or auto can. A lot of people are in the same boat here. It has to be a vendor specific tweak no?
+1, I am able to run my Corsair vengeance lpx 3200 @ its rated speed of 3200 on a MSI AM4 motherboard, but still only able to do 2933 stable on my gigabyte ab350-g3. Please sort it out in next wave of BIOS updates gigabyte!
I know it's been asked, hammered on, questioned to death and more.......
Is there going to be a future BIOS release that allows for the use of RAM at speeds of 3200MHz and higher, that have a C15 or C16 (or more) and double sided, on any of the future X370 (and B350) boards?
If you could please let me (and others) know, so we can either offload the RAM we have now and get C14 single sided RAM and be done.
Thanks!
My last discussion with AMD left me with the impression that while you *maybe* able to get it to work, they are not putting many (any?) resources into pushing 3200+ memory. As others have stated this is really a function of AGESA code, not specific vendor BIOS tweaks. We can make changes and get a specific kit to work, but as a platform we need updated AGESA code to make it viable on most kits. Your best bet now and for the foreseeable future is still single sided Samsung B >=3200.
Your problem is that's a question aimed at AMD, their AGESA implementation and the limitations of the IMC. The boards are largely similar on this one I think.
Personally I would leave it if you're able to hit 3000 ish at CL16 as gains will be minimal beyond that
Ok, and how come I am able to run my Corsair vengeance lpx at 3200mhz easily on my MSI gaming pro carbon by just enabling their A-Xmp feature and stable, however on my Gigabyte Gaming K5, nothing I do either manually or auto can. A lot of people are in the same boat here. It has to be a vendor specific tweak no?
Correct. Vendors can make tweaks for specific kits. It is something we do, but as a platform is not viable. There is simply no way to test, tweak, and get every kit working.
Let me explain what our guys explained to me when I posed the question: "Why can't we just take the manufacturers timings, pop them in, and validate all the kits?"
The answer I got is JEDEC spec. JEDEC spec only goes up to 2667 with specific timings. These timings have a very clear validation process. JEDEC spec works 99.9% of the time, and the .01% is usually due to a faulty component not the settings. The moment we step out of that spec we are more or less on our own.
Kits come with 4 timings, a speed, and a voltage. Behind that are dozens and dozens of subtimings. The same trial/error process you guys go through to get a kit to work is the exact same for our teams. Its time consuming, not guaranteed to work, and can change based on CPU, memory batch, etc, even if they are all the same model!
Long story short, as a platform, the only way to get most memory above 2933 (which seems to be the current "it works" speed for most kits) is through AGESA code.
Take a look back. We started with 2933 being unheard of. We tweaked, we released a ton of BIOS, and got some kits to work. Only with new AGESA code did 2933 become "mainstream". The process going forward is going to be the same. We can tweak, we can get some kits to work, but to see a paradigm shift in 3200 "working" will require new AGESA code with that aim in mind.
Right now I'm Offline I have made 16 posts
I joined May 2017
I've received 1 like
My gender is Male
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
The latest AGESA code allowed for up to 4GHz DDR4 to be selected and set, so I think the push is for 3200+ MHz ram is already there on AMD's side. And the fact that vengeance LPX 3200 seems to be running on literally all other vendor's motherboards at its rated 3200, seems to point towards it being a vendor-specific issue, at least with this particular kit. The last AGESA code was already heavily focused on getting hynix-based DRAM working at its intended speeds. Also, I think you mean 0.1% there, not 0.01% , & yes we understand it's time-consuming and tedious to work through every individual kit and verifying them for every board, but the demand for this from the consumers of these new boards is evidently there; so maybe gigabyte need to step up their game on this front; as other vendors seem to be dedicating a lot of time and effort towards ameliorating the DRAM & other stability/compatibility issues on this new platform.
The last AGESA code allowed for up to 4GHz DDR4 to be selected and set, so I think the push is for 3200+ MHz ram is already there on AMD's side. And the fact that vengeance LPX 3200 seems to be running on literally all other vendor's motherboards at its rated 3200, seems to point towards it being a vendor-specific issue, at least with this particular kit. The last AGESA code was already heavily focused on getting hynix-based DRAM working at its intended speeds.
I've asked the BIOS/validation teams to take another look at corsair LPX 3200 and see if we can fix it on the next BIOS.
Right now I'm Offline I have made 23 posts
I joined July 2017
My gender is Male
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
GIGABYTE - Matt I'm having problems with some usb devices not detected by the bios, is only the bios that gives my troubles once windows is loaded they work. Any chance of this being fixed with the next bios release?? I have a ab350 Gaming ver 1.
GIGABYTE - Matt I'm having problems with some usb devices not detected by the bios, is only the bios that gives my troubles once windows is loaded they work. Any chance of this being fixed with the next bios release?? I have a ab350 Gaming ver 1.
The last AGESA code allowed for up to 4GHz DDR4 to be selected and set, so I think the push is for 3200+ MHz ram is already there on AMD's side. And the fact that vengeance LPX 3200 seems to be running on literally all other vendor's motherboards at its rated 3200, seems to point towards it being a vendor-specific issue, at least with this particular kit. The last AGESA code was already heavily focused on getting hynix-based DRAM working at its intended speeds.
I've asked the BIOS/validation teams to take another look at corsair LPX 3200 and see if we can fix it on the next BIOS.
Thank you very much. I had about 5 posts asking about this, or at least some insight as to what timings would get this working. The thing that got me was that the LPX memory I had was on the QVL list for 3200, but I could never get it to run there, although you said if it was on the QVL, it should run at those timings. CMK32GX4M2B3200C16W
I've asked the BIOS/validation teams to take another look at corsair LPX 3200 and see if we can fix it on the next BIOS.
Thank you very much. I had about 5 posts asking about this, or at least some insight as to what timings would get this working. The thing that got me was that the LPX memory I had was on the QVL list for 3200, but I could never get it to run there, although you said if it was on the QVL, it should run at those timings. CMK32GX4M2B3200C16W
I asked them to test / verify that kit. Let you know what they say!
If you are having an issue with your soundblaster card being detected I believe we have a fix. Unfortunately it looks like it isn't a simple BIOS issue. Please submit a ticket to technical support. They will be able to assist you with an RMA (if needed).
Hi Matt, can you be more specific on this issue? How can we verify if your boards are affected? If my onboard sound dies after the warranty will GIGABYTE take care of me if no other external sound card work with my K7? Now I'm a bit scared thinking it is a hardware bug...
The issue isn't any sound card, its specifically the Sound Blaster. Haven't heard of people having issues with any others. The problem/solution was identified by US, AMI, and Soundblaster working together.
Hi Matt, can you be more specific on this issue? How can we verify if your boards are affected? If my onboard sound dies after the warranty will GIGABYTE take care of me if no other external sound card work with my K7? Now I'm a bit scared thinking it is a hardware bug...
The issue isn't any sound card, its specifically the Sound Blaster. Haven't heard of people having issues with any others. The problem/solution was identified by US, AMI, and Soundblaster working together.
For the record, I've had a soundblaster ZXR from day one and it hasn't given me any trouble in my K7. If I remember the from the deleted thread, wasn't it the Z model mostly? Or were there other issues?
Hi Matt, can you be more specific on this issue? How can we verify if your boards are affected? If my onboard sound dies after the warranty will GIGABYTE take care of me if no other external sound card work with my K7? Now I'm a bit scared thinking it is a hardware bug...
The issue isn't any sound card, its specifically the Sound Blaster. Haven't heard of people having issues with any others. The problem/solution was identified by US, AMI, and Soundblaster working together.
Thanks Matt. For a second I was saddened with the possibility of a hardware fault. Except the sporadic 'soft brick', my board have no problems with both lan adapters and no audio interference on the front (or back) panel. No random startup, no black screen, no blue screens or problem with crossfire. Memory are running under the specs (Samsung e-die). All USB ports are ok even on BIOS. By the way, the BIOS is spartan but it is very good to navigate with the keyboard. I miss a beefier sink on the CPU VRM but the FETS are solid and the temps under my gaming sessions are fine.
Your problem is that's a question aimed at AMD, their AGESA implementation and the limitations of the IMC. The boards are largely similar on this one I think.
Personally I would leave it if you're able to hit 3000 ish at CL16 as gains will be minimal beyond that
Ok, and how come I am able to run my Corsair vengeance lpx at 3200mhz easily on my MSI gaming pro carbon by just enabling their A-Xmp feature and stable, however on my Gigabyte Gaming K5, nothing I do either manually or auto can. A lot of people are in the same boat here. It has to be a vendor specific tweak no?
Yes it is a board/bios issue. They need to fix it, i dont care if the gains are minimal as the other guy claims it is still a gain/$.
skizzdog wrote: Jan 24, 2021 16:54:39 GMT -8 Hello I just built a pc using the Gig Z390 M Gaming board.I cannot figure out what drivers to load first.Idont have the CD that came with the board.Can i buy one some place.
arvindh wrote: Jan 22, 2021 18:49:37 GMT -8 Hi,im having 3HD(win10 & Mint) on Aorus B450.now want to install 4th HD with debian10.Is my current setup legacy/UEFI? what care should i take before installing 3rd OS on 4th HD.forum.gigabyte.us/thread/11477/b450-multiboot-legacy-uefi*
razor9103 wrote: Jan 22, 2021 12:00:23 GMT -8 New Z490 Vision D won't boot ... stuck at RED CPU error LED
lima567 wrote: Jan 20, 2021 15:13:51 GMT -8 intender thank you, will try doing that.
masc2279 wrote: Jan 20, 2021 10:45:24 GMT -8 polarox - need more info what board what block version ... I can tell you that I have the EKWB EK-Quantum Momentum TRX40 Aorus Master Monoblock and that block is worth every penny i went thru 3 different solutions and this one is insanely good.
polarox wrote: Jan 20, 2021 8:03:32 GMT -8 hi guys,
does anyone have the bitspower or EK monoblock for this motherboard? Is it worth the money?
intender wrote: Jan 19, 2021 11:55:39 GMT -8 lima567 this is a windows 10 20h2 issue. I had the same thing on one of my computers. I was never able to get logged back into my account on that PC. I moved that drive to another computer and copied over all data I wanted to keep and did a clean install.
joeym wrote: Jan 19, 2021 8:52:33 GMT -8 Is Asus working on a solution for the Intel 300 series?
lima567 wrote: Jan 18, 2021 20:02:50 GMT -8 Have issue “Something happened and your PIN isn’t available. Click to set up your PIN again.” (I disabled start up applications. Trying to get to save mode, when press F12, chose Windows boot, hit enter - gets me back to sign in page. Please help
sozehh wrote: Jan 18, 2021 13:42:41 GMT -8 soooo NOW ASUS is working on resizable bar too....GIGABYTE?
sozehh wrote: Jan 16, 2021 10:58:58 GMT -8 joeym ofc i've done it, signed and trying to spread the petition, gigabyte do your work please and add resizable bar for intel 300 series, it is not an old product, people like me spent 800 euros on aorus xtreme, don't tell me i have already an outdated mb
joeym wrote: Jan 16, 2021 7:15:27 GMT -8 I would strongly recommend that anyone who hasn't already signed the petition do so now. If you already signed it, please share it! This may help encourage all other motherboard manufacturers to follow suite. Link to the petition: chng.it/LKLksG4yQv
iuliug wrote: Jan 15, 2021 16:31:07 GMT -8 Yes ADD BAR support for all boards that support it - but GB will ignore this
vigo wrote: Jan 15, 2021 9:35:47 GMT -8 what is resizable BAR ?
desaccorde wrote: Jan 15, 2021 0:50:15 GMT -8 300 Series MUST be supported, no other way. MSI supports it. They may think they're pushing their customers for a premature upgrade, but guess what? Even if I upgrade, I wouldn't buy a Gigabyte board. Me and all my close friends will never buy Gig again.
johnyb0y wrote: Jan 14, 2021 4:58:11 GMT -8 @gigabyte, I've personally built with half a dozen of your boards and recommended you at least 5 times last year. This will stop if you screw Z390 users with not supporting Re-BAR.*
mezzer wrote: Jan 14, 2021 2:23:19 GMT -8 This will be my last gigabyte mobo if there's no resize bar support on 300 series.