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.

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. ***

Similar Messages

Takes unusually too much time for shut down R Macbook pro 15

During the shut down procedure I have the white screen for unusually long time. My R Mac book pro is a new one I have had this since the first day. I download a fresh OS X but still the same.

You're still under warranty. Take full advantage of it by calling Apple Care about your concerns.

Shutting down my Mac Pro Retina properly?

When I shut down my Mac Pro, I close all apps except the Finder. I've noticed that sometimes when I start up again, the Apple logo and the loading bar don't appear, and when I go into the desktop, the Finder is still open on the folder it was on before I shut it down the last time. But there's still the normal start up sound. I think this is because when I see the screen go black, I close the laptop screen straight away, and it hasn't truly finished shutting down yet. I've been trying to wait for a minute before closing the lid after the screen goes black, and it's been working: the next time I start up my Mac the Apple logo and loading bar appears as usual, and when I get on to the desktop, the Finder isn't open on anything.
My question is, is it really bad for the Mac if I close the lid before it properly shuts down, and I leave it in a kind of limbo state before I start it up next time? Because sometimes I'm in a hurry and I don't have time to wait a minute before closing the lid.

Hello animefan4eva,
After reviewing your post, it sounds like you were trying to shut down the computer but closed the lid befor it finished. I would recommend that you read this article, it may be able to help the issue.
Mac notebooks: Wait for your computer to fully shut down before closing the display - Apple Support
If you close the display on a MacBook Pro, MacBook, MacBook Air, PowerBook, or iBook while it is shutting down, the computer may not shut down properly.
Thanks for using Apple Support Communities.
Have a nice day,
Mario

Firefox consumes too much RAM, caused by js

I'm having problems with Firefox consuming too much RAM memory. Several people are complaining about this but I did some further research before posting here, using about:memory, and I found out that js-non-window and js-main-runtime are causing this.
When I start up a blank Firefox session I immediately have an allocation of 260MB of RAM. About 75-80% of this is taken up by those two js (javascript?) processes.
After opening about 10 tabs with different webpages the RAM usage has gone up to about 750MB. During the time the tabs are open most of the extra MB's are consumed by the window-objects (40MB per page, still seems quite a lot to me for just a news site with one article...) but after closing them the memory usage didn't go down and it transferred to the two already mentioned js processes. This transfer to the js processes is not always the case, it seems to happen only if I open a lot of tabs, let's say 10+ perhaps.
I tried disabling Javascript using the plugin SettingSanity, but this makes browsing quite uncomfortable of course and worst of all it doesn't solve the problem. The mentioned processes keep using the same amount of RAM.
I have this exact same problem on all my computers and laptops so it can't be a coincidence. Is there nothing I can do about this? Is this under investigation? How can a browser with 10 web pages open need almost 800MB of RAM?
And please don't answer "install more RAM". The pc I have most problems with has 2GB of physical RAM and I really do think that opening 10 web pages should be possible on such a computer. Doing the same in Internet Explorer consumes less than half the amount of RAM memory.
P.S: I sent this query using IE because I could't get to this page in Firefox. The "Ask This" button didn't work...

Try in Firefox's safe mode disable all plugins, and open with only a new tab set by using ''about:blank'' . As suggested above also consider as a test creating and using a new Firefox profile.
When I start like that I have around 70MB explicit shown in ''about:memory'' and that includes ''js-non-window'' of around 30MB
I know in the past I have opened more than 10 tabs on a machine with less than 1GB ram installed and not noticed problems.

When I shut down the Mac Pro, it restarts

Has anyone run into this issue with their Mac Pro? When I shut down the computer (either via the Ctrl + Option + Cmd + Eject or the Shut Down command from the Apple menu drop down), the Mac Pro will simply restart and take me back to my log-in screen.
At this point, I can hit the shut down button on the login window and it will shutdown, but this is annoying, a waste of time, and unnecessary.
I have tried performing an SMC reset, but it has not resolved this issue.
Specs: Mac Pro (2010)
3.33 GHz 6-Core
(2) 2TB Internal HDD
12GB ram
ATI 5870 graphics card (1GB)

I have noticed the exact same behaviour. It only happens when I have something plugged into one of the front USB ports (example : external HD, USB key)
Apparently the system crashes during the shut down process, and then reboots.
Unfortunately, I have not yet found a solution

Sleep or Shut Down with Mac Pro RAID Card?

