Memory issues

[Tamesh16]

Hello!
I got a blue screen on my Alienware r3 15 showing 'Kernel data inpage error'. Figured it might be memory seating issue, so I reseated all RAM and M.2 drives, wiped contacts with micro fiber cloth and dusted the board. 

The next boot was fine, but then froze during use and when rebooted the no memory could be detected. (no boot with power light pattern matching "Memory or RAM failure")

the system has two 8gb ddr4 sodimm so I swapped their positions and the memory works fine. Tested with TM5 with no errors. 

I assume it might be an improper seating issue, but should I get another set of sodimm just incase?

(I might buy one regardless its only $70 but just wanted to confirm what root cause this would indicate )

[RONOTHAN##]

Since you only got one BSOD before you reseated the memory, I'm gonna assume that one was probably just a software issue and thus not really relevant here. The first memory reseat probably didn't seat the memory correctly and caused the memory error code on the following boot, with the second reseat fixing that first one. 

 

If it's working fine as of now, I wouldn't bother replacing the RAM. If you keep getting blue screens, then I might start to consider it. 

 

1 hour ago, Tamesh16 said:

Tested with TM5 with no errors. 

Which TM5 config did you use? Different configs have different levels of stress, and some of them I'd be more inclined to trust than others. 

[Tamesh16]

5 hours ago, RONOTHAN## said:

Which TM5 config did you use?

I used extreme and medium 

No errors detected for both 

 

It could be but I will look out for any more errors. 

I notice online they mention the blue screen code I got might be os drive failure too but its a samsung 970 evo with minimal written to it in the few years I have owned it.

 

[RONOTHAN##]

9 hours ago, Tamesh16 said:

I used extreme and medium 

No errors detected for both 

Alright, Extreme1 Anta777 is a good config so I'd be willing to trust that it's probably fine. 

 

9 hours ago, Tamesh16 said:

I notice online they mention the blue screen code I got might be os drive failure too but its a samsung 970 evo with minimal written to it in the few years I have owned it.

I should mention that a couple years ago, there was a faulty batch of 970 Evo Plus's, so that might be what's going on here. I'm still more keen to call this just a one off error not to be seen again however and wouldn't go to replacing hardware just yet.