Can Bad RAM Cause Bad OS?

akoguiang

Commendable
Apr 22, 2016
9
0
1,510
Hey, guys. I posted something a week earlier about getting a blue screen after an hour or so. The RAM was the issue. So, I replaced the RAM with a new pair and no more blue screens! However, the computer still crashes, where the keyboard and mouse become frozen and opening Task Manager become impossible. The only way out was holding the power button and performing a hard reset. Unlike the previous solution with the blue screens, this problem with the hard crashes does not make the computer reboot automatically.

I reinstalled Windows twice with the bad RAM before getting the ones I have now. Should I reinstall Windows with the good ones?

TL;DR Can bad RAM modules cause corrupt operating system, and should I reinstall Windows?
 
Solution
Yes, you probably should: OS files may have been corrupted by your bad RAM before getting written to disk, file system structures may also have been corrupted as the OS read, modified and rewrote them to disk. Same goes if you run defragmentation, file copies and various other operations involving reading data from disk and re-writing it.

My Core2Duo got messed up really bad once due to a single bad bit of RAM when I upgraded it from 4GB to 8GB without doing a memtest86 burn-in to see if the memory checked out fine first. (It took five hours of burn-in before the first failure appeared and then I had the failure re-appear only on the same specific test pattern at that specific address but not on every pass.)
Yes, you probably should: OS files may have been corrupted by your bad RAM before getting written to disk, file system structures may also have been corrupted as the OS read, modified and rewrote them to disk. Same goes if you run defragmentation, file copies and various other operations involving reading data from disk and re-writing it.

My Core2Duo got messed up really bad once due to a single bad bit of RAM when I upgraded it from 4GB to 8GB without doing a memtest86 burn-in to see if the memory checked out fine first. (It took five hours of burn-in before the first failure appeared and then I had the failure re-appear only on the same specific test pattern at that specific address but not on every pass.)
 
Solution

Hi, I've already selected a best answer, but to answer your question, CPU temps never go above 50C when idle (when room temperature is relatively warm).