Unsolved
This post is more than 5 years old
1 Message
1
7910
March 24th, 2019 05:00
Aurora R8, not able to enable Intel XMP in BIOS
Hey! This is my first post and admittedly I am not overly familiar with all the technicalities of Intel XMP memory but I figured it would be a straightforward process.
First, I'd like to mention all drivers and BIOS are up to date (1.0.1). I have recently purchased two Aurora R8's (built the same except for Windows as one has Pro and one has Home, I will list at the end) which came with the stock DDR4 RAM. One of the two R8's arrived first and I immediately put in 2 X 16GB of Kingston HyperX Fury DDR4 2666MHz (into slots 1 + 3) which obviously supports Intel XMP. I was able to go into the bios and simply "enable XMP memory". I have even added a 3rd 16GB (into slot 2) stick the same memory/brand and Intel XMP is still enabled.
The second Aurora R8 arrives and I do the same procedure, update drivers, bios, windows updates, etc. I swap out the stock DDR4 2666MHz memory for three sticks of the same Kingston HyperX Fury DDR4 2666MHz and turn the computer back on. It's just a black screen. I eventually figure out it via reading forums it's a memory issue and I begin thinking the memory is faulty but I want to test it first. I leave one 16GB HyperX Fury in Slot 1 and turn the computer on, it states there is a memory change, I click continue, it boots into Windows and everything works. I restart and it still will not let me enable "XMP memory". I keep checking each memory stick individually in Slot 1 and each time the computer boots correctly. So, I then go add another stick into Slot 3 and the computer boots up to tell me the memory config has changed. I click continue and onto Windows we go. Still the BIOS will not let me enable Intel XMP. So, I then try to add 3rd Kingston HyperX stick back into slot 4 this time and same thing when I reboot - black screen and restart. I turned the computer and then I go and take a Kingston HyperX RAM stick out of the other Aurora R8 and stick one in slot 2. I now have all 4 RAM banks filled with 16GB Kingston HyperX 2666MHz sticks. I turn the computer back and get the message that the RAM amount has changed. Great! However, when I then restart I still cannot enable XMP. Why?! :) On the first R8, which now has 2 X Fury HyperX 2666MHz sticks in slots 1 + 3 I can enable/disable at my leisure. There is no difference between these computers. Can someone please offer some guidance?
The only difference between the two is R8 #1 has Windows 10 Home and R8 #2 has Windows 10 Pro regardless before I upgraded to Pro on R8 I could not enable XMP as all the steps mentioned above pre-date the upgrade to Windows Pro. :)
Specifications are identical on both Aurora R8 except for Windows:
Intel Core i7-9700K
NVIDIA GeForce GTX 1070
NVIDIA GeForce GTX 1060
256GB SSD PCIe NVMe- Boot drive
2TB 7200 RPM - Storage
850 Watt Liquid Cooled
Killer Wireless
Windows 10 Home on Aurora R8 #1
Windows 10 Pro on Aurora R8 #2
oreobro
16 Posts
0
July 4th, 2020 13:00
I agree Ram has always been plug-and-play without any issues I don't know why they have to be different but maybe they want you to buy theirs. Does anyone have any experience replacing the main boot drive when I ordered mine I ordered the 250 nvme . I've been thinking of replacing that with a 2 terabyte Samsung Evo Plus. If I had of known at the time I can specify then I would have ordered a 2 gig
cubicfang
53 Posts
0
July 4th, 2020 13:00
@oreobro
There is not much difference. I believe if I waited a bit longer the second time I turned on the computer, the XMP profile may be automatically loaded anyway. My point is that black screens just should not happen whatsoever. RAM is supposed to be plug and play. Somehow those Aurora mainboards work otherwise.
I installed different RAM a couple of times and consistently got black screens. I even cleared BIOS this time but still get a black screen for the first boot.
r72019
8 Professor
•
5.3K Posts
0
July 4th, 2020 14:00
Actually a 2+ minute black screen after changing the RAM is normal. The PC needs time to process the RAM change the first time after it loads. It will always do this after removing or adding RAM.
Also, if you didn't remember to disable windows fast startup (the default shipped with config for any pc or new win 10 clean install) before unplugging the pc and removing the ram it is treated by the pc as an incorrect shutdown/ power loss, which is really bad for the pc and means the ram was actually still in use by the pc.
oreobro
16 Posts
0
July 4th, 2020 15:00
I never heard about having to disable fast startup and I've built my own computer and replaced Ram many times without any issues., mind you that was in the old days lol. That being said it recognized my intel XMP hyperx Fury 3200 megahertz Ram right away didn't have to change anything in the Bios my computer is working fantastic. Enlighten us and tell us how that is bad for the computer. Does it corrupt system files
cubicfang
53 Posts
0
July 4th, 2020 15:00
@r72019
Gosh, I never heard about the fast startup thing. How bad would that be for the PC? I think I did unplug and change RAM twice recently without turning off fast startup at all. And I did notice unsafe shutdown counts increased by 2 or 3 as reported by HWiNFO.
I really missed the old times when upgrading RAM was a piece of cake. Maybe I am just a bit too old to mess around with PC hardware.
r72019
8 Professor
•
5.3K Posts
0
July 4th, 2020 15:00
Win 10 default is fast startup enabled that means when you click "shutdown" it goes into standby mode, it doesn't "turn off" like in prior windows versions, and ram is still being used by the pc..
oreobro
16 Posts
0
July 4th, 2020 19:00
I actually have that feature turned off because my computer was turning on by itself when I first got my Alienware. It's been perfect since
cubicfang
53 Posts
0
July 5th, 2020 11:00
@r72019
I now think you may be wrong on Fast Startup. With Fast Startup enabled, Windows 10 seems to just load data from the hibernation file on the hard drive to RAM. RAM does not keep anything without power, according to my decade-old computer knowledge.