Upgrading to iTunes plus
20/04/09 Filed in: iTunes/iPod
i have a powermac g5 puchased in 2005 that is freaking out. It's been to the genius bar at th southpark apple store and they couldn't figure out what is wrong with it. I'm thinking maybe it's the logic board, but hoping it's not. I was wondering if i could schedule some time for you to take a look at it and maybe definitively determine what's wrong.
it started with a kernel panic error. I tried resetting PRAM and eventually did a clean install of Leopard. It will boot, but then freeze and fans go on hyperdrive. I've ordered more RAM hoping that maybe the RAM is bad and i can get out of this less expensively. RAM hasn't arrived yet to try, but i'm kind of thinking that's not going to solve the problem.
this is the latest error message i got... which perhaps means something to you...
please let me know your rates and if we can set up a time for you to take a look...
thanks!
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000004 PC=0x000000000035C720
Latest crash info for cpu 0:
Exception state (sv=0x30db3780)
PC=0x0035C720; MSR=0x00009030; DAR=0x00000004; DSISR=0x40000000; LR=0x0003F9BC; R1=0x26CF3DC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0035C738 0x0003F9BC 0x000B0E54
Proceeding back via exception chain:
Exception state (sv=0x30db3780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x27186780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008; root:xnu-1228.9.59~1/RELEASE_PPC
System model name: PowerMac7,3
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x0009BCF0 0x0009C694 0x00029EA0 0x000AFA90 0x000B32F8
Proceeding back via exception chain:
Exception state (sv=0x30db3780)
PC=0x0035C720; MSR=0x00009030; DAR=0x00000004; DSISR=0x40000000; LR=0x0003F9BC; R1=0x26CF3DC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0035C738 0x0003F9BC 0x000B0E54
Exception state (sv=0x27186780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
BSD process name corresponding to current thread: kernel_task
------------
It would be great if the kernel panic was due to bad ram and many of them often are. The log isn’t conclusive however. The first thing to suspect is bad ram. I’d ask what quality of ram do you have currently? Crucial and Apple Ram is very good quality while companies like ram jet or kensington seem so to have a higher failure rate in my experience. You could try pulling one piece of ram at a time to see if the machine will boot successfully. Most likely if it is bad ram, both chips are not faulity. However keep in mind that Leopard 10.5 requires at least 512 megs of ram to boot.
Kernal panics are almost always hardware related. Unplugging any external devices can help troubleshoot the problem as well. The next most common reason for kernel panics is failing hard drives. This is the most common failure in all computers. However, if your drive took an entire clean install then it may be healthy. You can check the SMART status of the drive from within disk utility. It may be failing.
I’ll keep my fingers crossed that it’s not the logic board as well. I’d be curious to know if the Apple Store was able to boot from an external drive.
it started with a kernel panic error. I tried resetting PRAM and eventually did a clean install of Leopard. It will boot, but then freeze and fans go on hyperdrive. I've ordered more RAM hoping that maybe the RAM is bad and i can get out of this less expensively. RAM hasn't arrived yet to try, but i'm kind of thinking that's not going to solve the problem.
this is the latest error message i got... which perhaps means something to you...
please let me know your rates and if we can set up a time for you to take a look...
thanks!
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000004 PC=0x000000000035C720
Latest crash info for cpu 0:
Exception state (sv=0x30db3780)
PC=0x0035C720; MSR=0x00009030; DAR=0x00000004; DSISR=0x40000000; LR=0x0003F9BC; R1=0x26CF3DC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0035C738 0x0003F9BC 0x000B0E54
Proceeding back via exception chain:
Exception state (sv=0x30db3780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x27186780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008; root:xnu-1228.9.59~1/RELEASE_PPC
System model name: PowerMac7,3
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x0009BCF0 0x0009C694 0x00029EA0 0x000AFA90 0x000B32F8
Proceeding back via exception chain:
Exception state (sv=0x30db3780)
PC=0x0035C720; MSR=0x00009030; DAR=0x00000004; DSISR=0x40000000; LR=0x0003F9BC; R1=0x26CF3DC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0035C738 0x0003F9BC 0x000B0E54
Exception state (sv=0x27186780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
BSD process name corresponding to current thread: kernel_task
------------
It would be great if the kernel panic was due to bad ram and many of them often are. The log isn’t conclusive however. The first thing to suspect is bad ram. I’d ask what quality of ram do you have currently? Crucial and Apple Ram is very good quality while companies like ram jet or kensington seem so to have a higher failure rate in my experience. You could try pulling one piece of ram at a time to see if the machine will boot successfully. Most likely if it is bad ram, both chips are not faulity. However keep in mind that Leopard 10.5 requires at least 512 megs of ram to boot.
Kernal panics are almost always hardware related. Unplugging any external devices can help troubleshoot the problem as well. The next most common reason for kernel panics is failing hard drives. This is the most common failure in all computers. However, if your drive took an entire clean install then it may be healthy. You can check the SMART status of the drive from within disk utility. It may be failing.
I’ll keep my fingers crossed that it’s not the logic board as well. I’d be curious to know if the Apple Store was able to boot from an external drive.
Sells Consulting email