Benches macOS

8

Kernel Panic

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I have a powermac G4 MDD and I get a "Restart your computer ...." message from time to time. I have reinstalled the original OS 10.2.1 from a completely erased HD and I still get the message. I have ran Techtool Pro version 4 and it gives everything a good bill of health. After the most recent crash I copied the panic.log as you can see. Also, I have reset the PMU with everything unplugged and have tried a clean install using OS 10.3.x and even the latest Leapord, all retail upgrade DVD's. Sometimes the installs go fine w/o errors and at times I get errors during the install or optimization.

Any thoughts as to what is going on?

Thanks

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

Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x00000018 PC=0x000710e0

Latest crash info for cpu 1:

Exception state (sv=0x1F6B2C80)

PC=0x000710E0; MSR=0x00009030; DAR=0x00000018; DSISR=0x40000000; LR=0x0007

124C; R1=0x18183B00; XCP=0x0000000C (0x300 - Data access)

Backtrace:

0x00000000 0x0007124C 0x00063704 0x000685DC 0x0001E628 0x0001E814 0x000

24B30 0x00024CA8

0x0001F344

Proceeding back via exception chain:

Exception state (sv=0x1F6B2C80)

previously dumped as "Latest" state. skipping...

Exception state (sv=0x27C2C500)

PC=0x90074328; MSR=0x0200F030; DAR=0xE1D8F000; DSISR=0x42000000; LR=0x9000

6670; R1=0xBFFFD0C0; XCP=0x00000030 (0xC00 - System call)

Kernel version:

Darwin Kernel Version 6.1:

Fri Sep 6 23:09:31 PDT 2002; root:xnu/xnu-344.2.obj~1/RELEASE_PPC

panic(cpu 1): 0x300 - Data access

Latest stack backtrace for cpu 1:

Backtrace:

0x0008598C 0x00085DBC 0x00028B8C 0x0008F688 0x000926F8

Proceeding back via exception chain:

Exception state (sv=0x1F6B2C80)

PC=0x000710E0; MSR=0x00009030; DAR=0x00000018; DSISR=0x40000000; LR=0x0007124C; R1=0x18183B00; XCP=0x0000000C (0x300 - Data acc

ess)

Backtrace:

0x00000000 0x0007124C 0x00063704 0x000685DC 0x0001E628 0x0001E814 0x00024B30 0x00024CA8

0x0001F344

Exception state (sv=0x27C2C500)

PC=0x90074328; MSR=0x0200F030; DAR=0xE1D8F000; DSISR=0x42000000; LR=0x90006670; R1=0xBFFFD0C0; XCP=0x00000030 (0xC00 - System c

all)

Kernel version:

Darwin Kernel Version 6.1:

Fri Sep 6 23:09:31 PDT 2002; root:xnu/xnu-344.2.obj~1/RELEASE_PPC

8 replies

Sign in or join Beachball Help to reply.

  1. 0

    Thomas Bryant

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi! It looks like a cpu crash to me but I suppose it could also be caused by memory. Since it comes and goes I'd try removing some ram and run it a while since that won't cost you anything to try. Tom

  2. 0

    rwmartin

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Tom,

    Thanks for the quick reply. The unit has 1 Gig of ram and have tried different combinations w/o success. I guess I could buy some new ram since I bought the Powermac used on ebay a couple of months ago and I'm not 100% sure of the ram. I erased the HD again this evening and reinstalled (option install for the first time) OS 10.2.1. The install went flawless. After a couple of restarts I decided to run disk utility, verify permissions. The computer crashed with the same Restart your computer ..... I reviewed the panic log and the first line read: panic (cpu 1): vm
    pageinsert.

    Additional thoughts are welcome.

    Rich

  3. 0

    Thomas Bryant

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi! Yeah is points to a cpu problem. Have you tried a hardware test disc to see what it says? And also have you tried reseating the cpu. Tom

  4. 0

    rwmartin

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Tom,

    By the way, this is a dual processor system, 1.25 Ghz. I have retreated the processors with Artic Silver and have run the Apple hardware test and Techtool 4, they both report no failures. I'm at the point where it will probably be posted on ebay for parts.

    Thanks,

    Rich

  5. 0

    Texas Mac Man

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Kernal panics are usually caused by a hardware problem - frequently RAM or USB devices. When trying to troubleshoot problems, disconnect all external devices except your monitor, kbd & mouse. Do you experience the same problems?

    May be a solution on one of these links.

    Mac OS X Kernel Panic FAQ

    Mac OS X Kernel Panic FAQ

    Resolving Kernel Panics

    12-Step Program to Isolate Freezes and/or Kernel Panics

     Cheers, Tom 😉

  6. 0

    rwmartin

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Greetings,

    Thanks for the advice. I will review the links you've mentioned in your reply. I have eliminated all devices except keybd, mouse and monitor (Planar 20" LCD [VGA connection]). I even tried a different keybd and mouse, still the same crashes ("You need to start your computer...."). I could consistently duplicate the crashes by running disk utility/verify permissions - why? I try opening and closing other apps and I haven't beeen able to get it to crash. Is there hope?

    Regards,

    Rich

  7. 0

    rwmartin

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    After, once again, another PMU reset, I did a clean install of OS X 10.3.5 (erase and install) with the original ATI Radeon 9000 Video Card and it went flawless. I immediately upgraded to 10.4 and it also installed w/o problems. After a few restarts and verify permissions I installed the new ATI Radeon 9800 Mac edition video card and things are working fine.

  8. 0

    philomene251

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    @texas mac man

    Hello, you seem to be quite an expert concerning console logs! would you mind giving an eye to the last post of my topic and tell what yout think about it?

    it's here :

    http://discussions.apple.com/thread.jspa?threadID=1522002&tstart=0

    It would be really kind from you. I feel pretty desperate and helpless with usb/firewire related kernel panics happening again (I've tried everything for a month now)...

    cheers and sorry to rwmartin for interfering on his topic 😉