Mac Pro kernel panic error

[massimike]

First of all I want to say hello to everybody since this is my first post in MacRumors.....My name's is Massimiliano and I am from Italy.
Bothering you all expert guys as I am using mac since a while but I am not so good to understand such errors....surely as I'm a newbie!
I bought a used macpro still on apple warranty quad core 2.93 with 8gb ram from OWC and 4 hardrive 1 by apple factory. One WD caviar black 640gb 32mb cache, 2 HD 320gb which I am using with raid stripped. Morover I have a second DVD LG mounted.
It is happening that at least once a day the system give me a GSOD and when I switchd the machine on again the system give me the following reporting error:

Interval Since Last Panic Report: 188606 sec
Panics Since Last Report: 4
Anonymous UUID: 33612D32-8B49-4153-9D1D-61FF96098884

Sun Oct 11 11:31:50 2009
Machine-check capabilities (cpu 6) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 15
Intel(R) Xeon(R) CPU W3540 @ 2.93GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000800 invalid
IA32_MC1_STATUS(0x405): 0x0000000000000800 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0000000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0000000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0000000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0xfe1615000001009f valid
Channel number: 15
Model: MacPro4,1, BootROM MP41.0081.B03, 4 processors, Quad-Core Intel Xeon, 2.93 GHz, 8 GB, SMC 1.39f5
Graphics: NVIDIA GeForce GT 120, NVIDIA GeForce GT 120, PCIe, 512 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en2
PCI Card: NVIDIA GeForce GT 120, Display, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: HL-DT-STDVD-RAM GH22NS30
Serial ATA Device: WDC WD3202ABYS-01B7A0, 298,09 GB
Serial ATA Device: WDC WD3202ABYS-01B7A0, 298,09 GB
Serial ATA Device: WDC WD6401AALS-00L3B2, 596,17 GB
Serial ATA Device: WDC WD6400AAKS-41H2B0, 596,17 GB
USB Device: My Book, 0x1058 (Western Digital Technologies, Inc.), 0x1102, 0xfd300000
USB Device: Hub, 0x03f0 (Hewlett Packard), 0x2f24, 0xfd100000
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd130000
USB Device: Apple Optical USB Mouse, 0x05ac (Apple Inc.), 0x0304, 0xfd133000
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd132000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000
FireWire Device: built-in_hub, Up to 800 Mb/sec

Anyone have any idea of this could be?

Thanks for your help, really appreciated.
Ciao
Max

[cluthz]

Seems like its the RAM.

Insert the System DVD that came with the computer, hold D on startup and then run Apple hardware Test.

[massimike]

Seems like its the RAM.

Insert the System DVD that came with the computer, hold D on startup and then run Apple hardware Test.

