Benches MacBooks

5

Kernel Panic under heavy load

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

MacBook Pro 15" touchbar, MacOS Mojave. I get KP under high cpu and/or memory load (e.g. PHPStorm indexing several projects or Chrome loading many pages). Started maybe a week ago. What can cause this problem? Memory problems? Or PHPStorm itself?

Anonymous UUID:       CF9C5FCD-C55B-3EF9-7289-BD0CAB91FB60

Thu Dec 13 17:19:38 2018

*** Panic Report ***
panic(cpu 1 caller 0xffffff800c400601): "a freed zone element has been modified in zone ksyn_wait_queue: expected 0 but found 0, bits changed 0, at offset 0 of 328 in element 0xffffff805608b000, cookies 0x3f00117b9722e460 0x535213728646133"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.221.2/osfmk/kern/zalloc.c:1168
Backtrace (CPU 1), Frame : Return Address
0xffffff80247f3980 : 0xffffff800c3aca9d 
0xffffff80247f39d0 : 0xffffff800c4e6893 
0xffffff80247f3a10 : 0xffffff800c4d82ba 
0xffffff80247f3a80 : 0xffffff800c359ca0 
0xffffff80247f3aa0 : 0xffffff800c3ac4b7 
0xffffff80247f3bc0 : 0xffffff800c3ac303 
0xffffff80247f3c30 : 0xffffff800c400601 
0xffffff80247f3c90 : 0xffffff800c3ffde4 
0xffffff80247f3ce0 : 0xffffff800c3fe7bd 
0xffffff80247f3e10 : 0xffffff7f8efe1434 
0xffffff80247f3e90 : 0xffffff7f8efe38a3 
0xffffff80247f3f00 : 0xffffff800c86ffcc 
0xffffff80247f3f40 : 0xffffff800c9b5aab 
0xffffff80247f3fa0 : 0xffffff800c35a466 
      Kernel Extensions in backtrace:
         com.apple.kec.pthread(1.0)[773007A1-C7A7-3BC1-AEFF-783C4573D21F]@0xffffff7f8efdf000->0xffffff7f8efe8fff

BSD process name corresponding to current thread: phpstorm


🔧 Closest iFixit match: MacBook Pro 13" Two Thunderbolt Ports 2016-2019
Take-apart guides & videos on iFixit →
Double-check this is your exact model before ordering parts.

5 replies

Sign in or join Beachball Help to reply.

  1. 0

    Grant Bennet-Alder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You have kernel panics "all over the Map". This non-Trend correlates strongly with RAM memory problems (except in Mac Pro with Xeon processor and error-correcting code ECC memory).

    The reason for this is that MacOS slightly randomizes the load address of key routines, effectively "shuffling" the Memory Map on each restart. This is done as a hedge against fixed address malware attacks. The Bad Memory cell then appears in a different routine after each restart, and the symptom changes each time.

    Unfortunately, the "fix" is likely to be a mainboard exchange, and the Memory AND Boot drive components in TouchBar Macs are soldered to the mainboard. You are unlikely to get your files back during routine service. If you do not have and can not make a backup, be sure to discuss all options for Apple to copy your files for you. There may be an extra charge for this service, if they can even do it at all.

    You will need to make a complete backup before submitting your Mac for service. Some would suggest two backups by different means.

    Apple takes steps to protect your old information during service, and the drive will be completely erased if the board is refurbished and re-used as a spare part.

  2. 0

    terion.name

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    After further observations It seems to be related to phpstorm. Version 2018.3.1 is breaking my system constantly, 2018.2.5 under more heavy load. Log:

    Still it is not clear, phpstorm causes this issue, or it's heavy memory/cpu usage triggers an issue lying deeper in system or hardware

  3. 0

    terion.name

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Another panic, Graphics firmware encountered an exception. What is going on?(

  4. 0

    Grant Bennet-Alder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You have kernel panics "all over the Map". This non-Trend correlates strongly with RAM memory problems (except in Mac Pro with Xeon processor and error-correcting code ECC memory).

    The reason for this is that MacOS slightly randomizes the load address of key routines, effectively "shuffling" the Memory Map on each restart. This is done as a hedge against fixed address malware attacks. The Bad Memory cell then appears in a different routine after each restart, and the symptom changes each time.

    Unfortunately, the "fix" is likely to be a mainboard exchange, and the Memory AND Boot drive components in TouchBar Macs are soldered to the mainboard. You are unlikely to get your files back during routine service. If you do not have and can not make a backup, be sure to discuss all options for Apple to copy your files for you. There may be an extra charge for this service, if they can even do it at all.

    You will need to make a complete backup before submitting your Mac for service. Some would suggest two backups by different means.

    Apple takes steps to protect your old information during service, and the drive will be completely erased if the board is refurbished and re-used as a spare part.

  5. 0

    terion.name

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Oh. Can't say that I'm happy with your answer, but thank you anyway :(