Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Hardware - Troubleshooting and Discussion > Mac Desktops > PowerMac G5 dual 2GHz kernel panics

PowerMac G5 dual 2GHz kernel panics
Thread Tools
Andrew Stephens
Mac Elite
Join Date: Jan 2004
Status: Offline
Reply With Quote
Oct 30, 2008, 05:14 PM
 
Loads and loads. I'm not sure it's RAM but I'm not super great on crash logs: anyone got any thoughts?

Thu Feb 8 16:24:16 2007
panic(cpu 0 caller 0x000E7E14): vnode_put(464e948): iocount < 1
Latest stack backtrace for cpu 0:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000E7E14 0x000E7DC0 0x0010D564 0x0010D7DC 0x0010DA00
0x000FB124 0x000E1EE8 0x000E1A7C 0x000F4ADC 0x000ECE2C 0x000ED1EC 0x002AAE28 0x000AB930
0x6F613877
Proceeding back via exception chain:
Exception state (sv=0x4FCBB280)
PC=0x9000172C; MSR=0x0000F030; DAR=0xE0709000; DSISR=0x42000000; LR=0x0001C45C; R1=0xF007E910; XCP=0x00000030 (0xC00 - System call)

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
*********

Thu Oct 30 10:12:47 2008
panic(cpu 1 caller 0x0003E64C): wait_queue_assert_wait64_locked
Latest stack backtrace for cpu 1:
Backtrace:
0x00095564 0x00095A7C 0x00026838 0x0003E64C 0x0003E7EC 0x00062524 0x000A85DC 0x000AB880
Proceeding back via exception chain:
Exception state (sv=0x4741DC80)
PC=0xFFFF87F0; MSR=0x0200D030; DAR=0x0048B014; DSISR=0x40000000; LR=0x91075A78; R1=0xBFFFC820; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 8.0.0: Sat Mar 26 14:15:22 PST 2005; root:xnu-792.obj~1/RELEASE_PPC
*********

Thu Oct 30 11:32:08 2008


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000020 PC=0x000000000003FFD4
Latest crash info for cpu 1:
Exception state (sv=0x5C127000)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x00000020; DSISR=0x40000000; LR=0x0003FFBC; R1=0x36DE30F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x03599900 0x0002BDCC 0x002FBFE4 0x002FE980 0x002D6D40 0x002D61D4
0x00451E7C 0x0044FE1C 0x0044EEB4 0x00109608 0x000D6134 0x000FEB68 0x000D7214 0x0022D884
0x000FEBBC 0x0023AC20 0x000D623C 0x0023AC74 0x00236A04 0x0023D480 0x000FBB4C 0x000E97FC
0x000F5094 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0x03880C20
backtrace terminated - frame not mapped or invalid: 0xBFFFF030

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOStorageFamily(1.5)@0x43d000
Proceeding back via exception chain:
Exception state (sv=0x5C127000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x5C103000)
PC=0x90001F2C; MSR=0x0000D030; DAR=0x0008D9CC; DSISR=0x40000000; LR=0x0006202C; R1=0xBFFFF030; 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 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x5C127000)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x00000020; DSISR=0x40000000; LR=0x0003FFBC; R1=0x36DE30F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x03599900 0x0002BDCC 0x002FBFE4 0x002FE980 0x002D6D40 0x002D61D4
0x00451E7C 0x0044FE1C 0x0044EEB4 0x00109608 0x000D6134 0x000FEB68 0x000D7214 0x0022D884
0x000FEBBC 0x0023AC20 0x000D623C 0x0023AC74 0x00236A04 0x0023D480 0x000FBB4C 0x000E97FC
0x000F5094 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0x03880C20
backtrace terminated - frame not mapped or invalid: 0xBFFFF030

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOStorageFamily(1.5)@0x43d000
Exception state (sv=0x5C103000)
PC=0x90001F2C; MSR=0x0000D030; DAR=0x0008D9CC; DSISR=0x40000000; LR=0x0006202C; R1=0xBFFFF030; XCP=0x000000
*********