Run the apple hardware test the longest one but seem to be all ok :( !
Any other idea :confused: :confused: :confused: ????
Thanks
Max

[UltraNEO*]

What was the last hardware/software change you made? Maybe whatever you've installed/changed is causing the system to hang.

Also, check your console.. it should give you more of an idea as to what's causing the system to hang.

[rtrt]

a

[dcdc]

Hi Massimike
My advice is take the second DVD LG Drive out. I have had the same error (looks like a RAM error sometimes) with a similar DVD-RAM LG Drive on the same machine. Computer now passes extended Apple Hardware Test and am hoping the BSOD will stop...best o luck

[massimike]

Hi Massimike
My advice is take the second DVD LG Drive out. I have had the same error (looks like a RAM error sometimes) with a similar DVD-RAM LG Drive on the same machine. Computer now passes extended Apple Hardware Test and am hoping the BSOD will stop...best o luck

Did the Apple Hardware test failed before you removed your LG drive ? As I run the same test but the mac passed it?

[massimike]

i had issues with my upgrade memory way back.

if i looked in system profiler the memory status would show ecc errors. had the faulty dimms replaced and all been fine ever since.

mem also from owc - only hassle with the swap was the cost and time associated with posting from uk back to us.

I think I am going to try DDC solution first, than if the problem persist I will send back ram to OWC and ask for exchange. They should have lifetime warranty if I am not mistaken, am I?
At first sight I thought it was a software problem, but I seem to understand is only related to hardware problem. Is the ram such a delicate issue as it should be highly tested before sent out? Don't you think so?
Thank for your precious help you guys all.

[rtrt]

a

[massimike]

Guys, I'm not very good at understanding console or whatsoever regarding reporting error with mac. I'm almost a newbie in mac world and being a pc user for a long time some things still look a bit difficult to me. I'd like to post another screenshot which I had from the last GSOD:

Interval Since Last Panic Report: 28716 sec
Panics Since Last Report: 2
Anonymous UUID: 9636BF21-5A28-4BD3-9179-3A2970696AB3

Wed Oct 14 23:22:47 2009
Machine-check capabilities (cpu 0) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 15
Intel(R) Xeon(R) CPU W3540 @ 2.93GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000800 invalid
IA32_MC1_STATUS(0x405): 0x0000000000000800 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0000000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0000000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0000000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0xfe1f7d000001009f valid
Channel number: 15 (unknown)
Memory Operation: read
Machine-specific error: Read ECC
COR_ERR_CNT: 31720
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
Error overflow
IA32_MC8_ADDR(0x422): 0x0000000027a5d140
IA32_MC8_MISC(0x423): 0x87e1052f00080482
DIMM: 0
Channel: 2
Syndrome: 0x87e1052f
panic(cpu 0 caller 0x2a5c94): Machine Check at 0x00dab2b8, thread:0xd43fb7c, trapno:0x12, err:0x0,registers:
CR0: 0x8001003b, CR2: 0x61a4f000, CR3: 0x00100000, CR4: 0x000006e8
EAX: 0x00000940, EBX: 0x00004a08, ECX: 0x00000000, EDX: 0x811e18d0
ESP: 0x7c3c3bf0, EBP: 0x7c3c3c88, ESI: 0x00000000, EDI: 0x7c3c3ccc
EFL: 0x00000287, EIP: 0x00dab2b8

Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x819e18 : 0x21acfa (0x5ce650 0x819e4c 0x223156 0x0)
0x819e68 : 0x2a5c94 (0x590718 0x590805 0xdab2b8 0xd43fb7c)
0x819f58 : 0x29d8d2 (0x1 0x0 0x0 0x0)
0x7c3c3c88 : 0xdb64ea (0x6d01b000 0xe6a9000 0x7c3c3ccc 0x2c)
0x7c3c3d68 : 0xdbf52a (0x6d01b000 0xd6baa80 0x811e18ac 0x8118fc00)
0x7c3c3e68 : 0xdfff93 (0x6d01b000 0x8118fc00 0x0 0x225e69)
0x7c3c3ed8 : 0xd3e794 (0x6d01b000 0x0 0x7c3c3f58 0x22699d)
0x7c3c3f08 : 0x548049 (0xd625c00 0xd713140 0x1 0x29b50a)
0x7c3c3f58 : 0x54707a (0xd713140 0x863ec0 0x0 0x29f596)
0x7c3c3f88 : 0x5474d4 (0xd64b540 0x863ec0 0x0 0x229b94)
0x7c3c3fc8 : 0x29c68c (0xd64b540 0x0 0x10 0xde940e0)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AirPortBrcm43xx(410.91.20)@0xd31000->0xed8fff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x95d000
dependency: com.apple.iokit.IO80211Family(300.20)@0xd0d000
dependency: com.apple.iokit.IONetworkingFamily(1.8)@0xcf7000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
10B504

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: MacPro4,1 (Mac-F221BEC8)

System uptime in nanoseconds: 17872406159676
unloaded kexts:
com.apple.driver.AppleIntel8254XEthernet 2.1.1b7 (addr 0x116a000, size 0x118784) - last unloaded 85081200739
loaded kexts:
at.obdev.nke.LittleSnitch 2.2.05
com.apple.driver.AppleHIDKeyboard 1.1.5f1
com.apple.driver.AppleHWSensor 1.9.2d0
com.apple.driver.AppleTyMCEDriver 1.0.1d8
com.apple.driver.AGPM 100.8.15
com.apple.driver.AppleMikeyHIDDriver 1.1.7
com.apple.driver.AppleUpstreamUserClient 3.0.5
com.apple.driver.AppleHDA 1.7.4a1
com.apple.driver.AppleMikeyDriver 1.7.4a1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.GeForce 6.0.2
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AudioIPCDriver 1.1.0
com.apple.driver.AppleIntelNehalemProfile 11
com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a20
com.apple.driver.AppleLPC 1.4.6
com.apple.iokit.SCSITaskUserClient 2.5.1
com.apple.driver.AppleRAID 4.0.6
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleFWOHCI 4.3.4
com.apple.driver.Intel82574L 1.0.1b48
com.apple.driver.AirPortBrcm43xx 410.91.20
com.apple.iokit.IOAHCIBlockStorage 1.5.0
com.apple.driver.AppleUSBHub 3.7.8
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleAHCIPort 2.0.0
com.apple.driver.AppleUSBEHCI 3.7.5
com.apple.driver.AppleUSBUHCI 3.7.5
com.apple.driver.AppleRTC 1.3
com.apple.driver.AppleHPET 1.4
com.apple.driver.AppleACPIButtons 1.3
com.apple.driver.AppleSMBIOS 1.4
com.apple.driver.AppleACPIEC 1.3
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 90.0.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.0.11
com.apple.driver.AppleIntelCPUPowerManagement 90.0.0
com.apple.driver.AppleUSBAudio 2.6.4b15 - last loaded 9108713370345
com.apple.driver.AppleUSBHIDMouse 1.3.0f1
com.apple.driver.AppleHIDMouse 1.3.0f1
com.apple.driver.AppleUSBMergeNub 3.7.5
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.driver.DspFuncLib 1.7.4a1
com.apple.iokit.IOSurface 73.0
com.apple.iokit.IOBluetoothSerialManager 2.2.1f7
com.apple.iokit.IOSerialFamily 10.0.2
com.apple.driver.AppleSMBusController 1.0.2d0
com.apple.nvidia.nv50hal 6.0.2
com.apple.NVDAResman 6.0.2
com.apple.iokit.IONDRVSupport 2.0
com.apple.iokit.IOGraphicsFamily 2.0
com.apple.iokit.IOAudioFamily 1.7.0fc16
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 1.7.4a1
com.apple.iokit.IOHDAFamily 1.7.4a1
com.apple.iokit.AppleProfileFamily 40
com.apple.driver.AppleSMC 3.0.1d2
com.apple.driver.IOPlatformPluginFamily 3.4.0a20
com.apple.driver.AppleSMBusPCI 1.0.2d0
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.driver.BroadcomUSBBluetoothHCIController 2.2.1f7
com.apple.driver.AppleUSBBluetoothHCIController 2.2.1f7
com.apple.iokit.IOBluetoothFamily 2.2.1f7
com.apple.iokit.IOUSBHIDDriver 3.7.5
com.apple.iokit.IOSCSIBlockCommandsDevice 2.5.1
com.apple.iokit.IOUSBMassStorageClass 2.5.0
com.apple.driver.AppleUSBComposite 3.7.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.5.1
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOFireWireFamily 4.1.7
com.apple.iokit.IOAHCISerialATAPI 1.2.0
com.apple.iokit.IOSCSIArchitectureModelFamily 2.5.1
com.apple.iokit.IO80211Family 300.20
com.apple.iokit.IONetworkingFamily 1.8
com.apple.iokit.IOUSBUserClient 3.7.5
com.apple.iokit.IOAHCIFamily 2.0.0
com.apple.iokit.IOUSBFamily 3.7.8
com.apple.driver.AppleEFIRuntime 1.3.0
com.apple.iokit.IOHIDFamily 1.6.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 281
com.apple.iokit.IOStorageFamily 1.6
com.apple.driver.AppleACPIPlatform 1.3
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
Model: MacPro4,1, BootROM MP41.0081.B03, 4 processors, Quad-Core Intel Xeon, 2.93 GHz, 8 GB, SMC 1.39f5
Graphics: NVIDIA GeForce GT 120, NVIDIA GeForce GT 120, PCIe, 512 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en2
PCI Card: NVIDIA GeForce GT 120, Display, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: HL-DT-STDVD-RAM GH22NS30
Serial ATA Device: WDC WD3202ABYS-01B7A0, 298,09 GB
Serial ATA Device: WDC WD3202ABYS-01B7A0, 298,09 GB
Serial ATA Device: WDC WD6401AALS-00L3B2, 596,17 GB
Serial ATA Device: WDC WD6400AAKS-41H2B0, 596,17 GB
USB Device: iPhone, 0x05ac (Apple Inc.), 0x1292, 0xfd500000
USB Device: Hub, 0x03f0 (Hewlett Packard), 0x2f24, 0xfd300000
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd330000
USB Device: Apple Optical USB Mouse, 0x05ac (Apple Inc.), 0x0304, 0xfd333000
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd332000
USB Device: Logitech Camera, 0x046d (Logitech Inc.), 0x09a6, 0xfd320000
USB Device: My Book, 0x1058 (Western Digital Technologies, Inc.), 0x1102, 0xfd100000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000
FireWire Device: built-in_hub, Up to 800 Mb/sec

Any help, idea of helping me in sorting out this mess I'd be grateful. I am even thinking of replacing with original ram banks and try if the problem will happen again.
Thanks
Max

[Sun Baked]

If the My Book plugged into a powered hub? and are you using the power brick on the My Book?

Might try removing the USB hub and leave all devices disconnected. Just a quick check to see if a USB device spinning up and drawing too much power and crashing the USB port during a data request.

[massimike]

If the My Book plugged into a powered hub? and are you using the power brick on the My Book?

Might try removing the USB hub and leave all devices disconnected. Just a quick check to see if a USB device spinning up and drawing too much power and crashing the USB port during a data request.

Doesn't seems a problem relating to the ram instead of usb powering matter?

[MythicFrost]

I have an idea, open the application system profiler, go to the Diagnostics tab, does it show anything there?

Kind Regards

[massimike]

I have an idea, open the application system profiler, go to the Diagnostics tab, does it show anything there?

Kind Regards

I will try to translate it from italian as I am.
on 11th october I run apple hardware test and system profile said that has been passed.
Then it said something relating the automatic switch on test and this also reported ok.
What have you thought this could be, related to the system profiler?

[Sun Baked]

It is called eliminating an issue, and people with My Books have been getting crashes ... though most of those are FW crashes, a bus powered drive is a possibility.

Anyhow, old hubs have been know to cause similar issues to bad memory (aka, lots of kernel panics).

[MythicFrost]

No, but I've had my OS detect bad RAM once, it seems to have gone away now. Thought it might show something.

What type of Mac are you using?

Kind Regards

[massimike]

Hi guys,
after having decided to reinstall OS again system still crashes but the reports now seems different.....Any help???

Sun Oct 25 16:17:32 2009
Machine-check capabilities (cpu 6) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 15
Intel(R) Xeon(R) CPU W3540 @ 2.93GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000800 invalid
IA32_MC1_STATUS(0x405): 0x0000000000000800 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0000000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0000000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0000000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0xbe0000000001009f valid
Channel number: 15 (unknown)
Memory Operation: read
Machine-specific error: Read ECC
COR_ERR_CNT: 0
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC8_ADDR(0x422): 0x000000001baeb280
IA32_MC8_MISC(0x423): 0x6ed2cef70009088e
DIMM: 1
Channel: 2
Syndrome: 0x6ed2cef7
panic(cpu 6 caller 0x2a5c94): Machine Check at 0x0025f574, thread:0xef3db7c, trapno:0x12, err:0x0,registers:
CR0: 0x80010033, CR2: 0x2d59c000, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x00000001, EBX: 0x0dd855c4, ECX: 0x12ba2344, EDX: 0x00000003
ESP: 0x7c44bcf0, EBP: 0x7c44bdf8, ESI: 0x2d59c000, EDI: 0x00000000
EFL: 0x00000202, EIP: 0x0025f574

Backtrace (CPU 6), Frame : Return Address (4 potential args on stack)
0x7c348fb8 : 0x21acfa (0x5ce650 0x7c348fec 0x223156 0x0)
0x7c349008 : 0x2a5c94 (0x590718 0x590805 0x25f574 0xef3db7c)
0x7c3490f8 : 0x29d8d2 (0x1 0x72506465 0x636f746f 0x70536c6f)
0x7c44bdf8 : 0x25702c (0x7c44bf40 0x2d59c000 0x0 0x3)
0x7c44bf38 : 0x2a639c (0xdd855c4 0x2d59c000 0x0 0x3)
0x7c44bfc8 : 0x29c7ca (0xe6a8440 0x0 0x10 0xe6a8440)

BSD process name corresponding to current thread: Adobe Photoshop

Mac OS version:
10B504

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: MacPro4,1 (Mac-F221BEC8)

System uptime in nanoseconds: 19310018090769
unloaded kexts:
com.apple.driver.AppleIntel8254XEthernet 2.1.1b7 (addr 0x11b7000, size 0x118784) - last unloaded 82297387292
loaded kexts:
at.obdev.nke.LittleSnitch 2.2.05
com.apple.driver.AppleHWSensor 1.9.2d0 - last loaded 19047870001
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleMikeyHIDDriver 1.1.7
com.apple.driver.AppleTyMCEDriver 1.0.1d8
com.apple.driver.AGPM 100.8.15
com.apple.driver.AppleUpstreamUserClient 3.0.5
com.apple.driver.AppleHDA 1.7.4a1
com.apple.driver.AppleMikeyDriver 1.7.4a1
com.apple.GeForce 6.0.2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.1.0
com.apple.driver.AppleIntelNehalemProfile 11
com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a20
com.apple.driver.AppleLPC 1.4.6
com.apple.driver.AppleHIDKeyboard 1.1.5f1
com.apple.iokit.SCSITaskUserClient 2.5.1
com.apple.driver.AppleRAID 4.0.6
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleFWOHCI 4.3.4
com.apple.iokit.IOAHCIBlockStorage 1.5.0
com.apple.driver.AirPortBrcm43xx 410.91.20
com.apple.driver.Intel82574L 1.0.1b48
com.apple.driver.AppleUSBHub 3.7.8
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleAHCIPort 2.0.0
com.apple.driver.AppleUSBEHCI 3.7.5
com.apple.driver.AppleUSBUHCI 3.7.5
com.apple.driver.AppleRTC 1.3
com.apple.driver.AppleHPET 1.4
com.apple.driver.AppleACPIButtons 1.3
com.apple.driver.AppleSMBIOS 1.4
com.apple.driver.AppleACPIEC 1.3
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 90.0.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.0.11
com.apple.driver.AppleIntelCPUPowerManagement 90.0.0
com.apple.driver.AppleBluetoothHIDMouse 1.3.0f1
com.apple.driver.AppleHIDMouse 1.3.0f1
com.apple.driver.IOBluetoothHIDDriver 2.2.1f7
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.DspFuncLib 1.7.4a1
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.driver.AppleSMBusController 1.0.2d0
com.apple.nvidia.nv50hal 6.0.2
com.apple.NVDAResman 6.0.2
com.apple.iokit.IONDRVSupport 2.0
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.driver.AppleUSBAudio 2.6.4b15
com.apple.iokit.IOSurface 73.0
com.apple.iokit.IOGraphicsFamily 2.0
com.apple.iokit.IOBluetoothSerialManager 2.2.1f7
com.apple.iokit.IOSerialFamily 10.0.2
com.apple.iokit.IOAudioFamily 1.7.0fc16
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 1.7.4a1
com.apple.iokit.IOHDAFamily 1.7.4a1
com.apple.iokit.AppleProfileFamily 40
com.apple.driver.AppleSMC 3.0.1d2
com.apple.driver.IOPlatformPluginFamily 3.4.0a20
com.apple.driver.AppleSMBusPCI 1.0.2d0
com.apple.driver.BroadcomUSBBluetoothHCIController 2.2.1f7
com.apple.driver.AppleUSBBluetoothHCIController 2.2.1f7
com.apple.iokit.IOBluetoothFamily 2.2.1f7
com.apple.iokit.IOUSBHIDDriver 3.7.5
com.apple.driver.AppleUSBMergeNub 3.7.5
com.apple.driver.AppleUSBComposite 3.7.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.5.1
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOFireWireFamily 4.1.7
com.apple.iokit.IOAHCISerialATAPI 1.2.0
com.apple.iokit.IOSCSIArchitectureModelFamily 2.5.1
com.apple.iokit.IO80211Family 300.20
com.apple.iokit.IONetworkingFamily 1.8
com.apple.iokit.IOUSBUserClient 3.7.5
com.apple.iokit.IOAHCIFamily 2.0.0
com.apple.iokit.IOUSBFamily 3.7.8
com.apple.driver.AppleEFIRuntime 1.3.0
com.apple.iokit.IOHIDFamily 1.6.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 281
com.apple.iokit.IOStorageFamily 1.6
com.apple.driver.AppleACPIPlatform 1.3
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0

--------------------------------

second one:

Interval Since Last Panic Report: 96784 sec
Panics Since Last Report: 2
Anonymous UUID: 28391CE5-9D1D-4C1C-91F1-C9270B31234B

Mon Oct 26 21:10:16 2009
Machine-check capabilities (cpu 1) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 15
Intel(R) Xeon(R) CPU W3540 @ 2.93GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000800 invalid
IA32_MC1_STATUS(0x405): 0x0000000000000800 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0000000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0000000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0000000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0xfe1d86000001009f valid
Channel number: 15
System Profile:
Model: MacPro4,1, BootROM MP41.0081.B03, 4 processors, Quad-Core Intel Xeon, 2.93 GHz, 8 GB, SMC 1.39f5
Graphics: NVIDIA GeForce GT 120, NVIDIA GeForce GT 120, PCIe, 512 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en2
PCI Card: NVIDIA GeForce GT 120, Display, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: HL-DT-STDVD-RAM GH22NS30
Serial ATA Device: WDC WD3202ABYS-01B7A0, 298,09 GB
Serial ATA Device: WDC WD3202ABYS-01B7A0, 298,09 GB
Serial ATA Device: WDC WD6401AALS-00L3B2, 596,17 GB
Serial ATA Device: WDC WD6400AAKS-41H2B0, 596,17 GB
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd300000
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd320000
USB Device: Logitech Camera, 0x046d (Logitech Inc.), 0x09a6, 0xfa200000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000
FireWire Device: built-in_hub, Up to 800 Mb/sec

I desperately need help. If the problem persists I'll go and send my mac pro to apple for a fix....if they will be able to to help me......Hope they can solve the problem!

[MythicFrost]

You should contact Apple about this either via telephone or taking it in, I'd do the former as I don't like taking my computers into the store with any private data on my computer, they could look at it :eek:

This looks like a hardware problem to me, RAM, Processor maybe? I don't know.
I'd give Apple a call and get them to help you with it.

[Cindori]

run memtest for a day to see if your memory is bad, 95% chance it is.
if you give it to apple they are just gonna run memtest themselves anyway.

[massimike]

guys,
I replaced the OWC ram with the apple original ram and here it is :eek: :(
KP again:
Mon Nov 2 21:41:43 2009
Machine-check capabilities (cpu 1) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 15
Intel(R) Xeon(R) CPU W3540 @ 2.93GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000800 invalid
IA32_MC1_STATUS(0x405): 0x0000000000000800 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0000000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0000000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0000000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0xbe0000000001009f valid
Channel number: 15 (unknown)
Memory Operation: read
Machine-specific error: Read ECC
COR_ERR_CNT: 0
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC8_ADDR(0x422): 0x000000000bfa4940
IA32_MC8_MISC(0x423): 0x6ed2cef700081280
DIMM: 0
Channel: 2
Syndrome: 0x6ed2cef7
panic(cpu 0 caller 0x2a5c94): Machine Check at 0x012e0ea0, thread:0x80227a8, trapno:0x12, err:0x0,registers:
CR0: 0x8001003b, CR2: 0x126980f8, CR3: 0x00100000, CR4: 0x000006e8
EAX: 0x00000000, EBX: 0x00000000, ECX: 0xe00002c0, EDX: 0x00000000
ESP: 0x4d703930, EBP: 0x4d703ae8, ESI: 0x00000000, EDI: 0x4d70398c
EFL: 0x00000246, EIP: 0x012e0ea0

Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x819e18 : 0x21acfa (0x5ce650 0x819e4c 0x223156 0x0)
0x819e68 : 0x2a5c94 (0x590718 0x590805 0x12e0ea0 0x80227a8)
0x819f58 : 0x29d8d2 (0x1 0x0 0x0 0x0)
0x4d703ae8 : 0x12dd63f (0x7e19b00 0x4d703b1c 0x4d703b18 0x3cc9a247)
0x4d703f78 : 0x22f3e5 (0x7e19b00 0x0 0x0 0xbfffeaac)
0x4d703fc8 : 0x29c68c (0x863ec0 0x0 0x10 0x7fc1200)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AppleTyMCEDriver(1.0.1d8)@0x12db000->0x12e3fff
dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0x949000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x95d000
dependency: com.apple.driver.IOPlatformPluginFamily(3.4.0a20)@0xcd5000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
10B504

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: MacPro4,1 (Mac-F221BEC8)

System uptime in nanoseconds: 9553027537744
unloaded kexts:
com.apple.driver.IOFireWireSerialBusProtocolSansPhysicalUnit 2.5.0 (addr 0x104e000, size 0x8192) - last unloaded 1937238910510
loaded kexts:
at.obdev.nke.LittleSnitch 2.2.05
com.apple.driver.Oxford_Semi 2.5.0
com.apple.driver.AppleHWSensor 1.9.2d0
com.apple.driver.AppleMikeyHIDDriver 1.1.7
com.apple.driver.AppleTyMCEDriver 1.0.1d8
com.apple.driver.AGPM 100.8.15
com.apple.driver.AppleHDA 1.7.4a1
com.apple.driver.AppleUpstreamUserClient 3.0.5
com.apple.driver.AppleMikeyDriver 1.7.4a1
com.apple.filesystems.autofs 2.1.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.1.0
com.apple.driver.AppleIntelNehalemProfile 11
com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a20
com.apple.GeForce 6.0.2
com.apple.driver.AppleLPC 1.4.6
com.apple.driver.AppleHIDKeyboard 1.1.5f1
com.apple.driver.AppleRAID 4.0.6
com.apple.iokit.SCSITaskUserClient 2.5.1
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleFWOHCI 4.3.4
com.apple.iokit.IOAHCIBlockStorage 1.5.0
com.apple.driver.AirPortBrcm43xx 410.91.20
com.apple.driver.Intel82574L 1.0.1b48
com.apple.driver.AppleUSBHub 3.7.8
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleRTC 1.3
com.apple.driver.AppleAHCIPort 2.0.0
com.apple.driver.AppleUSBEHCI 3.7.5
com.apple.driver.AppleUSBUHCI 3.7.5
com.apple.driver.AppleHPET 1.4
com.apple.driver.AppleACPIButtons 1.3
com.apple.driver.AppleSMBIOS 1.4
com.apple.driver.AppleACPIEC 1.3
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 90.0.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.0.11
com.apple.driver.AppleIntelCPUPowerManagement 90.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice 2.5.1 - last loaded 1847820923562
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.0.0
com.apple.iokit.IOFireWireSBP2 4.0.5
com.apple.driver.AppleBluetoothHIDMouse 1.3.0f1
com.apple.driver.AppleHIDMouse 1.3.0f1
com.apple.driver.IOBluetoothHIDDriver 2.2.1f7
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.DspFuncLib 1.7.4a1
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.driver.AppleSMBusController 1.0.2d0
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.driver.AppleUSBAudio 2.6.4b15
com.apple.iokit.IOSurface 73.0
com.apple.iokit.IOBluetoothSerialManager 2.2.1f7
com.apple.iokit.IOSerialFamily 10.0.2
com.apple.iokit.IOAudioFamily 1.7.0fc16
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 1.7.4a1
com.apple.iokit.IOHDAFamily 1.7.4a1
com.apple.iokit.AppleProfileFamily 40
com.apple.driver.AppleSMC 3.0.1d2
com.apple.driver.IOPlatformPluginFamily 3.4.0a20
com.apple.driver.AppleSMBusPCI 1.0.2d0
com.apple.nvidia.nv50hal 6.0.2
com.apple.NVDAResman 6.0.2
com.apple.iokit.IONDRVSupport 2.0
com.apple.iokit.IOGraphicsFamily 2.0
com.apple.driver.BroadcomUSBBluetoothHCIController 2.2.1f7
com.apple.driver.AppleUSBBluetoothHCIController 2.2.1f7
com.apple.iokit.IOBluetoothFamily 2.2.1f7
com.apple.iokit.IOUSBHIDDriver 3.7.5
com.apple.driver.AppleUSBMergeNub 3.7.5
com.apple.driver.AppleUSBComposite 3.7.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.5.1
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOFireWireFamily 4.1.7
com.apple.iokit.IOAHCISerialATAPI 1.2.0
com.apple.iokit.IOSCSIArchitectureModelFamily 2.5.1
com.apple.iokit.IO80211Family 300.20
com.apple.iokit.IONetworkingFamily 1.8
com.apple.iokit.IOUSBUserClient 3.7.5
com.apple.iokit.IOAHCIFamily 2.0.0
com.apple.driver.AppleEFIRuntime 1.3.0
com.apple.iokit.IOUSBFamily 3.7.8
com.apple.iokit.IOHIDFamily 1.6.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 281
com.apple.iokit.IOStorageFamily 1.6
com.apple.driver.AppleACPIPlatform 1.3
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0

I think I need to bring my MP to apple support. I do not see any other solution as this could be a problem of logic board rather than video card or maybe airport extreme or the processor......Who knows???? I feel really disappointed and a bit worried. I would like to have my MP replaced but I think apple will not do it as they first replace the logic board and then maybe the processor.

[Dark Goob]

Hello-

I am having a similar error. But guess what the one thing that our two systems have in common is?

#1 > We both have a second LG optical drive in Bay 2
#2 > We both are running at.obdev.nke.LittleSnitch 2.2.05
#3 > We both are using external USB hubs and drives.
(are any of yours connected to the front ports?)

I get this error whenever I am burning to the second optical drive that's in bay 2. In my case it's an LG BH08LS20 BD-RW drive. But I am wondering if there is a power management issue that is involved. Do you have Toast installed?

[massimike]

Hello-

I am having a similar error. But guess what the one thing that our two systems have in common is?

#1 > We both have a second LG optical drive in Bay 2
#2 > We both are running at.obdev.nke.LittleSnitch 2.2.05
#3 > We both are using external USB hubs and drives.
(are any of yours connected to the front ports?)

I get this error whenever I am burning to the second optical drive that's in bay 2. In my case it's an LG BH08LS20 BD-RW drive. But I am wondering if there is a power management issue that is involved. Do you have Toast installed?

Ok I have LG drive too but not BD (I maybe use it a couple of times). Yes, I have toast but I use it when I burn CD/DVD ( maybe I burnt 1 dvd).
The problem could be related to the firewire drives:
1 wd book firewire 400 to firewire 800 ( connected to rear port)
1taurus enclosure firewire 800 (connected to rearport)
It is really unexpectable......

[strangeday]

Hi massimike,

I have a similar issue with my Mac Pro. I believe my issue with the kernal panics also has something to do with the RAM. Here's why:

Did you try installing your RAM cards into other slots? I tested this out before and one of my slots was not reading the OEM (original) RAM or the upgraded RAM from Crucial. I took my Mac Pro in to the Apple store, had the specialist check the RAM slots. He confirmed the problem and replaced the riser card (the part you slide the RAM into). We tested again, and the RAM was still not recognized in slot 2.

They now have to replace the "main logic board" :confused:

All of my RAM still shows installed and "OK" in slots 1, 3, 5, and 7 (temporary solution), but now (weeks later) I'm starting to get the kernal panics. I'm taking my machine in again today. Will report back in several days. Hopefully you are covered under warranty. My machine was just out of warranty, but luckily Apple is still covering everything. Good luck

[Dark Goob]

I wonder something: did any of you who are having these issues ever use the Migration Utility? Or does it have these errors from a total clean install also? Did you install Leopard first, and then upgrade to Snow, or did you install 10.6 fresh from a Snow Leopard install disc? I am thinking there could be some old driver or prefs that's causing the fans to let things overheat -- does your Mac Pro's fans make any small "knocking" or "ticking" sounds?

I am just wondering, because on another forum I saw that a user had fixed this issue by using SMCfancontrol (a 3rd-party utility) to force his fans to blow harder. Perhaps the RAM gets too hot, and fans don't blow hard enough, either from faulty temperature guages in the RAM or CPU, or faulty fan motors, somebody reporting incorrect RPMs or temps... Or a forced SMC reset should be tried but that won't fix a bad sensor in a RAM chip. The RAM would look fine to all utilities but would let itself overheat maybe. It always seems to be the DIMM in "Slot 0" which is at a spot of poor circulation perhaps? I was thinking of buying some clip-on RAM heat-sinks.

Another thing I noticed is that this always seems to happen to people who are booted into 32-bit kernel (forced-32-bit mode) but meanwhile even OS X 10.6 was defaulting into 64-bit when I installed it fresh, and Apple's site says Snow Leopard Server defaults to 64-bit on the early-2009 Mac Pros. Maybe there is simply an addressing error when you have 12GB of RAM and a 32-bit kernel... Does it still ge these errors if you are booted in forced-64-bit mode? I want to test that. No hardware will perform right if any process sends a 64-bit address to a 32-bit-only kernel.

But personally I do not pretend to understand kernel-related issues so I am really just purely speculating. I feel like it's going to be a real facepalmer, though, when we finally realize what caused this. BTW -- did you ever issue any terminal commands to set your bootup mode to 32-bit? Because in the "default" mode (which is supposed to be 32-bit) I think it loads both 32- an 64-bit kernels but the 32-bit is the main one, but some of the terminal commands will force the 64-bit one to not run at all, which maybe will not affect you till something tries to go past the 4GB barrier?

Just a wild guess...



On

[GLASSEYE22]

Hello thread,

I have also experienced a growing number of KPs on my old Dual 2.3 G5. I ran AHT, Rember, Tech Tools, Disc Warrior, all report OK. Swapped out ram for test and left out original 256 Apple pair, 8gb OWC remains. Removed all externals, still had panics. Another forum suggested to a fellow KP victim to make sure "processor performance" was on "highest" setting, not "automatic." Found under SYSTEM PREF/ENERGY SAVER/OPTIONS

I set mine on "highest" and have been KP free for a week, a record for this G5. This may be covering real problem but so far so good!

Ciao

[ildondeigiocchi]

Caro massimike,

La tua megliore soluzione sarebbe di chiamare applecare e parlare al ripresentante sul telefono spiegandoli il tuo problemo. E definitivamente qualche cosa di serio e al'ora sei in fortuna perche sei coperto dai servizi di Applecare. Non avere paura. Ti risolverano tutto. Scusa se non scrivo molto bene l'italiano... ma lo parlo meglio che lo scrivo (essendo un canadese di origine italiana).

ALL this is in ITALIAN so don't worry ppl lol :D

[massimike]

Caro massimike,

La tua megliore soluzione sarebbe di chiamare applecare e parlare al ripresentante sul telefono spiegandoli il tuo problemo. E definitivamente qualche cosa di serio e al'ora sei in fortuna perche sei coperto dai servizi di Applecare. Non avere paura. Ti risolverano tutto. Scusa se non scrivo molto bene l'italiano... ma lo parlo meglio che lo scrivo (essendo un canadese di origine italiana).

ALL this is in ITALIAN so don't worry ppl lol :D

Your italian is good, better than my english. I think I need to go through with this issue as this is really not that good! Thanks mate!

[massimike]

Hello thread,

I have also experienced a growing number of KPs on my old Dual 2.3 G5. I ran AHT, Rember, Tech Tools, Disc Warrior, all report OK. Swapped out ram for test and left out original 256 Apple pair, 8gb OWC remains. Removed all externals, still had panics. Another forum suggested to a fellow KP victim to make sure "processor performance" was on "highest" setting, not "automatic." Found under SYSTEM PREF/ENERGY SAVER/OPTIONS

I set mine on "highest" and have been KP free for a week, a record for this G5. This may be covering real problem but so far so good!

Ciao

Do you use your mac to do rendering as I do not. I do not think I am stressing a quad core processor 2.93 with photo retouching or even streaming with youtube.
I will try your setting and let you know.
thanks mate.

[flubber]

I'm experiencing the same problems with a Mac Pro Nehalem 2,66Ghz Quad core. I've read on apple discussions that the problem might be the processor tray.
I can regenerate the problem by encoding a movie or something, and doing a memory test with techtool pro. Techtool says that the ram is OK, but when you look at the kernel.log file in console, you see a whole list of errors. Besides, system profile shows "ecc-errors" for the third DIMM (the one the closest to the processor, the hottest one).
I can avoid the errors by using SMCfancontrol, but this doesn't look like a very good solution. A strange thing is that the fans always have the same (slow) speed, even if the computer is running very hot while encoding video. This looks like a firmware bug to me. Unfortunately, resetting the SMC didn't resolve the problem.
I think I'll visit the apple premium reseller tomorrow.

[Dark Goob]

I'm experiencing the same problems with a Mac Pro Nehalem 2,66Ghz Quad core. I've read on apple discussions that the problem might be the processor tray.
I can regenerate the problem by encoding a movie or something, and doing a memory test with techtool pro. Techtool says that the ram is OK, but when you look at the kernel.log file in console, you see a whole list of errors. Besides, system profile shows "ecc-errors" for the third DIMM (the one the closest to the processor, the hottest one).
I can avoid the errors by using SMCfancontrol, but this doesn't look like a very good solution. A strange thing is that the fans always have the same (slow) speed, even if the computer is running very hot while encoding video. This looks like a firmware bug to me. Unfortunately, resetting the SMC didn't resolve the problem.
I think I'll visit the apple premium reseller tomorrow.

Put heat spreaders on your DIMMs and hook up the computerto a UPS to make sure current fluctuations don't hose yr thirsty Pro.

[Infrared]

In 3 panic reports:


Memory Operation: read
Machine-specific error: Read ECC


From those reports:


Uncorrected error
DIMM: 0
Channel: 2



Uncorrected error
DIMM: 1
Channel: 2



Uncorrected error
DIMM: 0
Channel: 2


In one of those reports you have:


COR_ERR_CNT: 31720


Presumably that means "Corrected Error Count".

Google search:

http://www.google.co.uk/search?q=%22Machine-specific+error%3A+Read+ECC%22+%22mac+pro%22

[Techhie]

In 3 panic reports:



From those reports:







In one of those reports you have:



Presumably that means "Corrected Error Count".

Google search:

http://www.google.co.uk/search?q=%22Machine-specific+error%3A+Read+ECC%22+%22mac+pro%22

If you have already switched the modules around, my first guess would be a frayed gold connector on the slot. I would ask a genius about this, as good ram (especially ECC) is designed specifically to prevent errors.

[flubber]

Put heat spreaders on your DIMMs and hook up the computerto a UPS to make sure current fluctuations don't hose yr thirsty Pro.

Thanks for the suggestion, but I'm not going to try things out on my 6-months old mac pro. Such a machine should be working fine without adaptations. I just went to the Apple Premium Reseller. They told me that I need to get the RAM or the motherboard replaced.


Edit: I think I might have found the problem. I was able to regenerate the errors by running a lot of CPU-intensive processes.
On that moment, I took a look at the temperatures with hardware monitor. I saw that the cores of the Nehalem processor reached 78°C (174°F). The maximum temperature of the W3520 processor (mentioned on intel.com) is 67,9°C (154°F).
Since the memory controller is integrated in the Nehalem processors, it might be affected by the heath, which can cause memory problems.
It also explains why the problems immediately stop when I use SMCfancontrol.

[Dark Goob]

Thanks for the suggestion, but I'm not going to try things out on my 6-months old mac pro. Such a machine should be working fine without adaptations. I just went to the Apple Premium Reseller. They told me that I need to get the RAM or the motherboard replaced.


Edit: I think I might have found the problem. I was able to regenerate the errors by running a lot of CPU-intensive processes.
On that moment, I took a look at the temperatures with hardware monitor. I saw that the cores of the Nehalem processor reached 78°C (174°F). The maximum temperature of the W3520 processor (mentioned on intel.com) is 67,9°C (154°F).
Since the memory controller is integrated in the Nehalem processors, it might be affected by the heath, which can cause memory problems.
It also explains why the problems immediately stop when I use SMCfancontrol.

When I called AppleCare about this, their response was, "Reseat all your RAM."

I asked, "In the user manual, it shows heat spreaders (heat sinks) on all the memory. Do you think it's a good idea if I put heat spreaders at least on DIMM 0, the one reported in my panics?"

Their reply: "Yes."

I put a heat spreader on just DIMM 0, and I have not seen the temp rise over 64C, even encoding to AVCHD in Toast 10 which uses all the cores, AND running Second Life in the background with the heat of the GTX 285.

Also, when I reseated my RAM, I checked all the connections inside the machine especially to the optical drives, since I noticed many of us with this problem have multiple optical drives.

Another thing I did was to avoid using any software that might make pre-1.6 Java calls, such as Camino.

I also had the latest seed that came out the day after I reported these panics to Apple so it is possible that had something to do with it, though I cannot be certain since it makes no mention. It could also have just been from zapping PRAM and resetting SMC (when the ram was re-seated).

If a fan's power cable was loose don't you think that could affect their efficacy? Also the DIMMs that are closest to the outer door are not going to catch as much draft from the fans. That's why heat spreaders are so effective! Why do you think Apple shows the RAM with heat spreaders in the user manual itself? Y'know?

One last thing: what is the ambient temperature in your room?

[Dark Goob]

In one of those reports you have:
Presumably that means "Corrected Error Count".

Google search:

http://www.google.co.uk/search?q=%22Machine-specific+error%3A+Read+ECC%22+%22mac+pro%22

The ECC chips on the RAM could also be overheating. I just think the CPUs are much less likely to be the source of this, seeing as how they have giant industrial heat sinks on them while the RAM is sitting there roasting by the fire. I mean it's so cheap to put heat spreaders... Why not at least try it?

[flubber]

Today I'll bring the mac to an Apple premium resseller.
I've also thought about overheated dimms, but the errors start already at 36°C (97°F). The datasheet of the dimms says that they should still work fine at 70°C (158°F). Besides, hardware monitor shows the same temperatures for at least 2 of the 3 dimms, while only the dimm in slot 3 causes errors. (Also when I change places)

The CPU indeed has a giant heat spreader, but if the fans barely work, it can still overheat, I think. Especially when all the cores are being used for 100%
I also did reset the SMC, but it didn't matter. All the fans are properly connected, since I can see them work, and I can adjust their speed with SMCfancontrol.

Ambient temperature isn't abnormal. about 20°C when I turn the Mac Pro on, and about 24°C after an hour or two :)

(Besides, I didn't add an optical drive. I use the original configuration, with only 2 extra hard drives of 1TB)

[flubber]

Today I've been to the apple reseller. They told me the mac was fixed, so I asked what the problem was... They just replaced a RAM module. I had told them before that bank 3 was giving errors, and changing the place of the modules didn't solve this problem. So it was clear that the modules are fine...
So I asked if I could test the Mac Pro right away in the shop, which wasn't a problem for them. They even told me "Look, you're only running the same tests as we did".
After only two minutes, I was able to regenerate the errors. The Mac Pro is now AGAIN in for repair...

[Dark Goob]

Today I've been to the apple reseller. They told me the mac was fixed, so I asked what the problem was... They just replaced a RAM module. I had told them before that bank 3 was giving errors, and changing the place of the modules didn't solve this problem. So it was clear that the modules are fine...
So I asked if I could test the Mac Pro right away in the shop, which wasn't a problem for them. They even told me "Look, you're only running the same tests as we did".
After only two minutes, I was able to regenerate the errors. The Mac Pro is now AGAIN in for repair...


In my case, reversing the DIMMS changed the error from "Channel 2" to "Channel 0" ... so I am guessing for me, it is likely to be the module (maybe, its ECC chip?).

But one thing is, I am now told there are red LEDs on th dauhterboard itself, in the space between the two CPUs, next to each DIMM slot. If one of those lights turns on, it's a problem with the DIMM or that slot. Even if it passes Apple Hardware Tes and TechTool Pro, which mine do, the red light indicates a problem not detectable by those, he said — though he could not elaborate past that.

Another question I asked the AppleCare senior tech was, what order do you put differen brands of DIMMs in, if you have four of one brand, and two of another? Because I have four that I am guessing are factory RAM (Micron) and two that are from DMS, which is a Better Business Bureau A+ rated company. The DMS DIMMs are also sporting Micron chips, but the silicon color and wiring looks different than the other four modules).

Currently mine are like this:
(right front banks:)
4-empty
3-Apple
2-Apple
1-DMS
(left rear banks:)
5-DMS
6-Apple
7-Apple
8-empty

As my errors are now in Channel 0, which I *guess* corresponds to Slot 1 and/or 5, then one or both DMS chip(s) seem(s) to be the culprit... but wait. I asked him if the two DMS should be on the same side and he said yes, he reckoned they should both be on the same CPU, like this:

4-empty
3-Apple
2-DMS
1-DMS
(left rear banks:)
5-Apple
6-Apple
7-Apple
8-empty

Because if you just have 3 DIMMS it would be:

4-empty
3-Apple
2-DMS
1-DMS
(5-8 side empty)

I haven't had a chance to try it yet, nor to look for the red LEDs. I will check tonight and report back. This is such a weird issue.

Btw: what is the easiest way to cause the panic on yours?

[flubber]

I didn't see any leds burning next to the DIMM banks. I know there are some on the main board next to the SMC reset button, but they also didn't show any problems.
The problem also wasn't detectable by apple hardware test or techtool pro, but if you watch the kernel.log file during that test, you can see the dimm errors coming.

I can't easily regenerate the kernel panic, but I can regenerate the ECC-errors in the kernel.log file and in system profile.
To do that, I play and/or encode a high definition movie, run one or two benchmark tests at the same time, and do a memory test with techtool pro. This is quite CPU-intensive, so the errors start coming after about 2 minutes. The computer doesn't need to be turned on for hours in this case.

[Dark Goob]

I didn't see any leds burning next to the DIMM banks. I know there are some on the main board next to the SMC reset button, but they also didn't show any problems.
The problem also wasn't detectable by apple hardware test or techtool pro, but if you watch the kernel.log file during that test, you can see the dimm errors coming.

I can't easily regenerate the kernel panic, but I can regenerate the ECC-errors in the kernel.log file and in system profile.
To do that, I play and/or encode a high definition movie, run one or two benchmark tests at the same time, and do a memory test with techtool pro. This is quite CPU-intensive, so the errors start coming after about 2 minutes. The computer doesn't need to be turned on for hours in this case.

Hmm .. are ALL your DIMMs the same brand/model/size? Or do they vary? If so what positions are you putting them in? What DIMM errors do you get?

Thanks.

[flubber]

I'm using the original 3x 1GB from Apple, I have never touched them, and they are placed like they should (3: empty, 2: apple dimm, 1: apple dimm, 0: apple dimm).
The apple technician replaced the "defective" dimm, but it didn't make any difference. So it's clear to me that the problem isn't caused by the dimms, but the bank itsself is defective.
Now they are going to replace the processor tray, but not the processor. They said this was the last option.
So I told them about the built-in memory controller in the nehalem CPU, and successful stories on the internet about replacing the processor. He said that they didn't think about this, and that they should try it. Seems like they don't really know what they're doing, I have to tell them myself what they should do...

I don't know the exact errors in the kernel log (and the computer is now in for repair, so I can't check), but it was something like error on channel 0 dimm 2...
And System profile shows for dimm 3: ECC-errors.

[Dark Goob]

Switching my DIMMs around proved it to just be a faulty DIMM, because the Channel # in the panic changed. The Channel # refers to the DIMM slot. Channel 2 is Slots 3-4 and 5-6. Channel 1 is Slots 2 and 6. Channel 0 is Slots 1 and 5. It always reports DIMM 0 unless it was Channel 2 Slot 4 or 8, which I imagine could be DIMM 1 since that channel has two DIMMs per CPU.

The reason Slots 1 & 5 are both DIMM 0 is because it's the processor that is reporting this, an each processor only sees three Channels (0, 1, 2). How to isolate if it's the DIMMs is to reverse what order they are in and see if the channel # in the panic changes. You may also have to just swap the DIMMs in Slots 5 and 2, for instance, to see if a Channel 0 error was referring to Slot 1 or Slot 5 (it will change to Channel 1 if the bad DIMM was in Slot 5 and you move it to Slot 2; it will remain Channel 0 if it was in Slot 1).

In my case once I removed the bad DIMM, the panics went away even under the heaviest load testing. 10gb of RAM is still plenty for now.

[Dark Goob]

I'm using the original 3x 1GB from Apple, I have never touched them, and they are placed like they should (3: empty, 2: apple dimm, 1: apple dimm, 0: apple dimm).
The apple technician replaced the "defective" dimm, but it didn't make any difference. So it's clear to me that the problem isn't caused by the dimms, but the bank itsself is defective.
Now they are going to replace the processor tray, but not the processor. They said this was the last option.
So I told them about the built-in memory controller in the nehalem CPU, and successful stories on the internet about replacing the processor. He said that they didn't think about this, and that they should try it. Seems like they don't really know what they're doing, I have to tell them myself what they should do...

I don't know the exact errors in the kernel log (and the computer is now in for repair, so I can't check), but it was something like error on channel 0 dimm 2...
And System profile shows for dimm 3: ECC-errors.

