New BIOS 1902

[reupens]

It's up for the VIII HERO.

Change log...

[TH="class: width20 bg-gray"][/TH]

MAXIMUS VIII HERO BIOS 1902
Improve system stability

http://dlcdnet.asus.com/pub/ASUS/mb/LGA1151/MAXIMUS_VIII_HERO/MAXIMUS-VIII-HERO-ASUS-1902.zip

[Kiernon]

xator wrote:
After several hours testing this new 1902 here's what I've seen:

-After flashing 1902, XMP on my RAM is totally screwed. In fact, I cannot post, even clearing CMOS, unless I press MemOK! button. When that's done, my RAM posts at 2133Mhz no XMP (these are 2400Mhz memories).
If I enable XMP again, system won't boot, and i have to press MemOK! back again.

Then I have 2 choices:

1-Force mem @ 2133Mhz, no XMP. It works, boots into windows and everything seemed ok, till to the point where on heavy load system locks, and I get a wonderfull BSOD regarding memory.It shouldn't happen, timmins are alright, and hell, I'm underclocking the memory a bit, It should work no matter what...WTF?

2-Force memo @2400Mhz, no XMP. This is the setting I'm using right now. It works right, no problems so far. Timmings are a bit looser than on XMP preset, but It works.

So, to sum things up:

I think XMP detection changes are, obviously, being made. For some of you it may improve, and for some others like me it will totally break the system. I've got a 2400Mhz DDR4 Kingston HyperMax CL15 memory. These are fairly common brand in market, and affordable, so I expect this problem being fixed by Asus soon, or they will face plenty of complaints of people not knowing that this is a "bios update problem".

*Note: For any of you thinking I'm having a RAM HW problem, don't worry. I've tested Memtest on 1701 bios, and several video encoding benchmarks and it is fine. It only happens on 1902, so my HW is correct.

Please ASUS, check this problem ASAP.

Another great follow up, thanks xator.
Good info here. Brand seems to be a non-factor, and it's another 2400 kit affected. Interesting.

I'm fairly sure those who have had issues and posted haven't had "bad RAM" at this point. I know I have Memtested thoroughly like most of you to rule out hardware error, and have zero issues with the RAM itself.

So far, the common denominator seems to be certain kits under 3000Mhz, and specifically 1902 BIOS.

Hopefully someone from ASUS can possibly check into this? At least tell us we aren't crazy. 😛
It's a bit difficult to track things like this down when BIOS changes are always listed as "Improve system stability".

[xator]

Kiernon wrote:
Another great follow up, thanks xator.
Good info here. Brand seems to be a non-factor, and it's another 2400 kit affected. Interesting.

I'm fairly sure those who have had issues and posted haven't had "bad RAM" at this point. I know I have Memtested thoroughly like most of you to rule out hardware error, and have zero issues with the RAM itself.

So far, the common denominator seems to be certain kits under 3000Mhz, and specifically 1902 BIOS.

Hopefully someone from ASUS can possibly check into this? At least tell us we aren't crazy. 😛
It's a bit difficult to track things like this down when BIOS changes are always listed as "Improve system stability".

Finally I had to flash 1701 back again. Not even using 2400Mhz non XMP gave me the stability I needed. After a few hours, random reboots started happening.
I'm back on 1701, XMP working.

As you said, hopefully someone from ASUS will check into this, but please, soon. :cool:

[MFalorca]

Hi,

I had problems with this BIOS and XMP enable.

I've the Gskill Ripjaws V DDR4-2800MHz 2x8GB (F4-2800C15D-16GVR), and never had a problem with other BIOS, until this last one.

Everything at stock defaults (CPU, Voltages, etc!).

Reverting to prior BIOS 1701, fix the problem, and now I can run this kit with XMP enable.

Asus, please fix this!

[MFalorca]

xator wrote:
Finally I had to flash 1701 back again. Not even using 2400Mhz non XMP gave me the stability I needed. After a few hours, random reboots started happening.
I'm back on 1701, XMP working.

As you said, hopefully someone from ASUS will check into this, but please, soon. :cool:

