Overclock.net › Forums › Intel › Intel Motherboards › ASUS X99 Motherboard Series - Official Support Thread (North American users only)
New Posts  All Forums:Forum Nav:

ASUS X99 Motherboard Series - Official Support Thread (North American users only) - Page 1137

post #11361 of 15774
Quote:
Originally Posted by DJ_OXyGeNe_8 View Post

Anyone noticed 2101 bios gives weird settings for RAM

I've this ram : http://www.corsair.com/en-us/dominator-platinum-series-32gb-4-x-8gb-ddr4-dram-2666mhz-c15-memory-kit-cmd32gx4m4a2666c15

It has 2 profiles 2666 & 2800 and I know the same settings for both clocks 15 17 17 35 - 1.2 V (2666) - 1.35 V (2800)

When I choose profile 2 , it gives 17 18 18 37 - 1.4 V !?!?

Previous bios gave 15 17 17 35 - 1.35V

I did set manually

With 2001 bios 2800



with 2101 2666


if you don't like the XMP profile simply use the manual settings smile.gif
DeskStar
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 5930K Asus X99 Deluxe EVGA GTX980 Ti SC+ ACX2.0+ SLI 4x4GB Corsair Vengeance LPX 2800@2666MHz 15-15-... 
Hard DriveHard DriveHard DriveHard Drive
Samsung 950 PRO NVMe M.2 512GB Samsung 850 EVO 1TB Western Digital Black 2TB Corsair Force GT 240GB 
Optical DriveCoolingOSMonitor
Plextor PX-B320SA Blu-ray Corsair H80i AIO Windows 10, CentOS 7 EIZO S2433W 24.1" 1920x1200 60Hz 
PowerCaseOtherOther
Corsair AX860i Lian-li PC7FNWX Gigabit Internet Cyberpower Smart UPS PR1500ELCD 1500VA/1350W Si... 
  hide details  
Reply
DeskStar
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 5930K Asus X99 Deluxe EVGA GTX980 Ti SC+ ACX2.0+ SLI 4x4GB Corsair Vengeance LPX 2800@2666MHz 15-15-... 
Hard DriveHard DriveHard DriveHard Drive
Samsung 950 PRO NVMe M.2 512GB Samsung 850 EVO 1TB Western Digital Black 2TB Corsair Force GT 240GB 
Optical DriveCoolingOSMonitor
Plextor PX-B320SA Blu-ray Corsair H80i AIO Windows 10, CentOS 7 EIZO S2433W 24.1" 1920x1200 60Hz 
PowerCaseOtherOther
Corsair AX860i Lian-li PC7FNWX Gigabit Internet Cyberpower Smart UPS PR1500ELCD 1500VA/1350W Si... 
  hide details  
Reply
post #11362 of 15774
Hey all - I googled into this thread while searching for the dreaded 'bd' q-code errors that I randomly started getting.

I THINK I have that solved now (lowered RAM from 3000 to 2750 - set the voltages higher for boot (but normal 1.35 on 'eventual' voltage), and set the VCCSA to +0.075) - and now I am re-overclocking manually (not using XMP profiles or anything).

My question is this:

I saw on some threads that people OC'ed their cache as well. I did this before, but I don't want to waste time doing it again if the result isn't really noticeable. I am using my 5920k build for gaming ONLY... and I mean ONLY - it is a dedicated gaming rig.

So if overclocking cache simply creates instability in the OC for little to no gain - count me out!

I have achieved 4.625Ghz (125x37) on my custom water cooling loop @ AUTO voltage (1.312 in bios) - which I think is a good OC.

Any tips or suggestions are welcomed!

Any benchmarks showing specifically the difference between an OC'ed CPU and then an OC'ed CPU + OC'ed cache?
post #11363 of 15774
Core is king.
Cache will mainly benefit synthetic benchmarks, and heavily RAM/CPU intensive workloads. It is also tricky to overclock in conjunction with core and RAM, while maintaining a good balance of power savings and performance. Not that is can't be done, but that it will require more effort for little gain. Lots of the people around here are benchmark jockeys or just want to live on the bleeding edge...if all you are looking for is a good solid gaming experience, and cache overclocking is causing problems, it can be skipped all together, or revisited at a later date. Game on man, it doesn't sound like you will be missing anything but the headache from random lock ups or instability.
Blue540
(14 items)
 
x99
(18 items)
 
B.M.O.
(10 items)
 
CPUMotherboardGraphicsGraphics
6800k ASUS X99-A EVGA 980 FTW ACX 2.0 EVGA 980 FTW ACX2.0 
RAMHard DriveHard DriveCooling
Corsair Vengeance CMK32GX4M4B3200C16W Crucial MX100 WD Blue 1TB EK Supremacy EVO 
CoolingCoolingCoolingOS
EK 480 PE EK 240 PE EK D5 Vario Windows 10 
MonitorKeyboardPowerCase
Samsung 49KU7500 (curved 4k) Corsair K65 NZXT Hale 90 V2 1000W Thermaltake X9 
MouseMouse Pad
Logitch G100S X-Trac Ripper 
CPUMotherboardGraphicsRAM
6400k msi A75MA-P33 Sapphire 6670 passive hynix 2 GB dual channel 
Hard DriveOSMonitorKeyboard
WD  windows 8.1 e-machine wireless 
PowerCase
king win 600w custom built 
  hide details  
Reply
Blue540
(14 items)
 
x99
(18 items)
 
