I saw the cooments on OCN I think u should heed Ed's advice and practice on an old or dead board first imo
Printable View
I saw the cooments on OCN I think u should heed Ed's advice and practice on an old or dead board first imo
My new board, I'm very pleased with upgrade from EX58-UD5 to X58A-UD7, only one question, why is +12V info unavailable?
http://img217.imageshack.us/img217/2600/occt4200cr.jpg
+12v info isn't avialbe on my machine either
not a clue why.
G.SKILL Trident (3x4GB) 1600MHz 7-8-7-24-2N 1.65V (F3-12800CL7T-12GBTDD) on UD7
Just a few quick tests to get a feeling of it before putting it on SR-2.
Then a 3x2GB will move back to UD7, and finally can get my poor UD7 up and running too :).
It is running pretty smooth at rated speed with 1N on UD7. Not too bad a for a 3x4GB kit :)
3x4GB @1600MHz 7-8-7-24 1N 1.65v
http://img.techpowerup.org/101102/Capture046.jpg
It won't boot @1760MHz CL7, but is doing pretty good with CL8.
3x4GB @1760MHz 8-9-8-24 1N 1.65v
http://img.techpowerup.org/101102/Capture047.jpg
I'll be happy if it can do the same on SR-2 too.
I get the 12V, 5V and 3.3V under Aida64, but not under everest.
I posted a screenshot here.
What is more likely to cause the "recovering lost DRAM size..." error that causes the board to get into an infinite loop of reboots? Memory or board? I've heard that this error is plaguing Gigabyte X58 boards especially.
I have a X58A-UD7 rev. 2.0 here, and this error randomly comes up on system boots, even on OCCT-stable and stock settings.
oh, and memory is 3x OCZ Gold XTC OCZ3G1600LV1G
This is caused by unstable settings, most often not enough QPI/Vtt, ram voltage, or something else incorrect for your memory/uncore.
It's a feature, before this was added to the BIOS you would boot to windows with lost/missing memory and if you didn't look in the right places you wouldn't know and would be using 4GB out of 6GB or something like that.
You are seeing this because your settings are not as stable as you may think, try testing with memtest86+, HCI memtest, Prime96, LinX, ect and I'm sure you will find some instability somewhere.
hey LSD, my UD7 turns on automatically once i turn on the PSU switch at the back, doesn't post and throws a "88" code on the debug led, no response from the power on/reset buttons. I think i've shorted the "always on" 5V (violet) and yellow 12V rails by accident while tinkering with the Cosmos S touch power button... You think shorting the rails could've killed the mobo?!
88 is dead CPU, but can also be dead/incompatible PSU or dead motherboard.
So it could be any of the above, start testing components one by one if you can.
Do you mean Fail Safe, or Optimized Defaults? Are you setting your memory speeds, if so then that is not stock.
Either way, you will need to set your ram voltage (1.66v), uncore value (2 x ram multi), and QPI/Vtt voltage (1.25-1.35+ Depending on your CPU). Auto is not always going to work for everything, and is generally there so you can get into the BIOS with most any hardware and set things yourself.
Be sure you are using the latest BIOS as well.
has anyone tested the qpi/vtt voltage with a multimeter?
i have heard of severe dropping(1.69v vtt bios/1.59v real)
i dont have a multimeter but im having issues with my UD5
running ddr3-2000/uncore4000.my kit did it with ease on
my UD3R but wont on this MB.tried vtt up to 1.62v and it
still just boots into windows but freezes as soon a any load
is put to it(opening program/everest cachemem).
so if someone could test vtt with a DMM i would appreciate it
HardwareCanucks did, and found it to be fairly minimal drop, at least on the UD7
http://www.hardwarecanucks.com/forum...review-19.html
which is the best bios for UD7?
i have got i7 930, ud7 rev1, 3x2gb skill bi black, 300wd veloci
Most all of the official bios's are pretty good for the rev1. I had very good results with f6, but that may be because it was the one I happened to have installed when I did most of my testing. I dont remember any of them being bad.
Guys, after some tips. Ive had my UD7 a while now, but in the last 6 months ive not had much time for tweaking. Just the other week, I thought i'd get back to it, however ive come stuck when it comes to my memory (dominator GT). I cant get it running above 1600mhz at all. It worked fine on my Bloodrage at rated speeds, but I just cant get it stable on this board. Ive tried upping the VTT, different uncore/mem multi/FSB combinations etc etc and no joy. Had the memory voltage up to 1.67v, as I thought the board might be drooping a bit, but didnt want to go higher as my dominators GTs are early ones which I understand had quite a high failure rate.
Just wondering if theres anything Im missing. On F7 bios, my 980x is running 24/7 at 4.2ghz, 200x21 at 1.31v vcore, and have had it to 4.4ghz LinX stable.
Yes HT is on. My 980x is pretty middle of the road. Will do 4.4ghz at 1.38v but I run 4.2 24/7 these days to keep voltage down. Getting my memory sorted is my main niggle with this rig.
I've had my 980X running at 4.2GHz with HT on for ages, but i cant get stable any higher, unless i turn HT off. It's already at 1.39v. I have all 6 RAM slots filled though, with 24GB so it might be that...
I also have an ancient BIOS, so could be that too. But been putting off updating the BIOS until i know for sure that i can recover my RAID array if i update?
@MikeMK what are your temps at 1.38v? You have the same GTZ waterblock and radiator as me.
If you upgrade the BIOS you just have to be sure that after you load optimized and reboot that you go directly BACK to the BIOS and enable RAID again, then reboot back to the BIOS once more and move the array to the top of your hard disk boot priority.
Be careful, if you miss entering the BIOS with RAID not enabled (Default), then windows starts to load it will mess up your array. So be sure you are quick with the DEL key and you will be fine :D
No it's not the cpu or mem in my case she's stiff and cold, LSD i mean the board. What a bummer. Took out a wireless X360 controller with it as well as crippled my GTX480 which died next day...
well thanks for your input.
My UD7 is finally up and running again :)
It has been crunching continuously at 100% with these settings for over 50 hours now :)
http://img.techpowerup.org/101108/Capture012.jpg
what is better? higher bus speed or higher multiplier?
i'm running 21 x 200 to get 4.2Ghz,
would it be better/faster to run 19 x 221?
i have 1866 memory but only running it at 1600