When using XMP you must make sure the Vdimm or Vram is at 1.35V. Otherwise it will be at 1.2V then it won’t post.
when you don’t get lost how do you get the pc to post after that? Normally that require a cmos clear.
Stable overclock now can’t be touched
- Thread starter JamGeo
- Start date
when you don’t get lost how do you get the pc to post after that? Normally that require a cmos clear.
I always assumed XMP dealt with the voltage.
When I attempt XMP it will attempt to boot for a while and I see the XMP LED on my mobo to come on and then go off, fans spin up quite a lot. Then it will boot and the logo comes up and it goes to the ‘Boot failure detected’ screen and have 3 options of load optimised defaults and boot, load optimised defaults and restart and enter bios. The odd occasion XMP will work after waiting 5 minutes plus for it to boot, but once I restart my pc or shut down and boot back up it will get caught by the spinning up for a few minutes and the. Majority of the time will show the boot failure detected error
When I attempt XMP it will attempt to boot for a while and I see the XMP LED on my mobo to come on and then go off, fans spin up quite a lot. Then it will boot and the logo comes up and it goes to the ‘Boot failure detected’ screen and have 3 options of load optimised defaults and boot, load optimised defaults and restart and enter bios. The odd occasion XMP will work after waiting 5 minutes plus for it to boot, but once I restart my pc or shut down and boot back up it will get caught by the spinning up for a few minutes and the. Majority of the time will show the boot failure detected error
It is meant to. But just do a check. I have had occasions where XMP just loaded the MHz and timings but not the ram voltage.
long as you make sure those volts are dialed in by XMP and the stocks fail or can’t boot then that’s fair enough.
To get another stick of ram say 2400Mhz or 2666MHz won’t be a bad idea to eliminate your motherboard. Or test the ram in another system.
there are 2 situation here. Motherboard just crap. Or ram is broken. I am leaning towards the latter as I have had ram that can’t do XMP on arrival.
I gave it a quick try with adding XMP and manually adding 1.35v, I even increased it to 1.40v+ but still no boot. I’ve seen some ram that’s 3200mhz and I’ll try it, I will keep it regardless of it fixing it or not and then get gigabyte to RMA this board for me.
I feel like it’s RAM now, I’m on default bios settings with a bit of added extra to VCCIO and VCCSA to test if it’s something on the CPU and I’m getting perfect boots and restarts.
Thank you for your help and guidance, I feel you’ve taught me a lot with over clocking from what I already knew
I feel like it’s RAM now, I’m on default bios settings with a bit of added extra to VCCIO and VCCSA to test if it’s something on the CPU and I’m getting perfect boots and restarts.
Thank you for your help and guidance, I feel you’ve taught me a lot with over clocking from what I already knew
So on Friday my new RAM arrived. It was some HyperX 3200mhz which runs at 2400mhz standard.
I originally had issues applying XMP to the new RAM which was worrying but after manually adding VCCIO and VCCSA (both lower than 1.14v) it began to become more stable. So I decided to manually key in XMP settings and even use a dram voltage of 1.34v and all weekend it has been stable, the only time I’ve had boot failure detected is if I dropped the voltages too low, but I’m happy as I have a lot of wiggle room in regards to where the numbers are, I’ve even managed to tighten the timings for XMP.
I have done reading on other people using the Aorus boards with 9th gen i7 CPU’s, who have also reported strange behaviour with RAM, over locking and XMP.
sounds like you got a resolution. at XMP the ram should be running at 1.35V. i have tried to undervolt ram, odesnt make much sense to do it as ram dont get terribly hot like CPU does and they are more resilliant than CPU.
so deifnitely apply the 1.35V manually if bios is doign soemthing odd.