01-11-2007, 09:37 AM

Heh, it just seems to do this randomly. It's like instead of having the big BSOD(black screen of death), it just goes ahead with the kernel panic and shuts down.


Please help me! I have tried the following:

?-Resseting the PRAM
?-Resetting the PMU
?-Repair Permissions
?- Repairing Disk

It didn't work.

01-11-2007, 10:32 AM

Follow the steps and suggestions here:

http://docs.info.apple.com/article.html?artnum=25392

and here:

http://docs.info.apple.com/article.html?artnum=106805

01-11-2007, 06:23 PM

Done all that. Still crashes. Crash log:


Unresolved kernel trap(cpu 0): 0x400 - Inst access DAR=0x00000000003FD000 PC=0x0000000000000000
Latest crash info for cpu 0:
Exception state (sv=0x32F4C280)
PC=0x00000000; MSR=0x40009030; DAR=0x003FD000; DSISR=0x40000000; LR=0x0003C884; R1=0x1CF4BE10; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x02EA8F9C 0x000A9314
Proceeding back via exception chain:
Exception state (sv=0x32F4C280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x32F77A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0004): 0x400 - Inst access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x32F4C280)
PC=0x00000000; MSR=0x40009030; DAR=0x003FD000; DSISR=0x40000000; LR=0x0003C884; R1=0x1CF4BE10; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x02EA8F9C 0x000A9314
Exception state (sv=0x32F77A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
Model: PowerBook6,4, BootROM 4.8.3f1, 1 processors, PowerPC G4 (1.1), 1.33 GHz, 1.25 GB
Graphics: GeForce FX Go5200, GeForce FX Go5200, AGP, 64 MB
Memory Module: DIMM0/BUILT-IN, 256 MB, built-in, built-in
Memory Module: DIMM1/J31, 1 GB, DDR SDRAM, PC2700U-25330
AirPort: AirPort Extreme, 405.1 (3.90.34.0.p18)
Modem: Jump, , V.92, Version 1.0,
Bluetooth: Version 1.7.8f2, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Parallel ATA Device: MATSHITADVD-R UJ-825, 781.28 MB
Parallel ATA Device: ST910021A, 93.16 GB
USB Device: Bluetooth HCI, , Up to 12 Mb/sec, 500 mA

01-11-2007, 06:26 PM

You did a reinstall and it is still giving kernel panics and crashing?
From the first link:

Originally Posted by Apple

Reinstall Mac OS X

If an issue persists, reinstalling Mac OS X should resolve it.


For Mac OS X 10.2, 10.3, 10.4 or later, perform an Archive and Install installation.
Tip: You won't be able to return to your previous System following an Archive and Install installation, but you can select the "Preserve existing Users & Network Settings" option to retain your original applications and settings, documents, and user accounts.

For Mac OS X 10.1.5 or earlier, reinstallation of Mac OS X requires erasing the Mac OS X volume. This is described in the next paragraph.
If the issue persists, back up any necessary data, start up from a Mac OS X Install or Restore CD, erase the Mac OS X volume, reinstall Mac OS X and restore any additional Apple software.

Reinstall additional software one item at a time, restarting the computer after each install. For best results, use the computer for several hours after each installation to determine if that particular software contributed to the issue. Reinstalling everything at once without noting when the issue returned may lead to a need to repeat this process.

Warning: Choosing Erase and Install will completely erase the contents of the chosen volume before installing Mac OS X. Be sure to back up your files before continuing.

If these suggestions do not resolve your issue, contact AppleCare or your nearest Apple Authorized Service Provider for assistance.

If it is still giving panics, then the only thing I can suggest is taking it to Apple to have them look at/service it.

01-11-2007, 07:38 PM

¥eah, I've done that.