« New PowerBooks Contracted to Quanta and Asustek | Home | All I want for Macworld »

December 29, 2005

OS X Updates Damaging PowerBooks Lower RAM Slot (Updated)

Engadget has an interesting article on Mac OS X updates disabling or even permanently damaging the lower RAM slot in PowerBooks. It goes like this: after you update to Mac OS 10.3.9, 10.4.0, and 10.4.1 the PowerBooks' lower RAM slot spontaneously goes bad.

The current operating assumption is that the update actually makes the firmware controller or possibly the chipset get all wonky, which, in turn, may disable the lower memory slot (permanently).

It's a pretty serious claim and the lawyers are already working themselves into a lather over it.

I haven't experienced any such problem with my PowerBook G4 1.5GHz and I have two 1GB SO-DIMMs installed, but I'd be interested in hearing from people who have. Sound off in the comments if your lower RAM slot has gone bonky after an OS update.

UPDATE (2006-0131):

Apple has addressed the RAM slot issue with the PowerBook G4 Memory Slot Repair Extension Program.

Posted by jasonogrady at December 29, 2005 2:52 PM
Category: PowerBook

Digg This | Post to del.icio.us | Post to Furl




Trackback Pings

TrackBack URL for this entry:
http://www.powerpage.org/mt/mt-tb.cgi/8506

Comments

I have a PB 1.5 and had this problem. Apple was great and replaced the motherboard quickly. I think I was out my PB for only three days. (Interestingly, once the motherboard is replaced, the serial number doesn't appear in "About This Mac.") No problems since the replacement.

Posted by: David Molho at December 29, 2005 10:24 AM

I have been having a terrible time with signal dropouts and failures to connect to my wireless router after updating my G3/900 iBook to 10.4.3.

Posted by: Matthew Duett at December 29, 2005 10:35 AM

Lameass ambulance chasers! There's no way software will destroy hardware, it is obvious that these lawyers are taking advantage of users who don't know any better and have hardware failures then try to blame software for it. Just because two events happened in the same month does not mean the two are connected.

Trevor

Posted by: Trevor at December 29, 2005 10:57 AM

My RAM slot is dead as well. 15" 1.5 Ghz Powerbook

Posted by: Erik at December 29, 2005 11:48 AM

I have a PB 15 inch and I can confirm that this has happened to me as well ! Both RAM modules worked perfectly in the upper slot - the lower slot just gave up the ghost for no apparent reason. I am glad someone has a possible explanation ! Apple was quite good about agreeing to replace motherboard - but I had to wait a while for them to ship it to my Authorized Repair Reseller.

Posted by: Ian Procter at December 29, 2005 11:59 AM

I have two 1.25 GHz Powerbooks, I just realized that one of them has this problem, the other is fine. Thank goodness for Apple care.

For Trevor, yes this can happen, and is seems like it is happening.

Posted by: Greg at December 29, 2005 12:05 PM

Today a friend of mine had an issue where his 15" PowerBook's lower Ram slot stopped working - but we don't have any evidence it was caused by software upgrades. That seems far-fetched.
The Apple store here is replacing the logicboard, and he'll get it back in a couple of days.

Posted by: Curt Fiedler at December 29, 2005 12:10 PM

No problems here..... G4 15" Aluminum (first generation), shipped from the factory with two 256MB chips, replaced one with a 1GB for a total of 1.25GB. Everything's been happy, and I've had it two years now.

Posted by: Mason Brown at December 29, 2005 12:17 PM

Lameass lawyers or not software can easily destry hardware.

Posted by: me at December 29, 2005 12:32 PM

Gee...I found my dual 1.8 G5 was missing 1/2 its memory last night. Never thought to blame OS X updates! Actually, I pulled all the ram and reinstalled. All came back after this. Maybe someone should try this on a PB if they are having issues.

Posted by: BobE at December 29, 2005 1:03 PM

My 15/1.56 has lost it's lower ram slot. I have no idea if this happened during an update. Apple is replacing motherboards for this, so a lawsuit is a bit silly at this point.

Posted by: Scott Frey at December 29, 2005 1:11 PM

Interesting... I've lost the use of my lower RAM slot in a 15" PB 1.25GHz. Happened somewhere in the early 10.3 range, but I never considered an OS update as a possible cause, and have no way of backtracking to investigate now.

Posted by: Kennedy Brandt at December 29, 2005 1:41 PM

I have a 800MHz TiBook, which has had 1G of Ram working fine for nearly 3 years. Although this is the first I've heard of a OSX link, soon after I upgraded to 10.4, I have experience system panics and display anomalies. AppleCare which I had through September, told me that the 512Mb chip I had in my lower slot was non-standard in some way and was causing the problem, although it had worked flawlessly up until that time. Now I’m out of warranty and still haven’t replaced the memory. Keep us informed as this issue develops.

Posted by: Allan Robbins at December 29, 2005 3:43 PM

I work as a service repair technician and can confirm that the lower ram slot seems to fail on a regular basis on the Powerbook G4 15.2" 1GHz and up.

However, I have absolutely no belief that it is caused by a software update. Nearly every case that I've seen was not a result of a software update, and I have done in the neighbourhood of a dozen or more of these replacements. I believe this to be a defect in the logic board design rather than a software update issue, and really, if you look at the range of updates that people are suggesting that cause this issue, you have to wonder what could possibly be similar in ALL of those updates that would cause a memory controller failure in this fashion. I have also seen the outer slot fail in the same way as the inner slot, so it is not isolated to that particular area.

It just happens that software updates get blamed for most problems when, in my experience, it is due to some other outside but completely unrelated problem with the machine. A corrupted directory structure is a very common one that people seem to have when they claim that a software update 'crashed' their system and it won't boot afterwards. A quick DiskWarrior scan of the drive fixes it, I reinstall the OS, and I look like a hero. Of course, we're not talking about a software problem here, but it seems very strange that, once again, the software update process is being blamed for another problem.

While I wouldn't call this a common problem, it is certainly one I have seen a number of times on these units. The most common failures are still white spot LCD panels, superdrives, and hard drives.

Posted by: Rob Harrison at December 29, 2005 4:21 PM

I have a 15" 1.25ghz and bought some ram for the lower slot - i put it in and the machine won't boot.
i went through 4 bits of ram before i just gave up - it's all sitting in a drawer at home. never thought it would be a software upgrade....

Posted by: robbie hughes at December 29, 2005 4:42 PM

I just looked on my 1.25 Ghz 15" and sure enough, the lower slot RAM is not working, and system profiler says there's no RAM there. The machine came to me with the standard 2X256 mb RAM.

Posted by: Anthony Paonita at December 29, 2005 6:40 PM

"Thank goodness for applecare"???
I am laughing heartily at that. You pay Apple to extend the warranty, then they screw up your system with a software upgrade, and you're happy about it.

Posted by: Osculator V. Weems at December 29, 2005 6:53 PM

Since upgrading to 10.4 all my machines have suffered kernel panics often. This never happened under 10.3 My Graphite iMac, powerbook 15" 1.25ghz and my MDD machine, crash constantly! I would say that 10.4 is probably the worst version ever of OS 10. The iMac crashed twice on wake from sleep today alone. The MDD crashes in the middle of the night constantly and the powerbook gives me a black screen instead of waking from sleep every now and then. This never used to happen with 10.3 It is interesting to see others have the same problem. It seems as if the Mac community has been tight lipped about this until now. I hope that Apple reads the crash reports, mine have not been very nice.

Posted by: Eric at December 29, 2005 7:27 PM

Greg wrote:
> For Trevor, yes this can happen, and is
> seems like it is happening.

Hello Greg,

Please understand that I understand that failure of the bottom memory slot is happening. This seems like a problem with the Apple hardware that Apple needs to fix. And it sounds like Apple is fixing it, at least while the PowerBooks are under warranty. This is not a question, really--there's a problem with the Apple PowerBook hardware related to the bottom memory slot.

What is not happening is that the hardware problem (failure of the bottom memory slot) is being CAUSED by software updates. If you can show a causal relationship between a software update and a hardware failure, you are a god, literally, as you are actively defying laws of physics.

Software does NOT cause hardware failure, and no lawyer can change that very fundamental law.

Let me explain what software is. Software is a very long series of zeroes and ones, organized in a special order that make sense to a computer's processor, and cause the computer to do certain things that the computer is designed to do. If the software doesn't work right, you can get something called a crash, where the software stops working in it's prescribed manner. Then you reload the software, or new software, etc. and everything is fine.

If the software were to write bad values to the hard drive (something that is entirely possible) then it could destroy your install of the Operating System, forcing you to reinstall. This is completely possible for software to do as well.

Where you get into the realm of fantasy is this idea that software can destroy hardware.

Only in a very very limited sense would this be possible, so let's start by discussing that. Let's say you wrote some software specifically designed to destroy hardware. You wanted to exercise a hardware bit until it failed, for example. So you wrote a series of zeroes and ones to the same bit over and over as fast as possible. After years of twiddling the same bit, you may be able to cause a memory failure of that bit.

So, you say, didn't you just show that it is possible for software to cause hardware failure?

Yes, but that was 1. deliberate, and 2. took a very long time.

I hope it is obvious that Apple hasn't deliberately written software that would do the sort of thing discussed above. (If you think that, then I give up.) And it is obvious that the people blaming software updates for problems think that because the two events happened near simultaneously, that they must be causally connected. So whatever the problem is didn't take a long time to occur. Therefore, the two necessities for software causing a hardware problem have both failed. Therefore, the software updates are NOT causing hardware problems.

What is happening, is that there is a hardware problem (failure of the lower memory slot) and there is a software update (because they happen periodically), so people falsely connect the two in their mind.

Understandable, but incorrect. There is no causal relationship between the two.

As the comments to this article show, several people have had the hardware problem without any software udpates. This is because people are having this hardware problem anyway, and the software udpate is coincidental.

I hope I've cleared up at least a bit of this question. In summary, I don't discount that people are having lower slot memory failures, and that is a very irritating thing that Apple needs to fix. It just has nothing to do with what they do in software.

Trevor

Posted by: Trevor at December 29, 2005 7:33 PM

My TiBook 400 lower memory slot recently went down as well, although I cannot link it to a software update. Currently running 10.4.3.

Posted by: David Nobbs at December 29, 2005 7:38 PM

Trevor seems to not understand that software and hardware can INTERACT. For a while, there was a problem where Airport would not work if you had more than 1G of memory for example. It is perfectly possible that a software update could render a memory slot "useless" even if this does not necesseraly mean "harware failure". Given the close interactions between firmware, hardware and software, it is often hard to tell the difference when something has failed. Another example might be memory timing where Apple has
tightened the spec on a number of occasions, rendering third-party RAM unusable.

Posted by: Ole at December 29, 2005 8:58 PM

Without going in to all the details... SW can absolutely induce a HW failure. Writes to firmware, voltage parameter instructions, etc. Obviously not intentional meatheads.

Posted by: Walt at December 29, 2005 9:05 PM

I had this happen to me last year with a brand new pbook 15" 1.5ghz.... Luckily the nice people at Santa Rosa Apple Store swapped it (6 weeks old) for a new unit and it solved the problem. Diagonstic software clearly indicated lower slot fried....

Posted by: Richard at December 29, 2005 10:14 PM

Wha? I just checked and sure enough my 15" 1.5 GHz PB is showing only 1 GB of ram and I have 2 of the 1 GB chips installed. Running 10.4.3 and have done all of the updates. Even scarier - my warranty expires 1/13/06 and I detest paying for an additional warranty. Freakin hell - now I have to go to my local Apple Store and see what they say...

Posted by: Charlie at December 29, 2005 10:19 PM

Uh, Trevor. I've got a quick bit of fact that ruins your theory.

Firmware. It's software. It can ruin hardware. Since apple don't tell you when they're installing firmware updates on your machine anymore, how do you know that you're firmware hasn't been updated and that's caused the problem? I've seen all sorts of hardware end up dead just because of dodgy firmware. It never allows you to screw up twice though, which is always handy.

Posted by: Dasmo at December 29, 2005 10:27 PM

I have worked in large software/hardware system testing for a few years now I propose you can easily have software causing (or exposing) a harware problem. I have seen problems where the hardware spec was not being met but was not discovered until a software change (tighter timing, smaller.larger que, etc) exposed what had been flaky hardware all along. The way to test this is to go back to the old SW and see if the hardware works again. Be sure all software is back to the way it was (firmware, PRAM settings, etc) There could be a lawsuit if Apple was shipping non spec hardware that was not exposed until 10.4. I am not saying this is the case, only that a relationship is possible.

Posted by: M Miglin at December 29, 2005 11:11 PM

Open firmware is software abd it is on the motherboard.

Posted by: just me at December 30, 2005 12:29 AM

I had this exact problem upon updating to 10.4.1 and took it to the genius bar. They fixed in within about 10 days (while wiping the HD along the way.)

Posted by: Tom at December 30, 2005 1:51 AM

To Eric whos macs keep crashing:

Get new RAM.

I had to go through 4 different 512MB RAM modules for my 1.25 Ghz Powerbook before I found one that would not crash during the Apple Hardware Test. I literally sat at the service counter trying one chip after another. And as for 10.4, I believe that each version of OS X has become more demanding and less tolerant of mediocre RAM thus your new found crashes when you upgraded to 10.4. My 10.4.3 is rock solid and simply never crashes.

CVB

Posted by: CVB at December 30, 2005 1:57 AM

BE CAREFUL HOW YOU PICK UP YOUR POWERBOOK.

If you pick it up so it flexes (such as by one corner), eventually the pins on the bottom slot come loose. I had this after 9 months. Motherboard replaced under warranty. I've been careful how I pick it up since then, no repetition after a year. It doesn't happen to the 12" because they're not heavy enough to flex much, and I think most 17" owners use both hands anyway because they flex *a lot*.

Posted by: Wheel at December 30, 2005 2:07 AM

"Let me explain what software is." Trevor, stop being a pedantic turd. Are you fourteen or do you just sound that way?

Posted by: Aaron Vibert at December 30, 2005 2:33 AM

Trevor,
it seems likely that *this* failure is not caused by software. To say that software cannot cause failure is not completely accurate. I've certainly been warned many times not to over-hz-ify my crt display, and had one smoke when i deliberately did it anyway to avoid flicker.

i've seen a core stack burn up while running pattern tests.

i've seen mainframes of more than one manufacturer fail with memory related problems simply because they referenced memory too quickly - backing out the update in those cases restored full functionality.

just because these are relatively old examples doesn't mean it can't happen again, at least in my opinion.

My TiBook seems perfectly happy.

-jfg

Posted by: Jeff Gunter at December 30, 2005 5:40 AM

Wow. Some Mac angst that I can relate to. I had a 15" PB 1.25Ghz with 768 RAM. Worked like a charm for over a year. Probably around the time I upgraded to 10.4, I noticed the machine felt slower. Huh--I looked in the system profiler and it said I was only running 256MB RAM, which I found odd, so I opened up the unit and there were, in fact 2 chips in there---512 on the bottom and 256 up top. Thinking somehow the RAM had gone bad--not like this has EVER happened to me in 15 years of Mac use, but what the hell--I ordered up another chip. When it arrived, I installed the RAM and the machine wouldn't boot AT ALL. No configuration of the RAM would boot the machine, except the original set up--and then it still wouldn't recognize the RAM in the lower slot. I sent the PB back to my IT dude and he sent me a newer 1.5 GHz PB, which has it's own issues (random trackpad slowdown), so i don't know what the resolution for the problem was---but this is a REAL ISSUE

Posted by: Eric Silver at December 30, 2005 9:05 AM

I don't really think that this is a "software causing hardware damage" kind of situation, but it certainly does not require god-like powers. The WRT54G router I have uses software to control the output power of the analog amplifier (probably a single CMOS transistor. The default value is 29 and the range runs from 0-255. As I push it beyond 45-50 I can feel the transistor heat up quite quickly and I am almost positive that If I just type in something much higher and click apply I WILL damage the hardware beyond repair. This is a very simple situation, but I am very sure that the same thing is possible with any hardware that relies on the laws of thermodynamics to function. I would bet that a simple mis-calculation in kernel space could fry the processor in any of our Macs by ramping the fans down instead of up when cycling the CPU or video card.

Laurence

Posted by: Laurence F. Hawkins III at December 30, 2005 9:49 AM

I tend to ignore the opinions of people who post text such as "makes the firmware controller or possibly the chipset get all wonky." If they can't get a tad more specific than "wonky" they probably don't understand it.

Posted by: Dave B at December 30, 2005 10:21 AM

Actually it is not the RAM slot that goes bad it is something else in the RAM controller. You will find that if you have 1 chip installed in either slot, then the computer will recognize it, however as soon as you install 2 chips the lower slot is not recognized. I was a MG at an Apple store when this issue first started popping up - I was actually the first tech to escalate the problem to engineering, and may have been the first to see and diagnose the issue. It has nothing to do with a software update, although software updates will often show issues that have been there all along - such as faulty RAM that worked great in Panther, but will give kernel panics in Tiger. This is not a problem with the software, but while Panther may have been more tolerant of faulty RAM, Tiger is not. The same is true with this faulty RAM controller, I saw the issue with Panther as well as Tiger, but it is more frequent with Tiger, because of the way Tiger access the controller, and is less tolerant of the fault. Jason

Posted by: Jason at December 30, 2005 10:52 AM

Trevor, I can't find it at the moment, but I remember reading (possibly in TidBits) about a situation where somebody ruined an old hard drive by trying to access a location that did not exist. The arm tried to go too far and that was that. Hardware can be destroyed by software unintentionally. (no I'm not claiming that's what has happened here.)

Posted by: Joseph at December 30, 2005 1:36 PM

Trevor, you are an idiot.

Software CAN damage hardware. Your theories of laws of physics and such are juvenile and ignorant at best.

I'm not saying that specifically in this case the OS X updates are causing the RAM slot issue. But your blanket statement that software cannot damage hardware is just plain wrong.

Any hardware that has firmware can be screwed over royally by a firmware upgrade.

For example: Firmware for DVD player. DVD Drives typically are set for a specific region, but allow that region to be changed a few times for convenience sake. Software could quickly render that DVD drive incapable of playing any DVDs.

Same can be said for hard drives (causing them to stop working). Ever flashed a video card? You will find LOTS of discussions on the net about people trying to flash video cards and causing them to stop working.

I think I've said enough.

Posted by: Matt at December 30, 2005 1:37 PM

My 15" 1.5 ghz's lower RAM slot is dead also. I ordered another 512 meg memory card and installed. It worked until I restarted. So now I have 3 512 meggers that work, but only 1 will work in the PB at a time. I did not buy Applecare and am no longer in warranty. Will Apple fix this for a reasonable fee?

Joe

Posted by: Joe at December 31, 2005 11:15 PM

Fifteen inch 1.25 PB: Five months ago, I had the Apple store in London repair what, at the time, seemed to be a screen issue. They ended up replacing my screen.

When I got the computer back, it still wasn't working right. For starters, it had lots of sleep issues. When I put it to sleep for the night, it would come on periodically and always be hot in the morning with the fan running. And almost always, when I'd try to wake it, I'd have to do a hard restart. Then too, as time went on more and more frequently it froze: again, I had to do a hard restart.

So near the end of November, I took it in to my local Apple certified repairman. He had it for a month as he looked for a secondhand logic board to put in. But not finding a logic board easily, he initialized the hard drive and installed a clean system. Then he ran it--for eighty hours, he said--with no crashes or problems.

So he called me and suggested I try it again; maybe the problem was gone?

I picked it up and tried it and had few problems for the first day or two. So, because with my growing iPhoto database, my 756 of RAM wasn't cutting it, I bought a new gig DIMM from Memory4less. The minute I installed it I had nothing but constant kernel panics--and right at startup, never later. So I went to BestBuy and bought a different gig DIMM, Kingston brand.

Again, I put it in and had nothing but kernel panics, constantly and right at startup. Returned it and got a different DIMM from the same store, same brand--Kingston. Same problems.

Because I had not yet returned my Memory4Less DIMM, i then experimented with ever possible configuration of the four chips I had: one 256 Samsung original to the PB from Apple; one 512 DIMM I purchased a couple years ago from Memory4Less; one gig from Memory4Less purchased in late November; and one gig from BestBuy purchased a couple weeks ago. I tried each DIMM with every other DIMM, each one in each slot--both bottom and top. No matter what I did with the one gig DIMMS, I had nothing but constant kernel panics. When I replaced the original 256 DIMM and the later purchased 512 DIMM, I had the fewest kernel panics and could, at least, use the PB--although it was very unstable and had lots of power managing and sleep issues. But it only froze occasionally (once ever hour or so).

Then, I read this discusssion and tried one last thing: I pulled out the old 512 DIMM from Memory4Less and placed the original Apple/Samsung DIMM in my upper slot, leaving the lower one empty.

BINGO! It's been rock-steady ever since. But ssssslllllllloooooooooowwwwwwww!

So now what? Any suggestions? I'm out of warranty and wonder whether if I managed to find a new one gig DIMM that didn't have the slewing issues the two others have, apparently, whether I might live happily ever after despite having one empty slot. What do you all think?

Posted by: Tim Bayly at January 2, 2006 12:45 PM

I apparently had two go bad and just now realized it. My older 1GHz was running slow so I went to the store to buy another chip... Ended up walking out with a demo 1.67GHz 1GB RAM running 10.3. Updated it to 10.4 so I could run Migration Assistant and noticed that I was now running at 512MB but two 512's were in it... So I opened the old one (which came with 10.3 and updated to 10.4 as well) to pluck the card to trouble shoot when I realized I already had two 512's in it... Took it to the Genius Bar and was told I'd need a new logic board (or motherboard, can't remember). Anyway, the demo they traded out with me for a new one (native 10.4) but the 1GHz unfortunately is out of warranty and it's just cheaper to buy a 1GB card than a new LB.

Had I known about this issue before updating the new PB I would have documented how it pre-10.4 showed 1GB RAM and 512MB immediately after the upgrade.

Posted by: Thomas Witte at January 2, 2006 9:00 PM

There is too much arguing going on here, the fact is there is an issue. I don't care what caused the issue, I just want mine fixed. Apple needs to address the issue. Software, hardware, don't care. In fairness, to most people it would seem to be a software glitch, especially since I can boot up with Apple Hardware Test, run the tests, all check out at 100% (both slots and my RAM) but then I go to bootup and the system crashes or doesnt recognize the lower slot all of a sudden. Seems to me if the hardware test doesnt find any errors with it, OS X should be able to see it ok too.... apparently not.

Posted by: Bob at January 4, 2006 2:32 AM

The lower ram slot on my PB 1.5GHz crapped out on 20/12/05, the same day as the last group of updates. I swapped out the RAM in an effor to troubleshoot the problem and the lower RAM appeared... for about 24 hours. Then it disappeared again. Swapped the RAM modules again just to make sure they're good. They are. Concurrently, I lost the startup chime. About a week later, my bluetooth module suddenly became "unavailable." Yesterday Apple released a bluetooth firmware update and it magically reappeared again! Coincidence? I doubt it. Either the heat from the processor is frying the lower RAM slots or there is a major firmware problem going on here. At any rate, Apple needs to address this problem, whether or not it's covered by Applecare. My PB just went out of warranty before this happened. Now it's barely functional thanks to the lack of RAM. I don't think I should be responsible for $1200+ cost of logic board replacement.

Posted by: D Kern at January 5, 2006 4:01 PM

I had the same problem. 15" Powerbook 1.25Ghz aluminum -- 2GB of RAM became 1GB of RAM. I bought a new set of matching 1GB SODIMMs to replace what was in the machine, then realized after experimenting with it that the DIMMS were not to blame. I eventually bought a new 1.6Ghz powerbook to replace it. It was a good machine except for the missing 1GB.

Posted by: Linwood Ma at January 6, 2006 9:50 AM

I just had a shock when I looked at the System Profiler on my PB 15" 1.5GHz - the 512MB of RAM in the lower slot has disappeared! Obviously this is a fault that Apple should fix! Aaargh! I am so annoyed! It's under warranty, but with the look of the posts here, can it be fixed, and will it stay fixed?

Posted by: P Newton at January 11, 2006 9:04 PM

I have had this problem before I did the 10.3.9 update (I havent bought 10.4 yet) I have a 15" 1 Ghz used to have 768 Mb of RAM now I'm only on one 512 chip. Pro Tools doesnt really like to run on 512 so I've been screwed for about a year now since I mostly use it for mobile recording anyway. I shouldve sprung for the AppleCare. Oh well. Maybe they'll do a replacement thing like they did with the batteries, which my PB was a part of as well. I still will get a PB over a Dell any day, these are just minor setbacks. I just wish these problems weren't so costly.

Posted by: Matt Dale at January 13, 2006 5:13 PM

I might as well add my voice to the ranks of those who have lost their lower RAM slot on a PowerBook G4 1.5GHz. I had never heard of this problem before but after having installed the 10.4.4 update and noticing a huge slowdown I decided to see if someone had stolen my RAM over the holidays. Apparently, I suffered not from stolen RAM, but from a stolen RAM SLOT.

The prospect of losing my computer for even 3 days horrifys me.

Posted by: Steven Luscher at January 16, 2006 9:29 PM

I have a similar problem with my 15" 1.5 GHz, and I haven't upgraded to 10.4. Currently I have a 1 Gb SO-DIMM in the lower slot - nothing in the upper slot - and my machine is unable to boot.


Has anyone had any luck simply moving a single SO-DIMM from the lower slot to the upper slot?

Posted by: Chris Stroupe at January 19, 2006 11:01 AM

Will answer my own question, in case anyone's still reading this. Switching SO-DIMM from lower to upper RAM slot seems to restore my machine. Has proven stable through several restarts (hot and cold) and sleep/wake cycles.

And - sorry for not RTFA'ing - I had updated to 10.3.9 before all this happened.

Posted by: Chris Stroupe at January 20, 2006 9:02 AM

My 2 year old PB lost the lower memory slot last fall. I ordered a 1gb stick from Crucial.com and placed it in the top slot with no problems. However, when trying to put it in the lower slot, system would hang. Now I have a dormant 512 in the lower that I hope will someday be recognized again...

Chris, you should be able to move a good memory stick from the lower slot to the upper, just make sure you seat it firmly.

Posted by: Fr. Innokentii at January 21, 2006 1:26 PM

Symptoms:
* Loss of startup chime
* Slower system operation with lots of disk thrashing.

Tried:
Reset PRAM; Reset PMU. Fix disk errors. Diskwarrior. Onyx to clear the caches. Still slow.

Ran system profiler, and found the (factory-installed 512k) lower slot empty. Bummer. Calling AppleCare tomorrow... S/N W8433xxxxxx not in the recall list.

Posted by: Dana Leighton [TypeKey Profile Page] at February 20, 2006 8:28 PM

Same here. Not on the lucky list and have a semi-functional lower slot. If I have ram in both slots is says lower slot empty. If I have only 1 stick in the lower slot it sees it. If I then put in the other stick, lower slot empty again. Pah! what a lemon. Should have kept the 12in.

Posted by: BillM at February 25, 2006 1:38 AM

Dead lower slot too. Called Apple. Not in serial number range. Two months out of warranty. Apple said "Too bad. You'll have to pay." I don't think so. That's the last rotten Apple I'll ever purchase after the abusive treatment I've received from them.

Posted by: DonK at March 4, 2006 7:09 PM

Hi everyone:

Just wanted to reply to the comments about whether there was a possible lawsuit to pursue. There is, but I don't know much about it or how it works. The website has all this info, and you have to decide whether or not this is for you.

The website is

http://www.lawyersandsettlements.com/case/apple_powerbook_classaction

Posted by: Greg Ranieri at March 6, 2006 10:52 PM

I have this issue with a 867 Mhz 12" PowerBook. Was happening intermittently since SU to 10.3.9. Today after a 10.4.5 security patch reboot it failed permanently. :-( And as far as I can tell Apple is only acknowledging the problem on a small range of 15" PBs.

Anyone else heard of problems on 12" PBs?

Posted by: Fuat at March 8, 2006 3:26 PM

I had been using with no problems a 15" 1.5 GHZ with two kengsinton 1GB SODIMMS installed.

I won another one (same model) in a contest; took out one of the 1GB SODIMMS out of the older one and installed it alongside an old 256 memory card I had removed from the older one when I purchased the two 1GB cards.

After installing the memory I I checked "About this Mac" and System profiler and it showed the new memory installed, no problems (1.25 GB)

After aprox. 2 hours of testing this machine by running a memory-intensive video app I started to notice slow performance.

I Checked the system profiler. The lower slot was reported empty.

I opened and changed the cards from place (the 1GB upstairs and the 256 downstairs).

Still getting the "empty slot" condition.

I don't have Apple Care, I bought it second hand, this means I'm stuck with a powerbook with a half-useful logic board? sheesh...

Two questions:

1. Are there 2GB cards out there for this model of Powerbook

2. If I sell it, what would be the reasonable price to ask, taking in account this defect?

Thanks

Posted by: Arturo Gil at April 22, 2006 10:45 AM

Post a comment




Remember Me?



(you may use HTML tags for style)


Spotlight
PowerPage 10th Anniversary

Site News

Feeds

Affiliates

Sites we like

Recent Entries