Try this macro, it is an improved version that handles some problems that sometimes occur when you try to export a map without a proper MAP BORDER (And unfortunately, when you hide all the sheets, you also hide the map border, even if the map has one).

Note that the following macro still have some considerations:

• It expects the map to have a MAP BORDER layer and a map border on it. It uses this information to figure the size of the map and uses that size for all the sheets. This avoids the potential crash, and also ensures that all sheets are exported at the same size even if they are not filled with content
• Sheets in CC3+ can have characters that are not valid in windows file names, such as a slash. Such sheets WILL cause an error message, and can cause the entire process to crash. Make sure to avoid special characters in sheet names when using this macro. Note that sheets with such names may be in the drawing by default, such as "WATERS/RIVERS" or similar, sheet names in official templates were never created with file names in mind.
• Change the export settings in Tools -> Options -> BMP, JPEG, PNG before running the macro. Make sure to TURN OFF the launch image viewer option.

MACRO TTT
GFNSP FName *.PNG
IFERR end
GETLAYERL P0 MAP BORDER
GETLAYERH P1 MAP BORDER
SAUTOHIDEON
SSET;
:loop
SNEXT
IFERR end
SGETNAME SName
GL DName FName
APND DName _SHEET_
APND DName SName
APND DName .PNG
WBSM DName;P0;P1
IFP 1 loop
:end
SSHOWA
ENDM

Most probably there is a problem opening the map. CC3+ loads the last map on startup, so if something goes terrible wrong doing that, symptoms like that can manifest.

Easiest way is to make sure all instances of CC3+ are shut down (use task manager to kill them if required, or reboot your computer), then instead of clicking the CC3+ icon to start the program, double click on any map file instead as that will start the program with that map instead (Obviously, don't try to double click on the suspected problematic map, but try something known good, like one of the example files that came with the program)

It does. It is easy to see where the problem lies though. If it crashes while converting the final file, you'll be left with a fully functional temporary bitmap (the filename.bmp.jpg file) that contains the complete export, and if you looked at the export dialog during export, you'll also see that it is done with all the passes over the sheets.

On the other hand, if it crashes while CC3+ is rendering, the temprary bitmap will be corrupted (probably look like a half-finished export), and you'll also notice that the crash happened at the middle of rendering a sheet if you were looking at the export dialog.

ImageMagick is smart enough to use the disk as a cache if needed though, so even the 32-bit version should normally be able to handle any size output CC3+ is capable of producing.

When I try to work out where the problem lies, I often use a series of elimination step. Start by hiding half the sheets and testing, until I have narrowed down which sheet it is on, then do the same for the layers involved on that sheet. Then I start eliminating the entities on the sheet, half at a time.

Often, you can use quicker export options when you narrow down a problem. For example, exporting to bmp skips most of the final conversion step, and you can usually export at a lower resolution and turn off things like antialiasing, or even export without effects on. Just test with reduced export settings first to see if it still crashes, sometimes the conditions are no longer fulfilled for the crash when you do that, but if it still does, then it is no need spending 10 mins on each elimination step when you can spend 30 secs.

As for turning off progressive jpg, I have no idea whatsoever why that would help with anything. That option is used in the final conversion step, i.e. AFTER CC3+ have rendered everything, and have a complete bitmap to convert to jpg, while for me at least, it crashed during the actual rendering step long before that option can affect anything.

I seem to be able to reliably crash it. Did some testing, and seems to be down to building 20. It is right outside the area, but to avoid weird effect clipping at the edges, the render works with a slightly larger area than you select for the export.

Delete the building, and the export should go through. (You'll probably want to redraw it of course, but it is good just testing export once before that to make sure the problem is gone for you)