Kernel Panics - the iMac from ****

Question

Kernel Panics - the iMac from ****

About a month ago I bought an iMac, i7, 32GB RAM, 1TB SSHDD.

There is a thread elsewhere discussing a similar problem I'm having with my iMac. I believe the bulk of that thread involves issues with memory but mine is not.

Almost as soon as I turned on the iMac after unpacking it, I began having kernel panics. These kernel panics would trigger a restart of the iMac.

The first Apple Tech Support rep I spoke with was absolutely convinced that my problem was hardware related and, most likely, caused by external peripherals connected to the iMac.

The devices I had connected were: a Western Digital Studio II 3TB HDD, a Cyberpower USB battery backup (I was using the UPS software built into System Preferences), an Apple USB keyboard, an Apple USB SuperDrive and a Dell 21" monitor.

So I disconnected all the devices.

Still had kernel panics. But in looking at the console logs I did notice that Google Chrome seemed to be involved just before the restarts. In the other thread someone suggested that was just because it was the last application open when the iMac restarted.

I decided to do a complete OS reinstall.

Still got kernel panics. Of course I did the PRAM and SMC resets and even ran a hardware diagnostic test that showed everything was working just fine! (Doesn't it always?)

Around St. Paddy's day I called Tech Support again (and this is when I started documenting my phone calls to Apple) and spoke with a very intelligent young woman who looked at my console logs and decided that, indeed, Google Chrome was attempting to access a .plist file, was being blocked, and then the restart occurred. So, we moved the file to the desktop to allow it to rebuild itself just in case it was corrupted. She did warn me, though, that if this didn't work an OS reinstall was next.

I started watching the console logs after that call was over and although I did not have a restart, I did see the log entries of Google Chrome Helper attempting to access that file (which had been "deleted" and rebuilt). So, clearly (?), removing the file was not fixing THAT issue.

But...then...the computer froze. Locked up tighter than a drum. The only option was to turn off the machine and restart it. When I did that the computer rebooted, got to the white screen with the Apple logo and spinning gear and froze up.

Another call to Tech Support got me to do an Erase and Reinstall of the OS (what the former rep suggested). That worked just great, everything was working, I reinstalled my apps (rather than migrating them - dowloaded them "fresh" from the app store)...for about two hours.

When I returned to the iMac after eating dinner, once again, it was frozen solid. I turned it off and restarted the iMac.

This time I got to a white screen with a "ghostbusters" sign. (I have found out there is no "official" name for the circle with a diagonal line through it - other than a "universal NO sign" - so I just call it the "ghostbusters" sign.)

I have learned, from my past 15 years of running a computer network for a small independent school, that behavior usually means the hard drive is toast.

So...called Apple again.

At this point I'm talking with "senior" reps - get to bypass the ground level techs.

First thing she asks is "How close are you to an Apple store?"

"100 miles", I respond.

So she sets me up with an on-site call - unfortunately they have to put it into the system and then the on-site third party has to call to set up an appointment. However, they will call me back within 24 to 48 hours. (Yeah, right!)

You see, Apple can't take my word for it that there is something seriously wrong, in spite of numerous calls. They have to "send someone" to "see for themselves." OK, I get that.

So, last night, in desperation, I thought I'd try one more time and did an internet restore (command + option + r). I got to disk utility and noticed that the Macintosh HD partition was grayed out under the SSHDD entry on the sidebar. I did a disk repair and the repair reported "Invalid content in Journal", but said it repaired the disk. Upon restart, still "ghostbusters". Tried one more time and got the same thing. I'm guessing (HOPING) that when the tech arrives (if he ever does) they won't be able to do an internet restore since the drive should not show up. I didn't try that, but will tonight (since I can't do anything else with the iMac).

So, now I patiently wait for 48 hours to pass and then call Apple again and tell them I didn't receive a phone call. (Jeez, I hope I'm wrong.)

In the meantime, my iMac is a worthless, but beautiful, piece of junk on my desk.

I'm absolutely convinced the problem is the flash ram on the motherboard and my iMac needs to be replaced!

Posted on Mar 25, 2014 10:17 AM

Reply

Answer 1

andyBall_uk

Level 7

20,516 points

Mar 25, 2014 10:55 AM in response to John.Orban.who.lives.in.USA

>> I did a disk repair and the repair reported "Invalid content in Journal", but said it repaired the disk. Upon restart, still "ghostbusters".

After repairing the HD, did it stop being greyed out, and were you able to erase/install OS X ?.

Reply

Answer 2

Mar 25, 2014 10:58 AM in response to John.Orban.who.lives.in.USA

Whatever the reason a month old computer should not be behaving like this one.

I would be pushing to have it replaced not repaired.

Good luck, hope you get a satisfactory conclusion.

Reply

Answer 3

Mar 25, 2014 11:10 AM in response to andyBall_uk

Still grayed out, yes.

Didn't do a restore but will try tonight. But "guessing" if it was still grayed out I suspect the restore process shouldn't be able to see the drive.

Reply

Answer 4

Mar 25, 2014 12:47 PM in response to John.Orban.who.lives.in.USA

More oftern than not this type of behavior is casued by newer users Installing incompatible Ram, Instead of using Crucial ram from http://www.crucial.com

Or from Other World Computing http://www.macsales.com

The second reason for this type of behavior is from newer users thinking they need a Virus Protection, or Malware Prootection from some 3rd party that absolutly reeks havoc with Apple Computers. That being said if you have anything like Mackeeper, Symantic Products, Like Norton AntiVirus. McAfee, Trend Micro, or any of the hundred of Softwares that are available they DO NOT WORK AND CAUSE MORE PROBLEMS THEN THEY ARE WORTH,YOUR MAC NEEDS NOTHING.

If you have anything mentioned above go to there site and UnInstall there products.

And another little tid bit if you have more than one installed it really reeks havoc on your Mac.

Hope this Helps.

Don

Reply

Answer 5

andyBall_uk

Level 7

20,516 points

Mar 25, 2014 2:21 PM in response to John.Orban.who.lives.in.USA

If still greyed, then yes, presumably it won't be a suitable destination. You may be able to erase/partition it, but.

Reply

Answer 6

Mar 28, 2014 6:37 AM in response to John.Orban.who.lives.in.USA

Update:

Well, knowing I had to wait 48 hours for Dispatch to set up an on-site visit, and being the impatient type, I figured I'd try again to see if I could get this going.

So the partition was trashed. One of the times I called Apple Support they suggested I "Erase" the partition and reinstall the OS. I routinely clone hundreds of laptops each summer for the school where I work. What I normally do is simply create a new partition rather than erase the existing one. (This, by the way, is the way I did the very first reinstall of Mavericks when I first began experiencing the kernel panics.)

So - Disk Utility - create new partition - reinstall OS. Yep, that worked. Got the iMac back. No kernel panics so far - no restarts - going on two days.

By the way, Dispatch never called. BUT - to the credit of the last support rep I spoke with, she's on the case. She was going to call them for me yesterday but I told her to hold off a bit until I could verify last night that the iMac was still working OK. I was connected to it from work via screen sharing but about one hour later the connection was lost. I though it might have frozen like it did before. But when I got home it was working just fine.

I tried connecting to it this morning from work but can't. But that could be from any number of reasons I suppose.

The big issue is that, so far, I have not installed Google Chrome. One of the techs a couple of phone calls back helped find a .plist file that she felt was triggering the restarts. I'm a web developer and not being able to test websites I'm developing on Chrome, which controls 35% of the browser market - and growing - is just plain foolishness.

So...I'm going to install it tonight and look for that .plist file and change the permissions to "Everyone" access.

If Google Chrome is the culprit I've got to get it working.

To be continued...

Reply

Answer 7

Mar 29, 2014 10:51 AM in response to John.Orban.who.lives.in.USA

Don't you just hate it when you have to do all the troubleshooting yourself?

I installed Google Chrome and, immediately, started getting the error message of trying to access

com.apple.coreservices.launchservices.plist. Interestingly enough that file does not exist. It is not hidden either.

In a post I read on Google's site someone recommended using Chrome Canary. I installed it and the error messages went away.

Unfortunately, the kernel panics did not.

This morning, after two days of kernel panic free use of my iMac, they started up again.

One at 6:32 (EST) this morning 3/29/13 and one at 12:47PM (EST).

I'm starting to think there is a major flaw in Mavericks. I THINK I can go back to Mountain Lion since this iMac came out before Mavericks was issued. I think that's the next thing I have to try. In fact, I think I'm going to do that next.

Although...you know...as I think about it...why the heck should I have to do that? As is typically the case, I seem to be the only human being on Planet Earth with this problem so wouldn't you THINK that would indicate a hardware issue? Or are routine kernel panics and restarts the norm? The only minor annoyance is having to reset the default iTunes Media location since I store that on my network NAS. I used to have to reset my Dropbox account, but my NAS has a feature that will auto synch with Dropbox, so I don't even need to run Dropbox on my iMac at this point.

On the other hand...(just thinking out loud)...if I DO install Mountain Lion and the kernel panics continue, then I'd think that was more an indication of hardware problems? If they stop, then Mavericks is tainted. To whom do I submit my invoice for time toubleshooting this lunacy?

To be continued...

Reply

Answer 8

Mar 29, 2014 1:02 PM in response to John.Orban.who.lives.in.USA

Well, I've installed Mountain Lion and am running Chrome, regular version, with no error messages.

We'll see what happens over the next couple of days. So far so good!

Reply

Answer 9

Mar 29, 2014 7:33 PM in response to John.Orban.who.lives.in.USA

Seems that going "back" to Mountain Lion is fraught with it's own problems. I can't get the latest versions of iWorks, One Note is not available for Mountain Lion, the App Store keeps telling me to log in to download updates when I'm already logged in. This is really turning into a quagmire!

Reply

Answer 10

Mar 30, 2014 10:42 AM in response to John.Orban.who.lives.in.USA

Back to Mavericks. I need the functionality Mavericks gives and the apps it supports.

However, I did not install Google Chrome - either version.

However, I did install Creative Cloud and installed a bunch of Adobe apps before I went to bed last night. @ 7:25 this morning - another kernel panic. (BTW - have NOTHING plugged into the iMac except the Apple keyboard)

I don't know how Creative Cloud works (desktop app). It always lives in the status bar at the top right of the screen, so it was on, after installing a couple of gigabytes of apps just before I went to bed. I was going to wait until it finished and shut it down. I'll see if turning off Creative Cloud, except to authorize apps will stop that kernel panic.

But something is just not right. I've disconnected external devices. I've reinstalled the OS multiple times. I didn't leave Mountain Lion on the iMac long enough but would be willing to bet the kernel panics would have stopped. I'm beginning to think something is seriously wrong with Mavericks.

I know a guy pretty high up in engineering at Apple. I'm going to email him today with my dilemma and see what he thinks. Maybe there is a big update about to be released. But I'm afraid AppleCare is not going to be much help. As long as the iMac is "working", as far as they are concerned, the issue is solved.

Reply

Answer 11

Aslan87

Level 1

0 points

Apr 2, 2014 6:41 AM in response to John.Orban.who.lives.in.USA

I'm having a very similar issue. My kernal panics seem to be happening aver 2 to 4 hours. I looked in the logs, and have the same "Chrome cannot access stuff" line just before a kernel panic. My system specs are quite similar to yours, except i have a 500g ssd instead of a 1t sshdd.

I have uninstalled chrome and haven't had a kernel panic since yesterday at (1st one that day 10:56) 2nd one 1:22pm.

I too have been talking with apple about this issue. They did a clean reinstall and kept it for a couple days for testing and it cleared. I got it back and imidiatly reinstalled chrome not even considering it could have been the problem. I also have adobe cc, and haven't yet uninstalled it. So we'll see. I'll report back in a day or so.

So, you were still having panics with Chrome uninstalled and Adobe CC installed i see. I may not be done just yet.

Reply

Answer 12

Aslan87

Level 1

0 points

Apr 3, 2014 6:27 AM in response to Aslan87

It's not google chrome btw

Reply

Answer 13

Apr 3, 2014 6:45 AM in response to John.Orban.who.lives.in.USA

Thanks for the input. I should have updated this post.

Whenever I did an OS re-install (and I have done too many to count at this point), everything runs well for a while. That can be a day to a couple of days.

On 3/29 I did another OS re-install. I did not install Chrome or Creative Cloud. No kernel panic. On 3/30 I installed Chrome and got a kernel panic and reboot within 24 hours. I passed that info along to Apple and they sent me a program to run the next time I had a KP. I used this before when I was running servers at work. It sort of dumps every log file on the computer and sends it to Apple. Of course 24 hours and no KP.

I then installed Creative Cloud and, within a couple of hours got another kernel panic. I'm not saying Creative Cloud is the culprit, I'm just pretty confident I can trigger a KP with either Chrome or CC.

I'm getting more and more convinced this has something to do with Mavericks and this particular version of the iMac. I've been running Mavericks on my 2009 MacPro @ work almost from the day it was available with absolutely (as far as I can tell) any problems. I'm running Mavericks on my 2012 Macbook Air with no problems.

Anyhow, I'm waiting to hear back from Apple.

Reply

Answer 14

Aslan87

Level 1

0 points

Apr 3, 2014 7:35 AM in response to John.Orban.who.lives.in.USA

This is very disconcerting. I also have another iMac 2010 with mavericks and roughly the same software installed ,except i have adobe cc installed on this one and CS5 on the other one. I never even knew what a kernel panic was untill I used this iMac. I've looked in the adobe forums, and they said that kernel panics are likely caused by low level drivers or faulty hardware.

My most recent kernel panic: Today at 8:17am

Anonymous UUID:       F0D4E96F-7D4D-3DE2-51FF-4330B072E79F

Thu Apr  3 08:17:15 2014
panic(cpu 0 caller 0xffffff801c6dbe2e): Kernel trap at 0xffffff801c6525b7, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000000010619c000, CR3: 0x0000000038553045, CR4: 0x00000000001606e0
RAX: 0xdeadbeefdeadbeef, RBX: 0xffffff80599b0260, RCX: 0xffffff8067160510, RDX: 0xc0ffee12880ec6f8
RSP: 0xffffff83abb8bd80, RBP: 0xffffff83abb8bdd0, RSI: 0xffffff8060cc8708, RDI: 0xffffff80671604d0
R8:  0x0000000000000001, R9:  0xffffff83abb8bf20, R10: 0x0000610000171280, R11: 0x0000000000000206
R12: 0xffffff80671604d0, R13: 0xffffff801c61d580, R14: 0xffffff80599b0260, R15: 0xffffff80671604d0
RFL: 0x0000000000010206, RIP: 0xffffff801c6525b7, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x000000010619c000, Error code: 0x0000000000000000, Fault CPU: 0x0


Backtrace (CPU 0), Frame : Return Address
0xffffff839a307c50 : 0xffffff801c622fa9 
0xffffff839a307cd0 : 0xffffff801c6dbe2e 
0xffffff839a307ea0 : 0xffffff801c6f3326 
0xffffff839a307ec0 : 0xffffff801c6525b7 
0xffffff83abb8bdd0 : 0xffffff801c651df9 
0xffffff83abb8bed0 : 0xffffff801c64d7f2 
0xffffff83abb8bef0 : 0xffffff801c61fbc3 
0xffffff83abb8bf40 : 0xffffff801c61d5c8 
0xffffff83abb8bf70 : 0xffffff801c6c976d 
0xffffff83abb8bfb0 : 0xffffff801c6f3b46 


BSD process name corresponding to current thread: blender


Mac OS version:
13C64


Kernel version:
Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64
Kernel UUID: 9FEA8EDC-B629-3ED2-A1A3-6521A1885953
Kernel slide:     0x000000001c400000
Kernel text base: 0xffffff801c600000
System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)


