Come on man!!! How many times don't fix whats not broken!!!
Dino is spot on standard rigs you don't need to continually update Bios unless it specifically says in the change log that it fixes a problem you have.
**Official Gigabyte Z87X-OC Discussion Thread**
- Thread starter Nelly
- Start date
Come on man!!! How many times don't fix whats not broken!!!
Dino is spot on standard rigs you don't need to continually update Bios unless it specifically says in the change log that it fixes a problem you have.
Hi 8Pack,
Ok,ok I hear you Lol - have learned my lesson, but the rig is going great, so shall stick with Xo2. How u doing 8Pack?
Mark
I had to RMA my board on Thursday, on the phone they asked if I had the 860i PSU and found it strange that I had the problem with the 860 version. I'm hoping the replacement board won't have the same issue otherwise it will mean switching to a different board (board bought 2 weeks ago, PSU bought in May).
My problem was the power button (board/case) when pressed once would power up the fans (full speed), LEDs, optical drive and I assume SSD/HDDs. Pressing it a second time would then power on the motherboard and allow it to boot to bios.
The only way to turn everything off was to switch the PSU off at the back (or unplug it) as shutting down or holding the power button in would only turn off the motherboard but leave everything else running (and ramp the fans up to full speed).
Update:
I've had so many false positives that I'm taking this with a pinch of salt. Firstly all RAM I tried including the old RAM has resulted in boot loops.
Right, so I decided I could not get to the bottom of the boot loop issue and to RMA the board. But thought I'd give it another go before taking out the board.
Steps:
1) I unplugged everything and removed all except the cooler/RAM. It boot looped.
2) So I reset the CMOS - no boot loop.
3) plugged in the monitor into HDMI motherboard - no boot loop.
4) plugged the graphics card into the second slot and moved HDMI to graphics card - no boot loop.
5) plugged in second monitor into DVI port - boot loop straight away.
6) removed second monitor - boot loop.
7) Loaded optimized settings - no boot loop
I've been running like this now since yesterday and there is no sign of boot loop so far.
So, is it possible the graphics card could be causing this? Some kind of compatibility issue?
I've had so many false positives that I'm taking this with a pinch of salt. Firstly all RAM I tried including the old RAM has resulted in boot loops.
Right, so I decided I could not get to the bottom of the boot loop issue and to RMA the board. But thought I'd give it another go before taking out the board.
Steps:
1) I unplugged everything and removed all except the cooler/RAM. It boot looped.
2) So I reset the CMOS - no boot loop.
3) plugged in the monitor into HDMI motherboard - no boot loop.
4) plugged the graphics card into the second slot and moved HDMI to graphics card - no boot loop.
5) plugged in second monitor into DVI port - boot loop straight away.
6) removed second monitor - boot loop.
7) Loaded optimized settings - no boot loop
I've been running like this now since yesterday and there is no sign of boot loop so far.
So, is it possible the graphics card could be causing this? Some kind of compatibility issue?
Z87 XOC taking out Heaven world record for 3 GPU.
This board is very efficient in any config upto and including 3 cards as you can see from this result.
Results:
3 Card WR
3 x 290X 1185/1550
Gigabyte Z87 OC
4770K 6.2 DDR3 2600
Screeny
Bench Video
http://youtu.be/i_09C6BvtP4
HWbot link
http://www.hwbot.org/submission/246...e_preset_3x_radeon_r9_290x_8548.87_dx11_marks
4 Cards Rock stable too!!!
4 290X 1180/1550
Gigabyte OC
4770K 6.2/DDR3 2600
This board is very efficient in any config upto and including 3 cards as you can see from this result.
Results:
3 Card WR
3 x 290X 1185/1550
Gigabyte Z87 OC
4770K 6.2 DDR3 2600
Screeny
Bench Video
http://youtu.be/i_09C6BvtP4
HWbot link
http://www.hwbot.org/submission/246...e_preset_3x_radeon_r9_290x_8548.87_dx11_marks
4 Cards Rock stable too!!!
4 290X 1180/1550
Gigabyte OC
4770K 6.2/DDR3 2600
Last edited:
When I connect only the DVI port the PC goes into boot loop. So it is definitely that which is causing the issues.
Can't believe it's taken me this long to figure this out.
I've bought:
new PSU
new CPU
new Motherboard.
At least I now have a very powerful HTPC.
Edit:
Correction it's displayport and not DVI port as I've written in my post.
Edit2:
I now have both monitors working in dual setup. Both plugged to displayerports. It seems the issue was cable/adapter related. I had mini-displayport to displayport adapter which I removed and bought 2 new mini-displayport to displayport cables. All is well so far.
Last edited:
hello all i had planed to buy this board, but just as i was about to buy the did the black friday deal on the z87-oc force mb so i got that instead.
this is a upgrade from my old asus roc mb and q6600 running at 3.6 which ran for the guts of 7 years 24/7. So far i am well pleased with what ive got, and if it does as well as the q6600 it be a hell of a chip.
a few question's
on the mb there are 2 power connections atx_12v and atx_12v_2x4. my old Enermax Galaxy 1000W ATX2.2 Modular PSU only has connection for the atx_12v_2x4. is it ok just to use the atx_12v_2x4, or if i am to get a stable OC will i need a lead for the atx_12v as well.
the MB came with the F4 bios is this a good enough bios for what i want (i stable OC that can run 24/7) or should i flash it to a different one
this is a upgrade from my old asus roc mb and q6600 running at 3.6 which ran for the guts of 7 years 24/7. So far i am well pleased with what ive got, and if it does as well as the q6600 it be a hell of a chip.
a few question's
on the mb there are 2 power connections atx_12v and atx_12v_2x4. my old Enermax Galaxy 1000W ATX2.2 Modular PSU only has connection for the atx_12v_2x4. is it ok just to use the atx_12v_2x4, or if i am to get a stable OC will i need a lead for the atx_12v as well.
the MB came with the F4 bios is this a good enough bios for what i want (i stable OC that can run 24/7) or should i flash it to a different one
he he another 1000W galaxy user still going strong! Same here, though i'm on the none force board so can't help you out there.
Just nice to see someone else with the same PSU. Mines seen a lot of hardware changes and still doesn't break a sweat!
Just nice to see someone else with the same PSU. Mines seen a lot of hardware changes and still doesn't break a sweat!
Soldato
- Joined
- 25 Apr 2010
- Posts
- 5,289
- Location
- Ipswich
Just bought this board with my new build - I have also got some Avexir 2933mhz Ram along side this.
Going from the specs I should not have any issues but to make sure has anyone else here had problems running at that speed?
Going from the specs I should not have any issues but to make sure has anyone else here had problems running at that speed?
Just had a strange error, after running the windows hardware score test, on the subsequent boot up the motherboard wouldn't get past BIOS without having to reset to defaults as it said something about my hardware having changed.
So I have done this and then reset all my overclock settings to get everything back to normal and everything seems to be rebooting fine. Actually I can now have a stable O/C of 4.4 Ghz with a 1.275 VCore and previously it had to be 1.3VCore. Has my mobo updated itself without me knowing about it?! I am quite confused as it would BSOD at anything less than 1.3V.
Has this happened to anyone else at all?
So I have done this and then reset all my overclock settings to get everything back to normal and everything seems to be rebooting fine. Actually I can now have a stable O/C of 4.4 Ghz with a 1.275 VCore and previously it had to be 1.3VCore. Has my mobo updated itself without me knowing about it?! I am quite confused as it would BSOD at anything less than 1.3V.
Has this happened to anyone else at all?
Last edited:
Can somebody help me out? I'm trying to connect 5 fans (Corsair PWM fans) to the motherboard. I have a PWM fan splitter but I'm having a nightmare trying to get it to work.
If I plug the fan splitter into one of the SYS_FAN headers on the motherboard, all the fans connected to the spitter run at max RPM (the fans slow down properly if connected directly to the header). If I put the splitter into the CPU_FAN header, and connect one fan to the splitter, it runs fine, however the more fans I add to the splitter the faster they run.
For example, with 1 fan connected (to the master connection), it runs at 1400 RPM. Then with 2, 3, 4, and 5 fans connected they all run at 1400, 1500, 2200, 3100 RPM respectively.
I have no idea why this is happening, whether it's an issue with the motherboard or the splitter. If anything, I'd have thought adding more fans would reduce RPM as the power is being split among more fans...
Any help appreciated.
If I plug the fan splitter into one of the SYS_FAN headers on the motherboard, all the fans connected to the spitter run at max RPM (the fans slow down properly if connected directly to the header). If I put the splitter into the CPU_FAN header, and connect one fan to the splitter, it runs fine, however the more fans I add to the splitter the faster they run.
For example, with 1 fan connected (to the master connection), it runs at 1400 RPM. Then with 2, 3, 4, and 5 fans connected they all run at 1400, 1500, 2200, 3100 RPM respectively.
I have no idea why this is happening, whether it's an issue with the motherboard or the splitter. If anything, I'd have thought adding more fans would reduce RPM as the power is being split among more fans...
Any help appreciated.
Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,263
- Location
- Cornwall
Sorry if this has been asked before, but on this board, how do you adjust QPI/VTT voltage?
I occasionally get some BSOD with the code 0x00000124, which some suggest could be QPI/VTT voltage related.
I occasionally get some BSOD with the code 0x00000124, which some suggest could be QPI/VTT voltage related.
Soldato
- Joined
- 6 Jan 2013
- Posts
- 22,180
- Location
- Rollergirl
I'm getting BIOS freezes again. It only happens in console mode. Anyone else getting that?
Have you tried re flashing the bios to the same version - which bios are you on currently?
Mark