I'll be gone for a four-day weekend trip, which is longer than the 72 hours claimed for the Mac Pro RAID Card battery. If I shut down and come back four days later, the battery will presumably be discharged. What will happen when I restart?
Asked another way ... is 72 hours the maximum amount of time that the computer should be shut down or do I simply restart and wait for the battery to recharge and the write caches to be re-enabled?
The FAQ for the Mac Pro RAID Card http://support.apple.com/kb/HT1346 talks around this issue, but doesn't say whether it is a good or bad idea to allow the battery to discharge for "... any length of time." Please review the appended excerpt from the FAQ and advise on whether I should sleep or shut down.
Regards,
iPhoton
Question: Why does RAID Utility show a yellow light and report the status "Write cache disabled"?
Answer: The write cache is disabled automatically so data cannot be written to RAID volumes when the battery charge is not sufficient to back up cached data for 72 hours. This message is normally encountered when a RAID Card is used for the first time, when the battery enters a conditioning cycle once every three months, or when a computer with a RAID Card installed is shut down for any length of time.
If your RAID card's firmware is M-2.0.3.3 or later, or E-1.2.2.4 or later, you can use RAID Utility to force-enable the write cache while the battery conditions itself. Warning: If you enable the write caches before the battery is fully charged, you might lose some data if the power to your computer is interrupted.

Thanks to everyone who replied to my message. I did a proper backup and normal shut down on Wednesday night and restarted on Monday morning. That was over 100 hours later and certainly more than the battery is specified (72 hours).
When I restarted on Monday morning I noticed ... no change! The battery was fully charged according to the RAID Utility, I received no warning messages, there were no new events in the RAID Utility log ... it's as if the extended shutdown never occurred.
So, an extended shutdown appears not to be a problem and I won't worry about it again, not even on my next extended shutdown for three weeks at the end of the year.
Regards,
iPhoton

Should I shut down my mac pro every night

Just purchase a Macbook Pro, should I shut it down every night?

leroydouglas wrote:
Never heard that advice before. The kb certainly does not say that.
Big difference from your statement compare ""Apple does not recommend leaving your portable plugged in all the time."
I think using the battery regularly is a better interpretation.
I would submit that is the way most people use their Portables, close the lid.
You absolutely misunderstood I referred to BOTH "on power AND in sleep mode"
     not to: "closing the lid ,... sleep mode"
Using the battery regularly can mean anything as a generalization.
That advice on parasitic charging is correct.   Which referres to BOTH in sleep AND on power...   not however to merely "in sleep mode"
There is no etrecheck for parasitic battery charging,   ..... NOR is there any such check for both:
1. fast discharges
3. low discharges
As such that battery information you provided above doesnt report bad abuse / misuse of a battery.
Nor does / can Etrecheck report on physical abuse of any macbook, logically.
Battery abuse / misuse is a type of physical abuse, chemistry of the battery abuse, however its internal.
I did not say the KB article said that,    what it says:
http://www.apple.com/batteries/notebooks.html
"Apple does not recommend leaving your portable plugged in all the time."
So, you misunderstood.
Apples recommendation refers to micro-cycling the battery and to parasitic charging in the above quote, that it doesnt elaborate on the specifics of same
is irrelevant.
The implication from same is exactly this
*If you don’t plan on using it for a few hours, turn it OFF (plugged in or otherwise) ..*You don’t want your Macbook both always plugged in AND in sleep mode       (When portable devices are charging and in the on or sleep position, the current that is drawn through the device is called the parasitic load and will alter the dynamics of charge cycle. Battery manufacturers advise against parasitic loading because it induces mini-cycles.)
Keeping batteries connected to a charger ensures that periodic "top-ups" do very minor but continuous damage to individual cells, hence Apples recommendation above:   “Apple does not recommend leaving your portable plugged in all the time”, …this is because “Li-ion degrades fastest at high state-of-charge”.
                    This is also the same reason new Apple notebooks are packaged with 50% charges and not 100%.
