OS won't boot after adding more memory

Hello, I have one of the first Power Mac G5s (Single 1.8-Ghz, 8 DIMM sockets). The machine came with 512MB of RAM standard.
I'm trying to add more memory, but when I install additional modules, OS X doesn't boot up. I've tested the modules on their own, and they are fine.
When memory is installed in DIMM sockets 0 and 1, the computer is fine and boots up as normal. When I install the next pair, nothing happens. The computer turns on but nothing happens. Blank screen, hard drive isn't clicking, etc.
I've followed instructions from Apple, and I've attempted resetting PRAM, but nothing is working.
Should I reset PRAM before I install the modules?
Any advice would be appreciated. Many thanks in advance.

Sometimes even two batches of RAM from a "good" vendor like Crucial are incompatible, and you're saying each set works on their own but not when installed at the same time.
With the new set in, run AHT and Memtest to be sure. AHT should be able to load - but maybe not.
When swapping RAM, either boot into Open Firmware and reset-nvram or try the old keyboard "zap pram/nvram" routine.
It may be that the latest memory is trying to be "backward compatible" which doesn't always work. You're G5 1.8-SP is a very early Sept/Oct 2003 model.
You should always reset nvram when changing hardware configurations.

Similar Messages

IbookG3 wont recognize memory stick or burn disks after adding more memory

I recently added more memory to my old ibook. Now when I put my memory stick in either USB ports nothing comes up on the desktop. I also can't get anything to burn onto disc. Any ideas?

Hi, and welcome to Apple Discussions.
Have you tried removing the RAM to see if those capabilities return to the iBook?
How big is the hard drive and how much space remains available on it?

Mac Pro 2010 Won't boot after adding Ram

Just got my Mac Pro 2.8 a few days ago. My 4x2 8Gig Crucial Ram upgrade arrived today along with my SIIG FireWire400 PCIe card. It seems as though the Mac Pro won't boot with both the Crucial Ram and the Samsung Ram that came stock with the Mac Pro. I kept 2 of the 1 gig Samsung chips and put in the 2 4Gig Chips from Crucial. They are all the DDR3 1066 240 pin chips. I've moved the 4Gig chips to slots 1 & 2 and I've tried them in slots 3 & 4. I've moved the 1Gig Samsung chips accordingly. The power light on the Mac Pro blinks continuously when they are both installed. I even tried removing the new SIIG FireWire 400 card but that doesn't change anything. It seems as though combining these two types of ram just doesn't jive. Any ideas? I'm dragging the tower from queens to SoHo tomorrow to let the Apple Genius gang have a look at it.

FYI, when I did install the Registered or "buffered" 8 Gigs of Crucial Ram by themselves the system did boot up normally and a memory notification popped up and said that my ram was in the "correct" or "suggested" configuration. I can't remember the exact phrasing but the OS definitely gave me a thumbs up. So now I am trolling the web trying to find out if the Registered memory is ok. I'm fine to just have 8gigs for now. But don't want to jeopardize the stability of my system. So, Is it ok to use Registered memory and if it is, am I using a lesser quality of ram in doing so?

Windows 7 won't boot after adding a third partition with gparted

I needed extra space on my bootcamp partition so I :
1. resized macintosh hd partition with disk utility
2.booted with gparted live disk and "growed" the bootcamp partition
Now Windows doesn't boot. Any suggestions?

Hi,
your Topic says '...adding a third partition' whereas in your message you don't mention this third partition...
So what is the right one ?
Nonetheless you might have a look at EasyBCD http://neosmart.net/dl.php?id=1 to repair the Windows 7 bootloader.
Regards
Stefan

2009 Mac Pro Won't Boot after adding RAM (Crash-Keeps rebooting)

So I recently added new RAM that I purchased from OWC into my Mac Pro 4,1. It kept rebooting over and over and it gives me this error screen when it does. It doesn't get past the boot screen. I've since removed the RAM and replaced it with my old sticks (I discovered that the new sticks were the wrong speed 1333MHz vs 1066MHz). Still nothing.
This is incredibly urgent. Does anyone have any insight?

The hexadecimal stuff all over the screen is NOT a RAM panic. It is complaining about a USB problem and a caldigit driver.
The box near the center of the screen is saying you have the modules installed in the wrong slots.
Take it slow and simple. Install one module in the lowest-numbered slot on each side and work your way up on the RAM modules. You want to end up with the biggest modules in the lowest-numberd slots.
Remove all your USB devices for now to avoid that kernel panic.

Mac Pro won't boot after adding new hard disk.

I have 2 SATA back up disks which I want to install in my Mac Pro. But when I install them into my mac and hit the ON button, I hear a "click" and nothing happens. When I remove the hard drives the Mac will boot. I also tried it with only one of the two hard drives but no luck.
What could this be ?

There is a lack of just what these are, outside of assuming 3.5" SATA
Did you erase or format them? what make/model and bought from where?
Tried booting OS X DVD?
also, if this is Early 2009 and you are still on 10.5.8, you should strongly consider if you use ANY audio program or deivce, to upgrade to 10.6.5+
PS: unplug? after shutdown? or in order to shutdown?
That can add trouble to your boot drive.
Try safe boot also. And check the directory of all your drives.

M8330f PC won't boot after accidentally having I-pod plugged in prior to booting

