View Single Post
Old 05-26-2017, 03:38 PM   #11
serr
Human being with feelings
 
Join Date: Sep 2010
Posts: 12,557
Default

A few comments:

The premise of a bug in OSX 10.8 that was later fixed in 10.10 sounds like a wild guess. What specific bug? Is this a known reported thing?

Was this scenario there from day 1 after a clean install of 10.8? If the answer is "no" then the root cause is something else.

---

Run a ram test in a loop overnight. If it makes it through that, your ram is good.

---

I'd boot from a system backup clone or an older known system if there is any question with the current system. Rule out that variable that way.
If no backups were ever made/kept, you should start so you save hours/days of downtime next time. Ultimately you can clone your system to another drive volume (identical and bootable) or disk image file (not directly bootable until put back in a volume) for a backup and then do a clean install to your main system drive to test a clean system with no mystery variables.
serr is offline   Reply With Quote