Kernal Panics

I

ian27

It all started at 3......
Hello everybody

Over the last week or so I have been getting a lot a kernal panics. I am using a Power Mac G5 dual processor and haven't had these problems occur before. At first it only seemed to occur when I wish using Maya so I assumed that was causing it, but then it started happening with other applications and computer would (at times) start to run slow and lag. I have used Disk Warrior on both my internal and extrernal drive but this hasn't fixed the problem. I am a little concerned that it might be a hardware problem, how do I find out?

Here are the printouts from my latest panic.log file. I can't understand it but hopefully it might give somebody here a few clues?

=========================
Tue Aug 15 21:12:40 2006


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000003C4D734E PC=0x00000000008F0D3C
Latest crash info for cpu 0:
Exception state (sv=0x3E5E9280)
PC=0x008F0D3C; MSR=0x00009030; DAR=0x3C4D734E; DSISR=0x40000000; LR=0x008F0D24; R1=0x22093B40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00900814 0x008D9EE0 0x002E8BA0 0x002EAA6C 0x0008C4B0
0x000291C0 0x000233AC 0x000AC0AC 0xC2C2C2C2
backtrace terminated - frame not mapped or invalid: 0xBFFFF440

Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x8ce000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x6cb000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x6ef000
dependency: com.apple.NVDAResman(4.1.8)@0x705000
Proceeding back via exception chain:
Exception state (sv=0x3E5E9280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x3D765C80)
PC=0x9000B268; MSR=0x0200F030; DAR=0xE00FE000; DSISR=0x42000000; LR=0x9000B1BC; R1=0xBFFFF440; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8404 0x000ABD80
Proceeding back via exception chain:
Exception state (sv=0x3E5E9280)
PC=0x008F0D3C; MSR=0x00009030; DAR=0x3C4D734E; DSISR=0x40000000; LR=0x008F0D24; R1=0x22093B40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00900814 0x008D9EE0 0x002E8BA0 0x002EAA6C 0x0008C4B0
0x000291C0 0x000233AC 0x000AC0AC 0xC2C2C2C2
backtrace terminated - frame not mapped or invalid: 0xBFFFF440

Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x8ce000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x6cb000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x6ef000
dependency: com.apple.NVDAResman(4.1.8)@0x705000
Exception state (sv=0x3D765C80)
PC=0x9000B268; MSR=0x0200
=======================

Thanks guys,

Ian
 
Looks like a problem with the video card... could be hardware-related or not. Can you try running (in a loop) the Apple Hardware Test that came with your computer?
 
Because of the multiple occurrences of the following lines (I'm assuming you've got an NVidia video card, right?):

Code: 
com.apple.GeForce(4.1.8)@0x8ce000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x6cb000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x6ef000
dependency: com.apple.NVDAResman(4.1.8)@0x705000
 
yes, this is what I have.....

NVIDIA GeForce 6600LE:

Chipset Model: GeForce 6600LE
Type: Display
Bus: PCI
Slot: SLOT-1
VRAM (Total): 128 MB
Vendor: nVIDIA (0x10de)
Device ID: 0x0142
Revision ID: 0x00a4
ROM Revision: 2149
Displays:
BenQ FP71G:
Resolution: 1152 x 864 @ 75 Hz
Depth: 32-bit Color
Core Image: Supported
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display:
Status: No display connected
 
Okay, I run the hardware test and it found a problem with the memory but not with the video card. This was the error:

2MEM/10/4: DIMMO/J6700

I have four RAM chips in my computer, does this error give us any indication as to which chip might be causing the problem. As my computer is still under warranty, I am presuming that the company who I bought it from should be able to replace the chip for me right...

I am going to run the extended test just to confirm if this really is the problem.

Thank you.
 
You must log in or register to reply here.
Back
Top