Windows 10: BSOD after RAM upgrade

Hello all,

A week ago I recieved my order G.Skill Ripjaws V 16GB 2x8GB DDR4 3200MHz C16 F4-3200C16D-16GVKB

I had already one pair of the same ram up and running for 2 years.

After the ram installation the system recognize only 16GB and the other half appears as system reserved.

After 2-3 restarts the system collapsed and was giving BSOD with different messages each time.
I proceed to bios update and did a clean windows install on a new disk.

On the new installation i tried, successfully.. to mount the 2 pairs of ram and the system now recognize 32GB of RAM

Yesterday after the last update everything crashed again bringing back BSOD again with random messages like:

"IRQL NOT LESS OR EQUAL"



“MEMORY_MANAGEMENT”

“win32kfull.sys”



Any ideas? Broken Motherboard?? Or CPU??



Sys info and minidump


Thank you in advance,

:)

 

BSOD after RAM upgrade

Tried all of these and nothing worked. Still got random BSOD. I also noticed I was unable to left click the start button now. I read a few posts on that and tried suggestions with no luck.

I installed this RAM not realizing there were a lot of updates that installed upon reboot. Is there anything could have damaged as a result of not updating before installing new RAM?

 

Video card or RAM need upgrading?

Memtest: no errors after 10 hrs.
I'm going to perform the Primetest, later on. Get back to you on that.
I'm going to take it step by step, guys. I need to find the problem with this current computer. I might have to upgrade some components, so that it is still runnable. As for the new one, yes....i will build on it later. I need to find something decent 'gaming experience', all suggestions appreciated. THanks.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.