System uptime in nanoseconds: 51837122418202
last loaded kext at 51141322536745: com.apple.driver.AppleIntelMCEReporter          104 (addr 0xffffff7f9ed05000, size 49152)
last unloaded kext at 51228210690676: com.apple.driver.AppleIntelMCEReporter          104 (addr 0xffffff7f9ed05000, size 32768)
loaded kexts:
com.nvidia.CUDA          1.1.0
com.apple.filesystems.afpfs          11.1
com.apple.nke.asp-tcp          8.0.1
com.apple.filesystems.smbfs          2.0.1
com.apple.driver.AppleBluetoothMultitouch          80.14
com.apple.driver.AudioAUUC          1.60
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.filesystems.autofs          3.0
com.apple.iokit.IOBluetoothSerialManager          4.2.3f10
com.apple.driver.AppleMikeyHIDDriver          124
com.apple.driver.AppleMikeyDriver          2.6.0f1
com.apple.driver.AGPM          100.14.15
com.apple.driver.ApplePlatformEnabler          2.0.9d1
com.apple.driver.X86PlatformShim          1.0.0
com.apple.driver.AppleHDA          2.6.0f1
com.apple.driver.AppleUpstreamUserClient          3.5.13
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.GeForce          8.2.4
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.3f10
com.apple.driver.AppleHWAccess          1
com.apple.driver.AppleIntelHD5000Graphics          8.2.4
com.apple.driver.AppleSMCLMU          2.0.4d1
com.apple.driver.AppleLPC          1.7.0
com.apple.driver.AppleThunderboltIP          1.1.2
com.apple.driver.AppleIntelFramebufferAzul          8.2.4
com.apple.driver.AppleBacklight          170.3.5
com.apple.driver.AppleMCCSControl          1.1.12
com.apple.iokit.SCSITaskUserClient          3.6.6
com.apple.driver.AppleUSBODD          3.4.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          35
com.apple.driver.AppleUSBHub          666.4.0
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.5.1
com.apple.driver.AppleSDXC          1.5.2
com.apple.iokit.AppleBCM5701Ethernet          3.8.1b2
com.apple.driver.AirPort.Brcm4360          831.21.63
com.apple.driver.AppleAHCIPort          3.0.0
com.apple.driver.AppleUSBXHCI          670.4.0
com.apple.driver.AppleACPIButtons          2.0
com.apple.driver.AppleRTC          2.0
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          2.1
com.apple.driver.AppleACPIEC          2.0
com.apple.driver.AppleAPIC          1.7
com.apple.nke.applicationfirewall          153
com.apple.security.quarantine          3
com.apple.security.SecureRemotePassword          1.0
com.apple.driver.IOBluetoothHIDDriver          4.2.3f10
com.apple.driver.AppleMultitouchDriver          245.13
com.apple.kext.triggers          1.0
com.apple.iokit.IOSerialFamily          10.0.7
com.apple.driver.DspFuncLib          2.6.0f1
com.apple.vecLib.kext          1.0.0
com.apple.iokit.IOAudioFamily          1.9.5fc2
com.apple.kext.OSvKernDSPLib          1.14
com.apple.nvidia.driver.NVDAGK100Hal          8.2.4
com.apple.iokit.IOAcceleratorFamily          98.14
com.apple.nvidia.driver.NVDAResman          8.2.4
com.apple.iokit.IOBluetoothFamily          4.2.3f10
com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.3f10
com.apple.iokit.IOSurface          91
com.apple.driver.AppleHDAController          2.6.0f1
com.apple.iokit.IOHDAFamily          2.6.0f1
com.apple.driver.AppleSMBusPCI          1.0.12d1
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.driver.AppleSMC          3.1.8
com.apple.driver.IOPlatformPluginFamily          5.7.0d10
com.apple.driver.AppleThunderboltEDMSink          2.1.3
com.apple.AppleGraphicsDeviceControl          3.4.35
com.apple.iokit.IOAcceleratorFamily2          98.14
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IONDRVSupport          2.4.1
com.apple.driver.AppleSMBusController          1.0.11d1
com.apple.iokit.IOGraphicsFamily          2.4.1
com.apple.driver.AppleUSBHIDKeyboard          170.15
com.apple.driver.AppleHIDKeyboard          170.15
com.apple.iokit.IOUSBHIDDriver          660.4.0
com.apple.driver.AppleUSBMergeNub          650.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.6
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOUSBMassStorageClass          3.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.6
com.apple.driver.AppleUSBComposite          656.4.1
com.apple.driver.AppleThunderboltDPInAdapter          3.1.7
com.apple.driver.AppleThunderboltDPOutAdapter          3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily          3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter          1.4.5
com.apple.iokit.IOUSBUserClient          660.4.2
com.apple.driver.AppleThunderboltNHI          2.0.1
com.apple.iokit.IOThunderboltFamily          3.2.7
com.apple.iokit.IOEthernetAVBController          1.0.3b4
com.apple.iokit.IO80211Family          630.35
com.apple.driver.mDNSOffloadUserClient          1.0.1b5
com.apple.iokit.IONetworkingFamily          3.2
com.apple.iokit.IOAHCIFamily          2.6.5
com.apple.iokit.IOUSBFamily          675.4.0
com.apple.driver.AppleEFINVRAM          2.0
com.apple.driver.AppleEFIRuntime          2.0
com.apple.iokit.IOHIDFamily          2.0.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          278.11
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.AppleKeyStore          2
com.apple.driver.DiskImages          371.1
com.apple.iokit.IOStorageFamily          1.9
com.apple.iokit.IOReportFamily          23
com.apple.driver.AppleFDEKeyStore          28.30
com.apple.driver.AppleACPIPlatform          2.0
com.apple.iokit.IOPCIFamily          2.9
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.pthread          1
com.apple.kec.corecrypto          1.0


