Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Phat32 on August 29, 2011, 03:38:18 pm
-
I just bought the GA-P67A-UD7-B3 yesterday along with an Intel i7 2600K (http://www.canadacomputers.com/product_info.php?cPath=4_65&item_id=035532) and Mushkin Redline 8GB 1866MHz RAM (http://www.canadacomputers.com/product_info.php?cPath=24_311_312_613&item_id=040437). Everything has been working perfectly with the exception that the ram has been downclocked to 1333MHz. When I go into the BIOS and set the clock to be 1866, it will work for a while but then I BSOD. I tried to set the ram to 1.64V, I have not tried 1.66V yet however. While its running perfectly at 1333, I want to use the 1866 its capable of, largely cause I didn't pay the extra for the high end ram just to have it downclocked ;) Any ideas on what I can do?
-
Welcome Phat32
Pain in the but Huh!........2 ways really!.......first one the right way..........the second method if the first proves a false positive.........not sure that makes sense rereading what I just put down.
You may have a crook Memory module in the set..........this is the pain in the butt bit...........download and run Memtest with one module installed in slot one..........ten passes each module..........time consuming but the only way to be sure if there a problem with a dimm in the set.
I suspect you have a dimm that will fail..........if this is true.............you will have to RMA the entire set as there mached.
If they pass.... :o.....start by loosening the timings to 10-10-10-27 and try the 1.5......then 1.55......then 1.6..........if they will not run stable at the looser timings and a Volt bump..........Mmmmmmmmmmmmm!......post back what you find!
Aussie Allan
-
Thanks for the welcome and reply. I am at work for the next 4-5 hours.... .9-5 jobs SUCK..... when I get home I will give the memtest try. I doubt it the RAM only because using the defaults the MB wanted to use it ran without problem all night. Only when I changed the specs did it crap out on me haha.
-
I don't doudbt it.......Ive had some 1600 Memory that would run 24/7 at 1066..........but you want what you paid for!.........if they say 1866 and charge accordingly.......that's what you're entitled too..........and running at the timings that the spec quality control passed it at.
Aussie Allan
-
Hi and welcome.
The main problem is your memory as Allan has said. The RAM you purchased is a bit power hungry for these boards which like 1.5v sticks. It is possible to get faster (overclocked) memory to run but it will require at least the 1.65v. As you have found you cannot get 1.65 so it has to be 1.66v. Don't worry about the red warning. You will probably have to configure the timings yourself as well. The XMP probably won't work. ;)
-
Thanks for the help! I just set the timing and the Mhz according to the specs of the ram. As it turns out I was looking at a slightly different model, this 1866 RAM is indeed 1.5V not 1.65V as I had believed. Weird how i fraked that up!
It was just uppped but so far all seems well. Hopefully this will hold true for the night!
-
Often it is better to enter the settings manually that leave it up to the BIOS to fix them automatically. ;)
-
Good result Phat32 ... as kit gets better and faster .... more and more is left to the end user ... good thing I say !
If you are an enthusiast ... I would be very interested were you get re Memory timings (10-10-10-27) ;)
DM!....May I be the first of many....... Congrats on busting fourteen Grand ... what a lovely 38th Birthday achievement ....(Plus Vat) :-X
Aussie Allan
-
Hi Allan and thanks for the grats. Fifteen next! 8)
-
It was working perfectly all last night, and just for fun I ran a PCMARK 7 benchmark and it came back with *i think* 3527. Seems I just had to set the timings as well as the freq. Seems painfully obvious now but oh well. Thats what forums are for! Thanks for the help! :)
FYI for Allan: my timings are currently at 9-10-9-27
-
It was working perfectly all last night, and just for fun I ran a PCMARK 7 benchmark and it came back with *i think* 3527. Seems I just had to set the timings as well as the freq. Seems painfully obvious now but oh well. Thats what forums are for! Thanks for the help! :)
FYI for Allan: my timings are currently at 9-10-9-27
Yes the timings sound about right for your memory modules. Sometimes though it can pay to cut back on the speed and tighten the timings somewhat. Trial and error as usual. ;)
-
I used the values directly from Mushkin: http://www.mushkin.com/Memory/Redline/997007.aspx
-
Excellent news........people oftener forget..........tighter memory timing will have a far bigger effect on performance then frequency (speed) alone
Aussie Allan