Wierd Shiznit in asus bios

implosiveturnip · 19 Sep 2013 at 09:49

Hi all,

I only posted this here as I PRESUME it's a motherboard fault.

So last night I was doing some light benching in Catzilla, and after hitting the wall with my 670's, I decided to push the cpu a little higher. It's at 4.5 usually, and I have had it upto 4.7 stable before so no biggie, I'll bump it up, run another bench and call it a night.

Now this is when things got a bit odd. So I went into the BIOS and changed my multi to 46 and tried to boot. No issues, booted fine. Fired up real temp and P95 for a quick stability check and my CPU freq was still at 4500. Weird.

rebooted, checked in bios, multi still at 47. Odd I thought, so I played around with every setting I possibly could, even reset to defaults and nothing. The original OC still remained. I raised the BCLK a little to see if it made a difference, which it did, getting me to 4525.7 or something, but the cpu multi would not change no matter what when I booted to windows.

What the dog-poo is going on? Has anyone else come across this or similar before? I can't find anything on google really either.

I have not tried removing cmos battery yet. Will be trying that later. Not convinced it will do anything though. I'm pretty sure it's a ****** bios. It's been a bit odd since I updated a few months back. Nothing that I can really put my finger on until now, but just general quirkiness.

Spec is:

3770k w/h100 x2 noctua nf-f12
asus p8z77-v
16gb corsair vengence lp 1600 c9
120gb ocz solid 3 and 480gb crucial m5
x2 MSI power ed OC gtx 670 2gb
Antec true power new 750w
Fractal design r4

Any thoughts/insight would be helpful.

implosiveturnip · 19 Sep 2013 at 20:28

Anyone?

tipes · 19 Sep 2013 at 20:52

implosiveturnip said:
Anyone?

Try re setting bios to defaults and saving, and exit. re start and go back in to the bios and re load the bios from your downloaded bios - either latest or the bios that last worked ok. Once the bios has updated - boot in too bios and set defaults again, save and re boot back into bios and then put all your usual settings in + your overclock. this should hopefully fix the problem as it sounds like your bios has corrupted. Don't forget to set your correct ram timings as well or use XMP settings for the ram if correct.

Mark

implosiveturnip · 19 Sep 2013 at 21:01

Thanks dude; Bios corrupted. That's what I'm thinking. Just wanted some other perspectives before I go through the ballsache of repairing. Also I don't want to make it any worse! I'm going to clear the cmos and flash latest bios, probably on Tuesday as I'm away at this weekend.

But if anyone has any other theories or similar experiences etc I'd still like to hear about it

unclewebb · 20 Sep 2013 at 01:23

This is a common problem on many Asus motherboards. Make sure you are using the latest bios and load the default settings after you have flashed it before overclocking.

implosiveturnip · 20 Sep 2013 at 08:24

Really? Iv'e been using Asus boards on and off for years and never came across or heard of this. Oh well. I'll post my results on Tuesday as to whether I have it working or not.

I'm going to buy a new battery for the board too and try that first actually. Though I must say I have never once had a CMOS battery go flat.

unclewebb · 21 Sep 2013 at 16:44

Let me re-phrase that. This was a common problem on the Z77 series of Asus motherboards.

Do a Google search for

multiplier stuck asus z77

and you will see that you are not alone.

Make sure you are running the latest bios because this problem on your board has likely already been fixed by Asus. They do a great job of after sales support when they do have problems. I have one of their Z77 Pro boards and I am very happy with it and I still use my Asus P5B from about 7 years ago. It's been to overclocking hell and back many times and it still continues to run 100% reliably.

implosiveturnip · 21 Sep 2013 at 17:09

Thanks uncleWebb. I've no doubt about Asus' quality. And I managed to update the bios before I went away and it appears to have sorted it.

If I hadn't have gotten myself so bloody worked up about the whole thing, I might have thought to have searches for something like that. Instead it was much more retarded and elaborate and returned bugger all results :/

tipes · 21 Sep 2013 at 20:34

Glad your sorted. I take it you upgraded to latest bios?

Mark

implosiveturnip · 21 Sep 2013 at 20:41

Yeah I went to the latest. I don't know how stable it is as I haven't had chance to check it for a decent amount of time yet, and I won't do until Tuesday. Unclewebb was right, I was on the 18.04 bios (I think it was that number) and it was a known problem affecting some users. One thing I did notice, since going to the newest bios, I have to have the pxe option rom enabled in the bios to be able to use the gbe port on the board. And even if it's disabled, it still shows the oprom prompt at post. Just another one of those quirks that I've not been able to put my finger on. I bet by the time I get home it doesn't happen again. This board is haunted.