I've been waiting 10.8 to upgrade since 10.7.4 gave me kernel panics.
Today I did bought the upgrade and it didn't event complete the new OS install. It gave me Kernel Panic before finishing 10.8 installation.
That's very frustrating. I'm stuck in 10.7.3 for my Macbook 2009 should actually be compatible with Mountain Lion as Apple advertises.
I hope Apple has a fix for it soon. I'll go back and restore to 10.7.3.
Yesterday I was getting KP's every half-hour on my Mac Pro Dual Core with 10.7.4. I do not have any peripheral equipment. The system has one extra internal harddrive. I mainly use Adobe CS4 and Final Cut Pro (7.03). The KPs were random. Apple memory only. Many times the machine seemed to randomly log out and back in.
I did the following:
1) Repaired permissions: Nothing to repair. No problems found.
2) Ran Apple's hardware test. No problems found.
3) Rebooted with Command "R." Reinstalled the OS software. Twice it came back with an error that it was unable to download the necessary components. It finally went through and reinstalled 10.7.4.
4) The reinstall messed up Adobe CS4. I could open Photoshop, but when I tried to create or open a file a dialog would pop up indicating that there was a problem with version cue client. Closing this dialog caused Photoshop to quit.
5) Reinstalled the affected Adobe software which fixed the problem.
So far, I've had zero Kernel Panics. Fingers crossed.
And another this morning....
Interval Since Last Panic Report: 21833 sec
Panics Since Last Report: 2
Anonymous UUID: F4E78156-1C88-4E95-BD54-8471AF43A289
Mon Aug 6 08:10:24 2012
panic(cpu 1 caller 0xffffff80230b7b95): Kernel trap at 0xffffff80230876bc, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000020000000028, CR3: 0x0000000069fec055, CR4: 0x00000000000606e0
RAX: 0x0000000000000001, RBX: 0x0000020000000000, RCX: 0xffffff8041c80000, RDX: 0x0000000000000821
RSP: 0xffffff81836e34b0, RBP: 0xffffff81836e34d0, RSI: 0x00000000283baec0, RDI: 0xffffff80286190b8
R8: 0x0000000000000001, R9: 0xffffff802b7ae8e0, R10: 0xffffff80236bcc20, R11: 0xffffff7fa357c4e2
R12: 0xffffff80286190b8, R13: 0xffffff80417369d0, R14: 0xffffff80417369c0, R15: 0x000000013b79b000
RFL: 0x0000000000010206, RIP: 0xffffff80230876bc, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000020000000028, Error code: 0x0000000000000000, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff81836e3150 : 0xffffff802301d5f6
0xffffff81836e31c0 : 0xffffff80230b7b95
0xffffff81836e3390 : 0xffffff80230ce4ad
0xffffff81836e33b0 : 0xffffff80230876bc
0xffffff81836e34d0 : 0xffffff802307fe3a
0xffffff81836e37f0 : 0xffffff8023386522
0xffffff81836e3820 : 0xffffff80230e516c
0xffffff81836e39b0 : 0xffffff80230e3079
0xffffff81836e3c10 : 0xffffff80230e2fb5
0xffffff81836e3c40 : 0xffffff80232f0a52
0xffffff81836e3ca0 : 0xffffff80232f03a7
0xffffff81836e3d40 : 0xffffff80232f0170
0xffffff81836e3d90 : 0xffffff80231133f2
0xffffff81836e3dd0 : 0xffffff80230f2017
0xffffff81836e3e00 : 0xffffff80230ee909
0xffffff81836e3e20 : 0xffffff802310860f
0xffffff81836e3e70 : 0xffffff802334c56c
0xffffff81836e3ee0 : 0xffffff8023348b6f
0xffffff81836e3f30 : 0xffffff802334af60
0xffffff81836e3f60 : 0xffffff80233e14e3
0xffffff81836e3fb0 : 0xffffff80230ce9dd
BSD process name corresponding to current thread: uTorrent
Mac OS version:
Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64
Kernel UUID: 8D5F8EF3-9D12-384B-8070-EF2A49C45D24
Kernel slide: 0x0000000022e00000
Kernel text base: 0xffffff8023000000
System model name: iMac12,2 (Mac-942B59F58194171B)
System uptime in nanoseconds: 931564926375
last loaded kext at 32421785625: com.apple.driver.AppleHWSensor 1.9.5d0 (addr 0xffffff7fa4a11000, size 36864)
last unloaded kext at 149349747855: com.apple.driver.AppleUSBUHCI 5.1.5 (addr 0xffffff7fa399d000, size 65536)
Model: iMac12,2, BootROM IM121.0047.B1F, 4 processors, Intel Core i5, 2.7 GHz, 12 GB, SMC 1.72f2
Graphics: AMD Radeon HD 6770M, AMD Radeon HD 6770M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3231554538424655302D444A2D4620
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3231554538424655302D444A2D4620
Memory Module: BANK 0/DIMM1, 4 GB, DDR3, 1333 MHz, 0x0000, 0x563031443353463447423236383236383133
Memory Module: BANK 1/DIMM1, 4 GB, DDR3, 1333 MHz, 0x0000, 0x563031443353463447423236383236383133
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 18.104.22.168-P2P
Bluetooth: Version 4.0.9f8 10405, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: WDC WD1001FALS-403AA0, 1 TB
Serial ATA Device: OPTIARC DVD RW AD-5690H
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfd110000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 3
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 5
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x850b, 0xfa200000 / 2
I'm really angry now. This is my main computer and it's next to useless at the moment.
APPLE... Say something......
I can't find a consistency to the Kernal Panics on my iMac, although they seem to be in response to initiating too many process threads (my clicking in a number of applications). If I explore Console to see a pattern - I can't find one. As I have a 10.8 install also on my MacBook Pro I can compare.
I've been doing a lot today, some heavy processing and piping and so far so good. What is interesting is that power recycles are quick and usually solve the problem. I still clear caches and Repair Permission and PRAM & SMC Resets, although not for a whole day now!
I'm looking forward to a system update from Apple - can't help thinking they're working on this. I remember early iOS problems which were ironed out very well in the end (as millions of consumers may testify).
When I installed 10.7.4, I immediately began experiencing multiple kernel panics (at random times; sometimes while the machine had been sitting idle for several minutes). This is an iMac (early 2009 20 inch), model iMac9,1. The only remedy was to painfully (because I didn't have an immediately recent backup) go back to 10.7.3. As I've said before, I suspect these panics were caused by the fact that my hard drive is not original to the machine — I had to upgrade to a 1.5 T disk (Seagate), the original disk was only 350 G, and I was replacing an earlier iMac with a 500 G drive.
This possible cause obviously does not address those with MBPs who have not upgraded their disks.
However, I'm quite leery of upgrading to ML, fearing that the programming which caused the KPs in 10.7.4 is still there.
Question: anyone out there using ML on an iMac with an upgraded hard drive?
Hi everyone. I have been plagued with the 10.7.4 kernal panics and was contacted by apple support. Very helpful and was told that it seems that computers that have been upgraded in any way are having problems. Surprise, surprise I had upgraded to 8GB Ram (G-Skill) and even thought there were no reported problems with the memory with Memtest and Apples own Hardware memory testing, when I changed back to the original 4GB - everything is fine!
I upgraded to 10.8 and still rock steady .... Look, I know I may have just been lucky, but in this thread I have noticed more and more comments about new hard drives, memory modules etc been in the machines that are failing.
This worked for me. Good luck .... Hope my luck holds out!
Thanks. I guess this reply is quite useful in understanding what's going on with our macs.
Anyway... none of us just upgrated their computer "for fun", so I don't think that coming back to the previous configuration could be considered a suitable answer.
In my (always perfectly working) Macbook unibody late 2008, I just had 2 GB of RAM memory and a 160GB HD in the original configuration. Absolutely not enough for considering an hardware restore - and actually, not enough for upgrading to ML too.
I know where you are coming from, my move to 8GB was out of a need to get more from my MAC and now I have it sitting next to my machine and not in it. I'm not happy, but at least I can get my work done. Apple seem to have designed their software, in particular 10.7.4 to be more sensitive to different hardware configurations. They have messed up somewhere and I don't think they really know where. I was lucky to have a more recent system then yours and able to roll back my hardware. Again, I'm not happy, but I'm working.
All, please check out the following article (TS4088) regarding this issue if you have a mid-2010 15" MBP. This is a hardware issue and won't be repaired or fixed without Apple's involvement.
Just to let everyone know, I took my MBP into a Genius Bar. They have a specific test for the mid-2010 MBP that identified the VSI system on my laptop as bad. According to my "Genius", this affects 15" MBPs built from April through June of 2010. The good news is I'm getting a replacement motherboard for free, even though my Applecare ran out 6 weeks ago. It is apparently covered for the first 3 years from purchase, but is at Apple's option thereafter. It is a $390 if you have to pay for it yourself. Unfortunately, they don't stock the motherboard so it has to go to an Apple depot to be fixed and will take from 3-5 days.
I'd urge everyone with a 15" mid-2010 MacBook Pro who is experiencing intermittent kernel panics to read TS4088 and to take their laptop and a copy of the article to a Genius Bar so that it can be propertly identified and repaired. There is a test specifically for this model that can identify whether the video chip subsystem is at fault.