Thu Oct 30 12:30:51 2008


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000020 PC=0x000000000003FFD4
Latest crash info for cpu 1:
Exception state (sv=0x5C127000)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x00000020; DSISR=0x40000000; LR=0x0003FFBC; R1=0x36DE30F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x03599900 0x0002BDCC 0x002FBFE4 0x002FE980 0x002D6D40 0x002D61D4
0x00451E7C 0x0044FE1C 0x0044EEB4 0x00109608 0x000D6134 0x000FEB68 0x000D7214 0x0022D884
0x000FEBBC 0x0023AC20 0x000D623C 0x0023AC74 0x00236A04 0x0023D480 0x000FBB4C 0x000E97FC
0x000F5094 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0x03880C20
backtrace terminated - frame not mapped or invalid: 0xBFFFF030

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOStorageFamily(1.5)@0x43d000
Proceeding back via exception chain:
Exception state (sv=0x5C127000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x5C103000)
PC=0x90001F2C; MSR=0x0000D030; DAR=0x0008D9CC; DSISR=0x40000000; LR=0x0006202C; R1=0xBFFFF030; 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 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x5C127000)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x00000020; DSISR=0x40000000; LR=0x0003FFBC; R1=0x36DE30F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x03599900 0x0002BDCC 0x002FBFE4 0x002FE980 0x002D6D40 0x002D61D4
0x00451E7C 0x0044FE1C 0x0044EEB4 0x00109608 0x000D6134 0x000FEB68 0x000D7214 0x0022D884
0x000FEBBC 0x0023AC20 0x000D623C 0x0023AC74 0x00236A04 0x0023D480 0x000FBB4C 0x000E97FC
0x000F5094 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0x03880C20
backtrace terminated - frame not mapped or invalid: 0xBFFFF030

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOStorageFamily(1.5)@0x43d000
Exception state (sv=0x5C103000)
PC=0x90001F2C; MSR=0x0000D030; DAR=0x0008D9CC; DSISR=0x40000000; LR=0x0006202C; R1=0xBFFFF030; XCP=0x000000
*********

Thu Oct 30 13:07:15 2008


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000020 PC=0x000000000003FFD4
Latest crash info for cpu 1:
Exception state (sv=0x5C127000)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x00000020; DSISR=0x40000000; LR=0x0003FFBC; R1=0x36DE30F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x03599900 0x0002BDCC 0x002FBFE4 0x002FE980 0x002D6D40 0x002D61D4
0x00451E7C 0x0044FE1C 0x0044EEB4 0x00109608 0x000D6134 0x000FEB68 0x000D7214 0x0022D884
0x000FEBBC 0x0023AC20 0x000D623C 0x0023AC74 0x00236A04 0x0023D480 0x000FBB4C 0x000E97FC
0x000F5094 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0x03880C20
backtrace terminated - frame not mapped or invalid: 0xBFFFF030

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOStorageFamily(1.5)@0x43d000
Proceeding back via exception chain:
Exception state (sv=0x5C127000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x5C103000)
PC=0x90001F2C; MSR=0x0000D030; DAR=0x0008D9CC; DSISR=0x40000000; LR=0x0006202C; R1=0xBFFFF030; 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 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x5C127000)
PC=0x0003FFD4; MSR=0x00009030; DAR=0x00000020; DSISR=0x40000000; LR=0x0003FFBC; R1=0x36DE30F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x03599900 0x0002BDCC 0x002FBFE4 0x002FE980 0x002D6D40 0x002D61D4
0x00451E7C 0x0044FE1C 0x0044EEB4 0x00109608 0x000D6134 0x000FEB68 0x000D7214 0x0022D884
0x000FEBBC 0x0023AC20 0x000D623C 0x0023AC74 0x00236A04 0x0023D480 0x000FBB4C 0x000E97FC
0x000F5094 0x000ED4E0 0x000ED898 0x002ABDB8 0x000ABD30 0x03880C20
backtrace terminated - frame not mapped or invalid: 0xBFFFF030

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOStorageFamily(1.5)@0x43d000
Exception state (sv=0x5C103000)
PC=0x90001F2C; MSR=0x0000D030; DAR=0x0008D9CC; DSISR=0x40000000; LR=0x0006202C; R1=0xBFFFF030; XCP=0x000000
*********

Thu Jan 1 01:00:37 1970
panic(cpu 1 caller 0x0003E934): wait_queue_assert_wait64_locked
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x0003E934 0x0003EAD4 0x0003CAA8 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x4434B500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

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 Oct 30 14:58:12 2008
panic(cpu 1 caller 0x0009B174): mapping_alloc - empty mapping block detected at 2D29F000

Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x0009B174 0x0009A15C 0x00098F78 0x00062AC8 0x000A865C
0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x5CB76A00)
PC=0xFFFF8AA8; MSR=0x0200F030; DAR=0x0105E000; DSISR=0x42000000; LR=0x903B2478; R1=0xBFFFECE0; 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
*********

