Windows 10: BSOD after installing new RAM (W10 x32)

I just put a new RAM, 2GB, on my computer, and when I turned it on, it worked nice for about 3 minutes. Then it suddenly froze compltely with nothing responding.
First Firefox, then My Computer window, then everything, all this in about 10s. After another 20s, blue screen showing "critical process died" showed up. I managed to see that out of 4GB that I now had, 3,25 were usable (I thought W10 x32 supports 4GB?). I am uploading a report.
I am almost aboslutely certain that this had something to do with the new RAM since before that it worked just fine, and now fine again after I removed the new one.
Any ideas?

:)

 

Continuous BSOD after installing new RAM

I have bought new 4 GB RAM and placed it in my laptop today. When I turn on my laptop, it does very well until 10 minutes get the BSOD. I have at least 5 BSOD this time and it very annoying. I had to run Memtest86 and found no error. Had to run Windows Memory
Diagnostic but stuck in 14% forever.

What should I do??

BSOD dump link + Memtest: Minidump

My laptop:

Windows 10 Home SL 64-bit

4 GB RAM upgradeable to 8 GB

Intel Core i7 7200U 2.5 GHz

1 TB HDD

 

Continuous BSOD after installing new RAM

Hi Danang,

We appreciate that you have provided us the results as well as your laptop's specifications. Here's a

link which includes troubleshooting steps for Blue Screen of Death (BSOD) issues. Select the appropriate answer for the questions to provide you the troubleshooting steps for the issue.

Let us know how it goes.

 

Hi Steffan,

Welcome to the 10forums.

Please check {windows partition}\windows\minidump and check if there are any dump files saved.
The zip is empty of dump files.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial

Please check your mainboard manufacturer for BIOS updates.

 

I solved this problem by switching the sockets, the older RAM is in position 1, and the new one is in position 0.
They were both Kingston 2GB 800Mhz, but the newer one had latency 6, and the old one 5, so I think this was causing a confilict, but it does not any more. Also, I intened to upgarde w10 x32 to x64 when I figure out how to retain the key I used for the 33bit install.

 

Well done solving it *Thumbs