Have a MacBook Pro 15" Mid 2012 (Pre-Retina) that keeps restarting. It's running 10.13.6
When first bought the computer, I ran ASD on it and it passed. I then upgraded the computer and it ran fine for a while, and then the restarts began.
We've attempted to reinstall the OS via recovery mode, and it still restarts. And even in Safe mode the system restarts.
So either the firmware is corrupted, a part has gone bad, or a part is just not a good fit.
We tested the battery with Coconut Battery and found it to be in very good condition, and the AC adapter is an original 85W Adapter.
The Nvidia GPU could be the culprit, but the system will restart even when not doing anything graphic intensive (using Intel HD Graphics).
Of the parts upgraded were the CD-Drive (to a Blu-Ray Drive), the HDD (to an 2TB SSD), and the RAM (to 16GB 2133MHz).
I have upgraded many MacBookPro 9,1's before with 2133MHz RAM, but they were always the 2.7GHz model. This one is 2.6GHz, and while that shouldn't really make a difference I am grasping at straws.
Are there any other likely suspects? Or just swap the RAM to 1600MHz and see what happens?
When first bought the computer, I ran ASD on it and it passed. I then upgraded the computer and it ran fine for a while, and then the restarts began.
We've attempted to reinstall the OS via recovery mode, and it still restarts. And even in Safe mode the system restarts.
So either the firmware is corrupted, a part has gone bad, or a part is just not a good fit.
We tested the battery with Coconut Battery and found it to be in very good condition, and the AC adapter is an original 85W Adapter.
The Nvidia GPU could be the culprit, but the system will restart even when not doing anything graphic intensive (using Intel HD Graphics).
Of the parts upgraded were the CD-Drive (to a Blu-Ray Drive), the HDD (to an 2TB SSD), and the RAM (to 16GB 2133MHz).
I have upgraded many MacBookPro 9,1's before with 2133MHz RAM, but they were always the 2.7GHz model. This one is 2.6GHz, and while that shouldn't really make a difference I am grasping at straws.
Are there any other likely suspects? Or just swap the RAM to 1600MHz and see what happens?