Fatality X99M Killer 3.1
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=533
Printed Date: 28 Apr 2024 at 3:15am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Fatality X99M Killer 3.1
Posted By: sexpot
Subject: Fatality X99M Killer 3.1
Date Posted: 01 Aug 2015 at 11:04am
|
Hey guys, I've been out of the PC hardware loop since the early days of Sandy Bridge and have a question regarding my current hardware. I've purchased a 5820K, Fatality X99M Killer 3.1, Sound Blaster Z and have some concerns regarding pcie lanes and my devices. Idealy, I want to run the video card in the top slot, samsung SM951 ssd in the m.2 port, Sound Blaster Z in the last PCIe slot. Some HDD's in the sata ports as well. Will this all function without slowing down any lanes?? For instance, will the m.2 port be shared with the last pcie slot which will be occupied by the sound card and slow down the SM951 ssd? Also, will the sata HDDs slow anything else down? |
Replies:
Posted By: sexpot
Date Posted: 01 Aug 2015 at 12:36pm
|
Ok, after going through the manual, I want to confirm: - Top PCIe slot with video card connect = 16x speed - m.2 pcie slot connected = must not connect any device to sata port S_Sata3_2 - Sound card connected to PCIe3 slot = will run in 4x mode @ pcie 2.0 speeds - Additional sata devices: (S_SATA3_3 connector is shared with the eSATA port) (S_SATA3_2 connector is shared with Ultra M.2 Socket) 1 x SATA Express 10 Gb/s Connector (shared with SATA3_4 and SATA3_5) I7 5820k will therefore be able to support my devices in full speed according the the list above. Please correct if I'm wrong. |
Posted By: Xaltar
Date Posted: 01 Aug 2015 at 12:45pm
That should work perfectly  Enjoy your new build
 |
