This is on my 2013 15" i7 running High Sierra. I believe this is the error message I get when it restarts itself, "Your computer restarted because of a problem". Regardless, Below (& in my comment below about it since this keeps warning me about the 5000 character limit) I'll try to post the "more info" . Any thoughts? Thanks for any help!
[Re-Titled by Moderator]
MacBook Pro 15″, macOS 10.13
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 as much as you can here, by using the “additional text” Icon in the reply footer (looks like a paper with writing). (Once the report devolves into incessant software-names or incessant Base-64 dumps with lots of AAAAAA lines, you are done.)
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.
If you post your kernel panic here in its entirety, using the additional text icon in the reply footer, we do have some Readers (typically with developer background) who can attempt to interpret those panic reports. Even if no clear symptom emerges, this can still save a step if you DO need to contact Apple support later, because Apple Support specialists can read the panic reports you posted here, if you tell them what discussion or what Avatar.
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 as much as you can here, by using the “additional text” Icon in the reply footer (looks like a paper with writing). (Once the report devolves into incessant software-names or incessant Base-64 dumps with lots of AAAAAA lines, you are done.)
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.
If you post your kernel panic here in its entirety, using the additional text icon in the reply footer, we do have some Readers (typically with developer background) who can attempt to interpret those panic reports. Even if no clear symptom emerges, this can still save a step if you DO need to contact Apple support later, because Apple Support specialists can read the panic reports you posted here, if you tell them what discussion or what Avatar.
Try booting in Safe Mode, which clears caches and performs some other background tasks. It also prevents 3rd party extensions from loading. If you have no issues in Safe Mode, reboot normally and see if that corrected the problem.
Start up your Mac in safe mode - Apple Support
This one line explains most of the other symptoms:
<< Low disk space - This computer is running critically low on free hard drive space.>>
Mounted Volumes:
disk1s1 - Macintosh HD
Filesystem: APFS
Mount point: /
Used: 715.56 GB
Shared values
Size: 751.07 GB
Free: 32.64 GB
Available: 35.82 GB
That is not enough space available for normal operation. If you proceed without fixing that issue, your Mac will crash as often as daily and the error messages will be completely opaque.
Huh, that is the essence of your complaint.
You need to maintain about minimum 20 percent free on the boot drive. for a 751 GB drive that is around 150 GB. You might consider adding an external drive as well, and readers can advise about that.
DTBDFilms wrote:
Would going into Safe Mode do more than these things, or would it be more of a leave it in safe mode for a day to see if it crashes kind of thing?
Both. I’d suggest a safe boot then reboot normally. If the problem disappears, done. Else, run in safe mode long enough that you’d expect to have the issue.
It seems like your MacBook Pro is encountering a kernel panic due to a lack of memory allocation for a table. This could be caused by software conflicts or memory issues. Consider updating or removing recently installed software and running hardware diagnostics.
<<But, eventually it did restart. >>
Kernel Panic is Not ONE problem, it is one of THOUSANDS of problems.
To see if that is the SAME problem, please post the kernel panic report.
Another blatant issue is that your Time Machine is active, but the drive you are using is too small. The drive being used was not connected at the time of this report, but it looks like it is full at 999 GB. The recommended size is MINIMUM 2.5 times the size of what is to be backed up.
Time Machine does its work at low priority in the background. Backup gets no extra benefit from a backup drive that is FAST. So find a BIG cheap Rotating magnetic drive (any old speed) for backups.
As a result, you have not completed a successful disk-based Time Machine backups since June 17. However, you do have 11 local snapshot backups on your boot drive, the latest being 26 August at 22:07, and oldest from the previous day.
No, you run the report and post it here using the Additional Text option when posting. It is the report that contains no personal information. The crash report provides very little details that are useful to determine what actually caused the crash and the EtreCheck report will have more details about the crash with additional information that may be causing a conflict with the OS.
How to use the Add Text Feature When Post… - Apple Community
Thanks for your help. AS it's an older computer, I mostly use it for watching YouTube when I'm in the kitchen, so I haven't loaded much onto it in years except for browser updates. That said, this problem has existed for likely years and I figured it was just an aging computer. I'm also hesitant to update the OS b/c I have older software that I need and may either no longer work or require my going to a subscription service (hatred of those things!!).
Anyway, I tried to use the hardware diagnostics and I was taken to something calling itself internet diagnostics or something similar. The 1st time I did it I got to a screen like a bios where it warned me it could take a while. There were only a couple lines of text, so I walked away for a while. When I came back I was on the screen to pick the user account and log in, just like a normal restart. So, I tried it again and this time I ended at a screen with the same globe in the background, just like the start of the 1st time, but this time around there was a triangle with a large "!" in the middle. It read under this:
apple.com/support
-1007D
Any thoughts?
apple.com/support
-1007D
In Internet Recovery, these low negative thousands error messages indicate that your provided Wi-Fi Network is inadequate in some fashion, and cannot be used (for this purpose) in its current state. We have seen -1000 to -6000 reported, often with a letter appended.
Common problems include:
Hidden Network-name
required use of a proxy server to get Internet access
required use of a login page to get Internet access
Use of a login server or certificate to get Internet access
Use of PPPoE in the Mac to get Internet access (typically only applies to DSL)
Use of Fixed IP address rather than good old DHCP
Variance of the time by more than five minutes
Failure of Router to provide workable DNS server addresses, or providing 0.0.0.0 [may produce -2002f]
If you have an Ethernet port, you may in some cases be able to move your Mac close to the Router and connect to the Router using Ethernet.
The higher the number, the more obscure the problem.
If your battery was completely depleted, the Date&Time could have reverted to the default, which will not work. There is a terminal command to reset to current Internet Date&Time -- post back for assistance.
<< The panic report should be in my original post tho. >>
That's the panic report you had before, before you tried anything.
I want the panic report you get NOW
Thanks for that. What I did earlier to day was following instruction to "reset your NVRAM or PRAM" and then reset the System Management Controller (SMC). I was not familiar with the latter and had not done the former in many, many years. The problem is it usually takes a day for the MBP to need to restart, so I won't know immediately if the above steps helped. Would going into Safe Mode do more than these things, or would it be more of a leave it in safe mode for a day to see if it crashes kind of thing?
Thanks for that and I just did as you said, but again when I stepped away I came back to a screen to log in again. Last I saw, it was just the same two lines in something that looked kinda like a bios. Any idea what this means?
I was able to get it into Safe Mode, but it behaved really oddly there. Things like flickering screens, scrolling white backgrounds taking over the desktop, and more. I couldn't do much of anything. Couldn't even play videos on YouTube.
Does this tell you anything? I don't know how Safe Mode is supposed to work, but mine was basically unusable.
Thanks for any help!
You can't reliably play videos in Safe Mode, because one of the items not loaded is graphics acceleration drivers. By design, screen refresh will be wonky and slow, but it should be ultimately ACCURATE.
MacBook Pro keeps restarting and fans likely blowing harder than normal
