Blue screen crashes in Windows 7 when expanding memory

[cobito]

This is the company's PC#1. Before it completely dies, I decided to put in a couple of Kingston DDR2 667 modules I had lying around to bring the total to 6 Gb, enough to be able to play BF4.

The frequency of the 4 modules is 667Mhz, the timings are manually set to the Kington values (which are the slowest).

I ran Memtest86+ for a couple of hours and there were no problems. There are no problems on Linux either.

But there are problems with Windows 7 64-bit. Most often, a blue screen appears at startup, either during the Windows logo or when the desktop is about to load. Very occasionally, I've been able to finish the boot process and get a taste of Battlefield 4. During the game, I lost sound and it came back when I rebooted.

The blue screen says something about a device trying to corrupt the file system. This sounds like bad memory to me, but if Memtest doesn't show any errors and Linux works fine...

I think it might be a mapping issue, that Windows has set up a device using 32-bit memory addresses and when I started using 64-bit addresses, the device is overlapping with memory or something like that, since the change was from 4 to 6 Gb.

Any suggestions?

Thanks.

[Fassou]

-Check the motherboard manual for recommended slots for that configuration.
-Add a few tenths to the memory voltage.
-Boot with the slowest module alone to note the timings it assigns, then enter them manually.

Salu2!

[cobito]

Perfect, I'll do that. This morning I started to detect the first strange behaviors in Linux so it's exclusively a hardware issue.