Mac firmware upgrades do NOT fix the 4 GB RAM problem
The appearance of the Apple firmware upgrades released yesterday for late 2008 MacBooks, MacBook Pros and MacBook Airs was welcome news to me and other owners and many applied the upgrades immediately. I was one of those in that crowd and my experiences with trying to run my MacBook with 4 GB of memory were followed by many who also reported problems. Last night I grabbed the updates and applied them to my MacBook hoping I would be able to run with the 4 GB of memory I had purchased.
I left the MacBook running all night after popping 4 GB of memory in at 4 pm my time yesterday and it ran fine all night which gave me hope that the firmware patches had indeed fixed the problem. Prior to the firmware update my MacBook, like many are reporting, would get system freezes frequently every time 4 GB was installed. It would run fine with either 2 GB or 3 GB of memory installed, even using one of the RAM sticks that compromise the 4 GB loadout that fails.
This morning the MacBook was still running fine with no freezes and I was starting to feel pretty good about the fixes but that didn’t last long. Just a while ago my MacBook froze up while sitting idle, exhibiting the same errant behavior that plagued me before the update and that has been reported by many in the Apple support forums. It appears that Apple still has some work to do to fix these system hangs which I have proven with my own testing only occurs when >3 GB of memory is installed. I hope they get this nailed, there are many of us who would like to run 4 GB in our MacBooks and MacBook Pros. It’s important to note that failures are being reported whether Apple-supplied memory or third-party memory is used. The consistent factor is that the new Macs often cannot handle 4 GB of memory. Note that I haven’t seen any MacBook Air owners complaining of this problem but then I haven’t really looked for any.
It’s important to note that Apple never said these firmware updates would address this 4 GB problem. They didn’t say much of anything about what they fix but there are quite a few owners that were seriously hoping the patch would address this problem. I’m sorry to disappoint those of you affected.
Was this test done with the SMC 1.2 or 1.3 update applied? The 1.3 update came out about 8 hours later so if it was done with 1.2 could you test after updating to 1.3.
Both updates were applied for the test.
You need to send the memory back and get another set. I had the EXACT same problem with OWC memory and they switched it and it worked perfect and has not froze since. At the very least, try reeseating it.
I have reseated the memory countless times. I do not believe the memory is the problem, too many people are reporting the same issues. I believe that there is a problem with the new Macs and Apple will have to fix it.
If some folks can run 3GB or 4GB of memory on otherwise identical hardware with the same firmware, the variable here is the RAM itself. Folks are switching RAM out and having the issue go away as well. Perhaps this isn’t an Apple problem.
there were 3 updates though… EFI 1.3 and SMC 1.2 which came out at the same time… then about 8 hours later SMC 1.3 came out.. SMC 1.3 updates it to .B06
Doesn’t the air only support 2gb anyway, that would account for them not having the same issues
These posts are getting stupid James. I bought my RAM from Apple which brings me to 4GB which I have NO PROBLEMS! Maybe if you buy RAM that isn’t the cheapest you might get something that works.
YOU PAY FOR WHAT YOU GET!
It’s an apple issue.. they’ve admitted it.. even computers with apple installed memory have the problem.. the good thing is that it doesn’t occur in Windows so it likely can be fixed in OSX with an update…
who knows maybe today’s 1.3 SMC update helped with this issue…
Geoff: I agree.
Geoff, what garbage. Apple don’t actually manufacture RAM you know, there’s some reason that Macbooks are crapping out at this 4Gb level.
James, is there a Mac equivalent to memtest86 you could use to check the memory and see if errors come up?
I can’t believe some of you are blaming James for ‘buying cheap RAM.’ You all realize that your precious Apple computers are the ONLY computers on the planet that say they will work with 4gb of RAM and DON’T, or at best ONLY SOMETIMES and only (possibly!) if you pay exorbitant prices for the same third party memory you could buy elsewhere.
Sheer idiocy. This is another perfect example of sloppy Apple engineering, and the braindead fanboys are taking the consumer to task for not spending enough money to make the problem go away.
Lucky for me the 4GB that came with my Macbook Pro is working fine. I have not seen any of the problems reported by various users (fingers crossed that it stays that way). The issues I see are with the airport update (can connect to many AP’s but there is one that it just keeps saying invalid password for some strange reason) and the graphics tear that seems to be a know issue with the nvidia drivers.
Unfortunatly neither my issues were fixed with this update..
Hope everyones memory issues vanish soon as that is certainly anoying.
Geoff, I’ve just reread my post and I didn’t mean to be so inflammatory! Most memory these days are produced by a few companies and quality is generally high. This issue has been widely reported elsewhere.
I reacted to you calling James out as you having no issues doesn’t mean there isn’t one, either related to bios, memory controllers or any other QA tolerance issue.
I have a 4gb of Apple supplied RAM straight out of the factory and am getting exactly the same problem. Lots of system crashes and situations where I put the computer to sleep only to get it later and find the computer as hot as anything and fully awake – but with a nearly dead battery.
The computer even woke itself up from being shut down the other day and wore out the battery. I have never experienced this with Macs before as they’re usually the reliable computers.
You’re right James. There is definitely something wrong. However, when it works right, it’s a SWEET machine!!
Regards,
Jon Dee
Gavin, OS X has an excellent RAM diagnostic test. The RAM passes with flying colors, for me and for the others reporting the same problem.
Sounds like somehwere along the line, some part of the pc is very finicky about the ram. If it’s not happening when booting to windows, hopefully that means another patch could sort things out in OS X. I’ve seen some very weird things on pc’s happen when ram was moved around.
This used to be a great site but whenever I come here now it’s just one Apple post after another. It’s all very boring, especially considering the fact that the products are so badly engineered that something as simple as a RAM upgrade causes them to crash.
How many Macs with RAM problems will you put up with James before you stand up to Om Malik, tell him that you’re not going to post about Apple ads any more and go back to writing about something interesting?
Jake, sorry you feel that way. The majority of the posts here are non-Apple. We cover all facets of mobile technology and Apple products fit into that category.
We don’t do any coverage with an eye to ads. We cover what is topical and what we use. That hasn’t changed nor will it.
Me thinks you have some faulty RAM. I was having a couple problems (not major, as in sluggish performance) when I upgraded to 4GB. The firmware update fixed it.
Almost half the posts that are currently on your front page are about Apple or directly related to Apple and today is not unique. No other hardware manufacturer receives as much coverage from JKOnTheRun as Apple does these days.
This post (http://www.jkontherun.com/2008/12/apple–buy-a-ma.html) is simply regurgitating an Apple ad.
Apple’s Built in memory test for Macs (MacOS X) is only a very quick test.
using a full test from a tool like the 64bit enabled memtest 86+ that is modified to run correctly under Mac OS X, you can sometimes track down “rare” ram issues.
Using one such testing tool, I’ve been able to track down many cases of “intermittent” problems actually being caused by one or more bad ram modules
memtestosx.org (under $2, only needed if you have over 3 GB of ram, otherwise the free Rember is a GUI version of memtest)
note: The MacPro tower uses FB-DIMMS which include ECC, and will show in System Profiler if they encounter any errors.
I bought 5 Macbooks with a APPLE INSTALLED RAM upgrade and 0 problems! I feel that James continues to use this site as a soundboard for him to get attention!
Do us a favor James and keep your personal issues away from this site. You are going to lose another reader soon!
well Jeff, the problem is that his “personal issues” unfortunately are happening to a large number of others as well…
Geoff – Sorry but the reason I continue to enjoy this site is that James and Kevin DO write about what they are using. I am sure you will agree that we all benefit when JK write a review about the latest device they received and are using themselves. I would much prefer to hear from people who are putting these devices to heavy use rather than just a superficial overview.
James I’m just here to offer moral support. I have blogged about my problems with Apple before only to be flamed by fanboy idiots who assume I didn’t power the computer on.
You have my sympathies. I’m on the edge of buying an MBP with 4GB ram, and this issue frightens me. I’m upgrading because my CURRENT MBP is so unreliable.
Now I feel trapped. Wary of upgrading. Can’t keep using this system. Can’t change OS platforms.
Good luck to you with the mac issues and the rude fanboys
I have a major issue with the person above using MY domain as his identity! I have no affiliation with this person Geoff? I am requesting that James or Kevin remove this as Mobility Today does not agree with this person’s comment!
James,
In reading the Apple forum, those that got their machine replaced seem to be OK now. Have you gone to an Apple Store and talked to them about this?
BTW, unlike some I have no problems with your Apple coverage here. Well, except your desire to drag Apple into the cheap, cut-rate, low-profit, dog-eat-dog world of netbooks.
I’m not a MacBook user or owner, but from reading the posts here and using simple logic, I would deduce that the problem is either an OSX software bug or a system board hardware issue when configured with 4GB.
The fact that James is reporting such problems he is having with his notebook I feel is welcome. I applaud reviewers who not only look at, but purchase, own, and use the hardware they talk about and otherwise recommend. I have purchased highly-praised equipment in the past having the CNET editors choice stamp of approval, only to find out it was a piece of junk when I turned it on:
http://lgponthemove.blogspot.com/2008/09/first-impressions-gateway-p-7811fx.html
It doesn’t matter whether you are playing with a demo/eval unit or a retail item purchased from a store with hard cash – problems of any kind need to be expressed and brought to the attention of users, prospective buyers, and the manufacturer. How else will you encourage progress if you don’t open your mouth and tell the truth?
Hi, I was just wondering if the same problem occurs with a 5GB or 6GB memory condition, as apple has said the unibody macbooks can actually address 6GB.
hi has anyone found a remedy to this yet by way of update or anything ???