Bad Memory = Reinstall Windows?

[Billy777]

New build, installed the OS then ran Memtest86 with lots of errors.

One of the four RAM modules is clearly bad and will RMA.

Now, Windows 7 seems to run normally, but should I trust that install or is it better to run the install again when I get the memory problem sorted out?

Would one bad module cause a corrupt Win7 install?

 

[Brett928S2]

Hi

Ram has nothing to do with bad windows... just replace the stick...

All the best Brett

 

[gamerk316]

Yeah, replace the faulty stick(s). Nothing to do with the OS.

 

[Hawkeye22]

In this circumstance, it may not matter, but bad ram definately leads to corrupt files. After all, most files are in ram before theyt get saved to disk. In fact, I've had bad ram hose my system files before and had to reinstall the OS, after fixing the ram of course.

In you case, since the OS is working ok, you are most likely fine. If you are paranoid about it, reinstall.

 

[pjmelect]

Bad memory can lead to corrupted files on your operating system and to be safe you should reinstall. If you don't want to reinstall for some reason then try running as the administrator in a DOS box "SFC /scannow" if it comes up with any unfix-able errors then you must reinstall.

 

[djscribbles]

I would reinstall the OS. As hawkeye22 said, you can't know what got corrupted by the bad ram.

Especially since you just installed the OS, you likely don't have much to lose by doing it now; and any corruption may take a while to surface, making the reinstall more of a pain after you get all setup. Not to mention, you'll always be suspicious when you run into issues.

 

[drwho1]

Keyword **new build**
so just RMA your RAM, when you receive your replacement RAM test it again, if No Errors
you should be good to go. I wouldn't re install the OS. Is not needed for this situation.

I had a similar issue and my build was just over a year old, RMA my RAM, got the replacements in about 2 weeks, tested again (to be sure) and sure enough no problems.

After that I tested it further, with very intensive memory tasks like video editing while doing other stuff as well, and NO issues. My computer would shut down before I RMA my RAM with far less than that.

Is been over 2 months since I made the switch, NO problems since then.

 

[Hawkeye22]

Keyword **new build**
so just RMA your RAM, when you receive your replacement RAM test it again, if No Errors
you should be good to go. I wouldn't re install the OS. Is not needed for this situation.

I had a similar issue and my build was just over a year old, RMA my RAM, got the replacements in about 2 weeks, tested again (to be sure) and sure enough no problems.

After that I tested it further, with very intensive memory tasks like video editing while doing other stuff as well, and NO issues. My computer would shut down before I RMA my RAM with far less than that.

Is been over 2 months since I made the switch, NO problems since then.

Retesting your ram does nothing for checking for corrupt files on the drive. It just means your ram is now good.

Anytime I install new ram (especially if OC'ing) on an existing OS, I'll boot into a live linux CD or a memtest86+ boot disk to test ram before letting my OS actually boot using it.

 

[Billy777]

Thanks guys...

I'm going to clean install the OS again.. no matter what answer is correct, if I ran into trouble down the road I'd always have to wonder if it was from a corrupt installation.


And remember, don't make my mistake... always test your memory on a new build before you do anything else. :- )

 

[Billy777]

AND... Mushkin tech support and service are outstanding. They were all over me today, with a prepaid RMA and an "Advance RMA" where they ship the replacement tomorrow before they get the RMA back from you.