Overclock.net banner
2,221 - 2,240 of 9,907 Posts
Could just need a new BIOS update from Asus. I'm sure GSkill tested and binned the RAM.
After I had contact with the Gskill Support…the more VDD / VDDQ I need with my Strix 690-F and 6000 C36..it must be something with the bios / board….


The worst case would be to delete the 6000 c36 from the QVL List…

So maybe @shamino1978 and his team will find a solution to fix….?
 
After I had contact with the Gskill Support…the more VDD / VDDQ I need with my Strix 690-F and 6000 C36..it must be something with the bios / board….


The worst case would be to delete the 6000 c36 from the QVL List…

So maybe @shamino1978 and his team will find a solution to fix….?
i wonder when would gskill release spd flash to update the current sticks.
 
The XMP issue is 100% the Asus bios. The same ram that I had issues with in my Hero works perfectly in my Unify-x
 
The XMP issue is 100% the Asus bios. The same ram that I had issues with in my Hero works perfectly in my Unify-x
I feel that my mobo have nearly no quality assurance.
they tested 2 sticks of ram and hoped that 4 works xD

I only hope that these problems will be fixed, I'm waiting because I love Asus boards, my first Asus boards was an Asus CUSL2 on a Pentium III CPU.

I hope that nothing is changed in Asus and that I can still trust them as a company.
I have full trust of Shamino that is a very good guy, I'm absolutely not complaining about him,
but I feel that Asus lacks some quality assurance. You can't sell a mobo in this state IMHO, it's simply not "finished".
 
I don't understand something, with the latest beta BIOS my AI OC is crashing like crazy and I "think" that's because of the E-Cores OC (4.1 is a bit much, me thinks).
I thought Windows was supposed to leave E-Cores alone when we're gaming? Yet in Forza Horizon 5 I see load on (mostly) 4-Pcores and consistent (not max but still) load on all E-cores.
Line Font Tints and shades Symmetry Pattern

Something must be borked in the latest beta bios for the Apex, I can't use AI OC for P-Cores only anymore...otherwise it disables AI OC all together.
 
is 901 still the latest bios for the Strix Gaming D4 board? thanks
 
12900K / APEX / 2x16gb F5-6000U3636E16GX2-TZ5RS / EKWB Velocity2

Built system and installed 0811. Moved my windows 11 installation directly over from my Z690 Strix D4.
Set XMP1 and 1T. Stable over multiple days/runs of Memtest, Cinebench r23, 3d Mark, Flight Sim 2020, and 4 hours of COD Vanguard.
P-cores "Sync by Core Usage" ranging from all cores @ 50, to 53 single core.
38 Ring bus.
Default E-Cores.
Haven't tried tweaking anything else yet, but I'm very optimistic that I can squeeze a lot more out of the memory and a little more out of the cpu.
The 12900k's SP is 77, but it doesn't seem to mind.

The only annoyance is that Armory Crate has trouble detecting my dram rgb, even with optimized bios defaults. Asus software is SO bad.

When I switched from the z690 Strix D4 to the Apex, I switched from an NZXT Z73 AIO to the EKWB block, D5 Pump, and 360mm PE radiator.
This custom loop destroys the Z73. Temps are around 10c cooler at load, the cpu never even thinks about thermal throttling.
For the ram not being detected In the BIOS, check to see if SPD WRITE is enabled. It needs to be so the software can access it.
 
Are you running 2 or 4 sticks? 901 is the only bios I haven't tried yet, but I can't even get 4x16GB 3200Mhz stable (ram is 3600Mhz CL 14-14-14-34)
Currently running 2x16. I tested 4x16 on bios 812, didnt test on 901 but should be good also. 812 and 901 are similar for me on 2x16

link to 4x16 test I did

 
Thanks....I had a Hero. But that was recalled, and I got a choice to get an Apex and got it. Starting from the QVL settings is what I have always done and moved the settings from there. Thanks for the wasted response.
Can an Apex really not run memory at XMP speeds? Seems like it should be able to run XMP at a minimum.
Nah wasn't my point, Apex is the XOC board for Asus most people get it to do manual ram overclocking and ln2 overclocking... Yes, there would be a few that do get apex not to do that but I guess it's a rare combo especially with the participants in this forum. Manually plugging in the primary, secondary and tertiaries isn't too difficult to do if it's not in QVL and just play with voltages first to see what gets stable.

DDR5 has only been out for like 2 months people need to not expect it to be as proficient as ddr4 support and compatibility right out the gates especially if they are getting 6000+ speed dimms as those things are unicorns. There are a huge amount of memory manufacturers trying to get into the QVL list of DDR5 at the moment. IMHO the 6-month mark is when there may be more maturity for bios's support and qvl especially since we are going over the christmas/ny/chinese ny and easter holiday periods.
 
For the ram not being detected In the BIOS, check to see if SPD WRITE is enabled. It needs to be so the software can access it.
Just to clarify, the memory itself doesn't have any problems being detected. Armory Crate just has issues with detecting the ram's RGB. To get Armory Crate to detect the RGB, I had to install "G.Skill Trident Z Lighting Control". Then I rescan RGB headers in Armory Crate, and it detects them. Google search reveals issues with " ENE-RGB-HAL drivers". Other's report the issue occurring when Call of Duty Vanguard is installed. I do have Vanguard installed. That might indicate a drm conflict.

Then again, I did port my windows 11 install over from the Strix Z690 D4 to the 690 Apex. I usually reinstall the OS, but didn't have a lot of spare time over the holidays.

Thanks for your reply!
 
any info on what changed? And whats this microcode 12 i read about? Im on 0812bios, is this using an older microcode compared to 0901 and this one listed above? What does a newer microcode bring to the table....?
 
any info on what changed? And whats this microcode 12 i read about? Im on 0812bios, is this using an older microcode compared to 0901 and this one listed above? What does a newer microcode bring to the table....?
The microcode has something to do with AVX 512. Intel wants to disable AVX 512 support with newer microcode.... so it would be better to stick with a BIOS version that contains the old microcode
 
The microcode has something to do with AVX 512. Intel wants to disable AVX 512 support with newer microcode.... so it would be better to stick with a BIOS version that contains the old microcode
i dont think i have a use for avx512 as i dont disable my e-cores..
 
  • Rep+
Reactions: fortecosi
2,221 - 2,240 of 9,907 Posts