Well which one did they replace? Because Channel 2 refers to Slot 3, the same one giving you the ECC errors. The text "DIMM 0" does NOT refer to Slot 1; it just refers to the first DIMM in Channel 2. And since you only have one DIMM on Channel 2 (because Slot 4 would be DIMM 1, Channel 2), therefore Slot 3 is where your problem lies.

Does the error happen if you test with just two DIMMs, in Slots 1 & 2? What happens if you test in Slots 1, 2, and 4? Sounds like your Slot 3 is bad if yes, and just let them swap your board. The CPU being defective would seem to me to make a much more random effect than just Channel 2 always where the error is.

[flubber]

Today, my mac pro was "repaired" for the second time. This was the error:
AppleTyMCEDriver ReadCorrectable: Detected 1 errors on channel 2 dimm 0 package 0

So system profile showed ECC errors for dimm 3.

The first time, they replaced dimm 3, with no effect. Now they changed the processor board (without the processor, while I insisted to replace it too). I came home with the computer (drove 50 miles for the third time), and AGAIN the ECC errors showed up after some CPU-intensive tasks.
I'm getting tired of this, but I think I've got no other option than taking it to the Apple Reseller again...

[massimike]

Today, my mac pro was "repaired" for the second time. This was the error:
AppleTyMCEDriver ReadCorrectable: Detected 1 errors on channel 2 dimm 0 package 0

