PowerMac G5 crashes randomly...

[DreamReclaimer]

Hi, new to this site and to Macs in general. This is my wife's mac that she needs to do work for our new home business, so any help would be GREATLY appreciated.

From reading another topic, I know that I need to post the panic.log, so here are the last few times this happened:

*********

Sat Mar 10 20:06:19 2012


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000061 PC=0x0000000000221F34
Latest crash info for cpu 0:
Exception state (sv=0x00D20780)
PC=0x00221F34; MSR=0x00009030; DAR=0x00000061; DSISR=0x40000000; LR=0x00221F18; R1=0x48423760; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00238DCC 0x00222DA0 0x0023D528 0x000FBB4C 0x000E97FC 0x000F5094
0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0xA1B1C1D3
backtrace terminated - frame not mapped or invalid: 0xBFFF8390

Proceeding back via exception chain:
Exception state (sv=0x00D20780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x604CB000)
PC=0x90001B2C; MSR=0x0200F030; DAR=0x22886000; DSISR=0x42000000; LR=0x9461FB14; R1=0xBFFF8390; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x00D20780)
PC=0x00221F34; MSR=0x00009030; DAR=0x00000061; DSISR=0x40000000; LR=0x00221F18; R1=0x48423760; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00238DCC 0x00222DA0 0x0023D528 0x000FBB4C 0x000E97FC 0x000F5094
0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0xA1B1C1D3
backtrace terminated - frame not mapped or invalid: 0xBFFF8390

Exception state (sv=0x604CB000)
PC=0x90001B2C; MSR=0x0200F030; DAR=0x22886000; DSISR=0x42000000; LR=0x9461FB14; R1=0xBFFF8390; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC

*********

Thu Apr 5 11:13:16 2012
panic(cpu 0 caller 0x0021CAC8): btree_journal_modify_block_end: about to write corrupt node!

Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x0021CAC8 0x0021CC70 0x00243668 0x00241E04 0x0021F440
0x0023D460 0x000FBB4C 0x000E97FC 0x000F5094 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30
0x67657220
Proceeding back via exception chain:
Exception state (sv=0x604CBA00)
PC=0x90001B2C; MSR=0x0200F030; DAR=0x011B14E0; DSISR=0x40000000; LR=0x9461FB14; R1=0xBFFFE0F0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********

Thu Apr 5 11:17:33 2012


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000028 PC=0x00000000000FC0C8
Latest crash info for cpu 0:
Exception state (sv=0x583CB780)
PC=0x000FC0C8; MSR=0x00009030; DAR=0x00000028; DSISR=0x40000000; LR=0x000FAD5C; R1=0x482BB930; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x482BBB38 0x000FAD5C 0x000EAEA8 0x000EF6F8 0x000EF7CC 0x000EF9E4
0x002ABDB8 0x000ABD30 0xE77F8795
backtrace terminated - frame not mapped or invalid: 0xBFFFE840

Proceeding back via exception chain:
Exception state (sv=0x583CB780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x60833780)
PC=0x900437AC; MSR=0x0200F030; DAR=0x609A2000; DSISR=0x42000000; LR=0x946302D0; R1=0xBFFFE840; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x583CB780)
PC=0x000FC0C8; MSR=0x00009030; DAR=0x00000028; DSISR=0x40000000; LR=0x000FAD5C; R1=0x482BB930; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x482BBB38 0x000FAD5C 0x000EAEA8 0x000EF6F8 0x000EF7CC 0x000EF9E4
0x002ABDB8 0x000ABD30 0xE77F8795
backtrace terminated - frame not mapped or invalid: 0xBFFFE840

Exception state (sv=0x60833780)
PC=0x900437AC; MSR=0x0200F030; DAR=0x609A2000; DSISR=0x42000000; LR=0x946302D0; R1=0xBFFFE840; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********

Mon Apr 9 11:11:37 2012


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000058 PC=0x00000000000705EC
Latest crash info for cpu 0:
Exception state (sv=0x604AD000)
PC=0x000705EC; MSR=0x00009030; DAR=0x00000058; DSISR=0x40000000; LR=0x000705DC; R1=0x483C3CF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00070640 0x0006271C 0x000A865C 0x000ABB80
backtrace terminated - frame not mapped or invalid: 0xBFFFD790

Proceeding back via exception chain:
Exception state (sv=0x604AD000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x61107780)
PC=0xFFFF8ACC; MSR=0x0200D030; DAR=0x1ED05000; DSISR=0x42000000; LR=0x932AA3EC; R1=0xBFFFD790; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x604AD000)
PC=0x000705EC; MSR=0x00009030; DAR=0x00000058; DSISR=0x40000000; LR=0x000705DC; R1=0x483C3CF0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00070640 0x0006271C 0x000A865C 0x000ABB80
backtrace terminated - frame not mapped or invalid: 0xBFFFD790

Exception state (sv=0x61107780)
PC=0xFFFF8ACC; MSR=0x0200D030; DAR=0x1ED05000; DSISR=0x42000000; LR=0x932AA3EC; R1=0xBFFFD790; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC

*********

Mon Apr 16 11:19:39 2012
panic(cpu 1 caller 0x0009AD50): mapping_free: attempt to release mapping block (3B0D3E80) not on list

Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x0009AD50 0x00099EE4 0x00098C94 0x0006B440 0x0006B8C8
0x00057A38 0x00029234 0x000233F8 0x000ABEAC 0x8660210A
Proceeding back via exception chain:
Exception state (sv=0x60BAF280)
PC=0x9000AF48; MSR=0x0000D030; DAR=0x6C0D8000; DSISR=0x42000000; LR=0x9000AE9C; R1=0xF0302CA0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
*********
Thanks again!
Scott

 

[Giaguara]

Data access problem, and frame 0xBFFF8390 not mapped...

What was happening on the Mac when the kernel panic happened? What was the user doing?
Since when do the panics happen?
Was any software that would require drivers installed before the panics?

panic(cpu 0 caller 0x0021CAC8): btree_journal_modify_block_end: about to write corrupt node! <-- it might be good to check the disk and permissions with Disk Utility (/Applications/Utilities). Invalid node does not sound good (it would be like a map of the hard drive was corrupted).

 

[DreamReclaimer]

We bought this thing as a refurb from Newegg and it's been doing this since we got it about 2 months ago. It usually happens when she is working in one of the Creative Suite programs, but also occasionally at random when nothing is really going on.

I've talked to Newegg, they referred me to Mac, but since it's a "vintage" machine, I had to go back to Newegg to have them submit the request. Which is still pending. Yay.

I will try out the Disk Utility suggestion and post what I find.

Thanks!

 

[DreamReclaimer]

After much going back and forth between Newegg and the company that did the refurb (PlanITROI), they are going to replace the unit. I suspect this refurb was a late-afternoon-Friday job. There were some screws floating around the inside when we got it and they left off the sticker with the ID number they needed to verify it was one of theirs. Somebody just wanted to check it off the list.

Thanks for the help!

 

[Giaguara]

At least you had got it with Newegg's (some) warranty, so it's nice to know it got solved with the new unit.
(Even if it would have been "simply" just corrupted map of the HD that could have been solvable by formatting and clean installing everything on the HD, for the work machine that would of course have been some extra hassle in this case).