"Unfortunately, the process com.sec.ims.android has stopped." What does this error message mean?

I have a Samsung Note 3. It normally works very well, but I just got this error message: Unfortunately, the process com.sec.ims.android has stopped. OK When I selected "OK", the error message went away for just long enough to do something very quick (such as a single button click, a small scroll, etc.), then the same error message came back. After ignoring my phone for quite a while, I found a different error message: Process system isn't responding. Do you want to close it? Wait OK When I clicked "OK", the error message went away – and the original "Unfortunately" error message came back. I tried a slow-click of the right button, and the "Device options" dialog box came up – underneath the "Unfortunately" error message. And this time, the "Unfortunately" error message wouldn't go away, not even long enough to select from "Device options". My next step was a battery-pull power cycle. That appears to have resolved the problem – for now – but the few answers I found with a web search for the "Unfortunately" error message suggest it might recur again soon. --- So, two questions: - Does anyone have a general solution to the problem? I can pull the battery, but that's a hassle (remove armor, remove back of phone, pull battery, put everything back together). Ideally I'd like a fix that makes it go away and not return. Failing that, I'd like a fix that minimizes recurrence. - Can anyone explain what the process "com.sec.ims.android" is, and what it does? (A web search suggests that "IMS" in this context means "IP Multimedia System".) Is it specific to Samsung? --- Since I mention web search results, and they might not be there next time someone searches, here's a summary: - One reply suggests this [sic]: Go into settings>General>app manager>All> find contacts and open it then clear cache. If that doesnt help. Clear cache and data. Fixed it for me. - Another reply says that clearing cache and data in contacts fixes the problem, but only for a call or two. - Yet another reply says that dismissing the error message once solves the problem.