I hope Scott reads this because this is the same system he helped with: i5-2500K and DH67CL (I have W-7, W-8.1, Linux Mint, and Fedora installed on different SSDs, three Intel and one Crucial). This is not a warranty issue because the parts are too old.
To refresh the memory of anyone who cares, the system was completely non-operational because I used BIOS to match the 7-7-7-24 timing of RAM (I still don't understand why that was a problem, but that's water under the bridge). I was able to get it working by putting the motherboard into maintenance mode and then using recovery BIOS, thanks to Scott.
But ever since then, there have been two problems. I've never been able to see a pattern, but the time will sometimes be 6 hours later than it should, with this happening on both W-8.1 and Linux. I reset it and everything's fine. Worse, however, is that Ethernet connectivity will be lost, with a reboot fixing the problem, with this happening on both W-7 and Linux. What's strange is that I cannot remember losing Ethernet connectivity on W-8.1, but maybe that's just luck.
Idle temperatures for both processor and motherboard are in the high 20s due to a Noctua cooler and a fan blowing in from the side.
I tried four solutions: installing an Intel gigabyte NIC card, a new Ethernet cable, a different port on the router, and a new battery, but none of them fixed the problem. I have other systems using the same router and they never exhibit the time change or Ethernet drop-outs. I've run IPDT a number of times since then, but nothing bad every turns up. Scott mentioned at the time that there was a possibility that my screwing with memory timings in BIOS damaged the memory controller in the processor.
My questions are:
- Could a damaged memory controller cause the above problems. I would think it's possible.
- Is there a better utility I can use to test the memory controller?
- Could it be the motherboard? If so, how could I test it?
- Is there any other diagnostic test I can run?
I have a spare, used Ivy Bridge processor that I will install into the motherboard and run a long-term test, but first I want to exhaust any diagnostic possibilities with the current configuration.