Modded bios Rampage VI
Printable View
-
02-26-2021, 03:40 AMBigJohnny
Ive not had a double boot on my R6EE since I got it. Making me wonder if its hardware and not BIOS. Thats 401, 505, 603 and 702. I loaded the 901 stock variant and i just got hotter temps and a performance drop. Running 702 MC39 variant and working great. Tried a bunch of stock and modified and never a double boot with the exception of the first boot which is normal to get 2 if not 3. After that smooth sailing.
-
02-26-2021, 04:04 AMdennys2009
-
02-26-2021, 04:37 AMdennys2009
Those problems that I describe with R6EE, they have already been voiced in this branch
https://rog.asus.com/forum/showthrea...st+Encore+bios
especially please see it DESERTUM_0, restsugavan and others
And since July 2020, the problem has not been solved. -
02-27-2021, 05:16 AMBigJohnny
If I kill the power its the same as an initial set up and it will do a double boot every time on any of these boards. You are starting all over with memory training ETC. That's by design and is not a BIOS issue. Aura gets hung up that's one of the methods to clear it is to uninstall the software then kill the power and that reinitializes everything. I don't kill the power intentionally or even on accident. Machine is backed up with a 2200Va dual conversion online APC smart UPS.
But yeah, flip the switch or pull the plug it has to reinitialize the moment you kill the 5V standby power. Normal behavior. Want to prevent that? Dont kill the power to the PSU and take away the 5V standby. I got the same on an R6E and R6EE. Pull the plug and a lot has to happen coming back up, its going to do a double boot every time and not a fault, by design. Leave it with PSU on and plugged in and it doesn't happen. Ive not ever unplugged or switched off the CPU as a normal routine, only when I have my fingers in there messing with something.
Theres a lot that goes on on the initial power up from dead with 5V standby power removed. Our definitions of cold start evidently are different. -
03-04-2021, 02:36 AMInt8bldr
more uCodes again! this time only for core i9 109x0 XE
They continue to update frequently now... makes you wonder what the heck intel is doing, releasing a new ucode update every month... maybe they should just get it right once and for all, i.e. (safely) enable TSX again, improve cache latency performance instead of making it slower with every release, etc.
109x0 XE: ucode 3006 = cpu50657_platBF_ver05003101_2021-01-15_PRD_40827521
0x3101 - 0x3006 = 251 (decimal) build increments! lots of updates but what is completely unclear?
link here: https://www.win-raid.com/t3355f47-In...html#msg139167 -
03-04-2021, 04:44 AMrestsugavanREBAR Option for X299Attachment 87982
They'd working for RE-BAR feature for X299 platform to support NVIDIA RTX 3000 Series and AMD RDNA2 6000 Series GPU.
New microcode release oftenly mean your CPU was up to date feature and had recently patch for security issue.
Same as Windows Insider Build update weekly bring new features and lastest security patch. -
03-04-2021, 07:48 AMInt8bldr
Let's hope it's Rebar related uCode update. But wasn't that a bios main code update rather than uCode update. there is another thread on that so...
Also not buying that Intel need to do constant security patches at the uCode level. If it is that, then that just make things worse for intel - releasing a cpu full of holes that need to fixed with a monthly uCode like windows - nuts! s/w has several magnitudes more complexity compared to a CPU, so CPU's should not need a monthly security uCode patch unless it's extraordinarily poorly designed and engineered - I do not think the core i9 X series is poorly engineered at all, quite the opposite. that's why I do not get why they need to do monthly uCode updates... are they under so much pressure? They should stop this salami tactics, do a thorough review, design and code it right once and for all, release and be done with it in one final build. -
03-04-2021, 01:37 PMrestsugavan
Windows kernel each week trying to optimize it for best performance for all vendors CPU. Both Intel and AMD also ARM devices provided their microcode for its own products. Windows teams following their steps with code rewritten to take advantage of those microcode as max as they could.
Not only Core X i9 Series getting this issue.
Since Atom through Xeon class CPUs also the same.
Technology were developing every day. -
03-05-2021, 11:33 PMeinsindrei
Latest Modules
Latest Microcode 3101
Based on 0701 (from shamino)
Save your Profile before, needs to be flash via bios flashback (Note, CMOS Clear before)
Modules
EFI Intel RST for SATA - 18.31.1.5224
OROM Intel RST for SATA - 18.35.0.4635
EFI Intel VROC for SATA - 7.5.0.1030
EFI Intel VROC with VMD - 7.5.0.1030
OROM Intel VROC for SATA - 6.2.0.1034
OROM VBIOS SKL-KBL - 1049
EFI Intel Gigabit UNDI - 0.1.00
OROM Intel Boot Agent CL - 0.1.16
Microcodes
Xeon / CPUID 50650 / 8000002B / 2016-02-08
Xeon / CPUID 50652 / 80000037 / 2017-05-02
79x0xe / CPUID 50654 / 02006B0 / 2021-01-15
99x0xe / CPUID 50656 / 4003006 / 2020-12-31
109x0xe / CPUID 50657 / 5003101 / 2021-01-15
Link https://drive.google.com/file/d/1Av9...ew?usp=sharing -
03-06-2021, 01:13 AMInt8bldr
Thanks!
There is a newer uCode for 79x0 XE
New_cpu50654_platB7_ver02006B05_2021-01-15_PRD_0BFAA366
https://www.win-raid.com/t3355f47-In...html#msg137981
same same massive revision increase as 109x0 XE uCode 3101 you included in the BIOS. Think those two are kind of "siblings".