My computer won't boot after having my i-pod charge cord inserted in computer prior to booting. I have tried f8 f9 f10 f11 nothing is getting me to a point where I can actually get the computer to boot. I realize I may need to provide more info, but don't know what else to provide you right now. HELP!

I used version 1.B for my motherboard.
Yes i did. I describded what happens, when i run 1 and 2 sticks.
-If these are timings then - 9 9 9 25
-1600mhm before bios update and 1337mhz after update
-Voltage: 1.5V in auto probably
Edit1: I got a response on other forum -
Could this be true:Quote
The Hyper X Fury operate off of PnP and aren't compatible with the P55 chipset natively?
In that case i could try to refund the ram, cause the place where i bought it said its compatible with P55
Edit2: I added some info on what kingston homepage (no P55) says and specification pdf also what my seller says in description of this ram type:
I`am am confused, honestly.
Edit3: Aperrantly its might not support my p55 chipset, found a reply on another similar problem tread replied by kingston tech support:
Quote
Hi, I'm Jewel with Kingston Technical Support and would like to offer some clarification. Our currently manufactured memory, including the HyperX Fury line, is compatible with Intel 6-series chipsets and later. The DH55TC has an Intel H55 chipset which is part of the Intel 5-series chipsets. As such, the HyperX Fury memory is not compatible with your system and we do not currently offer any memory that would be compatible with your system. You can try looking online for recently discontinued part numbers like KVR1333D3N9HK2/8G or KVR1333D3N9H/4G which are compatible with your motherboard. If you are unable to return the memory to your place of purchase, please contact us and we will do our best to work with you. Please check http://www.kingston.com/company/contacts to reach support in your area.
If that`s the case then - outdated spec information everywhere...

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

Mac mini won't boot after RAM upgrade.

Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
Things I've tried so far:
1. Resetting the PRAM, no luck.
2. Holding option at start-up, shows no icon.
3. Holding shift, no luck.
4. Holding X, nothing.
How do I get it to accept a CD if it won't boot?

Welcome to Apple Discussions!
You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

My Mac Pro won't boot after installing the latest update

Im running the latest OSX on my mac and recenty did a small updated that i believe contain a few security thing and bug fixs but when restarting the machine after the update it would not boot again after the apple logo has appeard apple script is displayed on the screen contain what i think is boot script failing to run. I have been able to boot the system in safe mode. does anyone have and solution for this as i realy don't want to reinstall the OS
Thanks

The most common cause for "Won't boot after software Update" is Directory Damage that existed before the Update, but was made worse by adding files during the Update.
The most common cure for that Directory Damage problem is to boot in Safe Mode, which takes five minutes to repair the disk, then comes up demanding your username and password, even if you normally auto-login.
Rarely, third-party add-ons are made obsolete by an update. In this case, booting in Safe Mode (with few Apple extensions and NO third-party extensions loaded) works fine, even if normal mode does not work.
Have you tried normal mode again after your Safe Boot?

HT1423 I am adding more memory, should I replace the top two slots with the 4g memory modules, then place 2g memory modules on bottom slots. Does it even matter?

I am adding more memory, should I replace the top two slots with the 4g memory modules, then place 2g memory modules on bottom slots. Does it even matter?

I am adding more memory, should I replace the top two slots with the 4g memory modules, then place 2g memory modules on bottom slots. Does it even matter?

Macbook pro won't boot after installing update 10.9.3

macbook pro won't boot after installing update 10.9.3

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

My daughter's MacBook Pro was doing exactly the same thing. I don't know if it had anything to do with the latest update. She called me about a week ago saying that her MacBook began running slower by the day . She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning. I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive. She took it to the Apple store. Originally, they also thought it was the hard drive. It ended up being a corrupted operating system (Lion). Apple genius simply re-installed Lion and she's back up and running. Good thing she backed up right before it crapped out. She'll be restoring everything tonight. Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

Is there anyway of adding more memory to an iPod touch?

Is there anyway of adding more memory to an iPod touch as I am running out of space.
Thank you

It's annoying because the amount of memory apple advertise is not actually all for you to use. I bought an 8g iPod thinking it would be enough but didn't realise 2g of the 8g is already used for you!

Mac won't boot after updating to OSX 10.6.4

I am on my 3rd Mac that won't boot after updating to OSX 10.6.4. One MacBook Pro and two iMacs. I fixed one but the last two are getting the better of me. HD is not fried. Have tried every keyboard shortcut on startup, Disk Warrior via. Target Disk, repairing permissions in single user mode. The machines will not boot off of a CD or DVD and it will not boot up in safe mode. Something in the startup files is preventing startup. I am suspecting Sophos antivirus. I tried to uninstall it and trash it but I think it's still blocking something. Any help would be appreciated.

Got it! Not sure if removing Sophos had anything to do with it but here's what I did.
1) boot dead machine in Target Disk Mode (iMac)
2) boot good machine off Snow Leopard disk (MacBook)
3) install OS to dead machine- I found this next part very curious. When the install was complete the MacBook restarted as the iMac.
4) ran software updates
5) shut down MacBook then shut down iMac
6) rebooted iMac- all was good
I actually did this twice because a co-worker had the exact same problem on her MacBook Pro. Got both fixed today.
Thanks everyone for your help!

OS won't boot after adding more memory

Similar Messages

Maybe you are looking for