Mac Pro 3,1 black screen then fans on full

I have extensively researched this and from all accounts no one has ever found a fix - even with multiple known good GPU / various MacOS versions / new RAM / strip down and full cleaning (one guy even replaced the motherboard and PSU to no avail)

I have tried running it headless (physically removing the GPU(s)) and accessing via VNC viewer (thus eliminating GPU entirely) but still the same issue - after a period of time from accessing the login screen the mac will go black screen (there is an audible single 'tick' inside the case when this happens but no one has ever seen a LED warning inside the case if they have had the side off ....) then about 10 secs later the fans go on full throttle (default) and the only way to restart/shutdown is via the power button or the mains plug. As to whether the machine will restart ok or not, it seems entirely random; I have had a clear month of uptime or worst case scenario a wasted day of trying to get it running for more than a few seconds before the black screen.

...these 2008 Mac Pros still offer further usable life if this can be sorted out, so if you have experienced this and beaten the problem please save me and many others (it seems to be a very common issue!) from turning these well designed Mac Pros into landfill/reclamation.


My suspicions lie more with how the OS handles the hardware but it will in that case probably be something that has changed in everything OS since possibly Mavericks.

Safe boot makes no difference.


**Putting an Ubuntu drive in it and booting from that makes the issue go away completely**


I look forward to hearing from you if you can help or even tell me your experiences trying to troubleshoot this frustrating issue.


Many thanks


Andy

Posted on Jan 2, 2021 2:10 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 2, 2021 7:37 AM

Panic Reports are stored at:

/Library/Logs/DiagnosticReports


If you copy and paste that string into:

Finder > Go menu > Go to Folder


it will take you to where those reports are stored.


They are named with Date&Time and end in .panic

You can post the entire report here, by using the “additional text” Icon in the reply header (looks like a paper with writing).


Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.


There are three quick take-aways from any panic report.


1) The panic-reason,


2) the extensions present at the "scene of the crime", and


3) the BSD process in which the problem occurred.


One more item that is important is the names of any third-party Extensions you have added. They are shown FIRST in the extensions loaded section


Similar questions

65 replies
Question marked as Top-ranking reply

Jan 2, 2021 7:37 AM in response to Andrew Beardsmore

Panic Reports are stored at:

/Library/Logs/DiagnosticReports


If you copy and paste that string into:

Finder > Go menu > Go to Folder


it will take you to where those reports are stored.


They are named with Date&Time and end in .panic

You can post the entire report here, by using the “additional text” Icon in the reply header (looks like a paper with writing).


Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.


There are three quick take-aways from any panic report.


1) The panic-reason,


2) the extensions present at the "scene of the crime", and


3) the BSD process in which the problem occurred.


One more item that is important is the names of any third-party Extensions you have added. They are shown FIRST in the extensions loaded section


Jan 2, 2021 8:37 AM in response to Andrew Beardsmore

