Help with Kernel Panic log

Discussion in 'macOS' started by netnothing, Oct 31, 2009.

  1. netnothing macrumors 68040


    Mar 13, 2007
    Can someone take a look at this log and let me know what your thoughts are on the cause:

    Interval Since Last Panic Report:  3832698 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    43A231C1-5748-483B-806B-A420BB0FCA3D
    Sat Oct 31 12:30:55 2009
    Machine-check capabilities (cpu 2) 0x0000000000000006:
     family: 6 model: 15 stepping: 6 microcode: 198
     Intel(R) Xeon(R) CPU            5150  @ 2.66GHz
     6 error-reporting banks
    Machine-check status 0x0000000000000005:
     restart IP valid
     machine-check in progress
    MCA error-reporting registers:
     IA32_MC0_STATUS(0x401): 0x1000000020000000 invalid
     IA32_MC1_STATUS(0x405): 0x0000000000000000 invalid
     IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
     IA32_MC3_STATUS(0x40d): 0x0020000000000000 invalid
     IA32_MC4_STATUS(0x411): 0x0000000000000011 invalid
     IA32_MC5_STATUS(0x415): 0xb200001084200e0f valid
      MCA error code:            0x0e0f
      Model specific error code: 0x8420
      Other information:         0x00000010
      Status bits:
       Processor context corrupt
       Error enabled
       Uncorrected error
    panic(cpu 2 caller 0x2a5c94): Machine Check at 0x00f91723, thread:0x110c0b7c, trapno:0x12, err:0x0,registers:
    CR0: 0x80010033, CR2: 0x173be000, CR3: 0x00100000, CR4: 0x00000660
    EAX: 0x00000000, EBX: 0x10ffeac0, ECX: 0x00000001, EDX: 0x00000000
    ESP: 0x86b9bb00, EBP: 0x86b9bb28, ESI: 0x10fe2000, EDI: 0x00f9b308
    EFL: 0x00000002, EIP: 0x00f91723
    Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)
    0x7fda8fb8 : 0x21acfa (0x5ce650 0x7fda8fec 0x223156 0x0) 
    0x7fda9008 : 0x2a5c94 (0x590718 0x590805 0xf91723 0x110c0b7c) 
    0x7fda90f8 : 0x29d8d2 (0x1 0x6f725065 0x656c6966 0x696d6146) 
    0x86b9bb28 : 0xf89ca4 (0x7fcfd0a4 0x1 0x10fe2000 0x0) 
    0x86b9bc08 : 0xf8b4d4 (0xd9bd3f43 0x800004f5 0x0 0x0) 
    0x86b9bcd8 : 0x2a7a2b (0xffffffff 0x7fffffff 0x10 0x286) 
    0x86b9bcf8 : 0x224f87 (0x0 0xd9969f30 0x4f5 0x7fd06488) 
    0x86b9bd58 : 0x225d74 (0x1 0x110c0b7c 0x1100bc58 0x0) 
    0x86b9bdc8 : 0x226987 (0x110c0b98 0x4f5 0x86b9bde8 0x29f596) 
    0x86b9be38 : 0x226a2b (0x229b17 0x0 0x0 0x29f596) 
    0x86b9be58 : 0x229e5e (0x229b17 0x863614 0x0 0x2) 
    0x86b9beb8 : 0x22a214 (0xdb6055f0 0x4f5 0x0 0x484029) 
    0x86b9bef8 : 0x483d9a (0xc03 0x0 0x1c9bf98 0x484029) 
    0x86b9bf78 : 0x4ed85f (0x11bb67e0 0x10eb87e8 0x11f04424 0x0) 
    0x86b9bfc8 : 0x29d3fd (0x10eb87e4 0x1 0x10 0x11a42ac4) 
          Kernel Extensions in backtrace (with dependencies):
    BSD process name corresponding to current thread: Finder
    Mac OS version:
    Kernel version:
    Darwin Kernel Version 10.0.0: Fri Jul 31 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386
    System model name: MacPro1,1 (Mac-F4208DC8)
    System uptime in nanoseconds: 5453971653779
    unloaded kexts:	2.0 (addr 0xdeb000, size 0x12288) - last unloaded 81640850634
    loaded kexts:	1.9.2d0 - last loaded 16827484180	2.1.0	3.0.5	1.7.4a1	6.0.2	2.1	7.0.0	1.1.0	1.1.9	19	3.4.0a20	1.4.6	1.1.5f1	2.5.0	2.5.1	31	1.0.0d1	4.3.4	1.5.0	2.0.0	2.5.0	2.1.1b7	3.7.8	1.3.0	3.7.5	1.3	1.3	3.7.5	1.4	1.4	1.3	1.4	90.0.0	0	0	2.0.11	90.0.0	17	1.7.4a1	10	14	10	10	20	6.0.2	6.0.2	2.0	2.0.3	73.0	2.0	2.2.1f7	10.0.2	1.7.0fc16	1.3	1.7.4a1	1.7.4a1	40	3.0.1d2	3.4.0a20	3.7.5	2.5.1	2.5.1	3.7.5	3.7.5	2.0.0	4.0.5	2.5.1	1.6	1.6	1.6	402.1	2.5.0	2.5.1	4.1.7	2.0.0	2.5.0	1.8	3.7.5	1.3.0	1.6.0	3.7.8	1.1	1.0.0d1	6	281	1.6	1.3	2.6	1.3.0
    Model: MacPro1,1, BootROM MP11.005C.B08, 4 processors, Dual-Core Intel Xeon, 2.66 GHz, 6 GB, SMC 1.7f10
    Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
    Memory Module: global_name
    Network Service: Ethernet 1, Ethernet, en0
    PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
    Serial ATA Device: ST3500418AS, 465.76 GB
    Serial ATA Device: WDC WD5000KS-00MNB0, 465.76 GB
    Serial ATA Device: WDC WD10EADS-00L5B1, 931.51 GB
    Serial ATA Device: ST31000333AS, 931.51 GB
    Parallel ATA Device: SONY    DVD RW DW-D150A
    USB Device: Keyboard Hub, 0x05ac  (Apple Inc.), 0x1006, 0xfd500000
    USB Device: Microsoft Optical Mouse with Tilt Wheel, 0x045e  (Microsoft Corporation), 0x00d1, 0xfd530000
    USB Device: Apple Keyboard, 0x05ac  (Apple Inc.), 0x0220, 0xfd520000
    USB Device: Hub, 0x05ac  (Apple Inc.), 0x911c, 0xfd300000
    USB Device: Apple Cinema HD Display, 0x05ac  (Apple Inc.), 0x921c, 0xfd320000
    USB Device: Back-UPS XS 1300 LCD FW:836.H5 .D USB FW:H5, 0x051d  (American Power Conversion), 0x0002, 0x3d200000
    FireWire Device: built-in_hub, Up to 800 Mb/sec
    FireWire Device: OWC Mercury Elite-AL 1, Other World Computing, Up to 800 Mb/sec
    FireWire Device: ATA Device 00, OEM, Up to 800 Mb/sec
    FireWire Device: unknown_device, Unknown

    Machine was just doing a large file copy from one internal drive to the other. I didn't get the typical Kernel Panic just dimmed a bit and the fans went crazy.

    Mac Pro 1,1
    11 GB RAM

    Odd thing is this line:

    After the machine rebooted, I noticed that Riser_B wasn't showing in system profiler (it was before the panic). I reseated the Risers and both are showing now.

    Could this be the Riser was slightly loose?

    Thanks for any's much appreciated.

  2. Peace macrumors Core


    Apr 1, 2005
    Space--The ONLY Frontier
    Does one of your risers have 5GB of ram on it?
  3. netnothing thread starter macrumors 68040


    Mar 13, 2007
    Riser_A = 6GB (2,2,1,1)
    Riser_B = 5GB (2,2,512,512)

    Yeah, so it looks like the first reboot after the KP, Riser_B wasn't showing up....not sure if there was a problem with the riser being loose.

    After I posted this, I shut the machine down and pulled both risers and reseated them (didn't touch the RAM themselves). This time I left the cover off and Riser_A had a red light and wasn't showing up.

    Off again and this time I pulled both risers and also reseated RAM. Put both back in and right now they are being recognized.

    Now I cleaned my machine out this morning.....I had taken all the risers out to clean the dust. I made sure after the first boot that all 11GB was being recognized and it was. So something happened while Finder was doing the copy....and something happened so that the KP log only reported the RAM on Riser_A (the 6GB).

    Any thoughts?

  4. netnothing thread starter macrumors 68040


    Mar 13, 2007
    Also just as an FYI....none of this RAM is new. Haven't added any new hardware. Actually had just shut the machine down to clean in and outside it this morning.....previously it had been up 44 days straight with no problems.

    I'm guessing this is something related to the RAM and seating?

  5. Peace macrumors Core


    Apr 1, 2005
    Space--The ONLY Frontier
    One of your RAM chips on riser A might be going bad.

    Or it could just be you didn't have them seated properly.

    Give it a wait and see what happens next.
  6. netnothing thread starter macrumors 68040


    Mar 13, 2007
    What's weird is......the KP is reporting 6GB of RAM....which means that at that time Riser_A was was Riser_B not reporting (which is also what happened after the first reboot.....Riser_B was missing).

    It wasn't until after I pulled them all again that Riser_A had the red light.

    Guess this machine is just being picky with me today.

  7. netnothing thread starter macrumors 68040


    Mar 13, 2007
    Reseated all RAM again and ran Rember on the whole 11GB. So far so good. All tests passed fine. I'm guessing it was just loose RAM that caused the Kernel Panic (crosses fingers).


Share This Page