If anyone could shed a little light on this, I'd be extremely grateful. I have a 2006 mac pro 1.1 (intel cpu) that consistently stops responding after 4-5 minutes.
The mouse still moves but nothing else responds, this applies for both the hard disk and the installer disk. The diagnostic LEDs aren't indicating anything out of the ordinary and while it works, the audio and network functions correctly.
So far I have tried:
- Booting off original drive
- Reinstalling on original drive (snow leopard disk, clean install)
- Installing on new ssd drive (purchased for this machine)
- Running boot with D and Option/Alt + D held for diagnostic mode (ignores command for diagnostics but accepts f12 to eject and C to boot from disc)
- Checking each pair of ram cards on their own.
- Testing each ram riser/riser slot combination with ram that I know works (tested in another server)
Contacting Apple with this data, I was told that the Mac and Snow Leopard OS are too old for Apple stores to deal with and only an apple certified repair centre would take them.
If anyone has any idea what might be wrong and how I can better narrow down the cause of this, then I'm all ears and will update with whatever subsequent tests are suggested.
*For background: this machine will primaily be used for pulling cross platform libgdx code and compiling it for iOS. I had a hackintosh VM set up for it originally but wanted to have my compiled apps be 100% T&C compliant.
Also, this has been cross posted in Super User here: superuser.com/questions/1049421/
I've been struggling with this machine each weekend for about 7 months now.*
After running Apple Hardware Test thanks to JMY1000's link and assistance, I'm now furnished with the error code: 4SNS/1/40000001:VMBS which a quick search narrows down to a sensor issue with:
- The RAM/Risers (which I can reasonably discount from the above tests)
- The Graphics Card (Tested with another card, same error code)
- Logic Board (Looks like this is the problem unfortunately.)
Update 2: Tested a different graphics card (same model) and the error code is the same. Looks like this is a logic board issue unfortunately.