Maximus viii hero bios 1202

[ondersma80]

So... another new bios. Beta 1202 released just 4 days after 1102. So what the heck is still wrong with 1102 that warranted an emergency beta 4 days later? Anyone try it and have thoughts?




edit - edited thread title as bios is no longer a beta releease

[RogueEric]

I just flashed to 1202 this morning without issue. In my current settings I'm running at CPU clock of 4.6 Ghz @ 1.36V in Adaptive mode and 3000Mhz on the RAM at 1.37V and everything seems to be working great. The RAM comes with an XMP profile that is supposed to take it to 3400Mhz, but as I posted in the 1102 thread, anything above 3000Mhz DRAM clock will cause a no-POST and Q-code 55. Also adaptive mode does not seem to be working as HWMonitor and AiSuite both show CPU clock speed and voltage locked to 4.6 and 1.36 and 1.39 respectively. A previous suggestion was to disable SVID support but won't that cause the CPU to revert to manual voltage control anyway?

I'm keeping text logs of the profiles I've tested on my Google Drive here:

https://drive.google.com/folderview?id=0B6GEHtnIDVe8WHFKNmgwLVNNU1E&usp=sharing

[wasyl00]

RogueEric wrote:
I just flashed to 1202 this morning without issue. In my current settings I'm running at CPU clock of 4.6 Ghz @ 1.36V in Adaptive mode and 3000Mhz on the RAM at 1.37V and everything seems to be working great. The RAM comes with an XMP profile that is supposed to take it to 3400Mhz, but as I posted in the 1102 thread, anything above 3000Mhz DRAM clock will cause a no-POST and Q-code 55. Also adaptive mode does not seem to be working as HWMonitor and AiSuite both show CPU clock speed and voltage locked to 4.6 and 1.36 and 1.39 respectively. A previous suggestion was to disable SVID support but won't that cause the CPU to revert to manual voltage control anyway?

I'm keeping text logs of the profiles I've tested on my Google Drive here:

https://drive.google.com/folderview?id=0B6GEHtnIDVe8WHFKNmgwLVNNU1E&usp=sharing

I too have similar config (6700K @4.6 and RAM @3000Mhz, 1.35V using XML profile), but I cannot adjust CPU voltage to my needs. For some reason it doesnt matter if I use manual mode od adaptive and set Voltage to 1.350 the system will bump it to whatever if feel between 1.3 and1.4 and keeps changing. Most of the time sits at around 1.344. Why? I'm validating using AIDA64 with CPUID and dont understand why this is the case.

This is my second BIOS and I still have the same issue. I was trying clearing CMOS, resistalling Asus suite, followed the overclock guide to the word in the other thread. No Luck. Voltage does change to whatever value without my control.

I'm not panicking since I'm properly watercooled but I dont feel comfortable mobo hitting my CPU with such Voltage spikes out of control.

What I'm doing wrong ?

[skybone]

wasyl00 wrote:
I too have similar config (6700K @4.6 and RAM @3000Mhz, 1.35V using XML profile), but I cannot adjust CPU voltage to my needs. For some reason it doesnt matter if I use manual mode od adaptive and set Voltage to 1.350 the system will bump it to whatever if feel between 1.3 and1.4 and keeps changing. Most of the time sits at around 1.344. Why? I'm validating using AIDA64 with CPUID and dont understand why this is the case.

This is my second BIOS and I still have the same issue. I was trying clearing CMOS, resistalling Asus suite, followed the overclock guide to the word in the other thread. No Luck. Voltage does change to whatever value without my control.

I'm not panicking since I'm properly watercooled but I dont feel comfortable mobo hitting my CPU with such Voltage spikes out of control.

What I'm doing wrong ?

Similar problems on my end.

I've yet to really dig into manual config but it seems to be fine. Maybe it's reporting false information? I have 4.8ghz at 3.75v.
I couldn't load a saved profile from previous bios settings, just using gamer mode tuning with a few tweaks of my own so not a huge deal. The rest of the bios is functioning as the last ones were. I'm not in raid mode so I can't comment on that, pretty basic.


I also installed the Nov audio drivers and it fixed the sonic suite 2 compatibility with Win 10 Groove Music, this is good!
now only if the next update of sonic suite 2 could be compatible with logitech g35 headset...

[ondersma80]

scarystuff wrote:
EDIT: The sound is still crap! Still clicks every time an audio channel open or close and still crazy amount of noise on the mic unless you use that filter in Sonic Suite 2 that make you sound metallic instead. I don't understand why this mobo got such good reviews on the sound part. It was one of the reasons I specifically got this motherboard. 😞

I would join or create a new thread about the sound. Most of the reviews for this board reference great sound and I experience great sound - best onboard sound I have heard. Even swapping between an older Xonar DSX and back to the onboard and can't really tell the difference. You should proprobably gather common elements (PSU, other cards, gfx, software etc) between those displeased and see if there is a common denominator.

[Sandbagger]

This bios is a no go for me. Before I had constant error 55's and issues getting into windows in XMP mode using Trident 3000 16 GB x 4 DIMM. Immediately after using the same settings this bios started off with an error 55. Once I did get into windows I ran Prime 95 and errored out within a few seconds. Rebooted error 55 again. Back into windows Prime crashed again.

I reloaded 1102 bios no such issues and prime was fine for 30 minutes.

[Chino]

Sandbagger wrote:
This bios is a no go for me. Before I had constant error 55's and issues getting into windows in XMP mode using Trident 3000 16 GB x 4 DIMM. Immediately after using the same settings this bios started off with an error 55. Once I did get into windows I ran Prime 95 and errored out within a few seconds. Rebooted error 55 again. Back into windows Prime crashed again.

I reloaded 1102 bios no such issues and prime was fine for 30 minutes.

A lot goes on behind BIOS revisions. It is recommended to stick with a BIOS that is stable for your system. Unless a new BIOS specifically solves a problem or offers a new functionality that you plan to use, there is no need to update. Don't just update to get the latest and greatest. 😛

[Sandbagger]

I agree in most cases, but early on I will probably test every bios as I still have a few error codes that pop up when shutting down in event viewer that I am hoping get resolved soon. I notice no impact, but I hate seeing errors pile up with every power cycle.

[scarystuff]

Chino wrote:
A lot goes on behind BIOS revisions. It is recommended to stick with a BIOS that is stable for your system. Unless a new BIOS specifically solves a problem or offers a new functionality that you plan to use, there is no need to update. Don't just update to get the latest and greatest. 😛

Well that is kinda hard since we are not offered any changelog, just a generic message saying the BIOS fixes system stability.

[wasyl00]

scarystuff wrote:
Well that is kinda hard since we are not offered any changelog, just a generic message saying the BIOS fixes system stability.

+1 for changelog. I wish to see what was adjusted/fixed before flashing.

[RogueEric]

+2 for changelog. Especially when the last two updates have identical change captions.