So system profile showed ECC errors for dimm 3.

The first time, they replaced dimm 3, with no effect. Now they changed the processor board (without the processor, while I insisted to replace it too). I came home with the computer (drove 50 miles for the third time), and AGAIN the ECC errors showed up after some CPU-intensive tasks.
I'm getting tired of this, but I think I've got no other option than taking it to the Apple Reseller again...

Flubber I think we are on the same boat :(.
What I tried yesterday is testing the MP with a new fresh OS X installation. Only Apple s/w installed plus handbrake to stress the cpu.
After 5 mins of encoding plus safari with an youtube video KP appeared again.
The only thing I cannot understand is that I tried the test again and system appeared to be ok. As a matter of fact I noticed that KPs usually happened once and not a second time in same day session.
This will be pretty tough to sort the problem out even for apple repairer!!! :(:(:(
Really feel frightned. I would like my MP will be replaced :rolleyes:

[flubber]

I think you have to go through a lot of trouble before you receive a new Mac Pro...
You can look in the console (utilities) at the kernel.log file. In my case, I can see ECC errors showing up if the computer runs hot. So you might be able to see the KP coming.

I went to the Apple Reseller for the third time today. They actually just don't know what to do anymore (last time they said that a new processor board was the last possibility). So they decided to blame me. They never test the mac thoroughly, and if I test it (with movie encoding and benchmark tests), I can reproduce the errors after a few minutes. They told me that geekbench probably generates these errors and that I should come back when I have a real problem, or call Apple. The guy said that if he would run those heavy tests on his own macbook, it would also give some errors and that it was completely normal.
They also told me that the only thing they hadn't replaced was the processor. So I told them again about the built-in memory controller, and the guy just said that he "doesn't give a *****" about technical information because he wouldn't understand it :s
Anyway, I asked if I could test the Mac Pro in the shop, and this time with only movies, and not benchmark tests. After 15 minutes, the processor was at 82°C and the ECC errors showed up again, so I could prove them wrong for the third time. When I said that I had already driven 200 miles for a computer that still isn't fixed, the guy became angry. Quite funny because he shauted for a whole shop that it wasn't his fault that they couldn't fix my broken mac. Looks like they're getting quite desperate. The mac is now in for repair again... I think it deserves a soap :p

[massimike]

Hi guys,
Keep the fingers crossed, it seems I solve this problem out by replacing the CPU. I made some test and the machine now seems stable. I think now, after having read some post around, if the RAM is ok should fall on the CPU.
I will keep you informed. I really hope to be out of the nightmare.
Thanks to you all for your support and advices.
Cheers, Max.

[giffut]

... resetting the SMC: Turn off your Mac Pro, disconnect it from utility and press the startup button for about 10 seconds. Replug it and restart.

Do also a careful and throrough testing of your RAM slots. Start with one RAM bank test each of your modules; it takes some time, but it´s worth it.

If that doesn´t work, call for Apple help, because this is definitely a hardware problem - it´s now just to figure out, whether it´s temporary or permanent.

[VictorNT]

Recently I just upgrade to Leopard 10.5.8 using the 10.5.1 disk retail (archive and install) and adding the Time Capsule. Since this day I have an average 2/3 times KPs per week (mostly during the night when the machine is in sleep mode ?!? - the machine fans make big noise when it got KPs).

I have tried:
1) Reinstall a clean 10.5.8 (archive and install)
2) Eliminate all start-up items
3) Reset PRAM
4) Turn the Time Machine off
5) Do all tests with TechTool Deluxe and Rember (loop test on RAMs)
6) Repair permissions (using Disk Utility on the install disk) but there are always a lot of stuff... According to Apple you can safely ignore those messages:confused:

At this point I have 2 options in my mind:
a. Going back to Tiger :(
b. Looking a new Intel machine :confused:

One more thing: Since I upgrade to Leopard, it seems that the machine is not really in sleep mode (I still hear the fans). I have to force The machine entering into the sleep mode using the sleep command from main menu.

Thanks for any suggestions !

[Washac]

Recently I just upgrade to Leopard 10.5.8 using the 10.5.1 disk retail (archive and install) and adding the Time Capsule. Since this day I have an average 2/3 times KPs per week (mostly during the night when the machine is in sleep mode ?!? - the machine fans make big noise when it got KPs).

I have tried:
1) Reinstall a clean 10.5.8 (archive and install)
2) Eliminate all start-up items
3) Reset PRAM
4) Turn the Time Machine off
5) Do all tests with TechTool Deluxe and Rember (loop test on RAMs)
6) Repair permissions (using Disk Utility on the install disk) but there are always a lot of stuff... According to Apple you can safely ignore those messages:confused:

At this point I have 2 options in my mind:
a. Going back to Tiger :(
b. Looking a new Intel machine :confused:

One more thing: Since I upgrade to Leopard, it seems that the machine is not really in sleep mode (I still hear the fans). I have to force The machine entering into the sleep mode using the sleep command from main menu.

Thanks for any suggestions !

I bought my Mac Pro in June/July last year and all was well until I upgraded to Snow Leopard. I have since followed all the updates and
still would get a KP about once maybe twice a week. The panic always pointed towards DIMM 0 CANN 2 which is Slot 3.

Have dine all the memory testing and hardware testing and nothing has been thrown up, so assume that all my memory sticks are OK.
Somebody did mention it could be a specific memory call that causes the KP and maybe would,nt show up under test conditions.

I have since removed the mem stick in Slot 3 and for the last three weeks no KPs.

[VictorNT]

Thanks for the info. Unfortunately KP log for PowerPC machines don't have info related to the RAM. However, in my case, it ALWAYS pointed to the CPU #2 :mad:

Here is my recent KP log:

Unresolved kernel trap(cpu 2): 0x700 - Program DAR=0x0000000013C54000 PC=0x0000000000460000
Latest crash info for cpu 2:
Exception state (sv=0x4b8eea00)
PC=0x00460000; MSR=0x00089030; DAR=0x13C54000; DSISR=0x40000000; LR=0x00460000; R1=0x4B2635B0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00460000
backtrace terminated - unaligned frame address: 0x0000000E

Proceeding back via exception chain:
Exception state (sv=0x4b8eea00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x4136e780)
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:
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: 160084607478553
unloaded kexts:
(none)
loaded kexts:
com.apple.filesystems.msdosfs

[massimike]

I bought my Mac Pro in June/July last year and all was well until I upgraded to Snow Leopard. I have since followed all the updates and
still would get a KP about once maybe twice a week. The panic always pointed towards DIMM 0 CANN 2 which is Slot 3.

Have dine all the memory testing and hardware testing and nothing has been thrown up, so assume that all my memory sticks are OK.
Somebody did mention it could be a specific memory call that causes the KP and maybe would,nt show up under test conditions.

I have since removed the mem stick in Slot 3 and for the last three weeks no KPs.

I've been told by the technician who took care of my mac that he went through and replace the CPU as the dimm could respond badly when CPU failed, he said that they are related and since the RAM was ok in his opinion the best way to overcome the problem was that one of the cpu replacement.

Giffut:
I don't know if you related to me when saying to test the machine by restarting it and resetting SMC. Actually since I have the CPU replaced the problem seems desappeared.

[VictorNT]

Do you know a good tool to test the CPUs ?

[massimike]

OH NOOOOOOO!!!!!!! KP AGAIN :eek::eek::eek::eek:
I cannot belive! After having left my beloved MP at the Apple repairer for at least more than one month, when yesterday I was converting a video to into mp4 with Handbrake to put it on my iPhone, that damned KP show up again. Tonight when I am back home I squeeze it again and I'll see. After that I really do not know what to do!!!!! HELP ME! :confused:

[Washac]

OH NOOOOOOO!!!!!!! KP AGAIN :eek::eek::eek::eek:
I cannot belive! After having left my beloved MP at the Apple repairer for at least more than one month, when yesterday I was converting a video to into mp4 with Handbrake to put it on my iPhone, that damned KP show up again. Tonight when I am back home I squeeze it again and I'll see. After that I really do not know what to do!!!!! HELP ME! :confused:

Sorry to hear this news.

As I posted before my KP always pointed towards DIMM 0 CANN 2 which is Slot 3.

It was suggested by somebody to remove the Mem stick in that slot, which I
have done.

I did have three 1GB mem sticks, I have since replaced them all with two 2GB mem sticks in slots 1 and 2.
As of several weeks ago I have as yet not had another KP :)

