BSOD after change RAM...

[mocax]

bought Aftershock Bolt about 6 months ago.
It uses the ASROCK B365M-HDV motherboard, with 2x8GB ddr4 3200 RAM running at 2666

I changed the RAM to corsair vengeance 2x16GB ddr4 2666 RAM, in BIOS, I set it to run at 2400

Managed to boot up, but after 10-20 minutes of use, it suddenly BSOD.
Later did a memory diagnostic but came back no errors.

I notice the RAM DIMMs are seated quite near the CPU stock heat sink.

Is it possible that the RAM will fail when the CPU becomes hotter?

Will it be better to invest in liquid cooling?

 

[DJ Pork Chop]

How come u underclock the ram speed ?

able to let it run as stock(no changes) to see if gt bsod still?

 

[hellspawn_one]

no, the ram can sustain the heat output from the CPU. Your CPU would fail first before the ram due to heat.

Try running one stick of ram at a time.

 

[ragnarok95]

Reset Bios or try running at XMP.

 

[watzup_ken]

It is common for RAMs to be very close to the CPU. So it should not be the reason for the BSOD especially when you did not run into any issues with your previous set of RAM.

Agree to try and reset your BIOs. If that does not help, then try 1 stick at a time to determine if there is a faulty stick.

 

[SkyShroud]

update ur bios

 

[yusoffb01]

set default speed

 

[mocax]

Reset cmos by removing the battery.

if I set default speed using the XMP profile, windows immediately get bsod kernel security check failure... can't even go to recovery...

what are the possibilities?
1. RAM faulty?
2. motherboard cannot accept 2x16GB DIMM?
3. RAM doesn't work as advertised?

The original ram that aftershock installed was ddr4 3200, I guess need to buy new ones with at least 3200...

 

[wwenze]

Let me correct a possibly common misconception

It is often thought that running RAM at slow interface speed will always be more stable

The problem is, yes that is true but this assumes other settings are kept constant. Most of the time, they are not. The latency settings are usually automatically scaled by the BIOS/UEFI such that in terms nanoseconds they are still the same. Meaning, the RAM is still working as hard as before. And sometimes, when the latencies are set wrongly, this actually makes it less stable.

For the general user, the most stable you can get, is to set to auto config using SPD and use whatever the settings that your RAM tells your computer to set.

ADD: Auto config without XMP. XMP is not part of JEDEC standards. (XMP is developed by Intel as an extension to SPD) It includes higher-performance memory timings, which may not be fully guaranteed by every product combinations out there.

I'll illustrate with example:
https://en.wikipedia.org/wiki/DDR4_SDRAM

Say a motherboard or CPU says it supports DDR4-3200. Note that in the table in the wiki link, DDR4-3200 has standards like DDR4-3200W for 20-20-20 and DDR4-3200AC which is 24-24-24. A product that says it supports DDR4-3200AC, be it the RAM or the motherboard, can and has to take DDR4-3200W in other to be JEDEC compliant when it says it supports DDR4-3200W. However, if you do something like DDR4-3200 18-18-18 or 26-26-26 for example, this becomes a non-guaranteed operating condition.

This holds true even at lower interface speeds: XMP is like SPD in that both encode a list of timings to use for different interface speeds. And the XMP timing may not be the same as SPD.