F5F Stay Refreshed Power Users Overclocking i7 6700k OC x44 safe but xmp profile crashes

i7 6700k OC x44 safe but xmp profile crashes

i7 6700k OC x44 safe but xmp profile crashes

A
ajpate
Member
223
10-21-2016, 02:32 PM
#1
Hi this is my setup
CPU - i7 6700K (OCD to 4.4ghz with asus turning wizard)
Ram - ddr4 Gskill 3400mhz ram (2133mhz default, xmp profile crashes)
Mobo - Asus Z170a
I can easily overclock my CPU without issues, but every time I tried to enable XMP profile it would crash. I used asus optimal and it would try to run at 3000mhz but then it would shut down after a while. I’m really new to this and don’t know what to do right now. This is my second attempt at overclocking, and I’m a bit confused. Thanks for reading and helping!
A
ajpate
10-21-2016, 02:32 PM #1

Hi this is my setup
CPU - i7 6700K (OCD to 4.4ghz with asus turning wizard)
Ram - ddr4 Gskill 3400mhz ram (2133mhz default, xmp profile crashes)
Mobo - Asus Z170a
I can easily overclock my CPU without issues, but every time I tried to enable XMP profile it would crash. I used asus optimal and it would try to run at 3000mhz but then it would shut down after a while. I’m really new to this and don’t know what to do right now. This is my second attempt at overclocking, and I’m a bit confused. Thanks for reading and helping!

I
ImHiko
Junior Member
26
10-21-2016, 04:15 PM
#2
Adjust manual memory settings to latency configurations. Record the specific CAS latency your memory exhibits. If your memory runs at 3000MHz, consider lowering the CAS latency when downclocking. For example, with a 3000MHz speed, setting the memory to 400MHz below specifications can help. Try reducing the CAS latency to 14 or 15 and set command rate to 1 instead of 2 if the system boots.
I
ImHiko
10-21-2016, 04:15 PM #2

Adjust manual memory settings to latency configurations. Record the specific CAS latency your memory exhibits. If your memory runs at 3000MHz, consider lowering the CAS latency when downclocking. For example, with a 3000MHz speed, setting the memory to 400MHz below specifications can help. Try reducing the CAS latency to 14 or 15 and set command rate to 1 instead of 2 if the system boots.

_
_Gemini_
Junior Member
11
11-09-2016, 01:17 AM
#3
Use manual configurations on the memory to adjust latency settings. Set your memory to 3000mhz and write the specific CAS latency it has. It's also worth noting that if you configure the memory at 3000mhz, lowering the CAS latency can help when downclocking. Typically, setting the memory to 4000mhz below specifications and adjusting the command rate to 1 instead of 2 can improve stability during boot. I’m not sure how to manually set the latency for my Asus Z170A motherboard—it’s quite confusing with all the numbers. I tried to manually set it to 3000mhz and let the CPU auto-write at 4.5 GHz, which worked briefly before crashing. It seems my cooler Master Evo 212 isn’t sufficient, so I’m considering a H115i instead, though it’s defective. I’m really tired of water cooling and just placed an order for a Dark Rock Pro 3. I hope I can try to install it again once it arrives.
_
_Gemini_
11-09-2016, 01:17 AM #3

Use manual configurations on the memory to adjust latency settings. Set your memory to 3000mhz and write the specific CAS latency it has. It's also worth noting that if you configure the memory at 3000mhz, lowering the CAS latency can help when downclocking. Typically, setting the memory to 4000mhz below specifications and adjusting the command rate to 1 instead of 2 can improve stability during boot. I’m not sure how to manually set the latency for my Asus Z170A motherboard—it’s quite confusing with all the numbers. I tried to manually set it to 3000mhz and let the CPU auto-write at 4.5 GHz, which worked briefly before crashing. It seems my cooler Master Evo 212 isn’t sufficient, so I’m considering a H115i instead, though it’s defective. I’m really tired of water cooling and just placed an order for a Dark Rock Pro 3. I hope I can try to install it again once it arrives.