You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
I am getting occasional shut-downs. Today, my Mac crashed while I was surfing on Firefox.
Would anyone be so kind as to analyze this Apple Panic Report to find the source of today's kernel panic?
Thanks for your help.
Mac mini, macOS 10.12
Nothing obvious, except you have a 10 year old Mac (I've got a 2007 Mac mini, so I'm not being negative).
Do you have original RAM, or is it 3rd party? Sometimes 3rd party RAM can cause issues.
The only kernel extension you have is MalwareBytes, and that is not typically a problem.
You might post the EtreCheck report (free mode, you just want to do a copy & paste of the text report into a forum Additional Text box.
Nothing obvious, except you have a 10 year old Mac (I've got a 2007 Mac mini, so I'm not being negative).
Do you have original RAM, or is it 3rd party? Sometimes 3rd party RAM can cause issues.
The only kernel extension you have is MalwareBytes, and that is not typically a problem.
You might post the EtreCheck report (free mode, you just want to do a copy & paste of the text report into a forum Additional Text box.
Apple Hardware Test says it doesn't run on this model Mac mini.
A couple of crashes lately. Here's the most recent one.
There are almost daily crashes listed in Console/User Reports. Mac Mini must be restarting itself when I'm not around. Almost all start with nlastpass or plug-in container.
(Attached the one that doesn't, it starts with MRT.) Somehow I think this is software-related? Caused by Firefox? I'm running Sierra 10.12.6.
I found this similar discussion elsewhere https://www.jamf.com/jamf-nation/discussions/19701/macs-crashing-restarting-due-to-web-browsing
I agree with @BobHarris. The Panic does reference "Plugin Container" so maybe a Firefox add-on?
Also do you have any other Kernel Panics you can post so we can see if there is a pattern?
You can try running the Apple Diagnostics/Apple Hardware Test. For a system 10 years old you may need to run the Apple Hardware Test from the 2nd DVD that shipped with your Mac.
You can also try running Memtest86. Use the downloaded Memtest86 .iso file as a source for Etcher in order to create a bootable Memtest86 USB drive.
Yes, we had discussed my Kingston RAM in another thread. After I swapped and re-seated the RAM a few times, the crashes stopped for a while.
I suspect the Firefox LastPass plug-in might be causing CPU crashes, though how it's doing that, I have no idea, and neither does LastPass support. I attached a Console report from the last crash October 12. The LastPass app appears to be searching for a non-existent file, nplastpass
Will run the other tests and post again. Thank you for your help.
Mac Mini crashed this morning. Had to attempt to restart it several times, did not get the chime and progress bar did not complete. First time of attempted restart, fan ran with noticeable hissing sound but then quieted down. Finally, I reset SMC and SDRAM, got the chime, and startup was normal.
I noticed the power cord was loose. I was cleaning up around the Mac Mini the day before. I taped down the power cord. The connection on the back of the Mac has never been as secure as I'd like.
I did not get an Apple report for the crash today. Here is the report from Console User Reports. Plug-in container is involved again. Should I reinstall Firefox with plug-ins?
Also attached system.log from today just before crash ~10:48 a.m to after I rebooted it 11:50:22, after several tries.
Will run Etrecheck and Apple Diagnostics.
Apple Hardware Test (AHT)
Description
Apple computers ship with a pre-installed suite of hardware diagnostic tools, known as Apple Hardware Test (AHT). In principle you can start them by holding the d key while booting. Newer models support holding option d to load AHT over the internet. Refer to the official Apple documentation for details: Using AHT on Intel-based Macs, Mountain Lion, Mavericks and Yosemite. Apple redesigned the AHT, now called Apple Diagnostics, for Macs introduced after June 2013. Consult the reference codes to interpret the results.
If however, you reinstalled an older computer from scratch, the diagnostic tools might no longer be available. Unless you have the original disks that came with your computer, there seems to be no way to restore the AHT.
It happens that Apple provides disk images with AHT for most computers, but does not make the links publicly available. Various blogs and forums, mostly Riven by Five and MacForum.ro have gathered a list of download links. The rest were obtained by scraping http://download.info.apple.com/Apple_Hardware_Test/ for all the links of the form 0(18|22)-\d{4}-A.dmg.
Even though there's no guarantee that this list is correct or complete, some links can come in very handy to whoever is trying to debug hardware problems.
You can use the following terminal commands to determine the model and board ID of your computer:
sysctl hw.model | awk '{ print $2 }'
ioreg -l | awk -F\" '/board-id/ { print $4 }'
Download the AHT for your computer model and use the contents to restore the /System/Library/CoreServices/.diagnostics folder, then reboot while holding d to start the diagnostic tools. Alternatively you may try with a bootable USB stick, as described below. This is also the preferred way on OS X 10.11 or later, where the System Integrity Protection (SIP) no longer allows writing to system folders.
When trying to open an old dmg you may get the error 'legacy image should be converted'. To convert it to a newer format, open Disk Utility, in the menu Images click on Convert and select the dmg to convert and save it under a new name.
Note that there is no one-to-one correspondence between hardware model and AHT. For some models no hardware test could be found, while others seem to have multiple AHT. As the differences are not clear, feel free to try them out, to see which one works best for your hardware.
crabpaws wrote:
Yes, we had discussed my Kingston RAM in another thread. After I swapped and re-seated the RAM a few times, the crashes stopped for a while.
Kingston memory doesn't have a very good reputation on these forums. If you have their "Value" memory, then it is most likely the problem. Macs are extremely picky about the memory they use so it is best to only use the recommended memory listed on either the Crucial or OWC websites.
"nplastpass_xxxxxxxxxx" is the name of the log file and not the file that was part of the crash. Please post an EtreCheck report as @BobHarris suggested so we can look for possible software issues contributing to the crash. Posting a few more Kernel Panic logs would be useful to see if there is a pattern in the panics. I really suspect you have a memory issue especially with that Kingston RAM.
I gave up on using any RAM except for Crucial or OWC on our organization's Macs 20 years ago because of all the intermittent errors & crashes we would have when any other memory was installed. Since that time I've only ever encountered a few memory related issues with any of our Macs. Even using Crucial memory that is not identified as "Mac compatible" has caused problems on our Macs which proves to me that Macs are very picky about the memory they use.
Does this have any bearing on the Plug-in Container flag? nplastpass is the only app listed Console > User Report for the time of the crash:
I cannot find any file "nplastpass" on my Mac.
FYI, when running the Diagnostic tests, boot with Option-D and you will download the most recent tests direct from Apple, vs the 10 year old tests that are on your system.
Yes, I know, but this Kingston RAM worked without problems for 8-9 years. We have been unable to isolate the problem to the RAM.
Apple Panic Report for 2010 Mac Mini running Sierra
