Too Much RAM causing shut down? (2008 Mac Pro)

Question

Level 1

0 points

Too Much RAM causing shut down? (2008 Mac Pro)

I've got an older 2008, Mac Pro with an OWC SDD as my main drive running the latest version of Snow Leopard.

In the last several months I've been experiencing problems where the system will shut down (screen says it has gone to sleep and I cannot wake it) but the tiny white power light on the front of the computer stays "on".

The only way I have been able to get it to turn back on, is to power down holding the power button in, until the white light goes off. When i power back on, some times it will boot to the desktop, and other times, it will just get to the grey Apple logo and instantly go into sleep/ hibernation, etc (I'm not sure what it's doing).

Things I've tried to resolve the problem:

- Permissions repair (no problem) - using Drive Genius

- Disk repair (no problem) - using Drive Genius

- Uninstalled (or not installed) any of my typical post-reformat software

- Replaced RAM

- Replaced RAM riser

- Reset PRAM, (and other similarly suggested fixes)

- Disconnected everything except keyboard, mouse and monitor

At one point I went through all of my ram, tested it all and all passed using software similar to those recommended elsewhere in other Apple discussions

I once removed some ram from the bottom riser (hunting and pecking here) and this allowed me to boot. (I have had as much as 16GB of Apple approved ram across each riser, inserted into each dim slot as recommended by Apple.

Could this be a drive problem? I am using an OWC3gb SSD

Could it be a power supply problem?

The system is clean, and dust free. The system runs cool (within the recommened guidelines)

Is there something I might try that I haven't mentioned here?

Thank you so much.

Mac Pro, Mac OS X (10.6.7)

Posted on Apr 15, 2013 10:18 AM

Reply

Answer 1

Apr 15, 2013 10:40 AM in response to Joel DuBay

The Mac Pro 65lb tower uses Error Correcting Code memory. 8 additional syndrome bits are stored with each word in memory, and provide enough redundancy that if a single-bit error occurs, it is detected and corrected in less than one memory cycle. Double-bit errors are detected, but usually cannot be corrected, so they halt the machine with a kernel panic (machine check) to avoid poisoning your data.

So do not spend your time chasing memory problems in this Mac, and do not follow procedures suggested for other Macs that do not have error correction Hardware watching each and every memory cycle. Check About this Mac > ( More Info ) > Memory ... report showing each module, and be done with memory problems.

--------

The system log may hold important error messages that would lead you directly to the problem. I suggest the following procedure:

Walk away from your Mac for a while, noting the time.

If it goes to sleep and cannot be wakened, wait a few minute more and note the time.

Then restart it in whatever way you normally do, and immediately use Console to read out the system log from the appropriate time period. If it is baffling, post the appropriate sub-section here.

Reply

Answer 2

Joel DuBay Author

Level 1

0 points

Apr 15, 2013 11:12 AM in response to Grant Bennet-Alder

Thanks Grant Bennett-Alder.

All of the installed RAM is recognized in "About this Mac". ''

Would it be best to post a link to the Console file, or post just the "crash" section here?

Thank you,

Reply

Answer 3

The hatter

Level 9

60,990 points

Apr 15, 2013 11:19 AM in response to Joel DuBay

Did you focus on that OWC SSD?

Change the system to a non SSD.

In spite of OWC claims, use TRIM Enabler.

FBDIMMs the only things to watch are 'disappearing' not being fully reported, and their temps.

Anything over 70*C? Amazon has $32 2x2GB kit but seems like you are fine

I don't think you really need Drive Genius, clone backup image, very much a yes.

A utility to scan or and map out bad sectors, yes.

DG just uses what the OS uses when it comes to repair permissions, and they rarely are an issue.

Resetting SMC, yes.

I've seen a keyboard (or its attached cable) be the casue of a lot of small problems.

Obviously you are not using 10.6.7 but whatever you are using, a clean install and not an upgrade in place over SL to ML or Lion is going to avoid PowerPC/Rosetta and work better.

Reply

Answer 4

Joel DuBay Author

Level 1

0 points

Apr 15, 2013 12:14 PM in response to The hatter

Thanks, I am on 10.6.8

I downloaded and installed TRIM.

My RAM is very good, and not overheating.

I did a clean install prior to posting, using my SL install disk.

Any other thoughts on why this could be happening?

Cheers,

Reply

Answer 5

Apr 15, 2013 2:36 PM in response to Joel DuBay

Cut and paste the pertinent section here.

It may be large, but it still takes less space than a photograph.

Reply

Answer 6

Apr 15, 2013 3:21 PM in response to Joel DuBay

I would recommend you look at your energy saver settins in system preferences. I had the same issue with my Mac when I installed a SSD. It wouldn't wake up from sleep so I unticked "Put hard disk to sleep when possible" and that solved it. Also, you might want to check if your firmware on your SSD is up to date.

Good luck

Reply

Answer 7

Joel DuBay Author

Level 1

0 points

Apr 15, 2013 4:38 PM in response to Grant Bennet-Alder

So, it "crashed" for lack of a better word at 5:57 - see log below:

4/15/13 5:43:22 PM	UserEventAgent[138]	Cannot find function pointer NewPlugIn for factory C5A4CE5B-0BB8-11D8-9D75-0003939615B6 in CFBundle/CFPlugIn 0x1001247a0 </Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin> (bundle, not loaded)
4/15/13 5:48:18 PM	com.apple.WindowServer[89]	Mon Apr 15 17:48:18 Joel-DuBays-Mac-Pro.local WindowServer[89] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
4/15/13 5:49:40 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:40 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:41 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:42 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:43 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:45 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:46 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:47 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:48 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:49 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:50 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:52 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:53 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:54 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:55 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:56 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:57 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:49:58 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:00 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:01 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:02 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:03 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:04 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:05 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:06 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:08 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:09 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:50:10 PM	MagicanPaster[176]	[ERROR] [CmcReadSmcKey] SMC get key info fail: 0
4/15/13 5:52:59 PM	MIDIServer[200]	MIDIServer [200] starting; arch=x86_64
4/15/13 5:52:59 PM	MIDIServer[200]	PlugIn DigidesignFireWireMIDI.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
4/15/13 5:52:59 PM	MIDIServer[200]	MIDIServer relaunching because a 32-bit driver was found
4/15/13 5:52:59 PM	MIDIServer[200]	MIDIServer [200] starting; arch=i386
4/15/13 5:57:29 PM	com.apple.launchd.peruser.501[114]	(com.apple.AirPortBaseStationAgent[145]) Exited: Killed
4/15/13 5:57:29 PM	com.apple.launchd[1]	(com.apple.aslmanager) Throttling respawn: Will start in 10 seconds
4/15/13 6:32:36 PM	com.apple.launchd[1]	* launchd[1] has started up. *

Reply

Answer 8

Joel DuBay Author

Level 1

0 points

Apr 15, 2013 4:40 PM in response to JShimazaki

JShimazaki, thank you.

Nothing is ticked in the Power settings window, so drives don't go to sleep if not in use.

Reply

Answer 9

Apr 15, 2013 10:03 PM in response to Joel DuBay

This may seem like an overly simplistic suggestion, but:

Over the years, I've noticed that many Macs which are sluggish to wake respond pretty readily to simply pressing the Control key (not the Comnand key) - I first discovered this with many laptops, but it works equally well on many other models.

It's worth a try, and it's free.

Reply

Answer 10

Joel DuBay Author

Level 1

0 points

Apr 16, 2013 7:36 AM in response to Ron Herrmann

Thanks Ron Herrmann,

Unfortunately that does now work. Moreover, the system will just "die" (screen says it's going to sleep, etc) though the power button light on the front of the Mac is still lit.

The only way to even try to restart is by shutting the computer down (by holding the power button in) and starting from a cold boot.

But, even when I do that - most of the time it will power on, go to the grey Apple screen - and then immediately the screen shuts down (to black) and I can't use the computer.

Most of the time I have to wait a while in order for it to boot (again) to the desktop.

I could post another Console log today when it after it exhibits this behaviour if that would be helpful to anyone here trying to help me?

I do appreciate ALL of your support. I LOVE my mac and wish very much to fix it.

Reply

Answer 11

Joel DuBay Author

Level 1

0 points

Apr 16, 2013 7:59 AM in response to Joel DuBay

I want to make sure I am clear about what's happening -

When the system shuts down, or I try to restart the computer - it "sounds" like it is starting up, e.g. the fans turn, the dvd slots initializes, the red lights on the ram risers blink, etc....

BUT, as soon as I get to the Grey Apple logo, it shuts off - everything, except the power button light - the power button light stays ON.

Maybe this explanation helps more?

Reply

Answer 12

The hatter

Level 9

60,990 points

Apr 16, 2013 8:07 AM in response to Joel DuBay

I would never have realized except yesterday my Mac Pro was 'giving me fits'

I could not: zap PRAM

Resetting SMC did not help

Could not use Option key

Acted much like yours too.

Bad keyboard (or its cable) but I have 3 others to try and in desperation figured what the heck!

I think - didn't help me - but try w/o any disk drive present, just slide them all out for now.

That can rule out the drive and drive bay and even if the logicboard is - I tried "hot swap" drive bay 3, ever since I cannot boot if anything is in that drive bay. So I now use ODD ports and a PCIe card so I can use 6 drives.

And just in case for insurance I finally ordered ATI 5770 - wish it didn't take a week so fingers are crossed - 8800s are known to die on their own.

Reply

Answer 13

Joel DuBay Author

Level 1

0 points

Apr 16, 2013 8:23 AM in response to The hatter

Thanks The hatter,

I pulled all of the drives out, and the system booted and stayed ON. It just stays at the Grey screen flashing a file folder image (of course) because there is nothing to boot to 🙂

I tried slipping an ML drive into the first and second bay, but the system shut down immediately after getting to the grey screen. I'll make the assumption that becuase the OS was not written to a drive while in this machine, that it couldn't boot it. No?

Given the above mention of the machine staying on without drives in any of the bays, what might I try next?

I could grab a new drive and try installing OSX (Leopard, SL or ML)

What do you guys think?

Reply

Answer 14

The hatter

Level 9

60,990 points

Apr 16, 2013 9:08 AM in response to Joel DuBay

when you 'slip a drive in' be sure it is OFF. hot swap is not officially supported, Intel may not, there may be a way to recongigure ports in an accessible BIOS fashion.

Yes on new drive. Always have clone and spare. Got a workiing system? clone it and put it on the shelf.

2008 3,1? 10.8.3.

But... I would also setup 10.6.8 on another drive as well even if only for testing and such.

If you did an upgrade in place from SL to Lion or ML, that can cause mischief.

Leo support ended and you really don't want to go that far back, it feels like it was one beta after another to get to 10.5.8 and THAT had trouble of its own with the 2009s and audio or iTunes that was only 'fixed' with 10.6.2+

10.6.5 is req'd for the ATI 5770 so keep that in mind also if you did that upgrade.

Reply

Answer 15

Joel DuBay Author

Level 1

0 points

Apr 16, 2013 2:25 PM in response to The hatter

I installed a new HD with SL

Same problem. I tried to restart, it shut down before the grey apple screen appeared.

I'm baffled.

Power supply?

I haven't seen any glitches in video, so I'm not sure that video card replacement would do me any good.

Logic Board?

Reply