Help with a Kernel Panic

Question

Level 1

56 points

Help with a Kernel Panic

I have a Power Mac G5 quad core. I have been having kernel panics and can't figure out why. I thought it to be a software issue - so I got new hard drives and started fresh. Everything seemed better but have had kernel panic again. Does anyone know what hardware would cause this. I have done hardware tests with tech tool and with Apple tests and can't find any memory problems or anything else that sticks out. Any help would be MUCH appreicated.

Does this make sense to anyone:

Interval Since Last Panic Report: 4029042 sec

Panics Since Last Report: 1

Anonymous UUID: 691541CE-AA61-4E8A-8D69-C06D189F3BD4

Mon Apr 30 21:56:43 2012

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

Latest crash info for cpu 1:

Exception state (sv=0x633de780)

PC=0x0008404C; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00084034; R1=0x6362B2A0; XCP=0x0000000C (0x300 - Data access)

Backtrace:

0x0002EDF4 0x000857A8 0x00078B04 0x0007916C 0x0007A1C4 0x0007C4D0

0x002C4F54 0x000EF150 0x000F0808 0x000F1B20 0x0024AF04 0x00252AB8 0x0010A2D4 0x000EB3C8

0x000EC160 0x000FAF00 0x000FB458 0x000FB53C 0x003100AC 0x000B4448 0x00200400

backtrace terminated - frame not mapped or invalid: 0xBFFFF950

Proceeding back via exception chain:

Exception state (sv=0x633de780)

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

Exception state (sv=0x58e6ea00)

PC=0x9513BB6C; MSR=0x0200D030; DAR=0x0B5F3F64; DSISR=0x40000000; LR=0x95196F1C; R1=0xBFFFF950; XCP=0x00000030 (0xC00 - System call)

BSD process name corresponding to current thread: find

Mac OS version:

9L31a

Kernel version:

Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC

System model name: PowerMac11,2

System uptime in nanoseconds: 374274971426758

unloaded kexts:

com.apple.driver.Apple02DBDMAAudio 2.5.8f1 - last unloaded 3540283434

loaded kexts:

com.apple.driver.AppleTopazAudio 2.5.8f1 - last loaded 1126115004

com.apple.driver.AppleOnyxAudio 2.5.8f1

com.apple.filesystems.autofs 2.0.2

com.apple.driver.InternalModemSupport 2.4.0

com.apple.iokit.IOBluetoothSerialManager 2.1.9f10

com.apple.GeForcePPC 5.4.8

com.apple.driver.AppleTexasAudio 2.5.8f1

com.apple.driver.DiskImages 199

com.apple.driver.AppleTexas2Audio 2.5.8f1

com.apple.nvidia.nv40halppc 5.4.8

com.apple.driver.AppleSCCSerial 1.3.2

com.apple.driver.AppleDACAAudio 2.5.8f1

com.apple.driver.AudioIPCDriver 1.0.6

com.apple.driver.PowerMac11_2_ThermalProfile 3.4.0d0

com.apple.driver.AppleHWSensor 1.9d0

com.apple.iokit.AppleBCM5701Ethernet 2.2.3b1

com.apple.driver.AirPortBrcm43xx 367.91.22

com.apple.driver.IOI2CSMUSat 1.9d0

com.apple.driver.IOI2CLM7x 1.9d0

com.apple.driver.AppleUSBDisplays 2.0.2

com.apple.iokit.IOFireWireIP 1.7.7

com.apple.driver.AppleK2Driver 1.7.2f1

com.apple.driver.Apple_iSight 1.1.4

com.apple.driver.IOI2CMaxim6690 1.9d0

com.apple.driver.AppleSMUMonitor 1.9d0

com.apple.driver.IOI2CMaxim1631 1.9d0

com.apple.driver.AppleI2S 1.0.1f1

com.apple.driver.CSRUSBBluetoothHCIController 2.1.9f10

com.apple.driver.IOI2CPulsar 1.5.2d0

com.apple.driver.IOI2CControllerSMU 1.1.1d2

com.apple.driver.AppleFileSystemDriver 1.1.0

com.apple.driver.CSRHIDTransitionDriver 2.1.9f10

com.apple.driver.AppleUSBHIDMouse 1.2.4b3

com.apple.driver.AppleUSBMergeNub 3.5.2

com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1

com.apple.iokit.SCSITaskUserClient 2.1.1

com.apple.driver.XsanFilter 2.7.91

com.apple.iokit.IOATABlockStorage 2.0.6

com.apple.driver.AppleUSBHub 3.4.9

com.apple.iokit.IOATAPIProtocolTransport 1.5.3

com.apple.iokit.IOUSBUserClient 3.5.2

com.apple.driver.AppleK2SATA 1.0.4f2

com.apple.driver.AppleGPIO 1.3.0d0

com.apple.driver.MacIOGPIO 1.3.0d0

com.apple.driver.AppleMPIC 1.5.3