Contrary to popular myths about notebook batteries, there is protection circuitry in your Macbook and therefore you cannot ‘overcharge’ your notebook when plugged in and already fully charged.
However if you do not plan on using your notebook for several hours, turn it off (plugged in or otherwise), since you do not want your Macbook ‘both always plugged in and in sleep mode’.
A lot of battery experts call the use of Lithium-Ion cells the "80% Rule", meaning use 80% of the full charge or so, then recharge them for longer overall life. The only quantified damage done in the use of Lithium Ion batteries are instances where the internal notebook battery is “often drained very low”, this is bad general use of your notebook battery.
A person who has, for example, 300 charge cycles on their battery and is recharging at say 40% remaining of a 100% charge has a better battery condition state than, say, another person who has 300 charge cycles on their battery and is recharging at say 10-15% remaining on a 100% charge. DoD (depth of discharge) is much more important on the wear and tear on your Macbook’s battery than the count of charge cycles. There is no set “mile” or wear from a charge cycle in specific. Frequent high depth of discharge rates (draining the battery very low) on a Lithium battery will hasten the lowering of maximum battery capacity.
All batteries in any device are a consumable meant to be replaced eventually after much time, even under perfect use conditions.
If the massive amount of data that exists on lithium batteries were to be condensed into a simplex, helpful, and memorable bit of information it would be:
1. While realistically a bit impractical during normal everyday use, a lithium battery's longevity and its chemistry's health is most happy swinging back and forth between 20% and 85% charge roughly.
2. Do not purposefully drain your battery very low (10% and less), and do not keep them charged often or always high (100%).
3. Lithium batteries do not like the following:
A: Deep discharges, as meaning roughly 10% or less on a frequent basis.
B: Rapid discharges as referring to energy intensive gaming on battery on a frequent basis (in which case while gaming, if possible, do same on power rather than battery). This is a minor consideration.
C: Constant inflation, as meaning always or most often on charge, and certainly not both in sleep mode and on charge always or often.
From Apple on batteries:
http://www.apple.com/batteries/notebooks.html
http://support.apple.com/kb/HT1446
Bad discharging or battery use conditions:
Heat (due to environmental conditions or due to rapid discharges from heavy use = gaming / video editing)
Rapid discharging of the battery frequently causes chemical changes over time in the battery leading to decreased capacity and resistance of current flow.
The very worst use of your battery is often draining the battery very low, and worse still letting it remain in such a state.
*Most long-term rapid damage to the battery occurs from discharging it with high loading (gaming) conditions but paramount is avoiding deep and frequent low DOD (depths of discharge) in use.
Undesirable charging or charged conditions:
High perpetual SOC (state of charge), where the battery is always or very often connected to charge
Parasitic loading where the battery is both usually on and charging or worse both always charging and in sleep mode, since this induces mini-cycling of the battery.
Bad general handling conditions:
Temperature use conditions when either too hot (95F and above) or too cold (50F and below)
Storing your battery away with a low charge (40% and less) long-term.
Considerations:
Your battery is subject to chemical aging even if not in use. A Lithium battery is aging as soon as its made, regardless.
In a perfect (although impractical) situation, your lithium battery is best idealized swinging back and forth between 20 and 85% SOC (state of charge) roughly.
Further still how you discharge the battery is far more important than how it is either charged or stored short term.
Ultimately counting charge cycles is of little to no importance. Abuse in discharging (foremost), charging, and storing the battery and how it affects battery chemistry is important and not the ‘odometer’ reading, or cycle counts on the battery.
Everything boils down to battery chemistry long term, and not an arbitrary number, or cycle count.
Keep your macbook plugged in when near a socket since in the near end of long-term life, this is beneficial to the battery.

I want to shut down my mac pro (retina display) but when I try to it says that in the finder some operations are still open and i should go close or cancel them. The problem is that I have nothing running or in use. Is it the remote disc or what?

nothing seems to be wrong, so i am a little unsure of what the problem could be..

Press Alt, Command and Esc keys, select Finder in Force Quit and force close it. Then, you will be able to restart. You can also try to press Control, Command and Eject keys

What upgrade graphic card do i need for a early 2008 mac pro

I have a early 2008 Mac Pro. ATI Radeon HD 2600 XT 256 MB is what i have now. What is a good upgrade graphic card to get.

The GTX 780 6GB runs fine on the dual PCIe internal power cables -- as does the GTX 680 and Radeon HD 7950. The same can't be said of the GTX TITAN or GTX 780 Ti or Radeon R9 280X -- all of which require an auxiliary power feed to avoid a nasty power down of your tower at the worst moment when too much wattage is demanded of the Mac Pro's factory power supply.
Did I mention that the GTX 780 with 6GB of GDDR5 matches the 6GB of GDDR5 in the TITAN?
The one fallacy to my 'sweet spot' award has to do with OpenCL. In case you hadn't noticed, the AMD Radeon GPUs smoked the NVIDIA GeForce GPUs running Photoshop's OpenCL accelerated Iris Blur filter and rendering LuxMark's OpenCL accelerated Room scene.
- http://www.barefeats.com
So depends on budget, whether you want a PC card for less but no "early EFI boot screen" prior to drivers loading, and what apps and needs you have.
The one thing for sure is that 2600XT should have been retired ages ago and even more so with 10.8.3 and above, it could be trouble or just... PITA/POS.

