Can anybody show what performance gain you get by overclocking the memory?
Intel specs show Ivy Bridge CPUs are only good to max DDR3-1600. Samsung M379B5273DH0-YK0 shows sweet spot on my UD5H is 8-8-8-22 /1600 with trivial perofrmance gains above 1600.
I simply prefer disabling in bios any unused items, such as the secondary Atheros ethernet port and the firewire controller.Quote:
Originally Posted by sin0822
Whenever a discrete graphics card gets installed, I would then disable the onboard Intel HD 4000 graphics.
Beta bios version F9o works fine, so something new was introduced starting with F9q and later.
Yea I am aware it is less devices pinging the CPU it is helpful for extreme overclocking in some cases but in others doesn't make a difference, like I got 116.95mhz bclk and i didn't disable anything, not even TB. I will put in a request to check it out.Quote:
Originally Posted by vailr
Performance gains from OCed memory are only really noticeable in benchmarks. There really is very little real world advantage, but it is fun and allows you to push things further,t hat is why people OC. Density in memory is more important for daily use than speed.Quote:
Originally Posted by cab
Thank you. When don't they show density in the part # then?Quote:
Originally Posted by sin0822
I have Samsung M379B5273DH0-YK0 and g.skill F3-1600C8Q-16GAB -- which is denser?
Hi guys jus checkin i did things right.
Backup Bios = F8 (OC setting allready set)
Main bios flashed thru Q-flash in bios to F10x not @-Bios (should i have done?)
--- Things i disable when i OC.. Marvel ports, Audio, Wake on LAN, firewire, C1/C3
--- Enable or disable Intel Virtualization tech. (Does this help in any way?)
Everthin flashed fine...rebooted..I always press ESC to go into Advanced bios then F7 to load defaults..Enter...then F10 to Save n Exit..reboots shuts down once as allways then checked bios version F10x correctly displayed. Im sure Dram was showing 1.35V i then booted into windows...
Shutdown...CLR onboard CMOS
Enter Bios Dram showed 1.66 or 1.65 v which i think has allready been logged. I then went on to change to my OC settings. I set dram to 1.5v 2133 10 10 10 28 & 30 1N set VTT IMC (1.095v 1.1v) also tried (1.145 1.150)
Got the deadly beeps lots of boot loops. Then i noticed my dram voltage stuck on 1.47v (this is setting from backup bios) no matter what i select the voltage never changed. I did try 2 x 4GB 2133 which worked (tried HCI memtest no errors) 4 sticks givs me errors in 2 secs
Is F10x for Sammy + IVY only?? should it work with SB aswell ??
I know my max wud be DDR 2133 id be happy with that. Currently on 1866 9 9 9 27 1n no probs.
Need to check the following::
Does both Backup & Main have to be on F10x for the sammy fix to work??
Is Q-Flash the best way to flash ? (ive never had issues with this method)
Voltage for DDR 2133 10 10 10 28 1N is 1.5V ok ??
Any help wud be greatly appreciated.
AFAIK, there's no "crosstalk" at all between the main and backup bioses.Quote:
Originally Posted by irfs
Q-Flash can sometimes fail, such as when upgrading a Z68 board from a standard bios to a UEFI bios.
I normally do not use Q-Flash, and instead use the bootable USB thumb drive method, where the DOS version bios flasher is used.
[The DOS version flasher "efiflash.exe" is included with the F8 bios from the official support site:
http://www.gigabyte.us/products/prod...?pid=4139#bios ]
But that can also fail sometimes, and the Windows beta version B12.0723.1 atbios program did finally work for me, flashing from F10 to F10x.
Had to boot to Windows XP 32-bit to get it (atbios) to install, however.
I have @bios installed allready on Win7 X64 SP1Quote:
Originally Posted by vailr
Are you running 8GB 4GB x 2 config F10x bios? 2133 + should work fine. For me its 4 x 4 16GB + SB cant get to work on 2133
There shouldnt be any crosstalk between bioses but ive seen it happen quite a few times (before Statio advised me to reset CMOS on F10) Cmos reset fixed the Dram voltage for me on F10.
^flashing the bios from Windows is usually a bad idea, and should be a last resort if nothing else works.
Sandy Bridge usually can't use higher multipliers than 21.33x
Also if vDRAm is 1.65v that is because the DRAm multiplier is higher than 24x i was just told, it will auto set that vdimm, just for testing sake.
When i said memory density i just mean the size of the module, like 2gb, 4gb, 8gb.
Also memory that is double sided performs better than single sided in most cases.
Also there IS cross talk between the main and backup BIOS on every boot up, that is one of the good and bad parts of the dual BIOS system. It can cause odd behavior of both BIOSes don't have the same exact settings, like it is one reason BIOS profiles wont transfer after a BIOS flash.
Sin are you saying i should flash both to F10x and my 4 sammys will play together @ 2133 ? (Set both bioses exact same)Quote:
Originally Posted by sin0822
Its only 5.49am lol ive still got time to test. This wud explain the weird behaviour then every time i flash back to F8
well keeping the BIOSes the same is ALWAYs a good idea, but your samsung should be able to run all at 2133, i just don't know if your CPU IMC can do it, but it should be possible with Sandy Bridge, but IDk about 16GB. So if you had Ivy it should be easier.
F10X has a different startup sequence for the memory, thus it allows booting with samsung at higher frequencies, however this startup sequence might not be so good for other types of memory, and thus when this fix is incorporated into a final BIOS it will only use this startup sequence for the generic samsung memory and not the others, however down the line it might be more user select.
That is why i kept saying this is just to test out samsung memory OC.
well keeping the BIOSes the same is ALWAYs a good idea, but your samsung should be able to run all at 2133, i just don't know if your CPU IMC can do it, but it should be possible with Sandy Bridge, but IDk about 16GB. So if you had Ivy it should be easier.
F10X has a different startup sequence for the memory, thus it allows booting with samsung at higher frequencies, however this startup sequence might not be so good for other types of memory, and thus when this fix is incorporated into a final BIOS it will only use this startup sequence for the generic samsung memory and not the others, however down the line it might be more user select.
That is why i kept saying this is just to test out samsung memory OC.
Sin i tried it set both exact same settings in both bioses F10x it wud boot then get into windows but fail shortly after. HCI Memtest detected error in secs. Then when i restart the PC goes crazy into bootloops & beeps. Its funny cos i found i couldnt boot with my normal OC wid F10x got BCCode E1 or soma like that. Back on F8 both bioses and evrything sweet backed down to 4.9GHz for temp sakes.Quote:
Originally Posted by sin0822
I just today got my mates P8Z77-V PREMIUM + 16GB Sammy + i7 3700K He's on holiday for 3 weeks so ive got it to play aroun with. I tried to shoot straight for 2133 (10 10 10 28 1n) it failed in same way as UD5. Its got me thinkin it must be soma to do with 2nd & 3rd timings.
Im glad i didnt get Ivy thing runs toooo hot 4.6GHz needs round 1.375v 85c ++ when i set his to 1866 same timing as ud5 9 9 9 27 1n 1.45v boots fine. Asus bios very refined mouse very smooth but hell its so much to take in too many options make ur head spin.
So, I tried increasing BCLK again...101 MHz no post, 102 MHz no post, 104 MHz running fine and stable:D
There's a posted update for the INTEL Management Engine (ME) controller chip to firmware 8.1.0.1248:
http://www.station-drivers.com/forum...hp?f=32&t=3974
I flash upgraded using the included 64-bit Windows flash program.
Note: must be run from a DOS window command prompt:
"FWUpdLcl64 -f ME8.1.0.1248.bin"
ME firmware should be integrated into the BIOS update.
Yea,8.1.0.1248 is already in F6x (so, should be also in F10x).
The linked .rar file does include an ME version checker.Quote:
Originally Posted by stasio
So: before update flashing, the ME firmware was 8.0.x.x (didn't write it down).
So, this 8.1.0.1248 firmware is definitely newer than what Gigabyte may have attempted to provide via bios update.
There's no mention of any ME firmware updates here:
http://forums.tweaktown.com/gigabyte...fied-bios.html
My Z77-UD5H board shipped with bios version F4, have since flashed to F8, then four F9betas, then F10, and currently F10x.
Note: there's a still newer ME driver version: 8.1.0.1263, but a matching version firmware update doesn't seem to be out yet.
The Intel HECI.inf driver installer from the version 8.1.0.1263 driver package is dated: 2 JUL 2012.
Original F6x BIOS:
http://i3.aijaa.com/b/00348/10720867.jpg
yea please don't try to update ME on your own lol.
I see the GB/HWBot challenge closed with some sick scores... Aristidis 6m55.484 wow :shocked: & Dino, Zen pulled out some nice last minute updates...... 3D challenge also got some big numbers :up:
Sorry: the board referenced is the GA-Z77X-UD5H (running with the latest F10x bios + older ME 8.0.x.x firmwareQuote:
Originally Posted by stasio
[before running the Intel-provided updater] ), not your much newer board, the GA-Z77X-UP5 TH.
Can you provide a screen capture that would actually prove that an ME firmware (of whatever version) is included withinQuote:
Originally Posted by sin0822
any particular board's flashable bios code?
What if: the only method of updating the ME firmware is via separate utility (provided for that purpose by Intel)?
I'm not saying you're wrong, but I'd like to see some proof.
Why is there no ME firmware listed anywhere on this page?:
http://forums.tweaktown.com/gigabyte...fied-bios.html
Did any/all of these bios modders simply FORGET about updating the ME firmware?
:::::::::::::::::::::::::::::::::::::::::::::::::: :::::::::::::::::::::::::::::::::::::::::::
OK, to answer my own question: the Intel ME firmware is indeed contained within the motherboard bios.
With the Gigabyte Z77X-UD5H board's dual bios, I'm running bios version F10x + ME firmware 8.1.0.1248 in the Primary bios,
and F10x + ME firmware 8.0.13.1502 (screen shot below) is in the backup bios.
Attachment 129370
Hi Sin need big favor or you may allready know. I read somewhere that first version of UD5 (Blue cap) doesnt overclock memory so well where as the (Purple cap) version has no issues.Quote:
Originally Posted by sin0822
Is this true? Please find out for us.
Good news: there's a new Gigabyte Z77X-UD5H Bios version F12 out (dated 8/16/2012) that I can confirm: incorporates the latest Intel ME firmware, version 8.1.0.1248.
http://forums.tweaktown.com/showthread.php?t=28441
No notes for F12. May have included some other firmware updates as well, such as the Intel Raid controller, etc.
Hi what does this mean ? can i install latest MEI drivers now? im currently using the GB MEI ones that end in 1502 (im currently on F12 on both backup & main)Quote:
Originally Posted by vailr
How did you check the ME firmware version? Also do you have to enable PLL voltage for sleep to work (i7 2600k). Sorry for the 101 questions.
Thanx in advance
Yes, use the latest drivers, which station-drivers.com lists as being: 8.1.0.1281.Quote:
Originally Posted by irfs
Also: there's no apparent problem using those newer drivers with the older firmware.
Side note: the UD5H F12 bios has also resolved the non-boot problem when the secondary Atheros ethernet controller is disabled in bios setup.
The 64-bit Intel ME firmware version checker "MEInfoWin64.exe" is included with the ME firmware update package at station-drivers.com:Quote:
Originally Posted by irfs
http://www.station-drivers.com/page/intel%20chipset.htm
Note: right-click "Run as Administrator" to open a command prompt window.
Then type in "MEInfoWin64.exe" (without quotes) at the command line.
There's also other versions if using a 32-bit operating system.
i googled the latest mei drivers and found them on intels site. I just installed them now. I didnt bother unistallin the prev 1502 version just installed didnt ask me to restart but i did anyway. Seems to work fine.
I am running a gigabyte g1 sniper 3 mobo f3 BIOS, intel i7 3770k and 16gb gskill ripjaws 2133 cl9 memory. And after installing a second 3770k cpu i power on the system and it goes into a boot loop displaying error code 51 in the debug led.
So i tried taking out 1 stick at a time until it booted up with 2 sticks or ram in slots 1 and 3.
Any suggestions?
Take power lead out...hit onboard cmos reset..plug back in...check ur bios version make sure latest official ones installed on both bioses (F5).Quote:
Originally Posted by Zaxis01
BCLK on my UD5H was 100.00 then it dropped to 99.79
How did that happen?
did you update your BIOS?
Yeah I've updated 2-3 times. Originally BCLK was 100, I noticed the change because CPU & memory freq changed as well.Quote:
Originally Posted by sin0822
You can fix it by compensating in BIOS, but the last pci-e slot (at the end) stops working.
sounds like something for RMA. I typically use the last slot all the time. also, are you setting 100 or just auto?
It's on Auto, running @ 99.79 instead of 100+ dunno why it changed.Quote:
Originally Posted by ZenEffect
The last slot has an Asus wireless pci-e x1 network card, I bet none of the PCI-e 3.0 slots would work if you change BCLK.
odd... ive changed bclk hundereds if not thousands of times on ud5, ud3, and up5 without experiencing the issue you are having.
just to be clear, where is the last slot located? closest to cpu or edge of board?
the loss of .2 bclk and issues bclk makes me think your management engine firmware is busted unless im misreading something. when you change bclk to say 104bclk, does it stick or stay at 99.8?
It's the slot at the edge of the board, the one with the warning sticker that "requires Ivy Bridge CPU". When I change BCLK to 100.02, it changes correctly and shows ~100.05 but I also lose wireless. I assumed it was a BIOS bug and switched to F12, but it also happens with F8. I noticed it because it changed freq for CPU, memory, etc. I don't think .2 such a big deal, these days ALL hardware and software is flaky...Quote:
Originally Posted by ZenEffect
what if you go higher than 100.02? does it still drop out?
I didn't try, everything is on Auto except memory timings and cpu multiplier. I thought disabling spread spectrum would fix it, but there's no setting on the UD5H? I'm curious to know what happened.Quote:
Originally Posted by ZenEffect
If I set 100 in BIOS I get 100 in CPU-Z on my UD5H with F12.
Im not using a wireless lan card in the last slot however I do have one that came with my UD5H-WB & a slightly different one that came with my X79 UD5 I could test for you if nobody else is running a similar setup.
Here's what I get. Most of the time it's 99.8, then every few seconds I see transients of 91.1, 85.5, etc. lasting 1-2 seconds. The whacky transients happen only at idle, very stable under load. This z77 seems very flaky at idle, core temps jump around too 10-12 degrees, but much less so in Linux.
@ cab: what does CPU-Z show as Chipset Rev # & Southbridge Rev # (Motherboard tab)?
My 3570K (stepping 9, revision E1) & UD5H board with blue capacitors & F12 bios shows: Chipset Rev: 09, Southbridge Rev: 04.
Bus speed: stays mostly at 100.1 MHz, momentarily fluctuating lower maybe every 5 to 8 seconds down as low as 90.0 MHz or 92.6 MHz.
Bios settings for all voltages are set at default.
I've tested every combo of C states, auto BCLK, Manual voltages I can think of & my board looks fine on F12.
I'm fairly sure no board could actually run at 85 BCLK so its may be a software/clock gen issue.
http://i106.photobucket.com/albums/m...ityF12BIOS.jpg
Unless anyone else can replicate your issue & work out what the cause is I fear your board may be up the shoot.
### Edit ####
My board is also a blue cap chipset v9 south v4
Motherboard tab shows exactly the same as yours, and my screeshots from a month ago show that my BCLK was also 100.1 (and it may again as soon as the weather cools off).:cool:Quote:
Originally Posted by vailr
hey upgrade your CPuz to at least 1.61.3, you can't even validate with previous ones.
Even 1.61.4 is out or new G1-Killer™ CPU-Z 1.61.3.
Nothing wrong with CPU-Z, bios shows the same numbers.
Somehow your BCLK running in "Fail-Save Defaults" so try clear CMOS, press F7 and load "Optimized Defaults" + F10 "Save & Exit".
My Fail-Save Default => BCLK same as your:
http://i7.aijaa.com/b/00625/10782126.jpg
Edit:
If above didn't solve your BCLK value,
try to replace CPU and check if any socket pin bent.
I have same issue the bckl drops to 60.4, 70.6, 91.1 (F12 Bios) This happens when C3 C6 is disabled NOT when its on AUTO.
On Auto it sticks to 100.00
Any ideads when GB is releasing a Final Bios for UD5? Also i contacted there support on 21/08 how long do they take to get back to you?
Quote:
Originally Posted by stasio
Thank you, I reset CMOS using the mobo switch but BCLK is still 99.79. The hardware is very stable in Windows & Linux, it doesn't hang or BSOD, and it can run prime95 forever @4.0 GHz with stock voltage. Like I posted above, if I set BCLK to 100.01 the numbers look ok but the PCI-E card in the last slot is no longer detected, maybe NO cards would work! Any other ideas what caused this?
I said after clear CMOS, press F7 and load "Optimized Defaults" + F10 "Save & Exit"..
Must be bicycle. :rofl:Quote:
Originally Posted by irfs
.
AFAIK: the Z77X-UD5H version F12 is "final" (not a beta version).Quote:
Originally Posted by irfs
Not to say: there won't maybe be an F13, F14, etc. bios posted at some later time, however.
how can your BCLk drop to 60? or 70?
what are you using to measure bclk?
I just tried it again i disabled C3/C6Quote:
Originally Posted by sin0822
I have it recorded on my phone CPUZ 1.61.3 X64. I can try to post it here not sure if im allowed tho. If F12 is final how long does it take for it to show up on GB website?
why wouldn't you be allowed?
BCLK shouldn't swing, it might be an issue with the version of CPuz you are using. Does the same thing happen with 1.61.2?
When setting C3/C6 to AUTO BCLK sticks to 100 never drops. Thats wid same version of CPUZ. No biggy cos my main concern is the random boot loops on cold start. Do you still recommend setting both bioses exact same ?Quote:
Originally Posted by sin0822
Also Sin hopin you may know why GB changed to purple caps and closed gap between the mem slots and kept quiet bout it and still show blue cap version on there website. Also wanna know if purple cap version has more than 1 capacitor under the cpu socket. Hopin someone wid a purple cap version could help on this one. Also the UP5 does that have 1 cap under cpu socket?
When I try to enter Bios or Q-flash the screen says UEFI at the top and everything below is gone.
Sometimes on reboot the system hangs and restarts in the first 2 secs I think the Bios is corrupt and was going to Q-flash it but won't load Q-flash.
Should I do a bootable USB and try to reflash that way??
Quote:
Originally Posted by iboomalot
That kinda sounds like what happens when i get a boot loop. PC turns on get to that UEFI screen then switches off...then ON black screen ...then OFF...then ON n OFF maybe 4-6 times then it starts as normal. I dont think any bios updates are gona help this situation Gigabyte's Biggest FLAW in designing a board with dual bios. In the coming weeks or days peeps will see the UP7 which has the switch to OFF the dual bios function. This may be the only way to stop any crosstalk between the 2 bioses. If only GB used this on all there boards or stuck with 1 bios that works proper.
After sending my concerns to Gigabyte support on the 21/08
This is the response i finally got today.
Dear Gigabyte Customer
Due to a vast amount of emails received in non-working hours we couldn't reply your question earlier.
In order to help reduce the backlog and re-assess ticket status, can we please kindly ask you to re-submit your question by replying to this email with subject "STILL VALID" if our help is still required.
If you have found a solution to your question, there is no need to respond this mail.
Thank you for your understanding.
Please accept our sincere apologies for the length of time it has taken to respond.
You can also try to contact the place of purchase / manufacturer of your PC / local computer dealer for help.
Please notice you can also find some useful information at our website: http://uk.gigabyte.com
Best Regards
GIGABYTE Technical Support
Flaw!!!! its bloody fantastic mate gone are the days of corrupting BIOS's & having to swap the chip out, use a bios saver, hot flash between boards etc etc or even worse send your board back to have the soldered on chip re flashed/replaced because you borked it. I know you say you have a problem & fair enough this is what you feel may be contributing to it but come on how can you call it a flaw?Quote:
Originally Posted by irfs
It’s fair to say these things are always being developed & improved & the addition of the switch as far as I am aware is not to overcome an issue its a further enhancement/option....
I have against advice always had different bios's on different chips over many many dual BIOS GB boards & never come across an issue. I think Dino or Sin also mentioned somewhere that matching main & backup were no longer required with z77.
Mate i agree its a great board it would be fantastic if it didnt suffer from the boot cycle problem. What i didnt like is the fact that GB relsd this board when it wasnt really ready. I started on F4 had absolute nightmare issues, all sorts. After shutdown wouldnt start had to pull out power lead. loadsa loops, I think it even killed my SSD. I wasted money on new PSU then more money on Mem, then came the BIOS updates which sorted most of the horrible issues. It could be i hav 1st version blue cap i dont know, yes dual bios wicked function BUT if its gona interfere with stability then whats the point. Ive convinced my retailer to pickup my mobo tommorow swapin for Asus pro. Damn shame cos i really did like the UD5.Quote:
Originally Posted by C-N
This boot cycle problem is something I have seen a handful of people complain about on just about every GB board. I have had it myself on my old p67 ud5 never on the UD5H & sure some BIOS's boot better or quicker etc but for me its always been because the board was unhappy with something settings voltages wise & once found all was well again. Some of these people with problems may just plain have dodgy boards but I bet most are setup issues or maybe something like the BIOS not fully supporting certain hardware.Quote:
Originally Posted by irfs
Again I see what you are saying about the early BIOS's & sort of agree maybe they were or the board was launched premature however all manufacturers do this so there's no getting away from it unless you wait for a board/bios to mature before your purchase.
My board is a blue cap model btw & IMO it’s the best board I've had to date.
I hope all works out ok with the board swap.
New BIOS is out.
Thank you. There’s a serious BIOS error in fan control, I hope they’ve corrected it.Quote:
Originally Posted by stasio
BTW, my problem on the previous page -- BCLK less than 100 was caused by EMI interference from an Asus wireless network card. I removed the card and BCLK is back to normal.
Attachment 129719
is there to be any overclocking guides made for the UP series boards?
i have UP5 here, ive read sin's UD5H overclocking guide, wondering if the mosfet 3dpower control settings should be changed at all considering the major differences in the pwm system.
previous guides are fine, everything applies the same!
cool. i'll keep doing that then.
always hard to tell what i should push on water vs ln2.
Gigabyte Z77X-UP7 and Z77N-WiFi Preview (video)
http://www.pcper.com/news/Motherboar...rboard-Preview
Keeping main and backup BIOS the same will reduce the amount of times the dual BIOS error will come up, however the reason the switch was added in the UP7 was determined way before Z77 launch itself as disabling the dual BIOS can help make the reboot behavior much more consistent(so the system wont have the fully shutdown) and because it will help make OC recovery much smoother, it was actually the idea of the head BIOS engineer.
I think in the future perhaps you could see a disable switch again or perhaps even an option in the UEFI. But then you have to realize that dual BIOS helps a lot with BIOS corruption, which usually occurs with OC or BIOS flashes.
You really shouldn't be getting the db error unless your BCLK OC set from UEFi fails, or perhaps because of the type of CPU and memory config you are using. I honestly don't see it unless i fail BCLK OC from UEFI(windows is okay).
How come they didn't say one word about Thunderbolt ??Quote:
Originally Posted by vailr
b'/c neither board has it I guess. The UP7 doesn't have TB, it is already a 10-layer PCB, imagine having to add in a 3W controller, about 6 different support ICs+VRM(two DP switches, an HDMI switch, two 3.3 to 18V MUX, and 1-2 phase 3.3v VRM) just for TB. I think the same reason applies to the iTX
who cares about TB?
They do mention Thunderbolt, starting at 45:15 of the video.Quote:
Originally Posted by cab
Hi, Im having serious problems with what i believe is my mb. Whenever i first turn on the computer it will get to the windows logo screen and freeze, then i would have to reset computer and then load windows from the safe mode screen in normal mode. Then it would be fine for the day even starting and shutting down loads of times. Then i started getting bios is corrupt messages and it would load from the backup bios. I have taken the board back to where i bought and they have tested it and said its fine. This is my system any help would be greatfull
OS:win 7 pro 64bit
MB: Z77X-D3H
CPU: i5 3750k
GFX: 7850
PSU: Jentek 750w
Jentek PSU might be the culprit here. If it isnt providing stable voltage, or quick enough transient response it can create the issues you are describing. I will get a bios corrupt message if I power off at the exact right (guess its actually wrong) time or if i power cycle alot rapidly.
[QUOTE=ZenEffect;5138236]Jentek PSU might be the culprit here. If it isnt providing stable voltage, or quick enough transient response it can create the issues you are describing. I will get a bios corrupt message if I power off at the exact right (guess its actually wrong) time or if i power cycle alot rapidly.[/QUOTE
I got a new PSU as the Jentek turned out to be 5 years old as i got it from my dads old comp. System seems to be running fine now.
[QUOTE=GordyUK;5138932]tbh, ive never even heard of a Jentek PSU before you mentioned it :confused:Quote:
Originally Posted by ZenEffect
glad to see its working well for you now :)
I am loving my G1.Sniper M3 board but I do have one small gripe. On power on the CPU fan doesn't start for a few seconds. It then spins up to quite a loud RPM before dropping back to being silent. Seems strange to me but not enough worry to go hunting for. Has anyone else experienced this?
Parts list is in my sig.
A little background first. I originally purchased the UD5H back in June. First one wouldn't post at all. It had power to the power switch, but nothing would happen when I pushed it. I took it back for a replacement and everything worked flawlessly with the new board. It has been running fine since that time. one thing I didn't realize is that the @Bios software was running on my PC. I must have installed it as part of the driver install process and didn't realize it. I found out when I came home a few weeks ago to see @BIOS running and attempting to download a new BIOS update. I let it do its thing even though I've never updated a BIOS like this before.
Fast forward to 2 days ago. I boot up my PC and get a message that my BIOS is corrupt, and that it's loading the backup BIOS. That's fine I think, when I have time this weekend I'll update the first BIOS and all should be well. Yesterday when I try to boot I get no love. The PC powers up the fans for a second, I hear a click coming from what appears to be the z77 chipset area, some strange character flashes on the debug display, and then it shuts down. A few seconds later same thing happens. It just keeps doing this over and over.
I pulled out everything but 1 stick of ram, and no difference. I decide to call it a night and pick up again today. Today same thing happens, I try clearing the CMOS, manually switching the BIOS, leaving it unplugged for a couple of hours, swapping the ram to a different slot, no change.
Now it won't even power up. The power button still lights up, I hit the power button and nothing, doesn't even click or power up the fans.
So the changes that I am aware of:
1. a recent BIOS update, but it seemed to work fine after that update.
2. I recently plugged my case fans into the MB headers as my fan controller died. I set the fan profile to silent. It seemed to work fine for a number of days after that change.
There have been no new software installs or updates that I'm aware of.
I've contacted Gigabyte support, but have yet to receive a reply.
Any suggestions would be greatly appreciated. As it stands I can't even get to a point where I can flash the BIOS.
The BIOS switch works when the system is powered on, but not actually in an on state. So if you get a light on your power button, then switch the dual BIOS switch and see if it works.
Also try a full scal CMOS reset, IMO get a jumper and short the ClearCMOS pins, then take a screw driver and short the battery connector leads(remove the battery first) and do this for a small period of time, and of course unplug the PSU from the board first.
It could be that @BIOS did something, that is very off it would try doing that.
DoGMan: yea that is normal.
Thanks for the reply.Quote:
Originally Posted by sin0822
I've powered down, switched the BIOS switch, then tried restarting. No difference regardless of the position the BIOS switch is in. I've also tried switching it with power, again no difference.
I've done a full CMOS reset. Unplugged PSU from wall. Turned off PSU switch. Removed CMOS battery. Jumped CMOS reset pins. Held in CMOS reset switch. Left everything in that state overnight. I'll try shorting the battery connectors, but have a feeling that won't make much difference.
After a CMOS reset, it does the thing where it starts and stops a couple of times. After that it won't respond at all to a power button push.
Right now I have the MB out of the case with just the PSU, CPU, 1 stick of RAM, and the monitor hooked up. I even tried without the monitor.
id say get an RMA. Something must have gone wrong with @BIOS..
@mfarlow: maybe the PSU is faulty? Try a different one.
Tried that. Same issue with 2 known working PSUs.Quote:
Originally Posted by vailr
Yeah it's been 3 months since I've purchased it, so I'm betting they won't just replace it.Quote:
Originally Posted by sin0822
I'll probably just buy something else. 1 bad Mobo is one thing, but 2 in a row doesn't make me feel too confident in this board.
@mfarlow..... If I were in your situation I would try shorting the bios chips out to see if I could force the board to boot from the other chip. I have done this once before when I killed my P67 dual bios & have to say it took many goes to finally get the board to boot but it eventually did.
If the board will not power or spin fans this may be of no use but worth a go anyway. You may also have to power on off your PSU to reset the board but a less garbled post screen or bios light switching from main to backup should give you some evidence that you are getting there.
Thanks Sin is there any way to over ride this behaviour?Quote:
Originally Posted by sin0822
Thanks for the advice how do you short the bios chip?Quote:
Originally Posted by C-N
Right now I'm at the point where it won't even spin up the fans, but I'm still getting power to the board (the power button lights up).
Short pin 6 & 7 with a screwdriver this will force the board to try the other bios.
THC and I started to see how the UP5 kicks along
We threw in some 2666 hynix based modules and took it for a quick n dirty 32m run , exploring the DRAM overclockability alongside BCLK , CPU H100 - Memory air
http://www.odoc.dk/files/images/test...m-web-1024.jpg
yea the UP5 isn't half bad. I have the BCLK WR for Z77 with it, 117 almost(116.95)
Dogman, i don't think there is anything you can do, when it spins full throttle that is because it isn't being controlled, but then when the SIO kicks in the control it slows down.
damn Oliver, that's nice
Hey guys I got a little issue over here & wonder if anyone can help out?
The problem is I've reached the limit of something most likely my RAM or my CPU & wonder if anyone can tell me what happens on their board when they hit the IMC or RAM speed limit.
Below is about the max I can reasonably bench, it’s not as efficient as it should be but it runs. Just after this 2930 ~ 2950 it will fail SPI instantly irrespective of voltages or timings. Also as I creep over 2940 my board drops USB.... windows still runs but you can’t control it as the USB mouse/keyboard stops working.
http://i106.photobucket.com/albums/m...A646M19375.png
http://i106.photobucket.com/albums/m...A646M19375.png
@C-N: Ivy Bridge CPU specs require that the memory voltage stay within 5% of 1.50 volts.
Your Team Xtreem LV 2666 in comparison seems to require 1.65 volts (at the frequency you're running at).
One solution would be to replace with lower voltage memory, such as the 30 nm 1.35 volt 4 GB Samsung sticks.
Either that, or be happy with what your 1.65 volt memory can do.
Also note: the latest CPU-Z version is currently: 161.5
Thanks for the reply vailr, I am happy with what I got just would like some feedback from people as to what happens on there board as you max it out.Quote:
Originally Posted by vailr
As for the CPU-Z version, it works so I leave it alone but thanks anyway for the info.
@C-N Did you try to up imc and dram trm. voltages?
I find my board/setup only needed more IMC voltage to run a bit more BCLK @ 100 .92~.93 is its sweet spot. At the above settings any more than .94 made SPI fail the more you put on the quicker it failed. I also find too much IMC voltage brings on a vdimm wall.... too much IMC voltage means the more vdimm I add don't help & fails SPI quicker & quicker if you get my drift.
I did briefly test dram termination voltage but I have to admit not properly I just moved up & down a little but didn't find a benefit so I left it alone. Do you find it helps & if so what sort of percentage against vdimm do you find works for you?
Its ram chip specific for my asus board. Generally around 42% from vdimm. Samsung seems to need less v than bbse/pscQuote:
Originally Posted by C-N
Thanks mate I'll give it a try & ye I get the IC specific bit its always been like that with the stuff I've had too.Quote:
Originally Posted by Dumo
Quote:
Originally Posted by C-N
Got mobo swapped to Asus P8Z77-V PRO all seemed fine but occasionally i would get 1 boot loop. Swapped out for Gigabyte UP5 TH same issue 4 boot loops with my i7 2600K. Swapped i7 2600K to new one thanx to Intel and voila boot loops gone. My issue was CPU not mobo or mem at all that means UD5 was fine...oh well ended up wid a crackin board and a luvely i7 2600k @ 5GHz this time with less volts & a better IMC.
I take everything back !! Nothin to do with dual bios and crosstalk ! im absolutely happy now
MY prev cpu was either degraded or simply weak IMC strange cos once it booted everything was fine.