Kernel Panic on 2012 MacBook Pro

Just purchased Mid 2012 Macbook Pro 2.6 i7(non Retina) and system freezes when browsing using Chrome. I have had two system freezes in just 8 hours of computer use since bringing it home from the Apple Store. Both freezes came from using Chrome. Submitted bug report to Apple. 😟

Hello,

I read all the posts on this thread so far. Got my MacBook Pro 13" yesterday. Installed Chrome, Firefox, Spotify and Skype. Nothing else. yesterday I was not getting any Kernel Panic's, but today I used Chrome with Incognito mode and I got 3 Kernel Panic's in 3 hours (or so). I was also running Skype, Spotify and Firefox at the same time.

In the crash report, I also have that line with Google Chrome (in all 3 reports; I submitted all 3 to Apple).

I will use Firefox for this weekend (next 2 days) and see what happens. I am thinking of going to Apple Store on Monday if I still get these Kernel Panics over the weekend, without opening Chrome.

So you think this might be Chrome's fault? (I haven't used OS X before; just switched from Windows 7 yesterday so... I don't have that much experience with it; I am an ubuntu user though).

Thank you,

Nuker

I've been using Chrome on my Mac ever since it came out and have had no problems to date what so ever. Both regular and incognito modes work as expected. I do run Snow Leopard 10.6.8 still as I haven't upgraded to Lion, so this might be an issue with Chrome on Lion specifically.

I believe the issue is related to some sort of compatibility with the new video cards.

I think its the compatibility with google chrome. I havent used it in the last 3 hours. and I havent had a panic message again. early days yet though. but in comparison to before where I was getting a message an hour, there is a conisderable improvement

It might be an issue with the Adobe Flash Player. Adobe released an updated version of its Player two days ago (11.3.300.262) while the version that comes with Chromes (which cannot be updated / replaced by the user) is 11,3,300,257.

The update is supposed to fix crashes of Firefox so there might be a similar issue with Chrome / its FlashPlayer, HardwareAcceleration and the new Intel HD Graphics 4000in the new lineup.

Just had my first kernel panic on my brand new mid-2012 MBP that's almost 2 days old now, while using Google Chrome. I also experienced this on my early-2008 MBP that lead to its demise and Apple replacing the logic board free of charge (NVIDIA issue).... All of this in the period of one week. I strongly believe this is a Chrome issue since it's happened to me on two separate MBP's running Snow Leopard and Lion, respectively. "If it hurts, don't bend it that way" is the best solution in this case. If someone could make Google aware that several users are experiencing the same thing, that would be helpful in fixing future versions.

Johnny -

A number of users have had problems using Google Chrome on new MBP's - the only soultion I've heard of is downloading and installing the newest Chrome at https://tools.google.com/dlpage/chromesxs - try it and see if your Chrome issues will go away.

Clinton

I've also experienced the same thing. I just bought the 2012 MBP retina less than a week ago. first i had a wallpaper user problem which was fixed by delete the newly set up account to another new user. Then, the com keep crashing when I was doing work, twice in 3hrs.

Called APPLE and they told me to reinstall Lion OS. Reinstalled it 2 days ago and since it was crashed twice. I was using Chrome all the time too. It's stupid to change browser because I'm used to Chrome. The APPLE guy told me I could have replacement computer if reinstall Lion doesn't solve my problem. But if all 2012 MBP has the same problem it's too troublesome to get it replace and reinstall everything. 😟

Not sure what to do now. I hope the upcoming Mountain Lion OS will fix this.

I bought a Macbook Pro 13" 2.9ghz (Mid-2012) from apple.com

I downloaded Chrome as my browser, I got a kernel panic while I was on chrome and I was listening to songs on iTunes.

Called up Apple, lady says it might have been your song because the song went on a loop like a broken record, she said to do a software update. I did the software updates, less then 24hrs later I get another kernel panic. I was so ****** off because, my two friends have had a MBP for more than a year and they have not gotten ONE KERNEL PANIC. So i go to the apple store, swap it for a new one. Now i have this new MBP for 2 days, I downloaded chrome again because I NEVER THOUGHT CHROME can be the PROBLEM. I got another Kernel Panic while I was listening to music on iTunes and browsing on Chrome AGAIN. So this is my first kernel panic on this new MBP.

Should I return it again? I'm using safari now and chrome is out of my MBP all the way. Should I use it for like 5 days and see if I get another one?

There are 'known issues' with the new MBP's and Chrome. Just try using Safari or Firefox and see if your kernal panics go away.

Regards,

Clinton

aight mate. I will use it and if it happens one more time, IM GOING TO APPLE STORE! Im seriouslly so mad, it is such a hassle to download everything back. Specially if your new to the mac family; still learning the basics.

Return your machine to the Apple Store if you like, but this is an Apple software bug in the com.apple.driver.AppleIntelHD4000Graphics kernel extension.

Each of these panics is occurring at the instruction at offset 0x8a01 into the extension.

This is not the fault of Chrome or Final Cut Pro or of any other application, it's a bug in the kernel extension.

You can either wait for an Apple software fix or return your MBP for a refund - it's your call.

But there's no reason to debate it any further.

The software is broken, Apple needs to fix it and you can wait for a fix or not, period.

So your saying, if I return it and swap it for another one, I will have the same problem. So your advice is for me to get a full refund and buy a different computer? Am I correct?

I downloaded google chrome canary. and ive had no kernel panics for about 5 days !! try doing that. I dont think its a serious problem which requires yot to get a new macbook. people have already posted on here that exchanging macs hasnt solved the problem