Greetings,
Not once since I have owned my 2018 MacBook Pro (see sig for details) has it ever crashed... until yesterday, after I updated to OS X 10.14.4. Since the update, I had two crashes in one day. What did I do to fix the problem? I turned off FileVault. Stable. As a test, I turned FileVault back on... crashed within 2 hours. Turned FileVault off, stable.
It is important to note that FileVault has been on on my computer ever since new. The recent update appears to have broken my system. I tried to use console to view the coredump, but could not locate the actual crash. A quick search revealed the issues with the T2 chip related to FileVault, which is why I disabled it immediately.
If I wanted to view the actual coredump, where would I find it in the log files? In the past, I simply searched all the logs for the coredump, but something appears to have changed in the way OS X reports coredumps.
Joe
Not once since I have owned my 2018 MacBook Pro (see sig for details) has it ever crashed... until yesterday, after I updated to OS X 10.14.4. Since the update, I had two crashes in one day. What did I do to fix the problem? I turned off FileVault. Stable. As a test, I turned FileVault back on... crashed within 2 hours. Turned FileVault off, stable.
It is important to note that FileVault has been on on my computer ever since new. The recent update appears to have broken my system. I tried to use console to view the coredump, but could not locate the actual crash. A quick search revealed the issues with the T2 chip related to FileVault, which is why I disabled it immediately.
If I wanted to view the actual coredump, where would I find it in the log files? In the past, I simply searched all the logs for the coredump, but something appears to have changed in the way OS X reports coredumps.
Joe
