cancel
Showing results for 
Search instead for 
Did you mean: 

Deleted

MoKiChU
Level 40
430 Views
79 REPLIES 79

kens30
Level 11
Sorry to hear you are having this problem jeffrds but you should always load optimized defaults before updating your BIOS.
From what i understood you where on 1301 Bios and jumped directly to 1704 that was a big mistake and i hope you have not corrupted your bios.
You should have updated to BIOS 1401 first through your bios (no usb flashback) as it contained a CPU microcode and ME firmware update.
I Think that is your problem right there.

The only thing i can suggest is to use usb bios flashback to go back to version 1301 (always loading optimized defaults before and after update).
then next update to 1401 then 1602 and finally 1704 all through ASUS EZ Flash 3.

kens30 wrote:
Sorry to hear you are having this problem jeffrds but you should always load optimized defaults before updating your BIOS.
From what i understood you where on 1301 Bios and jumped directly to 1704 that was a big mistake and i hope you have not corrupted your bios.
You should have updated to BIOS 1401 first through your bios (no usb flashback) as it contained a CPU microcode and ME firmware update.
I Think that is your problem right there.

The only thing i can suggest is to use usb bios flashback to go back to version 1301 (always loading optimized defaults before and after update).
then next update to 1401 then 1602 and finally 1704 all through ASUS EZ Flash 3.


LoL don't overdo it, you can flash from an older bios. if it wasn't possible or not a good idea they would have told so in the release notes.
And if you dont run too crazy unstable oc's you can update perfectly without loading defaults. and if all else fails you can always reflash. even if you totally break it you can flash the dead mobo via the special usb port.

---SK--- wrote:
LoL don't overdo it, you can flash from an older bios. if it wasn't possible or not a good idea they would have told so in the release notes.
And if you dont run too crazy unstable oc's you can update perfectly without loading defaults. and if all else fails you can always reflash. even if you totally break it you can flash the dead mobo via the special usb port.


I may did overdo it bit but i have seen various cases like his updating Bios with OC not 100% stable especially ram causing various issues like he is.
You cannot restore a dead mobo with reflasing BIOS.
BTW the error code is RAM related so i suggest you check your ram 1 stick at a time with HCI memtest.

PerpetualCycle
Level 13
You can update the BIOS through flashback and it will update the microcode. When I flashed 1704 through flashback on my code X, it first updated the ME firmware (surprise to me), then the BIOS).

It is pretty common to have to redo over clocks with a BIOS update, and this one included BIOS tweaks, ME firmware, and microcode. I had to tweak my memory and CPU overclock after the update, though my issue was stability - nothing as serious as you are experiencing.

I see old save your configuration to USB, then reflash using flashback.

ROG Dark Hero Z790 | 13900KS @5.7 GHz | g.skill 2x48GB 6800 MT/s | ROG Strix 4070 Ti | EK Nucleus 360 Dark | 6TB SSD/nvme, 16TB external HDD | 2x 1440p | Vanatoo speakers with Klipsch sub | Fractal North XL case

PerpetualCycle
Level 13
It always has done a number of steps to update the BIOS itself. In the past though, it never printed out statements that it was updating the BIOS at each restart. This is new and I think made the multiple restarts more noticeable.

ROG Dark Hero Z790 | 13900KS @5.7 GHz | g.skill 2x48GB 6800 MT/s | ROG Strix 4070 Ti | EK Nucleus 360 Dark | 6TB SSD/nvme, 16TB external HDD | 2x 1440p | Vanatoo speakers with Klipsch sub | Fractal North XL case

Flourgrader
Level 7
Hi everyone,
I have Version ROG MAXIMUS X HERO BIOS 1602
2018/07/10 Installed.
I want to replace it with version 1704
2018/10/02
If I replace the BIOS I will loose all my customized settings.
I have saved from within the BIOS the current settings to a .CMO file.
My question is:
If I replace the BIOS to version 1704
will I then be able to load in the
.CMO file with my previous BIOS settings.
So, I don’t loose my customized settings?
Thanks

Flourgrader wrote:
Hi everyone,
I have Version ROG MAXIMUS X HERO BIOS 1602
2018/07/10 Installed.
I want to replace it with version 1704
2018/10/02
If I replace the BIOS I will loose all my customized settings.
I have saved from within the BIOS the current settings to a .CMO file.
My question is:
If I replace the BIOS to version 1704
will I then be able to load in the
.CMO file with my previous BIOS settings.
So, I don’t loose my customized settings?
Thanks


In the same bios screen where you saved your CMOS file., You have an option to save a text file. This file will record all your settings and can be an excellent basis for rebuilding your overclock.
NAME THE SANDWICH: – White Bread, Lots of Baloney, Russian dressing and served with a small pickle.?


Intel Core i7 8700K @5.1 Stable Delidded
Asus Maximus X Code

16 GB
G skill TridentZ DDR4 ​4266 (PC4 34100)
Corsair HX1000i digital
EVGA 1070 GTX TiSuperclocked+
Samsung NVMe SSD 960 pro M. 2
Samsung 860 Pro
Watercooled with EK block radiator fans etc.

no1yak
Level 8
No you can't use the .CMO file from a previous bios. Any up date to the bios will remove all previous setting. You can make a text file of your settings and then print it out so you don't have to remember what your settings were.

no1yak wrote:
No you can't use the .CMO file from a previous bios. Any up date to the bios will remove all previous setting. You can make a text file of your settings and then print it out so you don't have to remember what your settings were.


WTF then whats the frikkin point of any kind of setting backups or saves if they are gone during updates??
Dargus Maximus
~Explorer ~Engineer ~Guide
My Youtube channel - PC modding, streaming, gaming

KeksimusMaximus wrote:
WTF then whats the frikkin point of any kind of setting backups or saves if they are gone during updates??

Good question.
Most likely the answer: "no money" for testing and implementing BIOS updates as they should.