Early 2008 Mac Pro frequently shut downs during start up, Help!

Hello all,
My early 2008 Mac Pro has gradually started having the following problems:
It will often shut down when it goes to sleep.
It has shut down randomly a few times.
And just today it shut down about 5-10 seconds after being turned on. It took about 6 tries before I could get it to turn on.
I have tried all of theusual software remedies (disk utility, different startup drives, resetting the SMC, PRAM, etc.)
I have run apple hardware test on loop for several hours with no errors appearing...
The computer also often loads up to a circle with with a slash through the middle sign, though I am not sure if this is related (it started happening when it switched my system over to a SSD).
I am wondering if this is simply a slowly sying PSU and if replacing it might help? If there any way of monitoring this perhaps? I somehow thought that if it was the PSU then it would simply die completely rather than fade like this...
Any ideas much appreciated!

There are multiple threads and reports of issues with Icy Dock - there is one on Amazon that lines up properly.
The drive sled length of 2009-2012 Mac Pro are longer. Maybe OWC needs to be clearer.
You'e right half-way and maybe some corrupt plist or interferring process you have, or even another hardware item or cable - external - even printer drivers or something that refuses or does not like sleep. Controller card?
All around I'd have to vote for Samsung 830 model. Then Intel 520. Crucial is out with x4 now (Or is it "V"?)
SSD firmware continues to be trouble. Even May-June the SandForce firmware had major issue and reason to hold off any using theirs. Reason to see if yours needed to be updated. Someone last week with m4 found they had old firmware and needed to update it.

2008 mac pro shuts down over night with os 10.9.5

Updated clean install of OS 10.9.5 to new HDD on my 2008 Mac Pro running 10.6.8 via the app store: The Mac seems to shut down over night. Not overheating. Energy Saver, Computer sleep set to Never, and Display sleep set to Never. Screen saver set to never. Very odd. will see if it does it 3rd night in a row.
Also: anyway to get rid of the password log in when I turn Mac on?

Open the Console app and look for log entries right before your had to boot up the Mac. Post them here.

2008 Mac Pro 10.5.8 shuts down after hours of no use, Set to never shut down. Can be resumed pressing any key but all programs not in startup list need to be restarted and unsaved data lost .   New behavior. No system changes.

2008 Mac Pro 10.5.8 shuts down after hours of no use, Set to never shut down. Can be resumed pressing any key but all programs not in startup list need to be restarted and unsaved data lost .   New behavior. No system changes.

2008 Mac Pro 10.5.8 shuts down after hours of no use, Set to never shut down. Can be resumed pressing any key but all programs not in startup list need to be restarted and unsaved data lost .   New behavior. No system changes.

Labview 2010 vi using too much RAM and causing Crashes

hello everyone,
I was given a LV 2010 vi to integrate with another functionality.This Vi is used for a long time on XP and Windows 7 platform having various RAM size.it still runs fine on those PCs. This Vi has functionality that it waits for user to press start button that it reads data and plots.however i am not giving start command and it starts consuming too much RAM and resulting system Crash.
System Config: I have Core i5 CPU 650 @ 3.20GHz with 2 GB RAM and windows 7 .
Plz show some methods to prevent them and why it is happening.?
Note:1) i also checked my ram through windows test and it has no error.
2) windows shows me some low disk error sometimes.
plz help me out here i am stuck here for week.
thanks & regards

Post your VI if you are allowed, we cannot help you without that info...
If you are a beginner in LabVIEW, it will not take 1 day to gain some level. LabVIEW is a full featured programming language, it is very easy to program it wrong. I suggest you to start learn it using the online resources. You have an active LabVIEW licence? If so, you can access the "self-paced online training" via menu point "MyNI", see top of this website just next to your name (you need to connect your account to your licence in order to use the online training). Another option could be to pay for a virtual classroom course, get more info here: http://sine.ni.com/tacs/app/overview/p/ap/of/lang/en/pg/1/sn/n5nline,n24:12725/id/1582/ I did this a few years ago (Core 1 and 2.) and the tutor from NI was very professional, and it was also comfortable since you attend the class via internet from yoour home or workplace.

2008 Mac Pro 3,1 RAM burning up - running hot

