cancel
Showing results for 
Search instead for 
Did you mean: 

Bug found latest RIVE (not black edition) bios

Faithh71
Level 7
Lately I found some annoying issues with the rampage iv extreme bioses, this is happening since the older bioses already. When I shutdown my PC totally and boot the system immediately afterwards, the system doesn't post at all and the errorcode was always something random. Shutting the PC down and giving it 5mins the time before pressing the power button works fine. Changing some stuff in the bios like offset voltage from - to + same thing no post again or when you disable a few cores or enable/disable hyperthreading.

The bios on default settings no issues but once you set your overclock (offset voltage) this bug is present. I've tested everything to find out which settings cause this. The fix was putting cpu clock gen reset/clock gen filter/internal pll overvoltage from auto to disabled. It's one of those three settings that's causing it.
7,126 Views
11 REPLIES 11

HiVizMan
Level 40
Thank you I will forward this to the bios team.
To help us help you - please provide as much information about your system and the problem as possible.

Raja
Level 13
Faithh71 wrote:
Lately I found some annoying issues with the rampage iv extreme bioses, this is happening since the older bioses already. When I shutdown my PC totally and boot the system immediately afterwards, the system doesn't post at all and the errorcode was always something random. Shutting the PC down and giving it 5mins the time before pressing the power button works fine. Changing some stuff in the bios like offset voltage from - to + same thing no post again or when you disable a few cores or enable/disable hyperthreading.

The bios on default settings no issues but once you set your overclock (offset voltage) this bug is present. I've tested everything to find out which settings cause this. The fix was putting cpu clock gen reset/clock gen filter/internal pll overvoltage from auto to disabled. It's one of those three settings that's causing it.



This isn't a bug. It means your system isn't stable with the PLL settings at the OC you are applying or on auto. SImply adjust to the required value and run your system. There is no magic bullet with these settings - each CPU is different.

Raja@ASUS wrote:
This isn't a bug. It means your system isn't stable with the PLL settings at the OC you are applying or on auto. SImply adjust to the required value and run your system. There is no magic bullet with these settings - each CPU is different.


I think you misread or I haven't explained it properly. I don't get display when I'm booting the PC right after the pc fully shutdowns, but if there is a pause of 5mins between the shutdown & booting it does have display so it's not related to my overclock. The CPU PLL voltage is at 1.80V manually set but that's totally different than the Internal PLL overvoltage where you only can set Auto/enabled/disabled. Usually the internal pll overvoltage is needed when you go 4.9GHz but I'm only using 4.2GHz.

I'll try explaining again.

So I tried to find out which setting was causing this but I gave up and my last attempt was disabling internal pll overvoltage/cpu gen reset & filter at once and then my issue was fixed, hence why I said it's one of those three settings. Few minutes ago; I tested all of three settings individually out and it's definitely internal pll overvoltage causing it at auto.

Internal pll overvoltage wasn't there with older bios revisions if I'm not mistaken

Raja
Level 13
These three settings are all interrelated behind the scenes hence my advice.

The way the board POSTs and trains memory after a given point in standby will affect what is required to get it to POST again. Depends on the CPU, memory and what the memory controller likes.




You said it does not happen at stock in your earlier post and now you say it's not related to your overclock.

This is was what you said in your first post: "The bios on default settings no issues but once you set your overclock (offset voltage) this bug is present."

My answer above stands. At your OC, set things up as you need them to be for the system to be stable. Different CPUs may need a different setting for any of these PLL related parameters (Clockgen filer, internal PLL OV etc).

Raja@ASUS wrote:

My answer above stands. At your OC, set things up as you need them to be for the system to be stable. Different CPUs may need a different setting for any of these PLL related parameters (Clockgen filer, internal PLL OV etc).


No offense, this doesn't make sense at all. As I clearly said it won't give display after pressing the power button a second later BUT if I wait 5mins instead of a second it does give display.

My 2nd argument; moving it from auto to disabled fixes this issue. Even at auto/enabled or disabled I pass every stresstest for 12hours+ with this overclock.

Praz wrote:
When overclocked if you need to set internal pll overvoltage a particular way for stability then that is the setting you should use.


Internal pll overvoltage was just never needed unless you aim for 4.7GHz, basically if you couldn't get in Windows; enabling PLL overvoltage allows you to get in Windows. I need this setting for 4.9GHz which I never use anyways

Praz
Level 13
As Raja has wrote a couple of times now this is due to instability. A bug is something most everyone would experience using similar settings. When overclocked if you need to set internal pll overvoltage a particular way for stability then that is the setting you should use.

FireRx
Level 11
Agree wih Raja,
The same will occur on the R4E with Unstable settings. Each CPU is unique in this regard. :cool:
Intel Core i9 103900KS
Asus Maximus Z790 Extreme [bios 2801]
LG (34U97-s) Monitor 3440 x1440
Nvidia RTX 3090 FE
Windows 11 Pro
64gbz Memory

Praz
Level 13
You can beat yourself up about this but it will not change anything. When overclocked if you need a setting at a particular value you only have 3 choices. Set the value as needed, don't overclock to the point this setting becomes an issue or live with the instability that results from the use of the improper setting. Passing stress tests are only one indication of stability. Being able to actually use the system as well as proper bootup and shutdown are also stability related. Personally, I don't see Raja acting on this non-issue. I suggest you contact ASUS support for your region if you are still convinced this is a problem.

Praz wrote:
You can beat yourself up about this but it will not change anything. When overclocked if you need a setting at a particular value you only have 3 choices. Set the value as needed, don't overclock to the point this setting becomes an issue or live with the instability that results from the use of the improper setting. Passing stress tests are only one indication of stability. Being able to actually use the system as well as proper bootup and shutdown are also stability related. Personally, I don't see Raja acting on this non-issue. I suggest you contact ASUS support for your region if you are still convinced this is a problem.


This doesn't make sense either. Again for the 10th time, booting the system after a longer period it works fine but immediately afterwards it doesn't. It's common sense that if It wouldn't boot after pressing the power button a second later, it wouldn't boot either after 5 mins.

The default setting is auto, at the default settings it doesn't kick in at all but when you start OC'ing it does. I have the same issue going changing it from auto/enabled.

This is just a bug