com.apple.driver.AppleI2C 4.0.0d2

com.apple.driver.IOI2CControllerPPC 1.1.0

System configuration:

Model: PowerMac11,2, BootROM 5.2.7f1, 4 processors, PowerPC G5 (1.1), 2.5 GHz, 4.5 GB

Graphics: kHW_NVidiaGeForce6600Item, GeForce 6600, spdisplays_pcie_device, 256 MB

Memory Module: DIMM0/J6700, 256 MB, DDR2 SDRAM, PC2-4200U-444

Memory Module: DIMM1/J6800, 256 MB, DDR2 SDRAM, PC2-4200U-444

Memory Module: DIMM2/J6900, 1 GB, DDR2 SDRAM, PC2-4200U-444

Memory Module: DIMM3/J7000, 1 GB, DDR2 SDRAM, PC2-4200U-444

Memory Module: DIMM4/J7100, 1 GB, DDR2 SDRAM, PC2-4200U-444

Memory Module: DIMM5/J7200, 1 GB, DDR2 SDRAM, PC2-4200U-444

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x4318), Broadcom BCM43xx 1.0 (4.170.25.8)

Bluetooth: Version 2.1.9f10, 2 service, 1 devices, 1 incoming serial ports

Network Service: AirPort, AirPort, en2

PCI Card: GeForce 6600, display, SLOT-1

PCI Card: Apple 5714, network, GIGE

Serial ATA Device: ST1000DM003-9YN162, 931.51 GB

Parallel ATA Device: HL-DT-ST DVD-RW GWA-4165B

USB Device: hub_device, (null) mA

USB Device: Apple Cinema HD Display, (null) mA

USB Device: Bluetooth USB Host Controller, (null) mA

USB Device: Hub in Apple Extended USB Keyboard, (null) mA

USB Device: Apple Optical USB Mouse, (null) mA

USB Device: Apple Extended USB Keyboard, (null) mA

FireWire Device: iSight, Apple Computer, Inc., 200mbit_speed

FireWire Device: unknown_device, unknown_value, unknown_speed

Thanks

CD

Posted on May 2, 2012 7:30 PM

Reply

Answer 1

BDAqua

Level 10

239,183 points

May 2, 2012 7:52 PM in response to t4tennessee

One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...

PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive

Reboot, test again.

If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.

Check the System Preferences>Other Row, for 3rd party Pref Panes.

Reply

Answer 2

japamac

Level 7

24,400 points

May 2, 2012 9:51 PM in response to t4tennessee

(0x300 - Data access).....backtrace terminated - frame not mapped or invalid: 0xBFFFF950

Smells like RAM issues.

Use Memtest X or Rember for RAM testing.

None of the others do anything for intermittent errors.

They are all or nothing type tests, which are seldom the case with RAM.

Test ALL the RAM. Memtest in Single User Mode does this best.

Reply

Answer 3

May 3, 2012 6:20 AM in response to t4tennessee

Understanding crash logs isn’t easy and it’s hard (sometimes impossible) to decipher the cause of the problem. Take a look at Apple’s Crash Reporter document at http://developer.apple.com/technotes/tn2004/tn2123.html Also look at Tutorial: An introduction to reading Mac OS X crash reports

http://www.macfixit.com/article.php?story=20060309075929717

Kernel panics are usually caused by a hardware problem – frequently RAM, a USB device or a Firewire device. What external devices do you have connected? When trying to troubleshoot problems, disconnect all external devices except your monitor, keyboard and mouse. Do you experience the same problems?

To eliminate RAM being the problem, Look at this link: Testing RAM @ http://guides.macrumors.com/Testing_RAM Then download & use Memtest & Ramber.

Do you have an Apple Hardware Test disc (the AHT is on the Install/Restore DVD that came with your Mac)? Running the Apple Hardware Test in Loop Mode is an excellent troubleshooting step for finding intermittent hardware problems. It is especially useful when troubleshooting intermittent kernel panics. If Loop Mode is supported by the version of the Apple Hardware Test you are using, you run the Extended Test in Loop Mode by pressing Control-L before starting the test. Looping On should appear in the right window. Then click the Extended Test button.The test will run continuously until a problem is found. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure.In some cases, RAM problems did not show up until nearly 40 loops, so give it a good run.

May be a solution on one of these links.

http://docs.info.apple.com/article.html?artnum=106227What's a "kernel panic"? (Mac OS X)

http://www.macmaps.com/kernelpanic.htmlMac OS X Kernel Panic FAQ

http://www.index-site.com/kernelpanic.htmlMac OS X Kernel Panic FAQ

http://www.thexlab.com/faqs/kernelpanics.htmlResolving Kernel Panics

http://www.macfixit.com/article.php?story=20060911080447777Avoiding and eliminating Kernel panics

http://macosg.com/group/viewtopic.php?t=80012-Step Program to Isolate Freezes and/or Kernel Panics

 Cheers, Tom 😉

Reply