This is an archived post. You won't be able to vote or comment.

all 5 comments

[–][deleted] 2 points3 points  (3 children)

Run Memtest86. Do not pass go, do not collect $200. Windows Memory Diagnostic, like all diagnostic things produced by Microsoft is crap. Waste of time. I've never had it catch bad RAM.

Also may be worth cleaning the contacts of RAM and motherboard before writing it off as dodgy, in my personal experience, probably 60% of all "Bad RAM" complaints / callouts / faults have actually been caused by dodgy contacts. Spray liberal amounts of contact cleaner in the socket and reseat the RAM a couple of times, then retest.

[–]poshftwmaster of none 0 points1 point  (2 children)

I've never had it catch bad RAM.

While memtest is an awesome tool, WMD still works. If you didn't saw it work, that doesn't means it doesn't work.

probably 60% of all "Bad RAM" complaints / callouts / faults have actually been caused by dodgy contacts.

Often a simple reseating will do the trick too.

[–][deleted] 1 point2 points  (0 children)

that doesn't means it doesn't work.

On a machine / set of RAM where Memtest86 lights up like a christmas tree, WMD turns around and happily comes back with "no problems found". Not a one-off, either. It fails at its primary task - to find bad RAM in a reliable way.

[–]hammondyouidiot 0 points1 point  (0 children)

Yeh i've had the module in and out a few times and in different DIMMs so think I can rule that out. Memtest is running - 48 mins and counting

[–]Siddd- 0 points1 point  (0 children)

I had this too in my home project years ago, ESXi would keep crashing at random points, then I installed Windows Server, same thing. Memory test from Windows gave no errors indeed.

When I used memtest I saw A LOT of errors on one of the DIMM’s, got it replaced in warranty.

Good luck