Posted By: sexpot
Date Posted: 01 Aug 2015 at 12:49pm
|
Ty very much Xaltar for confirmation. I have one more question, my ram is Corsair LPX 16GB 3000MHz CAS15. Will I be able to run it on xmp profile with a 100 strap? |
Posted By: Xaltar
Date Posted: 01 Aug 2015 at 12:56pm
| I am not sure on that front, I don't have a 2011 system to try it out atm. Parsec does however, he should know more about XMP on the X99 platform. |
Posted By: sexpot
Date Posted: 01 Aug 2015 at 1:09pm
|
Ok thanks, I will wait to hear from him. My board is currently shipping so I don't have it here to test yet. Still waiting on parts so all I can do is read and ask questions :) |
Posted By: sexpot
Date Posted: 09 Aug 2015 at 5:37pm
|
Hey guys, Just got my new rig up and running. I'm having troubles with these last 2 drivers though. Can you tell me which one I need to install from Asrock's website?  |
Posted By: sexpot
Date Posted: 10 Aug 2015 at 9:34am
|
NVM above post, I got it figured out with the driver CD. Anyone have a template of settings to try for a stable overclock? |
Posted By: sexpot
Date Posted: 11 Aug 2015 at 11:13am
| Anyone able to get vccsa, uncore voltage to show up in any kind of monitoring software? I've installed both hwinfo and aida64 (trial version) and neither are showing me these voltages. Any help? |
Posted By: parsec
Date Posted: 11 Aug 2015 at 2:09pm
Regarding your memory question, only someone that owns your Corsair memory can tell you if the XMP profile uses the 125 strap. I don't, sorry. The provided memory OC profiles in the UEFI of my ASRock X99 board sets the BCLK to 125 for the 3000 profile. Those are not XMP profiles from the memory, but profiles provided in the UEFI. I've read it is possible to run memory at 3000 with the BCLK at 100, but requires some tweaking to get it working. About the VCCSA and Uncore/Cache voltages, the best I can tell you is this. In HWiNFO64, I suspect that the VTT or VIN6 reading is the VCCSA. Uncore/cache voltage is not there IMO. A new Beta version of HWiNFO64 was released that included enhanced monitoring on ASRock X99 boards. I tried it and found a problem, the VCore reading is gone. I posted a thread in the HWiNFO forum about this, which I'm sure will be fixed. Hopefully there will be new readings for us in HWiNFO64 soon.  ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
sexpot wrote:Posted By: sexpot
Date Posted: 11 Aug 2015 at 2:47pm
|
TYVM parsec I couldn't figure out which label was vccsa in HWINFO. I received the x99m killer 3.1 and am now trying to dial in some clocks. I've read that a 125 strap will not allow adaptive voltage. My xmp profile sets the 3000mhz on the 125 strap so I'm going to have to try other things with 100 strap. So far, no luck. I can boot into windows sometimes, other times it will boot loop and I have to reset CMOS to post. I've tried: DRAM: 3000mhz 100 strap 1.350 v 15-17-17-35 2t vccsa +0.200v CPU: Just set some manual voltages ~ 1.2 vcore & vcache. Left all the speed multiplers on auto I didn't want to push vccsa higher cause I didn't know what the actual reading was. Funny thing is when I booted into windows with that setting, cpuid shows 16gb ram at 2133mhz. I went into bios to check and it doesn't detect 2 of the ram modules, putting it into dual channel mode. AIYAH! - Getting 3000mhz on 100 strap is very stressful.  EDIT - HWINFO64 VCCSA = VIN6, just did some testing and confirmed. Going to try working that 3000mhz 100 strap further. |
Posted By: sexpot
Date Posted: 11 Aug 2015 at 9:17pm
|
3000mhz 100 strap ram seems no go with this ram/mobo combo. Atleast not with volts I'm comfortable running 24/7. One last question. After I found out my stable fixed vcore settings, how do I go about setting adaptive voltage to lower the core frequency and core voltage while idle? I'm currently testing the following settings with Real Bench 2.41, "stress test - 16gb ram 8 hours" 4300mhz cpu oc 43x100 bclk 1.2vcore, 1.85v input, llc lvl3 4000mhz cache 40x100 blck 1.2vcache 2800mhz ddr4 ram 15-15-15-35 1t 28x100 1.35v +0.15v vccsa |
Posted By: sexpot
Date Posted: 13 Aug 2015 at 12:41am
|
Finally got my clocks dialed in! I'm happy, my puter is happy and games are butter smooth! real bench stable 8hr stress test with 16gb ram usage. 12 thread/1100MB ram hci test overnight pass! Core freq: 4.3GHz 43x100 1.21v core (adaptive, love that idle volt  )1.85v input llc = lvl3 Cache freq: 4.0GHz 40x100 1.2v cache (fixed) Dram freq: 2800MHz 28x100 15-15-15-35 1t 1.35v 0.960 vcca Gaming loads in @ ~55 degrees celcius, real bench loads at high 70's. I can live with that and fans are running on low voltage for noise suppression. It's been a long and many hours of reading to get these clocks dialed in and was fun. |
Posted By: parsec
Date Posted: 13 Aug 2015 at 1:48am
|
Nice job on the OC, and it really wasn't a long time getting it dialed in, a day or so, right? I agree that VIN6 is the VCCSA voltage. I have a few suggestions for your OC and memory settings, although you may not need them at all. For the CPU VCore, you're using Adaptive voltage, with the VCore set to 1.21V, and I'm guessing the CPU VCore Adaptive Offset is on Auto, is this all correct? If that is correct, you can try setting the CPU VCore Adaptive Offset to a small negative value, such as -0.005V. That is, if you want to try reducing your CPU VCore even more. Question, are you monitoring the HWiNFO VCore reading? Sounds like you are if you are seeing the low idle voltages. That is, rather than the Core VID readings at the top of the HWiNFO sensor display. I always see a slightly higher VCore reading using Adaptive Voltage, compared to the VIDs. That is normal for Adaptive voltage. I was afraid getting your memory to run at 3000 would be difficult. One suggestion about getting that to work. Set the memory speed manually to 3000, with the BCLK at 100.0 MHz. Then set ALL the memory timings (and I mean ALL of them) to Auto. Keep you memory voltage at 1.35V, and the VCCSA at your value for 2800. Then try to boot, of course. If that works, you can then check what the Auto memory timing settings actually resulted in. You probably won't like them, but at least you got 3000 working. The HWiNFO System Summary screen will show the basic timings.Another trick, download the ASRock Timing Configurator ver:3.0.5 program from here: http://www.asrock.com/mb/Intel/X99%20OC%20Formula/?cat=Download&os=Win8a64" rel="nofollow - http://www.asrock.com/mb/Intel/X99%20OC%20Formula/?cat=Download&os=Win8a64 It's a Windows program, and worked with my X99 board. It shows all the memory timing settings, and lets you tweak them in Windows. They won't stick if you reboot, FYI. Question, what is the boot time from a cold/shutdown startup like with your board? ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: sexpot
Date Posted: 13 Aug 2015 at 7:20am
|
Hi parsec, for my adaptive vcore settings. I set the value to +0.01 and the turbo volt to 1.19. Under load it fluctuates around 1.20 - 1.21v. I'm monitoring vcore reading while benching with cpu-z. I only used hwinfo for vccsa value when I was entering volts into the bios and for max/average core temps. I've noted your suggestions on trying for 3000mhz ram again, but for the time being, I am content with 2800 and the low vccsa required to run it. Maybe later on I might try for 3000mhz if it really bugs me :p
I'll have to get back to you with the boot time. But from what I recall, it takes a good 2-3 seconds sitting at the asrock screen waiting to see if I want to go into bios or not. Once it passes the post, it's relatively quick from the spinning windows logo. EDIT - Just got home and timed a cold boot. 35 seconds from the time I pressed the power button to desktop screen. |
Posted By: sexpot
Date Posted: 29 Aug 2015 at 1:59am
|
Guys, is it just me or does the Asrock Post screen take quite a bit longer than normal to load? Everytime I reset the computer or cold boot, it sits at the Asrock screen asking if I want to enter bios or not for a long time. After that, it loads into windows really fast. Compared to previous boards, the post screen normally takes only 1-2 seconds. With this board, I'm sitting there looking at it for at least 20-25 seconds. Total cold boot time is around 30-35 seconds. Is it possible to speed this up?
|