These boards and CPUs *are finicky as hell with ram timings. Faster always equals bigger headache. Some kits work XMP flawlessly where others won’t run XMP no matter what you do. Add insult to injury and it gets worse when you change stock clocks on the CPU so it’s always beneficial to settle in your OC on the CPU and uncore first. I got lucky with the 3800 dominator I’m my specs. Runs XMP perfectly but I found I get better results dialing back to 3200 MHZ and CL16. Someone did a nice test and write up about a year ago showing the ludicrously priced 4200 MHz ram had inferior performance to 3600. Linus did one that showed anything over 3200 was a waste of money. Sounds good on paper but in this case faster doesn’t = better.*
First disable fast start up.*
The F1 prompt after a hardware fault is normal for the situation and a product of the underlying issue. What you have to remember is any recent board past DDR 2666 jdec stamdard is an overclock. The marketed XMP is not always attainable, sometimes you don’t get it and others you can actually do better. *Gskill is usually reliable and one of my go to kits. TridentZ or Dominator Platinum are all I use. Give me a moment here to check your kit. I’ll edit after.*
Edit: yeah that’s a decent kit but yes to the drawing board tweaking. Sometimes just entering timings manually is fine. Sometimes just upping the juice to 1.4V works fine. Sometimes just backing off the frequency a a bit and lower the CL too to make up for it works. I’ve had somewhere I load XMP, save and exist then don’t let it boot by spamming *the delete key and taking it out of XMP while the profile is already loaded then check the frequency is at your XMP and double check timings then save and exit. The last way has all the XMP values loaded but it’s not in XMP mode. Weird I know but I’ve done it successfully many times. *Another chip might run XMP fine as uncore differs with the silicon lottery just as much as the cores do. *Frustrating I know.*
On the bright side......
It wouldn’t be as much fun if everything just ran where it’s set to and what you selected worked 100% of the time! *That’s for the dell forums, mostly because those options don’t exist!*:rolleyes::cool:
The F1 prompt after a hardware fault is normal for the situation and a product of the underlying issue. What you have to remember is any recent board past DDR 2666 jdec stamdard is an overclock. The marketed XMP is not always attainable, sometimes you don’t get it and others you can actually do better. *Gskill is usually reliable and one of my go to kits. TridentZ or Dominator Platinum are all I use. Give me a moment here to check your kit. I’ll edit after.*
Edit: yeah that’s a decent kit but yes to the drawing board tweaking. Sometimes just entering timings manually is fine. Sometimes just upping the juice to 1.4V works fine. Sometimes just backing off the frequency a a bit and lower the CL too to make up for it works. I’ve had somewhere I load XMP, save and exist then don’t let it boot by spamming *the delete key and taking it out of XMP while the profile is already loaded then check the frequency is at your XMP and double check timings then save and exit. The last way has all the XMP values loaded but it’s not in XMP mode. Weird I know but I’ve done it successfully many times. *Another chip might run XMP fine as uncore differs with the silicon lottery just as much as the cores do. *Frustrating I know.*
On the bright side......
It wouldn’t be as much fun if everything just ran where it’s set to and what you selected worked 100% of the time! *That’s for the dell forums, mostly because those options don’t exist!*:rolleyes::cool:
