This discussion is archived
5682 Views 98 Replies Latest reply: Feb 21, 2006 8:50 AM by Gavin Brown
Currently Being ModeratedAug 2, 2005 10:13 AM (in response to Joe Rockmore)Edited by an Apple Moderator
It could conceivably be pure coincidence, but the SWU for 10.3.9 is when the reports started coming in. It appears that 10.3.8 or below doesn't trigger the issue, but 10.3.9 and Tiger does. The symptoms are: no boot chime, no power button light, and no lower RAM slot. At least in my case, they came sequentially--the boot chime and power button light preceded the RAM issue by a few days.
Possible explanations could be a) new power/temp management schemes that run the system a bit hotter, triggering a heretofore undetected solder joint failure, b) some goofy firmware snafu, or c) just coincidental timing with the culprit being an inherent design/production flaw that only reveals itself over time and under long-term processing loads.
For those of us with the issue, this is all just guesswork. We are hoping Apple discovers the truth and acts on it. I, for one, don't want or need a "mea culpa" admission of the flaw--I just want it FIXED IN MY MACHINE!
Is that too much to ask?!
Currently Being ModeratedAug 2, 2005 3:23 PM (in response to Joe Rockmore)After reading all of this I almost cancelled my order....I guess this is enough to make anyone paranoid, however I really wanted this notebook and so I called apple and had them change my order to 1 stick of gig instead of 2 512's, I hope that this particular logic board failure does not effect anything else, if not then I should be safe now as I don't anticipate needing anymore than a gig. question though, if you are only using 1 stick do they automatically put it in the upper slot?
Currently Being ModeratedAug 3, 2005 11:03 AM (in response to Scott Bass)People listen to this. I think it's a software problem. I have the same problem. lower slot "empty". I've tried swapping the sticks, they both work fine. They both also work fine own their own (only 1 stick installed) on either slots. What I'm saying is that if you install just 1 stick in your comp even in the lower slot it will work fine. Only when you install 2 you have a problem. Apple's being ********. There was one case the other day where the poor guy had his board replaced 3 times already and still had the problem. If everyone keep beating Apple they may fix this. (please!)
Currently Being ModeratedAug 4, 2005 7:17 AM (in response to Pitoon Varanyuwatana)Folks... this has nothing to do with software. I have it on pretty good authority it's a batch of bad logic boards... the guy mentioning the soldering of the slots was probably right. I had the same issue WELL before 10.3.9 even came out, had it replaced under warranty, and everything's been groovy since.
And the three-repairs-guy? I somehow doubt this. Apple usually won't repair the same machine three times. They'll replace the machine.
Oh, and in my experience, if you buy a laptop and intend to use it longer than a year, buy AppleCare. Every laptop I've purchased at my company (Windows-based or Mac) has had some debilitating problem that needed repair in the first three years. And by now I've purchased 50-60 laptops starting with Powerbook 5300s (Anyone remember the 5300 nightmare??)
Currently Being ModeratedAug 4, 2005 11:08 AM (in response to Marc Opperman)I sure hope you are right. I am on my third MLB right now, and if it fails I will expect a new machine as a replacement. In fact, if the issue is not formally acknowledged by Apple when my machine fails again, I will strongly push for a 17" as a replacement, as the issue does not affect 17" the way it seems to plague 15" PBooks.
It took 15 days each time for this repair. That means for the six months I have owned this machine, it has been out on repair for one full month. Yikes. My Pismo went 2 1/2 years without problems!
BTW, from the moment I got my PBook back from the Apple Store, the power light hasn't worked, which seems to be the early warning symptom for this MLB problem. You can bet I'll be looking at System Profiler every day to make sure all 1.5 GB of RAM is being recognized.
I actually use my machine for real production work (live audio recording/video editing). Downtime is NOT an option. I hope we see a quick end to this issue ASAP.
Currently Being ModeratedAug 4, 2005 1:35 PM (in response to Joe Rockmore)I don't know the cause, but here are the symptoms...
Frequent failure (9 out of 10 times) to re-start (chime, light, screen) with 512 in lower and upper slot. If I pull the upper 512 DIMM, re-start is fine. Upper 512 is Ramjet RAM, lower 512 is Apple. If I switch them, same problem. If I re-start only with Ramjet RAM in either slot, no problem.
I have Apple(Sometime)Care(s), but with posts stating that Apple will just remove the non-Apple RAM and send the unit back, there is no reason to send in. I either avoid re-starts, or pull the upper slot before a re-start. Kinda sounds like an undocumented feature on a Windoze machine.
Currently Being ModeratedAug 4, 2005 2:15 PM (in response to Joe Rockmore)Because of this issue I have recommended to the University that I work for that we should stop purchasing any Apple products until Apple admits responsibility and fixes the issue.
Currently Being ModeratedAug 4, 2005 2:23 PM (in response to Marc Opperman)The memory connector is a BGA ( http://en.wikipedia.org/wiki/BGA ) and while its possible that one of these connections failed over time, its very surprising that it would ONLY affect the bottom slot. I could be the memory controller, but again, why only the bottom slot? Unless there's some signal that is being overdriven and damaging a buffer on the controller, or a physical disconnect is happening in the PCB or the BGA connection, or the connector itself (my connector looked fine), I can't imagine what the problem is (unless its software).
And as for getting a new powerbook instead of three repairs, I've had my powerbook in for service three times - each time with a motherboard replacement. The first and third were for a faulty magnetic switch (which keeps the PB sleeping when the lid is shut) and the second was for a dead ethernet port after it came back from the first repair broken.
Only on this third motherboard has the lower-slot problem occurred, and it DID only happen when I upgraded to Tiger. I'd only had the Apple 2x256 RAM in it until I decided Tiger just needed more memory and my 2x1GB purchase only showed up as 1GB.
Getting AppleCare to repair your machine is a waste of time. Chances are that sometime down the road the lower slot will cease working again - and the next time you'll probably be outside of AppleCare's "protection".
Its a Design/Quality Control issue and Apple needs to address it.
Currently Being ModeratedAug 4, 2005 3:09 PM (in response to JDee)Well add anouther victom of this to the list.
As a mater of fact, I just cloned my drive to my portable Firewire and am running off that while my Laptop is in for repair.. Hopfully only once is al lI need to get this repaired properly.
Currently Being ModeratedAug 4, 2005 3:43 PM (in response to Megan Marshall)Megan,
Before the moderators close this thread, let me point out that any ANY repair needed on an Apple product is fixed at no cost to you as long as your product is still under warranty. If you bought a car, and one week after the warranty was up due to a bad solder the onboard computer would not work, you would not expect the dealership to fix it for free. I understand your point, that if this is a design defect Apple may decide, or be compelled to fix this problem outside of the warrantee. Until there is evidence that this is the case griping on this board is sour grapes. I suggest that you contact your States Attorney General, and go through proper channels. The AG can ask Apples to disclose the failure rate on the lower memory slot. Then and only then can we be sure that there is a design defect.
I hope that these failures are the exception and not the rule, because I am also a proud owner of one.
Currently Being ModeratedAug 4, 2005 4:39 PM (in response to Joe Rockmore)I have the exact same problem as Joe. It all started when I upgraded to Tiger a couple of weeks ago. I am getting the same error message which describes the SODIMM0/J25LOWER failing to be read. I tried reinserting the memory card in the lower slot. I then restarted my computer and my Powerbook was able to read the memory card. But this only lasted 10 mins and after that my computer froze and I had to reboot. When I was back to the desktop, I realized that my SODIMM0/J25LOWER had failed to be read again.
This happens over and over again after reinserting the memory card.
I never had this problem before I install Tiger, which leads me to believe that it is a software issue.
Anyone knows what apple is planning to do about this?
I love Macs, but Apple just seems to not do anything about this.
Currently Being ModeratedAug 4, 2005 6:07 PM (in response to Jose Zambrano)The lower memory slot in my 15" 1GHz Powerbook failed after I upgraded to 'Tiger' 10.4.1 from 'Panther' 10.3.9.
My powerBook is 18 months old and therefore out of warranty; but it was running perfectly OK BEFORE the upgrade to 'Tiger'. I have had no alternative but to purchase a new 1 GHz Logic Board at a cost here in London of just over £600!
It would be interesting to discover what percentage of people have suffered this problem with their 15' PB's AFTER upgrading to 'Tiger' ....
I too love Mac's and would not use any Windows PC or operating system other than OS X - but Apple have to address this problem - and soon. I am sure there are many more people 'world wide', not submitting to the Apple discussion forums, who are having the same problem - always the lower memory slot that fails ...
I also have to agree with Jose Zambrano when he suggests that this problem could be a software issue.
Currently Being ModeratedAug 4, 2005 6:46 PM (in response to Joe Rockmore)Same problem where with 10.4.x problems of wake up, not starting, etc. started happening. Just replaced the MB (under warranty) and the tech took out the 512MB lower memory to say it failed tests. I am waiting for replacement memory (3rd party) to see it is the problem or the problems others are reporting.