0

Score

Avatar
Chavira
1

Asked

My iMac can't boot any system, kernel panic?

History

Hi, first of all thanks for any help that you can provide me.

My computer can't boot the system, at the first time start to can't find the system and show me a folder with a question mark, so I try to reinstall the system (Lion) and can't boot from the CD or USB, just show up the apple symbol but never more than this. So I proceed to change the HDD for a new one and make a special partition with a bootable "OSX Lion Install" saved inside, and have the same problem.

But then in the apple logo screen start to appear the despicable screen of death (mac version) with the restart message or sometimes just the apple and a kernel panic code in the back, exactly this one:

Block Image

''''panic(cpu 1 caller 0xffffff80002c2cb5): "Machine Check at 0xffffff80002bcb60, registers:\n" "CR0: 0x000000008001003b, CR2: 0x000000010f66c370, CR3: 0x0000000000100000, CR4: 0x0000000000000660\n" "RAX: 0x000000009cc01065, RBX: 0x7fff

Debugger called: <panic>

Backtrace (CPU 1), Frame : Return Address

0xffffff8040c74ec0 : 0xffffff8000220702

0xffffff8040c74f40 : 0xffffff80002c2cb5

0xffffff8040c750a0 : 0xffffff80002d840f

0xffffff8045913b10 : 0xffffff7f816cef84

0xffffff8045913b50 : 0xffffff7f816c8552

0xffffff8045913c30 : 0xffffff7f816ca371

0xffffff8045913ce0 : 0xffffff80002c41f4

0xffffff8045913d00 : 0xffffff800022d2b5

0xffffff8045913d40 : 0xffffff800022dfa0

0xffffff8045913da0 : 0xffffff800022f353

0xffffff8045913e00 : 0xffffff800021e592

0xffffff8045913e20 : 0xffffff7f80bdd110

0xffffff8045913e60 : 0xffffff7f80bdd30e

0xffffff8045913e80 : 0xffffff7f80bd5d4f

0xffffff8045913eb0 : 0xffffff800062695b

0xffffff8045913f30 : 0xffffff8000626fb9

0xffffff8045913f70 : 0xffffff8000625b9f

0xffffff8045913fb0 : 0xffffff8000820057

Kernel Extensions in backtrace:

com.apple.driver.AppleIntelCPUPowerManagement(166.0)[7FCD8D98-D972-3973-A13B-DC551C536EE6]@0xffffff7f816c6000->0xffffff7f816effff

com.apple.iokit.AppleYukon2(3.2.2b1)[2DF7ECA3-F451-3F61-BF3D-6C5165E7DEFB]@0xffffff7f80bbb000->0xffffff7f80be6fff

dependency: com.apple.iokit.IONetworkingFamily(2.0)[59A00F6B-3710-3E07-9921-70C45782FF8C]@0xffffff7f80b5c000

dependency: com.apple.iokit.IOPCIFamily(2.6.5)[95ABB490-3AB5-3D5E-9C21-67089A9AE6A1]@0xffffff7f80821000

BSD process name corresponding to current thread: kernel_task

Boot args: root-dmg=file:///BaseSystem.dmg

Mac OS version:

Not yet set

Kernel version:

Darwin Kernel Version 11.0.0: Sat Jun 18 12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64

Kernel UUID: 24CC17EB-30B0-3F6C-907F-1A9B2057AF78

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

System uptime in nanoseconds: 2914537178''

------------------------------------------

After this I change the RAM memory and use the "Apple Service Diagnostic Disks" (ASD Dual Boot 3S123), for make a test of all the computer and the computer pass all the test without a problem, so the Apple Service Diagnostic Disks says the hardware haven't problem.

So I think this is a software problem. After this I try to upgrade the EFI/Firmware with the "FirmwareRestorationCD1.3" and follow all the instructions for do that, but the computer never show up a blinking light or a sound, like the manual say, just delay the start screen, but never read the disk. So I can't upgrade the Firmware.

After this I try all the start up combinations, delete the NV RAM, start up in safe boot mode, in verbose mode and nothing happen. I try to start in single-user mode and show up the kernel panic message again:

Block Image

efiboot loaded from device" Acpi(PNP0A03,0)/Pci(1FI2)/SATA(0,0)/HD(Part2,Sig00000000)

boot file path: \boot.efi

..Loading Kernel cache file '\kernelcache'…

……………

root device uuid is 'EFCE0516-346E-3C93-AF07-630CB2C3AED1'

_

panic(cpu 0 caller 0xffffff80002c268d): Kernel trap at 0xffffff80002bd45f, type 14=page fault, registers:

CR0: 0x0000000080010013, CR2: 0x0000000000000018, CR3: 0x0000000000100000, CR4: 0x0000000000000060

RAX: 0x0000000000000000, RBX: 0x0000000000000403, RCX: 0x0000000000000001, RDX: 0xffffff80008b0dba

RSP: 0xffffff800081bd50, RBP: 0xffffff800081bda0, RSI: 0x000000000000013a, RDI: 0x0000000000000000

R8: 0x0000000000000010, R9: 0xffffff800081bcf8, R10: 0x00000000000fffcf, R11: 0x000000000000000b

R12: 0xffffff800081bf10, R13: 0x0000000000018e0f, R14: 0x0000000000000000, R15: 0x0000000000000000

RFL: 0x0000000000010056, RIP: 0xffffff80002bd45f, CS: 0x0000000000000008, SS: 0x000000000000000

CR2: 0x0000000000000018, Error code: 0x0000000000000000, Faulting CPU: 0x0

Debugger called: <panic>

Backtrace (CPU 0), Frame : Return Address

0xffffff800081ba10 : 0xffffff8000220702

0xffffff800081ba90 : 0xffffff80002c268d

0xffffff800081bc30 : 0xffffff80002d7a3d

0xffffff800081bc50 : 0xffffff80002bd45f

0xffffff800081bda0 : 0xffffff80002c2b20

0xffffff800081bf00 : 0xffffff80002d840f

0xffffff800010beb0 : 0xffffff8000295c27

0xffffff800010bf00 : 0xffffff80006f7838

0xffffff800010bf40 : 0xffffff80006f6a66

0xffffff800010bf70 : 0xffffff80006f5cfb

0xffffff800010bfa0 : 0xffffff80002c6532

0xffffff800010bfc0 : 0xffffff80002b400d

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

0xffffff800010bff0 : 0xffffff80002b4359

Backtrace continues…

can\t perform kext scan: no kext summary

BSD process name corresponding to current thread: Unknown

Boot args: root-dmg=file:///BaseSystem.dmg -v

System uptime in nanoseconds: 0-907F-1A9B2057AF78 PDT 2011; root:xnu-1699.22.73-1/RELEASE_X86_64

---------------------------------------------

I try with a different system installation and with the original one come with the computer and have the same problem. I start to think this is a Logic Board exactly the CPU problem, but If someone have another idea can help me I really will appreciate it...

by the way, sorry for the bad English, is not my native language.

Thanks for your time : )

Edited by: machead3 and oldturkey03 ( )

Post Answer

0

Score

Avatar
Dan
45.7k

Answered

Accepted Answer

PermalinkHistory

I would disconnect the internal HD and with a bootable external or CD/DVD see what happens.

Does it boot up cleanly? If so the boot files are corrupted on the HD and you'll need to delete the partition and reformat the HD.

If you can't get it to boot the EEPROM where the firmware is loaded on has a problem. If you have access to the correct chip clip and a burner and access to the firmware file image you could try re-burning the firmware. Otherwise you'll need a new EEPROM or exchange out the logic board.

I think the firmware is corrupted, so I try to re-install it, but cant, in the apple web page have some instructions, something about hold the power button for some seconds and I will see a blinking light or a sound, but this never happend... So if you know another way to re-install the firmware, that will be great

Chavira,

I have try to boot in diferent forms, USB, DVD, direct in the HD and diferents OSX but always the same problem, stop in the white screen with the apple logo, and sometimes the kernel panic message appear, like the image in the top of this page...

Chavira,

What Apple (and other manufactures) do here is burn the chip before they install it (pre-program it). If you have the correct gear you can do the same thing. The only trick is getting the raw image file. The EFI firmware installer has it encrypted within it so you can't directly extract it from it. People have extracted the image directly from a good working EEPROM and then re-burn that to the corrupted EEPROM or the replacement EEPROM they then install. The only issue here is you need to get the exact same model system to get the image from and you really need to alter the imbedded serial number (as you don't want to be a direct clone). Otherwise its time for a new logic board.

Dan,

Have you tried going to an Apple Store to see if they can help you (without replacing the logic bd)?

Dan,

0

Score

Avatar
machead3
70.1k

Answered

PermalinkHistory

Sometimes the AHT must be run in advanced mode 2 or 3x to find a problem - the problem might t only occur when the unit is hot or stressed.

Could be your new HD is too fast for the old unit. It has a 3GB/s SATA speed - new drives are twice that - many here have found problems where drives "claimed" to be backward compatible or automagic detecting were found not to be compatilbe or needed "manual" jumpering to work.

If this Answer is helpful please remember to return and mark it Accepted.

I'm using the Apple Service Diagnostic Disc, and I run a lot of times, somethimes the system frozen, and i need restart it. About the HHD I already set the jumper for 1.5/3GB/s and still have the problem, but thank you for your help

Chavira,

0

Score

Avatar
M Taylor
153

Answered

PermalinkHistory

I would say the MLB is heading out the door. In my experience when a iMac cannot boot into any system internal or external it usually has to do with the MLB. HDD speed should make no difference.

I see, but why the Apple Service Diagnostic, cannot find the problem. And if the MLB have the problem, why this happened?

Chavira,

If you look in the crash logs you may find why the system froze/crashed. Because you "crashed out" of AHT it never gets to report what it finds. Not every repair is a DIY repair! Looking at your timeline and current problems replacing the logic board (if you feel it's economically feasible) would be my solution.

machead3,

Add Your Answer

View Statistics:

Today: 0

This Week: 8

This Month: 51

All Time: 710