OFFICIAL Bios ver. 2004 will not allow bios flashback THREAD

[mr_allroy]

Hi all,

It looks like at least a couple of us have an issue flashing back to earlier bios with ver. 2004. Both with the UEFI method and the usb flash back will not work (3 usb drives and none worked). The bios setting to allow this is enabled. I have a Z690 Hero.

If you have this issue please reply to this thread so we can keep all the info in one thread. It will help if you list your MB model as well.

Thanks
( I should also note that the voltage issues found in ver 1720 appear to be fixed in 2004.)

UPDATE - It seems that real time ram timings can't be changed using Memtweakit or any other tool. Was working on 1601. Can anyone else confirm this?

[TSportM]

Read the post, its very clear 2004 is not reversable READ

[AwenMilano]

TSportM wrote:
Read the post, its very clear 2004 is not reversable READ

hi there, i know like the title it say not reversable. i just want to share my EXPERIENCE.
with my combination of hardware 2004 was very unstable
still have xmp problem for me. xmp on = crash gaming + bsod
now i try xmp 1 but lowering speed in to 5600
seems stable now. 5800 also throw an error

[bass_junkie_xl]

bios 1504 strix wifi d4 ddr4 board zero issues @ 54 all core 51 ring dual rank 4133 mhz cl 15-15-15-35 . so far bios 1504 is solid . i will not try 1600 - 2004 bioses at all thanks guys for the warnings

[mr_allroy]

I can't seem to change my ram timings in real time anymore using MemTweakIt with ver 2004. I have been able to with all other bios. Can someone confirm this please?

[bscool]

mr_allroy wrote:
I can't seem to change my ram timings in real time anymore using MemTweakIt with ver 2004. I have been able to with all other bios. Can someone confirm this please?

Still works for me on z690 Apex with bios 2004.

Edit I modded the bios and have u code 15 so not sure if that makes any difference.

[iTriedOverclock]

Falkentyne wrote:
Microcode 15 works in 2004 if you delete the other microcodes and insert it. AVX512 works. bscool has it modded already. Just don't expect raptor lake to work if you delete all the microcodes. None of this flashback lockout has anything whatsoever to do with Intel and AVX512...

Thanks for pointing out they also replaced the microcode version with version 15. I understand how microcodes work, I run a 9900k in a Maximus VIII Formula. I just never saw any confirmation in this thread of AVX-512 working with this bios and Intel has been persistent with disabling it on Alder Lake. Does Asus still have the AVX512 options in bios 2004?
*

bscool wrote:
Still works for me on z690 Apex with bios 2004.

Edit I modded the bios and have u code 15 so not sure if that makes any difference.

Just want to confirm AVX-512 is still working on bios 2004?

[Merrick]

My experience is quite a bit different. I'm not doing any overclocking or anything like that, so since updating to 2004 I am not seeing any of the problem most people are reporting here. But what did happen to me is that my computer will no longer boot from the case power button after shutting down. So here's what happens:

1. Shut computer down through OS.
2. Push case button to restart - audible "click", fans get a slight kick - and that's it. Nothing else happens.
3. Repeat 2 as many times as you want - click, fan kick - then nothing.
4. Switch power off at the power supply, wait a few seconds, switch power back on at power supply.
5. Push case button - "click" - normal boot.

I installed the Intel ME update at the same time, so it is unclear which of the two is doing it or if it's the two together.

On suggestions I have cleared CMOS, replaces CMOS battery, reinstalled MEUpdate and BIOS. No help.

It has been suggested my ROG Thor Platinum 850W PSU (that boarsts "100% Japanese capacitors" in it's ad literature) has failing caps. I would think in that case I would have this problem "sometimes" and that cycling the PSU would fix the problem perhaps most of the time, but might need to be done more than once on occasion - nope. With everything I have tried on my own and everything Asus has had me try I must have recycled this machine over 50 times. The case power button fails EVERY single time as described and the PSU recycle fixes it first time EVERY single time.

Asus told me to RMA it. Seriously? The email directing me to RMA even says:

"Standard repair TAT is 7-10 business days, not including weekends or shipping time. Please note, the global outbreak of the coronavirus may result in delays that impact repair times, due to part availability and staffing limitations. Impact depends on the product and the specific case. We will do everything possible to get your product back to you as soon as possible. We’re sorry for any inconvenience caused."

So, seriously, tear my computer down and hope I'm only without it for a few weeks if I am lucky?

I'm at least waiting for next month's BIOS to see if that fixes it (there have been 5 BIOS updates in 6 months - so there will be one in October, too.)

Asus needs to step up quite a bit better on this. Hopefully they'll get a netter BIOs out in a week or so that fixes many of these problems.

[Merrick]

I should add, the information posted for the MEUpdate tool is as follows:

Intel ME
Version 16.1.25.1885v2
2022/09/16 9.15 MBytes
MEUpdateTool
Intel has identified security issue that could potentially place impacted platform at risk.
Use ME Update tool to update your ME.
*We suggest you update ME Driver to the latest Version 16.1.25.1885v2 simultaneously.
Please download the file and check the MD5 code first.
MD5: 83746cffb3d3bda45277db25d5318283

But when I check the MD5 value:

C:\Users\Merrick\Desktop\New folder (2)>fciv MEUpdateTool_16.1.25.1885_T.zip
//
// File Checksum Integrity Verifier version 2.05.
//
580b0a2a2647111b53de3516a659db7c meupdatetool_16.1.25.1885_t.zip

OK. So I'm pretty frustrated I didn't check that first. I wouldn't have installed it if I did. I'm just wondering if it could have done enough damage that it really can't be fixed by flashing or installed better BIOS/software on top of it won't fix it.

[RogScott]

Merrick wrote:
I should add, the information posted for the MEUpdate tool is as follows:

Intel ME
Version 16.1.25.1885v2
...
Please download the file and check the MD5 code first.
MD5: 83746cffb3d3bda45277db25d5318283

But when I check the MD5 value:

C:\Users\Merrick\Desktop\New folder (2)>fciv MEUpdateTool_16.1.25.1885_T.zip
//
// File Checksum Integrity Verifier version 2.05.
//
580b0a2a2647111b53de3516a659db7c meupdatetool_16.1.25.1885_t.zip

Same here. Hash for zip does not match the ASUS description (instead, I get same hash as @Merrick did above).

I also checked MD5 of several files inside the zip, including the MEUpdateTool.exe and the ME.bin, thinking maybe ASUS' MD5 was for one of those files rather than the entire ZIP file -- but none that I checked match the MD5 in the download page description.

Did ASUS post the wrong file?

[nostalgiafactor]

RogScott wrote:
I also checked MD5 of several files inside the zip, including the MEUpdateTool.exe and the ME.bin, thinking maybe ASUS' MD5 was for one of those files rather than the entire ZIP file -- but none of them match the MD5 in the download page description.

Did ASUS post the wrong file?

Same question. What is up with the MEUpdatetool update on Asus' page?