panic (cpu 3 ... "Machine Check at ....; and next day: panic (cpu 1 ... "TBL invalidation IPI timeout ...

Question

Panic twice within 30 hours grey screen content follows:panic (cpu 3 caller... "Machine Check at .... etc.Kernel Extensions in backtrace:     com.apple.driver.AppleIntelCPUPowerManagement (217.92.1) ...... etcMac OS version: 13F34 etcSystem model name: MacPro3.1 (Mac-F42C88C8)panic (cpu 1 caller .... "TBL invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x8 etcKernel Extension in backtrace:     com.apple.AppleFSCompression.AppleFSCompressionTypeZlib(1.0d1) etcMac OS version: 13F34 etcSystem model name: MacPro3.1 (Mac-F42C88C8)I have grey screen photos if needed, I do not know if System does or can log these occurrences.My Memory (RAM) lists ok in the System Information panel. An extended diagnostics run after the first instance listed no problems.Any ideas what is causing the grey screen panics. I have had also plenty of other problems last few weeks leading to recoveries as well as adding extra hard drive.  What worries me is Mavericks as most of my recent problems seem to have poppet up since going Mavericks, currently on 10.9.5Following is partial MiniProfile ex OnyX:Hardware:    Hardware Overview:      Model Name: Mac Pro      Model Identifier: MacPro3,1      Processor Name: Quad-Core Intel Xeon      Processor Speed: 2.8 GHz      Number of Processors: 2      Total Number of Cores: 8      L2 Cache (per Processor): 12 MB      Memory: 8 GB      Bus Speed: 1.6 GHz      Boot ROM Version: MP31.006C.B05      SMC Version (system): 1.25f4Memory:    Memory Slots:      ECC: Enabled      Upgradeable Memory: Yes        DIMM Riser B/DIMM 1:          Size: 2 GB          Type: DDR2 FB-DIMM          Speed: 800 MHz          Status: OK          Manufacturer: 0x0000          Part Number: 0x000000463732353642363145353830304600        DIMM Riser B/DIMM 2:          Size: 2 GB          Type: DDR2 FB-DIMM          Speed: 800 MHz          Status: OK          Manufacturer: 0x0000          Part Number: 0x000000463732353642363145353830304600        DIMM Riser A/DIMM 1:          Size: 2 GB          Type: DDR2 FB-DIMM          Speed: 800 MHz          Status: OK          Manufacturer: 0x02BA          Part Number: 0x202020202020202020202020202020202020        DIMM Riser A/DIMM 2:          Size: 2 GB          Type: DDR2 FB-DIMM          Speed: 800 MHz          Status: OK          Manufacturer: 0x02BA          Part Number: 0x202020202020202020202020202020202020        DIMM Riser B/DIMM 3:          Size: Empty          Type: Empty          Speed: Empty          Status: Empty          Manufacturer: Empty          Part Number: Empty        DIMM Riser B/DIMM 4:          Size: Empty          Type: Empty          Speed: Empty          Status: Empty          Manufacturer: Empty          Part Number: Empty        DIMM Riser A/DIMM 3:          Size: Empty          Type: Empty          Speed: Empty          Status: Empty          Manufacturer: Empty          Part Number: Empty        DIMM Riser A/DIMM 4:          Size: Empty          Type: Empty          Speed: Empty          Status: Empty          Manufacturer: Empty          Part Number: EmptyNetwork:    Ethernet 1:      Type: Ethernet      Hardware: Ethernet      BSD Device Name: en0      Service Order: 0    Wi-Fi:      Type: AirPort      Hardware: AirPort      BSD Device Name: en2      Service Order: 1    Bluetooth PAN:      Type: Ethernet      Hardware: Ethernet      BSD Device Name: en3      Service Order: 2    Ethernet 2:      Type: Ethernet      Hardware: Ethernet      BSD Device Name: en1      Service Order: 3    FireWire:      Type: FireWire      Hardware: FireWire      BSD Device Name: fw0      Service Order: 4PCI Cards:    ATI Radeon HD 5770:      Name: ATY,Hoolock      Type: Display Controller      Driver Installed: Yes      MSI: Yes      Bus: PCI      Slot: Slot-1      Vendor ID: 0x1002      Device ID: 0x68b8      Subsystem Vendor ID: 0x106b      Subsystem ID: 0x00cf      Revision ID: 0x0000      Link Width: x16      Link Speed: 5.0 GT/s    ATI Radeon HD 5770:      Name: ATY,HoolockParent      Type: ATY,HoolockParent      Driver Installed: No      MSI: No      Bus: PCI      Slot: Slot-1      Vendor ID: 0x1002      Device ID: 0xaa58      Subsystem Vendor ID: 0x106b      Subsystem ID: 0xaa58      Revision ID: 0x0000      Link Width: x16      Link Speed: 5.0 GT/s

Grant Bennet-Alder · Answer

I do not know if System does or can log these occurrences.Yes, it does, and this article tells you how to find the complete report:Mac OS X: How to log a kernel panicmachine check, code 4 or 5, multiple processors detecting it, often occurring in CPU power management, correlates with RAM Memory Errors in the Mac Pro tower and cylinder with Error Correcting Code memory. It does not occur in Macs without Hardware error correction. It would be nice if RAMs would just fall over dead when this happens, but that is almost never the case, and isolating the problem can be very difficult.TLB invalidation timeout is a multi-processor co-operation problem and can involve both CPU and GPU processors, but the full report will tell more.

 · Answer

Hi Grant,thanks for quick response. It seems that a Grey Screen on stratup saying "panic (cpu 3 caller ..." or "panic (cpu 1 caller ..." does not log as described in your reference. This makes sense to me because the system hasn&#x27;t done anything as yet except finding a serious fault? I am not dealing with an abort caused by any app or a sudden message requesting a restart.The Grey Screen display makes reference to Kernel Extensions in backtrace: in both cases different values and maybe hinting to a possible cause.Am I seeing this the wrong way?SigiPCook

Grant Bennet-Alder · Answer

Copy the kernel panic report into a reply frame on the forum and post it in its entirety.

 · Answer

Hi Grant,Thanks for coming back again. There is no panic dump in any of the logs and so it was not a matter of copy but transcribe but here it is. In the meantime the system has behaved itself ; no more panic. It may not be enough to nail down the cause, but I might mention that in previous runtimes (the day before) ViewNX 2 (a Nikon product) gave me plenty hangs. Could that have carried over to the next day and after a new startup (booting)?Following is the transcribed panic message from the grey screen and system stop:panic (cpu 3 caller 0xffffff80140dccc0) : “machine Check at 0xffffff7f959440878, registers: 
” “CRO: 0x000000008001003n,CR2: 0x000000010cd7c000, CR3: 0x0000000016d7e000, CR4: 0x0000000000000660
” “RAX: 0x0000000c637909e9, RBX: 0x0000Debugger called: &lt;panic&gt;Backtrace (CPU 3), Frame : Return Address0xffffff811783de80 : 0xffffff8014022f790xffffff811783df80 : 0xffffff80140dccc90xffffff811783e060 : 0xffffff80140f421f0xffffff8120b53d40 : 0xffffff7f9594094f0xffffff8120b53d80 : 0xffffff7f9593a2610xffffff8120b53e70 : 0xffffff7f959398d90xffffff8120b53f30 : 0xffffff80140ddcfc0xffffff8120b53f50 : 0xffffff801403758a0xffffff8120b53f90 : 0xffffff80140378d80xffffff8120b53fb0 : 0xffffff80140d7607      Kernel Extension in backtrace:        com.apple.driver.AppleIntelCPUPowerManagement(217.92.1) [1A9E8072-CBF3-39C2-8514-B8176259D3D7]@0xffffff7f95937000-&gt;0xffffff7f95961fffBSD process name corresponding to current thread: kernel_taskMac OS version:13F34Kernel version:Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64Kernel UUID: 9477416E-7BCA-3679-AF97-E1EAAD3DD5A0Kernel slide:     0x0000000013e00000Kernel text base: 0xffffff8014000000System model name: MacPro3.1 (Mac-F42C88C8)System uptime in nanoseconds: 53864504809

Grant Bennet-Alder · Answer

Kernel Panic, machine check, similar to the reports you have posted are likely to be caused by uncorrectable double-bit RAM memory errors. These double-bit errors are intended to cause a kern ale panic and halt the machine to avoid poisoning your data. In many cases, correctable errors have been accumulating before these occur. The Mac Pro features Error Correction Code memory. Single-bit errors are detached and corrected by Hardware with no slowdown, and an error indicator is set so that the error can be noted by a background process. These errors are tabulated in a report that can be read out whenever you please. it looks like this:About this Mac &gt; (More info ) &gt; Report &gt; MemoryThe information in this report is STATIC. If you want updated information, invoke the report again or choose File &gt; RefreshSo to find memory errors in a Mac Pro, go about your business as usual. From time-to-time invoke that report. DIMMs that are incurring memory errors need to be replaced.

 · Answer

Hi Grant,thanks so much, now I know what is happening.One more question: for what time period is the error accumulation in the System Report kept?As there are no errors reported on any of my DIMMs I assume they are only kept for some time and then get cleared.If a DIMM is faulty I would get a warranty replacement (I bought with life warranty).Greedy? retired people count the pennies!Thanks againSigi

Grant Bennet-Alder · Answer

Those error counters are cleared at Startup. (only)

Grant Bennet-Alder · Answer

For an error that may occur only once a day, and only under certain circumstances, you may have to wait for quite a while for it to happen again.It sure would be nice if memory modules would fall down dead once they made an error, but that is not the nature of these problems. It takes a while of careful watching to &#x27;catch it in the act&#x27;.