Problem with Dell Latitude D620

[Vegeta SM]

I have a problem with this laptop. I have Windows 7 installed, I have formatted it as if it were the system, but nothing. The problem is that when it enters the starting screen, it turns off completely. When I try it several times, I manage to get it to work fine. Any solution?

[cobito]

@vegeta-sm Could it be a temperature or power supply issue. Does it happen when it's still cold? Is the power supply okay: exposed wires, bent plug...?

[Vegeta SM]

It does it from the beginning, moreover, it seems that the more time passes, it is when it starts and works.
I just did a test and it turns out that if I remove a RAM memory module, it starts perfectly. I have tested both modules separately and in both slots and it works perfectly. This is getting on my nerves more.

[Sylver]

@vegeta-sm Try running a brush over the contacts on the RAM slots, a quick blow, and then reconnect them together as you always do. Do a BIOS reset just in case.

Saludos

[Vegeta SM]

@sylver said in Problem with dell latitude d620:

@vegeta-sm Try running a brush over the contacts of the RAM slots, a little puff and reconnect them together as always. Do a BIOS reset just in case.

Regards

I already did that, if one is used, it works fine, no matter the slot or module, the problem is when I put both, it loads windows and when it's about to start the desktop it turns off.

[Vegeta SM]

Could it be a problem with the charger that is no longer providing enough power? Because I just did another test, and I removed the internal WiFi card and it works with both modules.

[Vegeta SM]

Nobody could confirm it to me?

[cobito]

@vegeta-sm As I told you in my first response, a power failure is a possibility.

If it helps as a reference, I have an MSI M-662 (Core 2 Duo Meron) and it has something similar to yours. When I have two 1Gb modules, memtest shows errors. If I test each one separately in both slots, there is no problem. That laptop went through a pretty heavy operation that involved "unsoldering" the ethernet chip because the internal network had quite a few stability issues. Since then there have been no more stability issues but shortly after the memory problem started, so I blame it on the chipset itself (maybe I scratched something I shouldn't have).