B.M.O.
(10 items)
 
CPUMotherboardGraphicsGraphics
6800k ASUS X99-A EVGA 980 FTW ACX 2.0 EVGA 980 FTW ACX2.0 
RAMHard DriveHard DriveCooling
Corsair Vengeance CMK32GX4M4B3200C16W Crucial MX100 WD Blue 1TB EK Supremacy EVO 
CoolingCoolingCoolingOS
EK 480 PE EK 240 PE EK D5 Vario Windows 10 
MonitorKeyboardPowerCase
Samsung 49KU7500 (curved 4k) Corsair K65 NZXT Hale 90 V2 1000W Thermaltake X9 
MouseMouse Pad
Logitch G100S X-Trac Ripper 
CPUMotherboardGraphicsRAM
6400k msi A75MA-P33 Sapphire 6670 passive hynix 2 GB dual channel 
Hard DriveOSMonitorKeyboard
WD  windows 8.1 e-machine wireless 
PowerCase
king win 600w custom built 
  hide details  
Reply
post #11364 of 15774
Quote:
Originally Posted by LordX2 View Post

Hey all - I googled into this thread while searching for the dreaded 'bd' q-code errors that I randomly started getting.

I THINK I have that solved now (lowered RAM from 3000 to 2750 - set the voltages higher for boot (but normal 1.35 on 'eventual' voltage), and set the VCCSA to +0.075) - and now I am re-overclocking manually (not using XMP profiles or anything).

My question is this:

I saw on some threads that people OC'ed their cache as well. I did this before, but I don't want to waste time doing it again if the result isn't really noticeable. I am using my 5920k build for gaming ONLY... and I mean ONLY - it is a dedicated gaming rig.

So if overclocking cache simply creates instability in the OC for little to no gain - count me out!

I have achieved 4.625Ghz (125x37) on my custom water cooling loop @ AUTO voltage (1.312 in bios) - which I think is a good OC.

Any tips or suggestions are welcomed!

Any benchmarks showing specifically the difference between an OC'ed CPU and then an OC'ed CPU + OC'ed cache?
That's really good if you can do several hours stress with that vcore, but you need to take a reading using Aida or such while stressing - the BIOS will not show the actual operational vcore.
post #11365 of 15774
My real concern is the 'bd' Q-Code reboot problem coming back.

I mean - it came out of NOWHERE - and got so bad, I couldn't even get it to post and get into the BIOS to change settings one night.

Now I have the RAM at 2750mhz - which I know wont cause much if any difference for gaming..... but it BUGS me! I bought 3000mhz ram - and I would like to use it.

Not to mention - I will be nervous now EVERY time I start the system - wondering if the issue will come back again.

Did this thread ever get to the bottom of the cause?? I mean it is so weird for something to work fine for months, and then BAM - problems.
post #11366 of 15774
Quote:
Originally Posted by LordX2 View Post

My real concern is the 'bd' Q-Code reboot problem coming back.

I mean - it came out of NOWHERE - and got so bad, I couldn't even get it to post and get into the BIOS to change settings one night.

I had the same issue. My advice? Stick to 2400MHz / 2666MHz. 3200MHz isn't worth the hassle, especially if you have a weak IMC like me. Broadwell-E should improve things, but for now, our CPUs are only guaranteed to work at 2133MHz JEDEC spec RAM.

2400MHz and 2666MHz give you sentimental advantages like adaptive Vcore = lower idle temps, lower idle clocks due to 100 strap compatibility, no loss of performance in gaming: http://www.extremetech.com/extreme/198894-raming-speed-does-boosting-ddr4-to-3200mhz-improve-overall-performance.

In summary, DDR4 is being specced for the VASTLY easier Z170 boards, it is no longer guaranteed to work at those XMP speeds on X99. The reason for this? Companies are cheap and want to make as much dollars as possible. If bd occurs out of nowhere, it's an issue with training / IMC. Heck, even with mixed kits I can easily run 2666MHz out of the box with no tweaks and fully stable RAM.
Edited by Desolutional - 2/16/16 at 6:10am
post #11367 of 15774
Quote:
Originally Posted by Desolutional View Post

If bd occurs out of nowhere, it's an issue with training / IMC.

Thanks for the link on the RAM benchmarks - good read!

I still don't fully understand the whole 'training' thing with memory... In my experience with ram, it usually works or it doesn't. Can you give me the lay mans definition?

If it is the internal memory controller, then should I worry about my CPU if it happens again?
post #11368 of 15774
Quote:
Originally Posted by LordX2 View Post

Thanks for the link on the RAM benchmarks - good read!

I still don't fully understand the whole 'training' thing with memory... In my experience with ram, it usually works or it doesn't. Can you give me the lay mans definition?

If it is the internal memory controller, then should I worry about my CPU if it happens again?

Hello

DDR4 uses pass/fail windows at the electrical level during POST to align the necessary signals. This has been discussed at length in this thread as well as the R5E and Haswell-E Overclock threads. Reviewing these 3 threads should provide the info you are looking for.
post #11369 of 15774
Does anyone know where the MB temperature sensor is on Asus X99 boards? I couldnt find the sensor layout in the manual. I mean PCH, VRM etc temp sensors are placed logically at their respective sections but i got no clue where MB temp sensor is.
post #11370 of 15774
Ok - I will read up on the technical stuff for that..

Final question on the issue: Is there a way to prevent it from happening again?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › ASUS X99 Motherboard Series - Official Support Thread (North American users only)