Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2009 mac pro ram question?
- Thread starter CapnDavey
- Start date
- Sort by reaction score
Every time you change the hardware config, you should reset pram with "Command + P + R" on startup. That will probably solve it.
If a module is bad I would try taking out one module after another and try rebooting until it works. That why you'll know which one is broken.
If a module is bad I would try taking out one module after another and try rebooting until it works. That why you'll know which one is broken.
When testing the RAM stick one by one, you may blow all the dust away from the slot as well.
In my own experence. There is no need to do PRAM reset after RAM config change. However, quite a few members here report that a PRAM reset fix their RAM issue (especially wrong RAM speed). So, unless you are running a unflashed Maxwell GPU. Or still using the old method in Yosemite to activate TRIM. Reset PRAM should not cause any damage / trouble. Always worth a try before other trouble shooting.
In my own experence. There is no need to do PRAM reset after RAM config change. However, quite a few members here report that a PRAM reset fix their RAM issue (especially wrong RAM speed). So, unless you are running a unflashed Maxwell GPU. Or still using the old method in Yosemite to activate TRIM. Reset PRAM should not cause any damage / trouble. Always worth a try before other trouble shooting.
There is some simple troubleshooting you can do before returning.
Remove all the RAM from the system. Take two RAM modules and insert them according to this image:
Start the system and see if it will boot. If not, try two different modules. If it will again not boot, then you may have some kind of incompatibility going on.
If it will boot, add two more modules and try starting the system. Repeat until you either have all modules in use or until you are no longer able to boot.
Using this trial and error approach, you should be able to find the bad module (if one is indeed bad). If the system ends up booting with all RAM in place, consider running a memory test.
Remove all the RAM from the system. Take two RAM modules and insert them according to this image:
Start the system and see if it will boot. If not, try two different modules. If it will again not boot, then you may have some kind of incompatibility going on.
If it will boot, add two more modules and try starting the system. Repeat until you either have all modules in use or until you are no longer able to boot.
Using this trial and error approach, you should be able to find the bad module (if one is indeed bad). If the system ends up booting with all RAM in place, consider running a memory test.
Last edited: