New mobo - wont retain o/c settings

Forums › Desktop computing › New mobo - wont retain o/c settings

1 | 2

toejam316

1516 posts

Uber Geek
+1 received by user: 888

Trusted

Lifetime subscriber

#1810405 2-Jul-2017 14:09

From what it sounds like, I think it'd probably be something as simple as the overclock being stable once the system has booted, but not while booting, I imagine due to the extra voltage draw from everything starting up.

Try going through your motherboard and turning off everything you're not using, it may make a difference. The other thing is to see if you can apply the overclock later on in the process, for instance my Z97 has support for an overclocking app with profiles in the OS, so you could apply the overclock after Windows boots.

Join Quic Broadband with my referral - no sign up fee and gives me account credit

Anything I say is the ramblings of an ill informed, opinionated so-and-so, and not representative of any of my past, present or future employers, and is also probably best disregarded.

BiggusDoggus

391 posts

Ultimate Geek
+1 received by user: 4

#1810410 2-Jul-2017 14:50

toejam316:

From what it sounds like, I think it'd probably be something as simple as the overclock being stable once the system has booted, but not while booting, I imagine due to the extra voltage draw from everything starting up.

Try going through your motherboard and turning off everything you're not using, it may make a difference. The other thing is to see if you can apply the overclock later on in the process, for instance my Z97 has support for an overclocking app with profiles in the OS, so you could apply the overclock after Windows boots.

Thanks toejam.

But no, it has nothing to do with the overclock - the double beeping/two splash screen is happening even with no overclocking at all.

It appears it may be the video card. I have taken it out completely, uninstalled all Radeon software etc, and it is booting fine so far.

I seem to recall I updated the GPU bios in it a couple of months back, as I couldn't get the DisplayPort to work with a replacement monitor. I can't be certain at all, but maybe the issues with the old mobo started around then? I don't know for certain.

Is it possible that if I go back to the earlier bios version that may resolve the issue?

Your mother was a hamster and your father smelled of elderberries

BiggusDoggus

391 posts

Ultimate Geek
+1 received by user: 4

#1810512 2-Jul-2017 17:17

Right, so after reinstalling the video card the issue has returned. I rolled back the GPU bios to the previous version, no change.

I have lodged a ticket with Gigabyte as I now literally have no clue as how to fix this.

Your mother was a hamster and your father smelled of elderberries

BiggusDoggus

391 posts

Ultimate Geek
+1 received by user: 4

#1835234 1-Aug-2017 20:51

Right.

So I ended up returning the card to the store under warranty. They sent it away, and 4 weeks later it was "repaired" and sent back.

For those 4 weeks I was running the display through the onboard graphics, with zero issues.

The first full start with card installed - 2 beeps, double splash screen, bios reset. ###%%@#$$$$!!!

However....on a hunch I have changed running my monitor from DisplayPort to DisplayPort to HDMI (card) to VGA (monitor). And....over half a dozen startups and no issues whatsoever (other than the fact the monitor doesn't really like running 1920 x 1080 through VGA - the screen blacks out occasionally).

Is this a "thing"? Is it at all possible that there is either something wrong with the DisplayPort sockets in the card or monitor, or the cable itself? The evidence so far say "yes", but that makes little sense to me.

Your mother was a hamster and your father smelled of elderberries

BiggusDoggus

391 posts

Ultimate Geek
+1 received by user: 4

#1836240 3-Aug-2017 09:04

Confirmed. And what the hell? After all that drama, including replacing the motherboard, it turns out it was simply the DisplayPort cable. Not even the port on the card.

I swapped the cable out for another (higher quality, not-off-ebay) one and the problem has disappeared.

Who would have thought that would be a thing - the cable must have been causing a short or something somewhere, which didn't happen all the time (but at least 80% of the time), and only when fully powering back up.

Odd. It does make a me laugh a little though - what exactly did the supplier "repair", I wonder?

Your mother was a hamster and your father smelled of elderberries

1101

3141 posts

Uber Geek
+1 received by user: 1143

#1836355 3-Aug-2017 10:48

BiggusDoggus:

Odd. It does make a me laugh a little though - what exactly did the supplier "repair", I wonder?

possibly no "repair" done .
Would have been sent back as 'no fault found' & maybee someone said it was "repaired" to keep everyone happy.

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

BiggusDoggus

391 posts

Ultimate Geek
+1 received by user: 4

#1836365 3-Aug-2017 11:03

1101:

BiggusDoggus:

Odd. It does make a me laugh a little though - what exactly did the supplier "repair", I wonder?

possibly no "repair" done .
Would have been sent back as 'no fault found' & maybee someone said it was "repaired" to keep everyone happy.

I did find a bit of thermal paste they hadn't completely cleaned up, so maybe they replaced the GPU...

Your mother was a hamster and your father smelled of elderberries

1 | 2