TheAffxct

rulik006
Z690 Classified does not booting with G.Skill Flare X5 Samsung B-die 
with one stick in any slot motherboard wont boot - 53/54 loop
with two sticks it will boot, but will see only half 
Memory works perfectly with other boards - Msi Z690 Force and Asus Z690-F Strix

I have A-die and it was not great for me at all. Like legit regressed optimisation. I have no idea if there’s something I’m doing that’s fundamentally wrong.

TheAffxct

EdgyBloke
BIOS 2.05 is ROCK SOLID. I have tried everything to reproduce some of the issues being produced here and can’t no matter what I do, and likely EVGA won’t be able to either.

If your having issues I honestly have no Idea what to tell you at this point. Feel free to report them, and maybe EVGA will figure out what’s going on, but you may want to try more troubleshooting first or simple things like reseating and cleaning memory.

I know this might be frustrating to hear, but almost everyone I talk to agrees 2.05 is great with massive improvements over 2.03, so it’s hard to understand why only a couple of people are seeing issues.

My only other suggestion is to flash the BIOS from within the BIOS and not Windows.

2.05 is good, but I think there are some faulty Dark samples floating around because I have come across a few posts over the last 3 or so months mentioning severe issues with RAM relating to non-detection and stuff like that that is pretty much experience-breaking.

This BIOS seems fine. It shouldn’t, but it definitely seems better than 2.04 in every department including memory and training speed. I’m going to chalk my weirdness with 7400 being down to my 13700K IMC. I have a SP 79 (P 89) and RPL MCs tend to scale alongside P SP, so I’m going to deduce that 7400 is too borderline and I’ll get an i9 sometime later on. Unfortunately they were temporarily out of stock on the day I sold my 12900K, so I had to grab the 13700K.

I’m sure there’s nothing wrong with my actual board, board-to-board variance seemed very low amongst Dark samples with 12th Gen and all we’ve changed is our IMCs and our memory ICs. I’d probably be able to 8400 if I had the right bin, it’s just one of those things. It’s disappointing that 7400 has so much re-train variance though. I maintain that 2.04 really did seem to suck though.

TheAffxct

Mr. Fox

TheAffxct

EdgyBloke
BIOS 2.05 is ROCK SOLID. I have tried everything to reproduce some of the issues being produced here and can’t no matter what I do, and likely EVGA won’t be able to either.

If your having issues I honestly have no Idea what to tell you at this point. Feel free to report them, and maybe EVGA will figure out what’s going on, but you may want to try more troubleshooting first or simple things like reseating and cleaning memory.

I know this might be frustrating to hear, but almost everyone I talk to agrees 2.05 is great with massive improvements over 2.03, so it’s hard to understand why only a couple of people are seeing issues.

My only other suggestion is to flash the BIOS from within the BIOS and not Windows.

2.05 is good, but I think there are some faulty Dark samples floating around because I have come across a few posts over the last 3 or so months mentioning severe issues with RAM relating to non-detection and stuff like that that is pretty much experience-breaking.

This BIOS seems fine. It shouldn’t, but it definitely seems better than 2.04 in every department including memory and training speed. I’m going to chalk my weirdness with 7400 being down to my 13700K IMC. I have a SP 79 (P 89) and RPL MCs tend to scale alongside P SP, so I’m going to deduce that 7400 is too borderline and I’ll get an i9 sometime later on. Unfortunately they were temporarily out of stock on the day I sold my 12900K, so I had to grab the 13700K.

I’m sure there’s nothing wrong with my actual board, board-to-board variance seemed very low amongst Dark samples with 12th Gen and all we’ve changed is our IMCs and our memory ICs. I’d probably be able to 8400 if I had the right bin, it’s just one of those things. It’s disappointing that 7400 has so much re-train variance though. I maintain that 2.04 really did seem to suck though.

My RMA is arriving tomorrow. I believe that to be the case for me. Only one of the BIOS positions is working. The other two are unflashable.


What I can't explain is why 2.03 works flawlessly and 2.04 and 2.05 have bizarre issues. I have flashed back and forth among all three and the only way everything functions correctly is if I am running 2.03. The bizarre issues are things like BIOS multiplier settings not being applied and unexplainable drops in frequency under load. I always save screenshots of BIOS settings and I know there is not something I am setting differently.

This I would chalk up to a board issue. Back in September while studying for something, I got into a small scuffle with bscool on OCN about this topic because of how chuffed I was with the Dark that I had grabbed at -40%. I was saying that it was the only board to buy etc. He got a bit put off because he started listing off issues Dark users were having, and when I researched this forum I realised that there must be some actually faulty samples that either have completely broken aspects, or react very badly to firmware updates.

My personal sample scared me the other day when I had that weird issue where the indicator lights would disappear and I was thrown off by the fan thing. Eventually I came to find why the fan thing was happening and I also seemed to find a conclusion to the weird dark state of the board (no it wasn’t Dark mode).

I’ve since been very relieved because I always thought that I had a good sample being that I was lucky enough never to have ran into weird issues. With 2.05, my board seems to be totally fine, but I had to settle for a 7200C34 @ 1.38V because I frankly can’t rely on my world’s worst 13700K to do 7400+ reliably. At the very least I managed to flatten out my 2s/3s nicely again at 7200 without causing clustered errors. It’s underwhelming, but efficient and reliable, and my M-die required 1.605VDD/1.515VDDQ for 7200C32 anyway, which wasn’t daily’able.