[massimike]

Sorry to hear this news.

As I posted before my KP always pointed towards DIMM 0 CANN 2 which is Slot 3.

It was suggested by somebody to remove the Mem stick in that slot, which I
have done.

I did have three 1GB mem sticks, I have since replaced them all with two 2GB mem sticks in slots 1 and 2.
As of several weeks ago I have as yet not had another KP :)

I already have sticks of 2gb each for the 4 all slots. Still painful to upgrade with 4gb stick fr all slots, but this will be my next step. In Italy there is no OWC and 4gb sticks ram cost a fortune. The only way is to buy the ram and to have them send them to me but custom duty are pretty high. So wait for someone going to USA and buy me those pieces of jewellery.

[Washac]

I already have sticks of 2gb each for the 4 all slots. Still painful to upgrade with 4gb stick fr all slots, but this will be my next step. In Italy there is no OWC and 4gb sticks ram cost a fortune. The only way is to buy the ram and to have them send them to me but custom duty are pretty high. So wait for someone going to USA and buy me those pieces of jewellery.

Sorry did not explain that very well.

I had a 1GB Mem stick in slot 1, 2 and three...

Because my KPs always pointed towards DIMM 0 CHANN 2 which is slot 3 I removed the Mem stick in slot three. Using only slots 1 and 2 things stablised over several weeks with no KPs