Problem: 2008 Mac Pro Tower running hot.
Possible causes: Power Supply? Fan not working? Machine has 667 mhz RAM not 800 mhz.
PSU was chirping like a cricket a few weeks ago. I pulled it out, air cleaned it (and the entire Mac, vacuumed all the dust) and left PSU out for 12 hours to static discharge, etc. When I put the PSU back in, it was working and the chirping was gone.
Successfully used the MAC for a few days, no probs other than 2 DIMMS went bad. I went away for 2 weeks, tried to start-up the Mac yesterday and it wouldn't power on at all, no light. I unplugged it, tried different outlets, power cords, etc. Then I removed any changes that I had made previously (i.e. installed diff HD and 2 new RAM DIMMs to replace the ones that burned up) before going away. I removed PSU and let it sit while I cleaned the 2 DIMMs that had seemed to overheat before I went away. Put it all back together (PSU, old DIMMs which were cleaned and left HD #3 out) and it powered up. I then noticed that I was down from 32 GB RAM to 16 GB very quickly. The machine had also "shut down because of a problem" during that time then restarted and ran for a bit. I repaired the 16 GB RAM by cleaning it, brought it back up to 32 GB again and within minutes it was back to 24 GB. I pulled the RAM cards out and they were hot. The last 8 GB to go were likely the only DIMMs I haven't cleaned yet. I don't know how long that fix will last. Seems like we have a pattern of over heating.
Any ideas? Is it the 667 mhz RAM? The PSU? The fan? (How do you test a fan?)
Thank you for your time.
2008 Mac Pro 3,1
2x Quad Core 2.80 Ghz Intel Xeon
32 GB RAM (667 mhz)
3 HD's
10.9 OS Mavericks
Logic Pro X

First the RAM must be made for your computer as determined by Apple:
https://discussions.apple.com/docs/DOC-6413
Thus you have an early 2008 Mac Pro if it is a Mac Pro tower and not a MacBook Pro notebook.
The RAM must be either preinstalled by Apple, or from a place that sells lifetime warranty early 2008 Mac Pro RAM.
Just because you got PC6400 DDR2 ECC 800 Mhz FB-DIMM with 256 bit wide memory architecture, as the specs call for,
does not mean the RAM is compatible. Only RAM stated to be for "early 2008 Mac Pro" is compatible with those towers.
http://www.macsales.com/ (OWC) http://www.datamem.com/ and http://www.crucial.com/ all sell RAM by stating the time of year and model name.
Do not buy ValueRAM. If after doing that it doesn't work, some directions for other interior repairs exist on http://www.ifixit.com/ and http://www.xlr8yourmac.com/
Check to make sure the circuit your machine is on is giving off the full amp called for by specs and that current is not split to other devices, and you have either a UPC or surge protector power cord that can handle that ampere. If there is any chance the machine was plugged in during a lightning storm, your power supply may be fried even with a surge protector or UPC being there. No surge protector is 100% lightning foolproof.

Firefox uses too much ram

My FIrefox has been using too much RAM as of late. I have followed all the steps in the firefox support page about checking for possible plugins that may or may not be using too much RAM, but after starting firefox in safe mode, there really wasn't much of a difference. Maybe like 5k kb less, but it's still not enough to account for the 1.7million kb that firefox ends up using with one tab open.
I like to leave my pc on for a bit, and sometimes I'll leave firefox running with a tab open while I'm using other applications, but even if i restart my firefox, the RAM usage does not decrease. After closing all applications and leaving only firefox running, it appears to be around 1.5million kb. Only if i restart my whole pc does the RAM usage drop back to normal levels, and then it ramps back up after a period of time.
I would like to get this resolved soon, or at least figure out the cause of this.
http://puu.sh/9ihMr/585bac7192.png
http://puu.sh/9ihPx/4a9da78104.png
My system has:
2x2GB DDR3 Kingston memory modules
Radeon HD5850 with 1 GB of RAM
AMD Phenom II X4 955 processor 3.20GHz
Windows 7 Professional, SP 1 64-bit OS

Start your Computer in safe mode with networking. See if there
is still a problem.
It could be the work of one of your add-ons, or even add / mal-ware.
Look thru your add-ons list and make sure you know what each one is
there for. Also, check the programs that are on your computer
'''Windows > Start > Control Panel > Uninstall Programs.'''
'''Mac: Open the "Applications" folder'''
Go thru the list and use a web search to check any that you don't
know what they are.
'''''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-caused-malware Troubleshoot Firefox Issues Caused By Malware]''''' {web link}

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

Similar Messages

Maybe you are looking for