DDR4 Overclock - Lost Money - Safe?

Scythan

Reputable
Oct 10, 2015
4
0
4,510
Hey guys I recently finished my Z170 ASUS Deluxe Skylake build and after having one mobo DOA and the other BSOD oddly (and after RMAing both) I have found a quasi-stable (W10 errors) system. However, I am running my RAM at 2100 (stock) when I paid extra money for 3200 rated GSkill RipJaw RAM. As such the pressure is high in me to use XMP to clock the RAM at 3200 but I am concerned this is what CAUSED the BSOD (which resulted in the computer no longer displaying video, so it was irreversible) of the second board. I am scared to <death> and not an expert in overclocking. Many of you will say it's not worth my time as RAM benefits are minimal but I do transfer large (100GB+) files between drives often and did pay extra for 3200 MHz RAM. What should I do and how should I do it?

EDIT: This experience has been difficult for me despite the fact that I've built PCs for years. Upon analysis I find that the uncertainty I feel is due to the 'cold case' nature of my misfortune and not really knowing if setting up the auto-XMP profile (Which changed a vast amount of configurations in the UEFI BIOS) 'bricked' the second board, or set the RAM to something that induced instability etc. or if I was stupendously unlucky and had two bad boards in a row. The statistical likelihood of that seems rather incredible to me, but I have to acknowledge its possible. I created this account only to ask you fine folk for answers, beseeching your knowledge to make me feel a little more secure in my new rig and also advise on my best course of action on my RAM. Thank you so much.
 
Solution
You might as well try it as you paid for it. I have my doubts that XMP bricked the second board. A CMOS clear didn't help? Tried running Memtest 86 bootable version on sticks individually? What are your Windows 10 errors?

Scythan

Reputable
Oct 10, 2015
4
0
4,510


It doesn't make too much sense to me either, but I have to entertain it as the most likely possibility. CMOS clear did not help, no, though there was debate between ASUS techs how to do that, one suggested removing the battery and the other suggested bridging two metal pins with a metal object - both were tried. Both denied there was any such thing as 'Level II' or 'Tier 2' support. I find their convictions suspect.

The W10 errors surround the Start Menu/Cortana not working, this seems to be a widely reported bug that upon clicking the Start Menu doesn't appear and the most useful suggestion thus far has been to leave on the 'most recently used' list and, knock on wood, the issue hasn't re-appeared yet.

Because the RAM is intended to clock at 3200 it seems sensible to me that going into the UEFI and selecting the 3200 MHz XMP profile that clocks the RAM at that should be a one-and-done but what I seek to learn here is whether or not that can cause system instability.
 

Scythan

Reputable
Oct 10, 2015
4
0
4,510


Due to the short term that Skylake (6700K specifically) has been on the market and the Z170 architecture when this was happening (about a month ago) I was unable to find any updated drivers beyond what the board was running on.

The 'final solution' was, after RMAing the second board (an ASUS Z170-A from Newegg, the previous RMA being the same thing) buying a $155 more expensive (and identical in all regards except bells and whistles) Z170 Deluxe from a local retailer (Fry's). It could have been a 'bad batch' at NewEgg - improperly stored or some such but two DOA mobos in a row is a statistical anomaly I have a very tough time choking down as coincidence.

This has prevented me from bringing the RAM to 3200MHz on the Deluxe.
 
Fixing Cortana on Win10 can be tried as follows(worked for me). In Task Manager, you should just be able to "end" the background process Cortana. It should restart itself, and Cortana should be working again. May see the issue again though time to time. I guess the good news is that your up and running again, though as you pointed out, to DOA boards seems pretty unlikely. If you think the RAM is somehow causing the problem, maybe try an RMA there. Perhaps the XMP profile itself was made incorrectly, and it's adjusting one of the settings/voltages way higher than it should be.