System Profile:
Model: iMac14,2, BootROM IM142.0118.B00, 4 processors, Intel Core i7, 3.5 GHz, 32 GB, SMC 2.15f2
Graphics: NVIDIA GeForce GTX 780M, NVIDIA GeForce GTX 780M, PCIe, 4096 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738454655352D474E4C2D46
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738454655352D474E4C2D46
Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738454655352D474E4C2D46
Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738454655352D474E4C2D46
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x111), Broadcom BCM43xx 1.0 (6.30.223.154.63)
Bluetooth: Version 4.2.3f10 13477, 3 services, 23 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
USB Device: FaceTime HD Camera (Built-in)
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple USB SuperDrive
USB Device: Keyboard Hub
USB Device: Apple Keyboard
Thunderbolt Bus: iMac, Apple Inc., 23.10

Reply

Answer 15

Apr 3, 2014 7:52 AM in response to Aslan87

Not to be too much of a PITA, but don't post the whole output like this. I sure as heck can't read it and it seems to me the console log is as important or more important than the kernel panic report. All that junk at the top (how do you like that "tech-talk", is the values of the various registers in the CPU, I think. You need to be a rocket scientist to make any sense of that. Save it for tech support.

The console log is going to tell you what was going on prior to the KP, and even then, I can't make head nor tails except I keep seeing "Google Helper" trying to access a file, being denied access, and that seems to put a strain on the CPU.

I just checked my MacPro console log and see the same error message popping up - but it's not crashing my iMac.

I'd be curious to know if bad RAM can turn up OK in the Diagnostics check but still be causing this problem? Maybe the Diagnostics test isn't thorough enough. I'm going to search for a RAM check program, something that will really wring out the RAM, and run that tonight. I don't know how many folks buy iMacs with 32GB or RAM, so maybe it's a problem at the higher end since the other thread seems to be isolated to 32GB iMacs.

Reply