-
All replies
-
Helpful answers
-
Sep 27, 2012 12:48 PM in response to Doc Doughertyby eleft,I have the same exact problem with a brand new MacBook Air, 2.0 GHz, 8GB RAM, 500GB disk, running 10.8.2. Random freezes, uncorrelated with Chrome use. They happen every hour or so.
-
Sep 28, 2012 3:01 AM in response to Adrianortby avt232,Same problem here. Brand new MBA 4GB RAM... First time a Mac freezes on me like this for 9 years..
-
Sep 28, 2012 3:02 AM in response to avt232by avt232,(not using Chrome, was using Safari at the time of freeze)
-
Sep 28, 2012 7:45 AM in response to Adrianortby Robert Pettengill1,A couple of thoughts on this issue:
I have an 2GHz/8GB/256GB/11" Air and like many people had the issue with crashing when running google crome, I stopped using crome until it was updated and had a few minor remaining issues that seem to have been resolved with the last two updates.
I use my Air heavily for software development wtih java, eclipse, solr, mongodb running all the time. I also use part time for video and image editing with Apple tools and Photoshop as welll as the usual email, web, and social uses. It is more stable than my old air was under lion now with weeks between hangs (althought not back to a snow leopard never ever crash level of stability).
As I understand it, the crome related crashes were because crome triggered a specific bug in the video driver. It is possible that other applications can trigger similar bugs. If you did an upgrade install you may have an old driver or corrupted config file. If you don't see any software association with the crashes and running some specific piece of software and you are sure you have a clean OS install - it is likely a hardware issue. Remember the new Air has a new cpu, chip set, and graphics chip and the associated drivers will be new as well, so there are bugs and your specific hardware may be marginal and more apt to trigger them.
Crashes every few hours are intollerable. I'd suggest taking a copy of your system logs showing the crashes every few hours to the Apple Store and politely asking them to fix it or give you a machine that works.
Best wishes, this is one sweet machine, when you have a good one.
-
Dec 25, 2012 3:50 AM in response to Adrianortby plaski.pl,Hi everyone!
I have the same problem.
Bought MB Air 2012 in US, brought to Europe (Poland).
After 5/6 days of using my freezeing problem started.I've been in Apple Service Center, they replace mainboard
(so they change almoust everything except screen and battery, becouse every main part is soldered to board).
Still have problem...
I've noticed that this problem occurs always when I'm using Safari with or without Flash.I've tried to close it, plug in charger, press anything on keyboard. No respond, only hard reset...
PS
Ofcourse I've updated system.
Never use Chrome on Air.
-
Dec 26, 2012 1:50 AM in response to eleftby eleft,Update: my problem went away after performing a clean reinstall of the operating system.
-
Feb 9, 2013 7:46 AM in response to Adrianortby Swetsenegger,I have the same issue on my macbook air 5,2 (mid 2012) 2Ghz Core i7 8GB.
Cannot pinpoint it to any specific app. Happens once every few weeks.
I did run hardware test and it didn't find anything in particular.
Strange.
-
Feb 27, 2013 8:06 PM in response to Swetseneggerby williamwoodstock,I have the same issue on a brand new Macbook Pro Retina with 8GB memory. This happens twice a week. Totally unacceptable. I had the Genius bar do a series of tests which revealed nothing. If I wanted these problems, I would have bought a Microsoft product. Maybe I need to return this $2500 laptop and buy a Linux box.
-
Feb 27, 2013 9:05 PM in response to williamwoodstockby Doc Dougherty,My freezing issue was resolved (after many weeks of work and many different AppleCare advisors) by isolating and removing a bad prefs file. The support person who finally provided the useful help walked me through a binary sort that took six or seven cuts of removing half of the prefs files and rebooting. Then it might take a day or two for the problem to reappear. It was really painful but when it started working it just kept on working. Then we would go back and put half of the set that was known to contain the problem file back in and reboot and see if the problem reappeared. The advisor had some ideas of where the problem might lie so the knowledge that came from Apple was really helpful or it might have taken twice as long. On the way to getting the good help, a number of things got messed up, including a lot of permissions that had to get reset correctly. Very frustrating, but ultimately successful. I am glad I kept at it since the problem was not resolved until well after the initial warranty was over. If you have a trouble ticket, keep using the same number until you get a satisfactory fix confirmed. Everybody seemed to want to help, but it took a long time to get connected to the person who actually unwound the "fixes" from others and went after the root cause.
-
Mar 3, 2013 7:23 AM in response to Robert Pettengill1by devil-doll,Crashes every few hours are intollerable. I'd suggest taking a copy of your system logs showing the crashes every few hours to the Apple Store and politely asking them to fix it or give you a machine that works.
I've tried to find the specific system logs in Console, but I get overwhelmed by the volume of them.
Could you name the exact ones you would look at / forward to Apple?
I know they know which ones, but I'd like to know as well, for my own edification.