Hi,

I'm one of the guys that had that problem, with BIOS prior to 1701, with Gskill Ripjaws V DDR4-2800MHz 2x8GB (F4-2800C15D-16GVR) kit.

Today, before change the memory kit, I flashed my MB with BIOS 2001, and check again if this issue is still happening, and yes...it was!

Then, I've changed my memory to a new kit I bought, and that was the Gskill Trident Z DDR4-3000MHz 2x8GB (F4-3000C15D-16GTZ).

After installed this new kit, the MB run smooth and without any issue described above!

The Gskill Ripjaws V DDR4-2800MHz 2x8GB (F4-2800C15D-16GVR) was in the initial QVL List of this MB, and I can't understand why Asus doesn't do nothing to fix this, even after so many people claimed about this situation!

[Menthol]

There are two methods to update your bios, bios flashback method and EZ-Flash method, both require formating a small capacity USB drive in FAT 32, unzipping the bios file and copying it to the USB drive from there it changes
USB Flashback method you need to change the name of the bios file, for Hero it would be M8H, then place the USB stick in the flashback port as identified on your I/O plate and pressing the flashback button until you see the LED by the bios chip flash, it will flash slow and steady then increase the flash rate until it stops flashing
EZ-Flash method the USB drive can be inserted in any USB port, boot to bios, navigate to tools-EZ-Flash, click on the drive with the bios, click on flash, it will read the file and ask if you want to update, click yes and let it do it's thing and restart

If your system is working great as is there is no need to update your bios for no reason

[JET_1983]

i just upgrade from old 1302 to 1902
there is no changes

everything working good and blast , also xmp profile working good .
cpu temp and motherboard chipsets temps get down a little

that was good upgrade for me at all 🙂

[alternety]

I have a Maximus 8 Ranger. Win10 is installed. I don't believe it is the anniversary edition. BIOS 1902. I loaded the latest drivers.

System running fine and then I can't boot. One day I rebooted the machine and it went to BSOD with non-helpful information. I spent days figuring out the next step. I created a new bootable C drive (from a non-current backup). I replaced the original C drive and booted. Everything worked. Breathes major sigh of relief. Then later in the day I rebooted: BSOD!

When the machine was rebooting, I got a screen with a scary message. Something to the effect of : Surprise you useless miserable low life customer, we have updated your system with nasty, and perhaps fatal, stuff (you can't prevent) and we are not going to tell you what it is or take into consideration that it may utterly screw your system, because it is really not your machine anymore (it is now ours to do as we wish, no matter how you feel about it) and we will do anything we want to. Love MS.

It appears that whatever MS is updating destroys the system. Any ideas how to recover from this mess? Is it likely that reverting to BIOS 1702 (or another release) will resolve it?

Help greatly appreciated. It is my wife's machine. Now down for a couple of weeks after taking several weeks to go to new mother board and then go from Win7 OEM to Win10 retail without losing programs or data. Not an expert (check with my wife to confirm that). Please - I am getting tired of fighting off the dog for the dinner bowl. And this house is not really big enough for the two of us.

PS - Why does this forum not default to a rational editor format?

[Medico]

First, to try to troubleshoot what is going on, you should post the specifics of her hardware, the Windows 10 version, and the BSOD details. Screenshot will be enough and helpful or written down if you wish to do it that way.

[alternety]

OK. Hardware is as described. No modifications or additions. At this point I have no idea what version of Win10 MS downloaded or what "fixes" may have been installed. What I had, ran just fine. Ripjaws RAM, running at stock speeds. No attempt at overclocking. Regular old stuff.

BSOD says essentially: Win 10 needs to be fixed. No error codes. I think an offer to do a clean install. No links from the failure screen (or the one after if I rebooted again) yielded anything useful. No fix.

I am downloading a Win10 ISO to see if that can be used for anything.

[Medico]

When I said version it is the Windows 10 build. That is located system, in about and OS build. When you had the BSOD, you said there were not memory dump files? Doing clean install may solve those issues especially it happens frequently.