Thu Oct 30 15:16:32 2008
panic(cpu 1 caller 0x0009B174): mapping_alloc - empty mapping block detected at 2D29F000

Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x0009B174 0x0009A15C 0x00098F78 0x00062AC8 0x000A865C
0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x5CB76A00)
PC=0xFFFF8AA8; MSR=0x0200F030; DAR=0x0105E000; DSISR=0x42000000; LR=0x903B2478; R1=0xBFFFECE0; 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
*********

Thu Oct 30 15:27:28 2008


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000004 PC=0x0000000000063114
Latest crash info for cpu 1:
Exception state (sv=0x4F8BF280)
PC=0x00063114; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x00063064; R1=0x36EBBDB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00062FDC 0x000A865C 0x000ABB80
backtrace terminated - frame not mapped or invalid: 0xBFFFED50

Proceeding back via exception chain:
Exception state (sv=0x4F8BF280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x4EF8F780)
PC=0x903B22E4; MSR=0x0000F030; DAR=0x01683000; DSISR=0x42000000; LR=0x903B2258; R1=0xBFFFED50; 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 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x4F8BF280)
PC=0x00063114; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x00063064; R1=0x36EBBDB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00062FDC 0x000A865C 0x000ABB80
backtrace terminated - frame not mapped or invalid: 0xBFFFED50

Exception state (sv=0x4EF8F780)
PC=0x903B22E4; MSR=0x0000F030; DAR=0x01683000; DSISR=0x42000000; LR=0x903B2258; R1=0xBFFFED50; 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
*********

Thu Oct 30 15:44:53 2008


Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000004 PC=0x0000000000063114
Latest crash info for cpu 1:
Exception state (sv=0x4F8BF280)
PC=0x00063114; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x00063064; R1=0x36EBBDB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00062FDC 0x000A865C 0x000ABB80
backtrace terminated - frame not mapped or invalid: 0xBFFFED50

Proceeding back via exception chain:
Exception state (sv=0x4F8BF280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x4EF8F780)
PC=0x903B22E4; MSR=0x0000F030; DAR=0x01683000; DSISR=0x42000000; LR=0x903B2258; R1=0xBFFFED50; 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 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x4F8BF280)
PC=0x00063114; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x00063064; R1=0x36EBBDB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00062FDC 0x000A865C 0x000ABB80
backtrace terminated - frame not mapped or invalid: 0xBFFFED50

Exception state (sv=0x4EF8F780)
PC=0x903B22E4; MSR=0x0000F030; DAR=0x01683000; DSISR=0x42000000; LR=0x903B2258; R1=0xBFFFED50; 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
*********

Thu Oct 30 15:51:48 2008
panic(cpu 1 caller 0x000A4EC8): simple lock (0x0038EFA0) deadlock detection, pc=0x0003C674

Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A4EC8 0x0003C674 0x0002E768 0x0001ED8C 0x0001FFD4
0x000242C8 0x0002E9BC 0x000ABEAC 0x69637420
Proceeding back via exception chain:
Exception state (sv=0x4EC71500)
PC=0x90039D38; MSR=0x0000F030; DAR=0x010A2000; DSISR=0x42000000; LR=0x907DEE1C; R1=0xBFFFEC10; 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

*********

help:advice:repairs:www.doctorhappymac.co.uk parts:www.doctorhappymacparts.co.uk
     
P
Moderator
Join Date: Apr 2000
Location: Gothenburg, Sweden
Status: Offline
Reply With Quote
Oct 31, 2008, 11:47 AM
 
Well who is...

All those crashes are not for the same reason, I think. The first few are implicating that there's something in the storage subsystem, but the latter ones say something else. That's a good reason to suspect RAM, but it could also be something on the harddrives.

General advice: run the hardware test disc, run Disk First Aid and reinstall the latest Combo update (you seem to be on 10.4, correct?) to see if that helps. If that won't do it, try pulling some RAM.
     
Andrew Stephens  (op)
Mac Elite
Join Date: Jan 2004
Status: Offline
Reply With Quote
Oct 31, 2008, 12:12 PM
 
Originally Posted by P View Post
Well who is...

All those crashes are not for the same reason, I think. The first few are implicating that there's something in the storage subsystem, but the latter ones say something else. That's a good reason to suspect RAM, but it could also be something on the harddrives.

General advice: run the hardware test disc, run Disk First Aid and reinstall the latest Combo update (you seem to be on 10.4, correct?) to see if that helps. If that won't do it, try pulling some RAM.
Hello P

Thanks for the input. So far I have:

Pulled the ram (in pairs). No joy, it's still going down.
Run diagnostics - no problems reported
Run extended tests in Tech Tool pro - minor errors in the file system all fixed - still falling over
Run memtest on the ram - all passed
Archive and installed OSX back up to 10.4.11 - still crashing
Super duper copied drive to back up internal drive and switched to running from backup drive, less crqshes but still going down.

