kernel panic problem

Question

Level 1

9 points

kernel panic problem

Hello,

I have a 2008 iMac running on Mountain Lion. Recently I had a problem with Kernel, but when I restarted the computer it seemed to be right. I was able to start the OS and work without problems that single time. I checked the hard disk and it was ok, and then the permissions and I fixed some problems with the disk utility. Then I switched off the Mac and I haven´t been able to start it since that time.

I tried to reboot the pram, start in safe mode, single mode, from cd and from the recovery disk it doesn´t work. I have even tried to start from an USB as a recovery MacOS diskbut it also doesn´t work.

When I start the Mac i get to see the Apple logo, and then three vertical black lines cover part of the screen and the computer reboots. Sometimes i get a message over the white screen with the Apple logo:

panic(cpu 0 caller 0xffffff800415fc5): "process 1exec of /sbin/launchd failed, errno 8"0

Debuger called: <panic>

Backtrace (CPU 0), Frame : Return Address

0xffffff807d22be10 : 0xffffff8003e1d626

0xffffff807d22be80 : 0xffffff8004155fc5

0xffffff807d22bef0 : 0xffffff80041390f7

0xffffff807d22bf10 : 0xffffff8004168dc1

0xffffff807d22bf50 : 0xffffff8003e1b6e1

0xffffff807d22bf90 : 0xffffff8003eb8c63

0xffffff807d22bfb0 : 0xffffff8003ece14c

BSD process name corresponding to current thread: init

Mac OS version:

Not yet set

Kernel version:

Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; rot:xnu-2050.24.15≈1/RELEASE_X6

KErnel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36

Kernel slide: 0x0000000003c00000

Kernel text base: 0xffffff8003e00000

System model name: iMac8,1 (Mac-F227BEC8)

system uptime in nanoseconds: 812065858

I don´t knowif this is a hardware or a software problem. The thing is that I´m not able to stratup the OS by any way

I woud be gratefull for any help.

iMac (24-inch Early 2008), OS X Mountain Lion (10.8.1)

Posted on Sep 6, 2013 1:13 AM

Reply

Answer 1

baltwo

Level 9

62,386 points

Sep 6, 2013 12:06 PM in response to sergiofromm

Post the entire panic report.

Reply

Answer 2

Linc Davis

Level 10

209,739 points

Sep 6, 2013 1:33 PM in response to sergiofromm

Back up all data, then reinstall the OS. You don't need to erase the startup volume, and you won't need your backup unless something goes wrong. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.

If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it.

Reply

Answer 3

baltwo

Level 9

62,386 points

Sep 6, 2013 1:54 PM in response to Linc Davis

I don't recommend doing anything until the KP's posted.

Reply

Answer 4

sergiofromm Author

Level 1

9 points

Sep 9, 2013 6:27 AM in response to baltwo

That´s the entire message it shows. It ends with the nanoseconds and then reboots automaticaly. I´ll check it anyway, but I think that´s all.

Reply

Answer 5

baltwo

Level 9

62,386 points

Sep 9, 2013 12:21 PM in response to sergiofromm

I've never seen one so truncated. Peruse these forums for kernel panic and you'll note what a normal one looks like. Anyway, boot into safe mode (restart holding down SHIFT key). If no KP, then most likely some 3rd-party software item is the culprit. If KP, then most likely hardware related. Run the Apple Hardware Test suite, extended tests at least twice, followed by Rember. See

OS X About kernel panics,
Technical Note TN2063: Understanding and Debugging Kernel Panics,
Mac OS X Kernel Panic FAQ,
Resolving Kernel Panics,
How to troubleshoot a kernel panic, and
Tutorial: Avoiding and eliminating Kernel panics for more details.

Reply

Answer 6

Sep 9, 2013 3:52 PM in response to sergiofromm

"process 1 exec of /sbin/launchd failed, errno 8"

means that the system, while starting up, was unable to launch the primary program used to launch everything else. That program is /sbin/launchd (a hidden file normally not touched or seen by a user.) The error code 8 is found in the file /usr/include/sys/errno.h

#define

ENOEXEC

8

/* Exec format error */

which means your installation is bad. You will have to reinstall the operating system as Linc Davis suggested above. Sorry for the bad news.

Reply

Answer 7

nbar

Level 5

7,037 points

Sep 9, 2013 3:55 PM in response to Brian Bechtel

There is no definitive conclusion one can draw from this KP report. The drivers would be loaded before launchd at boot. There are no drivers even listed. I am still skeptical that this is the whole kernel panic report.

Reply

Answer 8

sergiofromm Author

Level 1

9 points

Sep 10, 2013 12:21 AM in response to sergiofromm

Sorry for the low quality of the photo. I have no way to cappture the screen and I made it with a phone. This is the hole KP. Since I´m not able to start in any mode, the only thing I can try is to use another mac conected by firewire to try to identify if the problem is caused by hardware.

Thanks for your help 🙂

Reply

Answer 9

nbar

Level 5

7,037 points

Sep 10, 2013 12:58 AM in response to sergiofromm

Use target disk mode (firewire) to backup your data. Can you subsequently start your machine from internet recovery? What happens?

Here is a better image of what was posted, to other members:

Reply

Answer 10

aqua80

Level 1

0 points

Jan 27, 2014 3:06 PM in response to sergiofromm

How did this was resolved ?

I have exactly the same problem on my imac mid 2007... after a restoration from time machine with an external drive on firewire, the computer doesn't start anymore... even with shift or command + r keys....

the restoration went good and then there was a message to restart the computer, which resulted in this screen...

don't know what to do !

mac os x install disc #1 is in the cd-rom and the backup external drive is in the cd drive...

thanks !

Reply

Answer 11

Jun 19, 2015 11:21 AM in response to aqua80

I'm now in the same position as@aqau80 above, stuck in a loop where I cant restart in recovery pattern. I did manage to start up in single user mode but nothing really happened, got a kernal, a load of text then it restarted and threw the same error again. Occasionly get a progress bar but gets stuck at 50%.

This appears to have happened from a Yosemite update but am now stuck (I don't have access to another mac, although I have managed to create a new Yosemite Install on a USB disk, if only I could start up from it).

Is there any further guidance, @aqua80, were you able to resolve your issue?

Reply