My MBP, 2018, has since a couple of months back started to crash. It happens sometimes a few times in a row and sometimes it works for a couple of hours before it happens.
When checking the crash logs it says kernel. Is there anything else to do than to hand it in for repair? Since it´s getting old it might not be worth it really.
Including the etrecheck report below.
[Re-Titled by Moderator]
MacBook Pro 13″, macOS 14.6
your EtreCheckPro report says panics have occurred. but can not pinpoint exactly WHY. That will need a real panic report.
Kernel Panic Reports are stored in the Folder at:
/Library/Logs/DiagnosticReports
If you copy and paste that string into:
Finder > Go menu > Go to Folder
it will take you to the Folder where those reports are stored.
Kernel panic reports are named with Date&Time and start or end in ‘panic’
If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).
Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.
your EtreCheckPro report says panics have occurred. but can not pinpoint exactly WHY. That will need a real panic report.
Kernel Panic Reports are stored in the Folder at:
/Library/Logs/DiagnosticReports
If you copy and paste that string into:
Finder > Go menu > Go to Folder
it will take you to the Folder where those reports are stored.
Kernel panic reports are named with Date&Time and start or end in ‘panic’
If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).
Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.
The issues you are encountering are VERY obscure. it is possible MacOS is calling the debugger in working MacOS system code, for issues that simply "can not be happening".
It is possible that if the Bad VM Page Queue report is accurate. In that case, the underlying issue may be a festering RAM memory problem. This code has been thumped on in daily use in millions of situations for decades, and absent genuine Hardware issues like RAM memory errors, it is vanishingly unlikely to be a newly discovered bug, found only by you.
First, you should 'go through the motions' by running the user diagnostic, but it is unlikely to find a problem. IF it does find a problem, save, and preferably PRINT the report. The user diagnostic generally finds GROSS errors, and its 'success' error code means no faults detected in the limited time allowed, and does NOT mean "All is well".
if you present your Mac at the Genius Bar, without a reliable way to induce the problem, they will fiddle with it for a while and likely return it to you, un-repaired. Genius Bar technicians are NOT trained to read panic reports, so they will not likely attempt to do so. Having them get on the Phone to Apple Support for help while you are still standing in the store can take quite a while, and can be tedious.
Next step is to contact Apple support, directly, and point them to this public discussion. They can read the information posted, but they never take our conclusions for granted. They have their own more rigorous methods.
First responders have a checklist of things to try. Be polite and professional and follow their recommendations, EXCEPT: DO NOT ERASE your Mac, because that will ERASE all the saved panic reports, which [in my opinion] include several very important "smoking gun" calibre reports. Deliberately ASK for a specialist to read your panic reports. If they see an issue, they can DIRECT an Apple Service Provider to change your mainboard. (The actual repair cost will likely be yours to bear unless under warranty or AppleCare PLUS.)
¿What is the date of your most recent backup, and by what method? If the mainboard is replaced, your files will NOT be returned to you.
nest step is to run the user diagnostics:
Use Apple Diagnostics to test your Mac - Apple Support
the diagnostics run for a very brief period of time, and in that time, can detect only GROSS errors. The result code of 'no faults detected' is not equivalent to "All is Well".
<< "panicString" : "panic(cpu 0 caller 0xfffffff01ed801bc): macOS panic detected\nDebugger message: panic. >>
That one is likely to be caused by third-party virus scanner calling the debugger to stop your Mac "to protect you".
This is the essence:
"macOSPanicString" : "panic(cpu 0 caller 0xffffff800d917043): vm_page_queues_remove - bad page q_state
That is a truly bizarre problem. It should NOT be happening.
do you have additional different panic reports?
That´s odd, i haven´t installed any virus program, i just recently did a factory reset on it.
And yes, i have quite many more panic files, looking quite similar. Attaching the same line from another file below:
"panicString" : "panic(cpu 0 caller 0xfffffff029a881bc): macOS panic detected\nDebugger message: panic\nMemory ID: 0xff\nOS release type: User\nOS
Thanks for answering!
I found a bunch of panic files. They are bigger than "additional text" allows though so i had to remove some of it.
This is the first part.
and here comes part 2
(i did remove a massive amount in the middle with non-formatted text)
and finally part4
I see, many thanks for your analysis! I'll think about a possible next step.
I have everything backed up on my NAS so that´s alright.
My MacBook Pro has since a couple of months back started to crash