I'm leaning towards an intermittent fault on the motherboard. This morning the machine managed about 3 hours before panicking, it may be heat related.

damn kp's!!

help:advice:repairs:www.doctorhappymac.co.uk parts:www.doctorhappymacparts.co.uk
     
P
Moderator
Join Date: Apr 2000
Location: Gothenburg, Sweden
Status: Offline
Reply With Quote
Nov 2, 2008, 02:53 PM
 
Hmm. The minor disk errors are a natural effect of the kernel panics, so no clues there. I also suspect either motherboard or PSU. Around the era that that machine is from, there was a batch of bad capacitors that will boil and short out when too hot - you may be unlucky and have one of those that only surfaced now.

If you suspect that heat may be the problem, you can use one of the many monitoring programs to keep an eye on the temperatures. My favorite is Temperature Monitor (free), but feel free to try a few and see which one you like. Things to watch out for is a temperature that never seems to settle on a stable value but only keeps climbing.

Finally, one of my standard iMac hints is to vacuum out all the intake vents to improve airflow. That might be useful here as well - that model requires some massive airflow to work.
     
Northeastern292
Forum Regular
Join Date: Feb 2007
Location: Brushton, New York (middle of nowhere)
Status: Offline
Reply With Quote
Nov 26, 2008, 04:57 PM
 
Originally Posted by P View Post
Hmm. The minor disk errors are a natural effect of the kernel panics, so no clues there. I also suspect either motherboard or PSU. Around the era that that machine is from, there was a batch of bad capacitors that will boil and short out when too hot - you may be unlucky and have one of those that only surfaced now.

If you suspect that heat may be the problem, you can use one of the many monitoring programs to keep an eye on the temperatures. My favorite is Temperature Monitor (free), but feel free to try a few and see which one you like. Things to watch out for is a temperature that never seems to settle on a stable value but only keeps climbing.

Finally, one of my standard iMac hints is to vacuum out all the intake vents to improve airflow. That might be useful here as well - that model requires some massive airflow to work.
I have a similar problem in a Power Mac G4 FW800 model. The temperature just keeps slowly climbing, and then after a while, the machine freezes.
The Mac Collection:

Power Mac G4 Sawtooth at 450MHz, Power Mac G4 Gigabit Ethernet at 400MHz, three Power Mac FW800's at 1.0GHz, MacBook Pro at 2.0GHz, my late father's G3 iMac at 350MHz, an iMac at 500MHz, a PowerBook G4 (12-inch VGA) and a PowerBook 170
     
P
Moderator
Join Date: Apr 2000
Location: Gothenburg, Sweden
Status: Offline
Reply With Quote
Nov 27, 2008, 09:26 AM
 
At what temp does the machine freeze? If it's a fairly low one, then some chip on the motherboard, or more likely an electrolyte capacitor, is failing. If it's higher, then you have a cooling problem, at which point you can start by cleaning the machine thoroughly (dust build-up causes heat, and can even cause fires) and replace the fans if that doesn't work.
     
Northeastern292
Forum Regular
Join Date: Feb 2007
Location: Brushton, New York (middle of nowhere)
Status: Offline
Reply With Quote
Nov 27, 2008, 12:39 PM
 
Originally Posted by P View Post
At what temp does the machine freeze? If it's a fairly low one, then some chip on the motherboard, or more likely an electrolyte capacitor, is failing. If it's higher, then you have a cooling problem, at which point you can start by cleaning the machine thoroughly (dust build-up causes heat, and can even cause fires) and replace the fans if that doesn't work.
Concerning my machine, it freezes at fairly low temperatures (like 105-110˚). I've sort of been in denial that the machine has something wrong with it.
The Mac Collection:

Power Mac G4 Sawtooth at 450MHz, Power Mac G4 Gigabit Ethernet at 400MHz, three Power Mac FW800's at 1.0GHz, MacBook Pro at 2.0GHz, my late father's G3 iMac at 350MHz, an iMac at 500MHz, a PowerBook G4 (12-inch VGA) and a PowerBook 170
     
shdwghst457
Junior Member
Join Date: Sep 2009
Status: Offline
Reply With Quote
Sep 15, 2009, 02:53 AM
 
is your g5 a dual processor 2.0, or a dual core 2.0? i have DC2.0 that has been KPing for similar sounding issues.
     
   
 
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Top
Privacy Policy
All times are GMT -4. The time now is 10:55 PM.
All contents of these forums © 1995-2017 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2017, Jelsoft Enterprises Ltd.,