Support in other languages: 
Reply
Paper Tape
estorch
Posts: 2
Registered: ‎09-09-2010
Location: Germany
0

Bluescreen on a S20 4105 with Windows 7 64 when populating DIMM6

I have a new S20 4105 and want to install 24 GB Memory. I have 6 x 4 GB Modules Kingston KTL-313E/4G. Windows 7 64 works fine with 5 DIMMs installed. When i install DIMM6 i get a Bluescreen when booting Windows. The Memory Modules are OK. Every Test under DOS (Memtest, PC-Doctor from Lenovo) says: 24 GB RAM are OK. I get the bluescreen too, when i try to enter Diagnostics via F11with installed 24 GB Memory. I use a quadro FX3800.

How can i use 24 GB RAM?

IPnaSh
Posts: 2,281
Kudos: 334
Solutions: 108
Registered: ‎06-05-2010
Location: Rosario, Santa Fe, Argentina
0

Re: Bluescreen on a S20 4105 with Windows 7 64 when populating DIMM6

Did you test DIMM6 bench alone?

IPnaSh
First Spanish Community Guru

Español Comunidad en Español  English English Community   Deutsche Deutsche Community

Lenovo title=
Paper Tape
estorch
Posts: 2
Registered: ‎09-09-2010
Location: Germany
0

Re: Bluescreen on a S20 4105 with Windows 7 64 when populating DIMM6

I `ve tested every memory DIMM Module alone.  They are all ok.

IPnaSh
Posts: 2,281
Kudos: 334
Solutions: 108
Registered: ‎06-05-2010
Location: Rosario, Santa Fe, Argentina
0

Re: Bluescreen on a S20 4105 with Windows 7 64 when populating DIMM6

And DIMM6 with DIMM5?

IPnaSh
First Spanish Community Guru

Español Comunidad en Español  English English Community   Deutsche Deutsche Community

Lenovo title=
psuturtle
Posts: 510
Topics: 5
Kudos: 124
Solutions: 65
Registered: ‎02-22-2010
Location: NC
0

Re: Bluescreen on a S20 4105 with Windows 7 64 when populating DIMM6

It's going to be hard to figure something like this out, but there's a chance that there's something with the Kingston memory causing a problem.  One suggestion (and probably the one you'll get from the tech support lines) is to use official Lenovo options for these parts.  These parts would be tested and officially supported on S20.  Probably not the answer you're looking for unfortunately.

 

The only other suggestion I have would be to remove any additional HW that you might have installed from the base config to make sure it's the memory causing your issue.