OK - stripped whole machine down to eyeball the logic board and clean out dust etc from various nooks and crannies such as the PSU etc, reassembled and further testing revealed that pressing the little diagnostics button between the memory risers (use a special Apple tool nylon stick thing) gives expected lights as per service manual (standby yellow (trickle power), pwrg green (good - all power rails are functioning), EFI green (EFI loaded) and no EFI GPU light - as I am running a non Mac GPU that doesn't give a boot screen - goes to login screen without it.

Looked good; relieved to see no CPU over heats etc. ...

BUT - the exact moment the Mac black screens and the fans start to speed up, retesting by pressing that diagnostics button shows the PWRG green light DOES NOT now show (i.e. one or more power rails are malfunctioning).

Thought I'd update this in case others with similar issues find this thread.

@Grant - thank you for responding; I had seen your helpful advice on another older (and 10 page !!) thread. Think I just need to try swapping out a PSU first, unless you have different idea?

Jan 30, 2021 8:32 AM in response to Grant Bennet-Alder

I just had a look & nothing suffixed with .panic but there's two of these at or around the time the mac had issues - sadly I did not make a note of the time it went down although I suspect from the info contained these occurred shortly after boot and are a few minutes apart

'fseventsd_2021-01-29-171712_Big-Mac-Pro.crash'

Process: fseventsd [59]

Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/Support/fseventsd

Identifier: fseventsd

Version: 1223.10.1

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Responsible: fseventsd [59]

User ID: 0


Date/Time: 2021-01-29 17:17:07.710 +0000

OS Version: Mac OS X 10.11.6 (15G22010)

Report Version: 11

Anonymous UUID: 90AA9F3C-A72F-CCC9-C4E0-A18FD9C282B0



Time Awake Since Boot: 76 seconds


System Integrity Protection: enabled


Crashed Thread: 48


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000010a540000

Exception Note: EXC_CORPSE_NOTIFY


VM Regions Near 0x10a540000:

MALLOC_LARGE 000000010a440000-000000010a540000 [ 1024K] rw-/rwx SM=PRV

--> Process Corpse Info 000000010a540000-000000010a740000 [ 2048K] rw-/rwx SM=COW

STACK GUARD 0000700000000000-0000700000001000 [ 4K] ---/rwx SM=NUL stack guard for thread 1


Jan 30, 2021 8:35 AM in response to Andrew Beardsmore

the second one occurs after 250 seconds

'fseventsd_2021-01-29-172015_Big-Mac-Pro.crash'


Process: fseventsd [299]

Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/Support/fseventsd

Identifier: fseventsd

Version: 1223.10.1

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Responsible: fseventsd [299]

User ID: 0


Date/Time: 2021-01-29 17:20:05.890 +0000

OS Version: Mac OS X 10.11.6 (15G22010)

Report Version: 11

Anonymous UUID: 90AA9F3C-A72F-CCC9-C4E0-A18FD9C282B0



Time Awake Since Boot: 250 seconds


System Integrity Protection: enabled


Crashed Thread: 11


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000106bbc000

Exception Note: EXC_CORPSE_NOTIFY


VM Regions Near 0x106bbc000:

MALLOC_LARGE 0000000106b3c000-0000000106bbc000 [ 512K] rw-/rwx SM=PRV

-->

Dispatch continuations 0000000106c00000-0000000107c00000 [ 16.0M] rw-/rwx SM=PRV

Jan 30, 2021 9:37 AM in response to Andrew Beardsmore

These two most recent posts are NOT similar to your previous ones.


They are segmentation faults -- references to areas of I/O or memory not mapped to any task.


They occurred in the File System Event Daemon, the always-running File system event processing task. You should consider doing a through Disk Repair, especially of your entire boot drive (each partition separately including the physical device.)

Apr 8, 2021 3:44 PM in response to Andrew Beardsmore

Yup, a Mac Pro 3,1.


Unaltered bios etc.


Crashing went on for a couple of years, steadily getting worse and worse. Swapping motherboards didn't reduce the frequency, but did reduce the severety. In hindsight, I'm not actually sure when the problem started - System never had issues with a GTX 480 and running Mountain Lion. Problem seemed to be introduced somewhere after upgrading the OS (several times), the card, and the drivers.


Both before and after, I was fiddling with different configurations of Nvidia and CUDA drivers. Used a website (http://www.macvidcards.com/drivers.html) to determine and download the best drivers based on my OS.


I'm running Yosemite (OSX 10.10.5). I could technically move the 3,1 up one more version, but I'm terrified it'll become (even) less stable.


I've never had the logs checked by an expert.

Jan 2, 2021 9:20 AM in response to Andrew Beardsmore

If the System Management Controller fails to turn the fans speeds DOWN over several seconds, they fail-safe to full speed. The fans going full speed are a side effect of some sort of serious malfunction that stopped processing -- they are not the cause of the malfunction.


My guess was that there might be some stored panic reports.


But If you are on the trail of bad power -- then by all means, press ahead with that first.

Jan 30, 2021 6:49 AM in response to Andrew Beardsmore

<< 45 minutes later and the exact same issue occurred. >>


Kernel panic for ANY reason will present very similar symptoms.

You should check the logs again and see if you have a stored panic report.


The 'approved method' for this debugging is to strip the machine down to the smallest working set of parts that can do anything, run it that way for a while, then slowly add aback one component at a time until it ides, then suspect the last-added part.

Feb 16, 2021 12:35 PM in response to Andrew Beardsmore

I'm joining in here, on the off-chance that sharing my similar nightmare will help contribute to a solution getting found.


MacPro 3,1, Yosemite, Nvidia GTX 680. I have a very similar issue, and nothing I've tried has ever fixed it. The only thing that even made a dent in it was replacing my motherboard, which changed it from a hard crash with spinning fans and auto-reboot to a softer crash that at least leaves logs.


For me it's a cascading failure. I'll run fine for a week or two, then crash. The next crash will come much sooner, maybe a day or two. Then after a couple hours, then after a minute or two, rendering the computer useless. Before the motherboard replacement, it would stop booting altogether. The only way to get the system up and running again was stripping out everything leaving just the boot drive, one stick of RAM, and putting back the stock graphics card it came with. System would boot, and then I could put everything back and it would run fine again for 1-6 weeks.


Since replacing the motherboard, it never runs smoothly for more than 2 weeks, but it also rarely stops booting. I can usually re-stabilize by resetting PRAM and SMC, restarting, booting in safe mode, restarting AGAIN, then doing another fresh restart. Why do I have to do that several times before the system stops crashing? No idea. But it works for a while. Then sooner or later, it always crashes again. Could be idle, could be in the middle of heavy work. There's no pattern.


Here's other things I've tried that have NOT solved the problem:

  • 3 other Nvidia cards have been tried. Some made it worse, none made it better.
  • Many different configurations of nVidia and CUDA drivers, including ones recommended for my exact build of Yosemite.
  • Cloned my boot drive (SSD), and ran an OS repair. All it did was make my nVidia drivers invalid.
  • Swapped in the cloned SSD and started running on that. Drive is slightly larger, and plugged into a different bay, just in case. No change, so it's definitely not a hardware issue with the boot drive.
  • PSU has been tested and found good, though not replaced.


I'm desperate to find a fix, and just about out of ideas. Upgrade to El Capitan and pray...?


Mar 3, 2021 11:59 AM in response to Andrew Beardsmore

Hard to say. System has been stable for a couple of weeks, and I don't want to jinx it. If past experience is a guide, it could start crashing again any day.


That said, the most recent thing I tried came from stumbling onto a very old thread about a related error message. It suggested moving the graphics card to slot 2, as slot 1 in the 2008 MacPro was a bit flaky.


Did something that simple do the trick? I don't know yet. But maybe worth trying?

Mar 4, 2021 1:46 AM in response to Sailordoom

hmmmm - I even tried it without optical drives and/or graphics card and it would crash (headless; using VNC viewer to log in). My current conclusion based on the fact that it has stayed powered on at the login screen for over a week but crashes within an hour or two or sometimes even 5 mins once you have logged in, is that the graphics card controller chip on the logic board, or the board itself in that area, is failing due to heat stress over time; as I understand it logging in fully engages the GPU and as the GPU itself has been eliminated from the list of culprits then the controller chip is the next item in that chain. Replacing the logic board is a big job so currently this is only a hypothesis.

Mar 9, 2021 4:29 PM in response to Andrew Beardsmore

No new crashes yet, but that of course could change at any time ; )


I turn my Mac off every night, so that would statistically bring down the frequency of crashes, just by being on for fewer hours a week.


Interesting to hear that the slot change had an impact! This issue is rare enough that I suspect it's a confluence of multiple issues, and that might be why it's so hard to find a clear fix. Card slot seems to be PART of the problem, but not the whole deal.


I don't remember if it came up earlier - Are you running NVIDIA's web drivers, most specifically the correct ones (including CUDA) for your OS? Getting my system to its current state took a motherboard swap, slot shift for the graphics card, AND the correct drivers. Other things that may have helped included a fresh battery on the motherboard, a whole lot of cleaning and resetting of PRAM/NVRAM...

Apr 20, 2021 9:19 AM in response to Grant Bennet-Alder

No, no kernel panics in either Linux or Mac boot drives I’ve tested it with (appreciate you’re working hard on many threads but you may recall this from earlier responses). System goes instantly off without leaving log trail to examine. In Ubuntu, (used to test and eliminate MacOS) it will stay on at login screen for as long as you leave it (I tried a fortnight) - login, to either MacOS or Ubuntu and you get between 2mins and 2hrs45mins.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac Pro 3,1 black screen then fans on full

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.