Best stable ddr4 3000 with xmp profile

[elkido122]

I plan on getting on ddr4 ram at 3000 and running it with my msi Z170a gaming m5 using xmp to make it go to 3000. I currently have Corsair lpx ddr4 in xmp at 3000 but feel it's not stable in xmp and getting page fault in non pages area is cause of this ram at 3000 not liking xmp. I do not have anything changed with the cpu either, everything stock there. Anyways is there at better more stable ram at that speed like Gskill or something? Thanks sorry for the ramble on

 

[UsandThem]

I plan on getting on ddr4 ram at 3000 and running it with my msi Z170a gaming m5 using xmp to make it go to 3000. I currently have Corsair lpx ddr4 in xmp at 3000 but feel it's not stable in xmp and getting page fault in non pages area is cause of this ram at 3000 not liking xmp. I do not have anything changed with the cpu either, everything stock there. Anyways is there at better more stable ram at that speed like Gskill or something? Thanks sorry for the ramble on

The best, most stable RAM are the ones that are MSI's QVL (Quality Vendor List) or certified by the RAM manufacturer to work properly with your motherboard:

https://us.msi.com/Motherboard/support/Z170A-GAMING-M5.html#support-mem

http://gskill.com/en/configurator?manu=55&chip=2484&model=2500

http://www.corsair.com/en-us/memory-finder

 

[elkido122]

thanks for the reply man. i ran memtest86 for 3 hours and no errors. i ran a ssd health test and it was good to. what the heck would of caused the page fault in non paged area then? is the ram just not cooperating at 3000 or something? idk

 

[UsandThem]

thanks for the reply man. i ran memtest86 for 3 hours and no errors. i ran a ssd health test and it was good to. what the heck would of caused the page fault in non paged area then? is the ram just not cooperating at 3000 or something? idk

Probably a Windows 10 bug/issue. There seems to be a lot of weird ones lately. I just finished figuring out why a few of my SSDs were sitting at 100% disk activity with nothing going on. The reason? A Windows 10 update bug.

BTW, are you using the latest MSI BIOS for your motherboard (1.C)?

 

[elkido122]

I am using the the 1.C bios yes. Yea possibly windows who knows

 

[elkido122]

 

[Hail The Brain Slug]

I'm inclined to say that unless you have defective sticks, that memory is quite good and stable. I have 4x8GB of the corsair vengeance lpx 3000 in my x99 build with timings tweaked a lot and its perfectly stable in memtest and Windows. I do have the voltage up a little to 1.42 but that's for ny timings, it was stable at the default XMP settings at the rated 1.35 volts.

Also have the same memory in two other systems working perfectly well.

That bsod could be caused by CPU instability or overclocking. I notice you say everything is stock but in order to run 3000 memory it changes the strap to 125MHz, unless you change your multipliers to account for the 25% increase, you might have the cpu running at too high of clockspeeds. (Or too low voltage for the clocks)

 

[elkido122]

I thought turning on xmp and leaving everything else is OK. Usually they say you can. Anyways I haven't touch anything cpu related. It's only 200mhz overclock since it puts it at 4.2. At that speed I doubt it needs more voltage or anything changed.

 

[Hail The Brain Slug]

I thought turning on xmp and leaving everything else is OK. Usually they say you can. Anyways I haven't touch anything cpu related. It's only 200mhz overclock since it puts it at 4.2. At that speed I doubt it needs more voltage or anything changed.

If you have the XMP setup, it's not possible for your CPU to be at 4.2. The frequency will have to be a multiple of 125, so 4.25 is possible. Check your frequencies at idle and load in CPU-z to see what multiplier and frequency it's running at.

 

[elkido122]

 

[elkido122]

that was at idle. let me do one for under load.

 

[Hail The Brain Slug]

I think you might not have the XMP setup properly. It's my understanding that in order for the memory to run at DDR4-3000 it has to have a strap of 125, so your multipliers change.

Grab a shot of your memory tab?

 

[elkido122]

 

[elkido122]

 

[elkido122]

that should be what you were asking for

 

[Hail The Brain Slug]

Well, I stand corrected. Although I thought the XMP profile for 3000 was supposed to switch to a 125 strap. Care to take some pics of your bios settings for that?

I only think this because I have the same memory, and the XMP profile switches both systems I've setup with it to a 125 strap/125MHz FSB.

Some reading around the internet, people believe a 125 strap is more stable for 3000 than a 100 strap.

 

[elkido122]

which bios setting?

 

[Hail The Brain Slug]

A pic of what's on this screen, then scroll down and a pic of the DRAM settings.

 

[elkido122]

 

[elkido122]

hope that helps
let me know

 

[Hail The Brain Slug]

hope that helps
let me know

Nope! I thought I was onto something but it all looks normal. Sorry to make you do all that for no conclusion. It must just be an x99 thing with 3000 requiring a 125 mhz strap. (Both HW-e and BW-e setups I've worked with required it).

You could try experimenting with overclocking the CPU or changing straps if the bsod happens frequently or reliably enough to see if you can get it to stop.

You could also try forcing the memory speed to 2800 or increasing system agent voltage or something, too. Maybe the memory is fine but the memory controller is being finicky.

 

[elkido122]

i just find it weird that the ring frequency it at 4.1 but when i look in cpu-z my cpu is constantly at 4.2 like there is no idle clock speed lol. thats fine its not that much stress on it now is it?

 

[elkido122]

 

[elkido122]

its not bad if my system is constantly running 4.2ghz and that there technically isnt an IDLE speed correct? temps are fine

 

[Hail The Brain Slug]

its not bad if my system is constantly running 4.2ghz and that there technically isnt an IDLE speed correct? temps are fine

It's fine - it's probably just your power profile in windows. If you set it to High Performance, it never clocks the CPU down (I deliberately do this on my desktops).

I did notice the voltage was low on your idle screenshot at 0.792 volts - I believe if speedstep doesn't clock the CPU down the voltage should not go down, either. Unless I am mistaken, this could lead to some issues with low voltage for the 4.2 GHz clock, although I admit I have no idea why it would do that.