I now have a 2GB Mem stick in slot 1 and the same in slot 2.

I have nothing in slots 3 or 4.

So seem to have stopped my KPs, now have to find out if it was the 1GB Mem stick which was in slot 3 or a problem with the slot itself.

Might just leave it seeing as at the moment things seem stable with no KPs, fingers crossed.

[massimike]

Sorry did not explain that very well.

I had a 1GB Mem stick in slot 1, 2 and three...

Because my KPs always pointed towards DIMM 0 CHANN 2 which is slot 3 I removed the Mem stick in slot three. Using only slots 1 and 2 things stablised over several weeks with no KPs

I now have a 2GB Mem stick in slot 1 and the same in slot 2.

I have nothing in slots 3 or 4.

So seem to have stopped my KPs, now have to find out if it was the 1GB Mem stick which was in slot 3 or a problem with the slot itself.

Might just leave it seeing as at the moment things seem stable with no KPs, fingers crossed.

Why not to ask Apple to replace the card where the ram resides. Because is not that fair to have to slots out of order!

[Washac]

Why not to ask Apple to replace the card where the ram resides. Because is not that fair to have to slots out of order!

Yes I know what you are saying but I have read of people having every board changed that can be changed and the CPU and still they get the KPs.

On the slot front I have enough memory for my needs at the moment.