If anyone here is having strange issues with memory detection, infinite training loops, screwed up BIOS chips, or other severe issues, it is likely you have a partially or fully faulty sample and should proceed with an RMA ticket.

Kadao

TheAffxct

Mr. Fox

TheAffxct

EdgyBloke
BIOS 2.05 is ROCK SOLID. I have tried everything to reproduce some of the issues being produced here and can’t no matter what I do, and likely EVGA won’t be able to either.

If your having issues I honestly have no Idea what to tell you at this point. Feel free to report them, and maybe EVGA will figure out what’s going on, but you may want to try more troubleshooting first or simple things like reseating and cleaning memory.

I know this might be frustrating to hear, but almost everyone I talk to agrees 2.05 is great with massive improvements over 2.03, so it’s hard to understand why only a couple of people are seeing issues.

My only other suggestion is to flash the BIOS from within the BIOS and not Windows.

2.05 is good, but I think there are some faulty Dark samples floating around because I have come across a few posts over the last 3 or so months mentioning severe issues with RAM relating to non-detection and stuff like that that is pretty much experience-breaking.

This BIOS seems fine. It shouldn’t, but it definitely seems better than 2.04 in every department including memory and training speed. I’m going to chalk my weirdness with 7400 being down to my 13700K IMC. I have a SP 79 (P 89) and RPL MCs tend to scale alongside P SP, so I’m going to deduce that 7400 is too borderline and I’ll get an i9 sometime later on. Unfortunately they were temporarily out of stock on the day I sold my 12900K, so I had to grab the 13700K.

I’m sure there’s nothing wrong with my actual board, board-to-board variance seemed very low amongst Dark samples with 12th Gen and all we’ve changed is our IMCs and our memory ICs. I’d probably be able to 8400 if I had the right bin, it’s just one of those things. It’s disappointing that 7400 has so much re-train variance though. I maintain that 2.04 really did seem to suck though.

My RMA is arriving tomorrow. I believe that to be the case for me. Only one of the BIOS positions is working. The other two are unflashable.


What I can't explain is why 2.03 works flawlessly and 2.04 and 2.05 have bizarre issues. I have flashed back and forth among all three and the only way everything functions correctly is if I am running 2.03. The bizarre issues are things like BIOS multiplier settings not being applied and unexplainable drops in frequency under load. I always save screenshots of BIOS settings and I know there is not something I am setting differently.

This I would chalk up to a board issue. Back in September while studying for something, I got into a small scuffle with bscool on OCN about this topic because of how chuffed I was with the Dark that I had grabbed at -40%. I was saying that it was the only board to buy etc. He got a bit put off because he started listing off issues Dark users were having, and when I researched this forum I realised that there must be some actually faulty samples that either have completely broken aspects, or react very badly to firmware updates.

My personal sample scared me the other day when I had that weird issue where the indicator lights would disappear and I was thrown off by the fan thing. Eventually I came to find why the fan thing was happening and I also seemed to find a conclusion to the weird dark state of the board (no it wasn’t Dark mode).

I’ve since been very relieved because I always thought that I had a good sample being that I was lucky enough never to have ran into weird issues. With 2.05, my board seems to be totally fine, but I had to settle for a 7200C34 @ 1.38V because I frankly can’t rely on my world’s worst 13700K to do 7400+ reliably. At the very least I managed to flatten out my 2s/3s nicely again at 7200 without causing clustered errors. It’s underwhelming, but efficient and reliable, and my M-die required 1.605VDD/1.515VDDQ for 7200C32 anyway, which wasn’t daily’able.

If anyone here is having strange issues with memory detection, infinite training loops, screwed up BIOS chips, or other severe issues, it is likely you have a partially or fully faulty sample and should proceed with an RMA ticket.

In this case I think it's only a software problem, the 54, 55, 7F loop existed before. The A-die sticks that stopped working with 2.04 and 2.05 worked OK with 2.03 and other computers as stated by rulik006 and myself. It's not a matter of bios config or settings I would say, as only one stick is detected on BIOS with the 2.04 and 2.05. I would say that the guys working the bios just need to dig deeper into it and fix it.
 
Unfortunately, RMAing is not an option for everyone I would say, as I believe I'm not alone. I live in Angola (Africa),and I have to import my gear from the US via DHL, FEDEX, UPS, etc. Shipping anything back to the US would cost me north of 400usd. If something stops working or does not work as intend I just have to put it aside and forget about it.
 
This is actually my second evga motherboard. Had a z490 dark kingpin, that first had the post code indicators stop working, and a couple of months later the board just died one day, it would no longer turn on.
 
 

rgarodnick

Shraf2k
I'm stuck on A2 as well. z690 dark, 12700k, gigabyte aorus 6000 memory. That's 2/3 bios slots down.

Are you on 1.15 bios?

rgarodnick

Shraf2k
Incorrect

2.x bios revisions are all for 13th gen CPUs. 1.15 was perfectly stable for my 12900k for many months.

rgarodnick
Fair enough.

While I stand corrected, my thought still holds true to only update bios when needed, either to fix something that's broken or for better stability. For those having issues on 2.x with ADL, is there much to gain by going past 1.15?