Hi xychangli,
I have a configuration with the same MB and CPU. It was built a month ago. I observe the same behaviour on boot up.
My 2700X is not overclocked but rather set to negative VCore voltage bias on top of the default settings. I did this because I was not completely satisfied with the overall thermals of the system and wanted to lower the temperature footprint with another 7-10 °C. Virtualization is off. Fast boot is on. AURA lighting is off for all system components.
The GPU in my build is an nVidia GeForce GTX 1060 and it is plugged in directly, i.e. I have NOT used a PCIe 16x riser.
RAM kit is Corsair CMK16GX4M2B3000C15 set to 2933MHz profile.
All in all nothing is overclocked. The build acts as an HTPC / medium stress gaming PC so I do not need to rev it up.
Did a lot of testing while I was tweaking the thermals. Tried dozens of voltage scenarios across the default factory settings, manual input, +bias, -bias. The same amount of effort went into advanced BIOS settings as well.
Pretty much experimented with everything. Q-LEDs did what you are describing the whole time.
To me there are two explanations at this point:
1. MB is supposed to work like that for some insane extremely overly cautious reason, i.e. extensive system integrity testing on every boot sequence
2. This is a BIOS bug that is yet to be fixed despite there being a couple of revisions behind our backs
I am out of ideas and can only pray that this Q-LED thing is not a symptom for a more sinister problem that will catch on us further down the line and, God forbid, cause a hardware issue.
Keep a close eye on upcoming BIOS updates. Let's hope this gets addressed.
Facebook
Twitter
Instagram