F5F Stay Refreshed Hardware Desktop System crash detected, kernel error occurring.

System crash detected, kernel error occurring.

System crash detected, kernel error occurring.

T
therealboss13
Member
Find
161
06-01-2018, 10:35 PM
#1
I received a 2018 MacBook Air that has been experiencing Kernel panics after being dropped quite hard. It operates for roughly five minutes before shutting down completely. I attempted a full factory reset and installed a fresh OS from a reliable boot source, but the issue persisted. Based on what I understand, Kernel panics can stem from the CPU, RAM, or hard drive. Since this model lacks removable RAM or hard drive, I replaced the logic board. The new board matched the old one exactly, including the Kernel panic problem. Further investigation revealed that in older Macs, the battery could sometimes be responsible. After testing, I confirmed the battery isn’t the cause. Now I’m curious—what could be behind these crashes? Can any component trigger a Kernel panic? I thought they mainly affected data handling and resource management, linked to the hard drive, RAM, or logic board. Is that accurate? The error message shows "cpu 1 caller 0xfffffff0191d3578" and "Kernel Version: Darwin Version 22.1.0." Please let me know if you need more details.
Reply
Reply
T
therealboss13
06-01-2018, 10:35 PM #1

I received a 2018 MacBook Air that has been experiencing Kernel panics after being dropped quite hard. It operates for roughly five minutes before shutting down completely. I attempted a full factory reset and installed a fresh OS from a reliable boot source, but the issue persisted. Based on what I understand, Kernel panics can stem from the CPU, RAM, or hard drive. Since this model lacks removable RAM or hard drive, I replaced the logic board. The new board matched the old one exactly, including the Kernel panic problem. Further investigation revealed that in older Macs, the battery could sometimes be responsible. After testing, I confirmed the battery isn’t the cause. Now I’m curious—what could be behind these crashes? Can any component trigger a Kernel panic? I thought they mainly affected data handling and resource management, linked to the hard drive, RAM, or logic board. Is that accurate? The error message shows "cpu 1 caller 0xfffffff0191d3578" and "Kernel Version: Darwin Version 22.1.0." Please let me know if you need more details.

Reply
Reply
1
101PINGO
Member
Find
154
06-10-2018, 03:10 AM
#2
Inspect your thermal layers. The drop might have damaged the heatpipe section of the cooler.
Reply
Reply
1
101PINGO
06-10-2018, 03:10 AM #2

Inspect your thermal layers. The drop might have damaged the heatpipe section of the cooler.

Reply
Reply
W
wert30
Member
Find
62
06-14-2018, 02:25 AM
#3
That’s the one where the heat sink isn’t linked to the fan at all. Still worth looking into.
Reply
Reply
W
wert30
06-14-2018, 02:25 AM #3

That’s the one where the heat sink isn’t linked to the fan at all. Still worth looking into.

Reply
Reply
A
alerabbit
Posting Freak
Find
840
06-30-2018, 10:02 PM
#4
Are you referring to the fans being connected to the logic board and the top case, or is it about the heat sink linking to the CPU? Also, your code appears identical on both the old and new boards—why would that happen? I’ll look into it, thank you.
Reply
Reply
A
alerabbit
06-30-2018, 10:02 PM #4

Are you referring to the fans being connected to the logic board and the top case, or is it about the heat sink linking to the CPU? Also, your code appears identical on both the old and new boards—why would that happen? I’ll look into it, thank you.

Reply
Reply
L
LFPC
Member
Find
98
07-05-2018, 08:51 PM
#5
The usual operating temperature ranged from the lowest 55°C to the highest 67°C. It wasn’t perfect, but it stayed within acceptable bounds. The Panic code shifted to a specific instruction set: "cpu 0 caller 0xffffff 01e1ab578." This change adds to the confusion—why do kernel panics alter their codes? It’s not uncommon for such updates.
Reply
Reply
L
LFPC
07-05-2018, 08:51 PM #5

The usual operating temperature ranged from the lowest 55°C to the highest 67°C. It wasn’t perfect, but it stayed within acceptable bounds. The Panic code shifted to a specific instruction set: "cpu 0 caller 0xffffff 01e1ab578." This change adds to the confusion—why do kernel panics alter their codes? It’s not uncommon for such updates.

Reply
Reply