actually nvm about the C1E thing, the settings work, just in BIOS it reports lower for some reason.
Printable View
actually nvm about the C1E thing, the settings work, just in BIOS it reports lower for some reason.
Hi i have a question for you gurus. I have the 3960x overclocked to 4.6 ghz when i start to prime 95 this cpu it seems my ud7 is downlocking the cpu back down to 3300 mhz after a couple of minutes of stress testing according to cpuz 1.59. When i stop prime 95 the cpu frequency goes back to 4600mhz. Anyway ideas why this would be happening?
heat? Thermal throttling. its around 90C, if your CPu is reading 80C it might actually be a bit hotter and throttling. Check power saving features, turn them off.
Thanks for the reply, I only have 1.27 volts going through it with H100 and the temps reported on real temp is only high 60s to very low 70s? even when i detune to 4.4 ghz it still happens but it take about 45 mins of prime 95 to happen as opposed to 1 min @ 4.6 its defenitly throttling but what setting in the bios is there to stop this from happening.
Gigabyte X79-UD7 SLI Gaming Overclocking Motherboard Unboxing & First Look Linus Tech Tips
http://www.youtube.com/watch?v=_i7y1k1nTrw
turn up PWM settings mate, it might help, but i don't think that is the problem. With these new Digital PWMs, they really have a lot of failsafes in place for heat, if you are watercooling, then you probably don't have any airflow around the CPu socket area, and that might cause problems. At 4.8ghz my CPu pulls 300W, CPU 12v intake only, not at the wall. So try this, in 3D BIOS section turn up the CPU PWM Vcore temperature to 140C, i think that is the max, turn up CPU current capability to 128% on Vcore as well in that same menu. Turn Cpu PWM Switching frequency down to 900khz.
in the advanced settings menu, where you set turbo multipliers, there are two options, one for TDP(watts) and one for TDC(ciurrent) Set TDP max turbo watts to 500W, set TDC max turbo current to 300A. Those can also cause throttle.
i updated the list
I made my mini review od the UD7 as well :) Will still update this as I think I will be borrowing new proc this coming weekend :D
http://bartman1973.wordpress.com/201...g-motherboard/
Hi sin0822, I do have one that will have a 3930K onboard & 16Gb of G Skill Quad Channel 1600 C9 RAM, just hoping to get some similar comments & feedback, as the UD7/OC is getting...that's all.
You helped me a bit with my sig setup, got a G1 Sniper when my X58A UD7 died, and the Sniper SUX, so I lashed out and got some X79 bits.
Hopefully I will get another UD7, after RMA :)
Cheers
That's a real nice looking board.
I just started playing with my UD7 yesterday, seems like a really well made board. This is also my first Gigabyte motherboard; I hope I made a wise decision. However, I’ve noticed a few issues I’m hoping are related to immature BIOS. I’m also not a pro at sandy bridge, so don’t hesitate to correct me if I made a configuration mistake or I’m misunderstanding.
Using the F3 BIOS if I set CPU vcore to 1.4 I noticed it loaded windows at 1.47v and once I applied a load with prime95 it scaled up to 1.53v? :confused: Both voltages measured from vcore read point and multimeter. With F4b BIOS the vcore also overvolts 1.4 to 1.47, but at least remained steady while under stress tests. CPU-Z voltage seems off by a very large margin for this board.
On either BIOS I cannot currently load base clock gear ratio 1.25, only 1.00x will boot. Has anyone has any luck with this setting?
Finally I have no mouse support in UEFI, except in F3b, and then the Y and X axis are inverted so I have to hold my mouse sideways. :rofl:
yea 1.25 with lower BLCK, try 1.67 with 90 blck and 1.25 with like 98. They are working on the dividers i am told.
http://valid.canardpc.com/show_oc.php?id=2122253
Really? no mouse support, and you tell us your exact model of your mouse and the BIOS? F4B right?
The reason your vcore is increasing under load is becuase of LLC, goto 3d power menu in BIOS, and set Vcore Load line to 0.6 or 60%
I hope Gigabyte sends you a fat check in the mail Sin. You are the unofficial Gigabyte support team here at XS, and anywhere else I have looked. It seems they have made NO....0 effort towards supporting the last few Gigabyte boards I have owned, and thus far none for this board, which is a big reason I have not ordered one. Thanks for all your efforts Sin in trying to give support to the guys in the forum.
If anyone has looked at the Asus X79 threads you will notice a different story. Best support I have seen on any motherboard I have owned. Go to NewEgg and see how many Asus X79 boards you can find, almost none, most sold out, then Gigabyte boards, pretty much all are available.
Thanks can you tell me what kind of memory you have and the CPU?
Also did you try changing the USB legacy device settings?
haha thanks, but honestly i only do it for he fun of it. I just enjoy messing around with hardware, and since i work with it a lot i figure i can help out users who are having the issues i had. Nothing any of you wouldn't do.
BTW there is also Dino lurking around, and also tweaktown forums is their offical USA forums, and http://forum.giga-byte.co.uk/index.p...a0f6&board=5.0
but i do know what you mean.
That is very very odd. Is easytune working by any chance? Try uninstalling it, its worth a shot.
Can you list exactly what your settings are? Take a screenshot in the UEFI, and post em up for me?
Have you tried a different BIOS? F3? or F3K? Or F2? All the same?
Anyone tested F4b ?
So I finally got my X79-UD7 system put together... sadly it will not even POST. It stops on debug code 6A(IOH SMM initialization - WTF is this?). No beeps. Also one of the fans doesn't start spinning immediately. If I remove all the RAM it does beep. If I remove the video card it does not beep. I also tried my GTX 260, but no luck. I've tried running with the RAM in like every possible configuration. Any ideas?
PSU - Corsair AX1200
RAM - 16gb Crucial Ballistix Tracer DDR3-2000
GFX - GTX 560 Ti (til the new card shows up...)
SSD - OCZ Vertex 3 120gb
maybe its a DOA board? can you try another PSU? or another CPU? Try one stick of memory?