This question already has an answer here:

Whenever I select classified symbology for a raster layer ArcMap will crash/close and give the message/ prompt to send error report: "ArcGIS has encountered a serious error.."

The problem is not associated with the data itself as it happens for any raster.

I have uninstalled ArcGIS 10.3 and reinstalled ArcGIS 10.4 and reset my normal file and the error still happens. There doesn't seem to be any issues with the install and the issue is new. I had been using ArcGIS 10.3 for a while with no issues.

The only change on my computer I can think of is I updated my AMD Radeon Display driver recently. However I have tried disabling it and running ArcMap and the same error occurs.

marked as duplicate by PolyGeo arcgis-desktop May 17 '16 at 9:46

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • I have the same damn problem. It also crashes on me when I use the dissolve tool but I get no error. I have tried uninstalling and installing but to no avail – ziggy May 14 '16 at 18:02
  • 2
    Hi Ziggy, looking through some other posts on here I came across this one:gis.stackexchange.com/questions/193236/… One person suggested a conflict with AVG. I disabled AVG and that looks like it may have fixed my issues. If you use AVG try turning it off and see if the error still occurs. Or if you use another Antivirus program it could be causing the same issue. – awvanwychen May 14 '16 at 18:13
  • 1
    @awvanwychen have you been using ArcGIS 10.3 and AVG together for some time? If so it may be a new update to AVG that's causing the issue. This issue has appeared a few times over the last couple of weeks so might be a new issue worth reporting to AVG (if they'll even listen) – Midavalo May 14 '16 at 20:51
  • I do have avg il give that a try! – ziggy May 15 '16 at 2:51
  • @Midavalo Yes I had been using ArcGIS with AVG for the past year and ArcGIS 10.2.2 for about a year before that with no issues. I will report the problem to AVG and hopefully it will be resolved with a future update. – awvanwychen May 15 '16 at 16:14