VBA & Macro Problems

Fix Excel 2016 Crashes When Running VBA Macros With Outlook Open

Algirdas JasaitisAlgirdas Jasaitis Nov 20, 2026 869 views

Question details

Identify why Excel 2016 crashes during long-running VBA macros when Outlook is open.

Fix Excel 2016 Crashes When Running VBA Macros With Outlook Open
Product
Microsoft Excel 2016 and Microsoft Outlook
Device & OS
Windows; version not provided
Scenario
A VBA macro opens and closes multiple workbooks and copies large blocks of data into a consolidated sheet while Outlook is open.
Observed behavior
Excel may close and reopen with a recovered workbook. Previous Application events have sometimes reported error ID 1000 and referenced ntdll.dll, although a crash may leave no corresponding event.
Before you start

Note whether Outlook is open and which workbooks and add-ins are active when the crash occurs. Use a small, representative set of workbooks to make repeated tests faster.

Solution 1Recommended

Isolate the crash with breakpoints and controlled tests

Use smaller test runs and progressive breakpoints to narrow down where the crash occurs and whether Outlook or an add-in affects it.

1
Open the VBA editor

In Excel, press Alt+F11 and open the module containing the macro. Click the margin beside a line or press F9 to set a breakpoint.

2
Narrow the execution range

Run the macro with F5, then place additional breakpoints before and after workbook opening, data transfers, and workbook closing. Repeat the test to identify the last checkpoint reached before Excel closes.

3
Compare Outlook states

Run the same test once with Outlook open and once after closing Outlook. Record whether the crash occurs in each case.

4
Test without Excel add-ins

Close Excel, press Windows+R, enter excel /safe, and open the workbook for another test. If the issue changes, use File > Options > Add-ins, select an add-in type in the Manage box, and click Go to disable add-ins for testing.

Isolate the crash with breakpoints and controlled tests
What breakpoints can show: A breakpoint pauses execution before its line runs; it does not automatically identify a line that crashes Excel. Use several checkpoints and repeat the test to narrow down the failing operation.
Free Microsoft Office alternative

Work with Excel files in WPS Spreadsheet

WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office file compatibility, making it easy to move everyday spreadsheet work between applications. It does not repair Microsoft Excel or guarantee that an existing VBA macro will run unchanged.

Open and edit Microsoft Excel XLS and XLSX filesWork with spreadsheet data in a familiar interfaceUse a free, lightweight suite for everyday Office tasksMove common spreadsheet documents between WPS and Microsoft Office
microsoft office alternative - wps office

Frequently Asked Questions

Does a crash that mentions ntdll.dll mean that file is the cause?

Not necessarily. In Event Viewer, check Windows Logs > Application for the crash time and record the full event details. The named module alone does not establish the underlying cause.

How can I tell whether Outlook contributes to the crash?

Run the same reduced macro test with Outlook open, then close Outlook and repeat it. A difference in results is a useful clue, but it does not prove which component is responsible.

Why didn't my breakpoint stop on the line that crashed Excel?

A breakpoint pauses before the line where it is set; it does not automatically catch a crash elsewhere. Add breakpoints around workbook operations and rerun the macro to find the last checkpoint reached.

How do I test Excel without its add-ins?

Close Excel, press Windows+R, enter excel /safe, and open the workbook. If the result changes, review add-ins under File > Options > Add-ins and use the Manage box and Go button to disable them for further testing.

Is there a known new Excel 2016 clipboard limit causing this crash?

The crash alone does not establish a new clipboard limit. Test smaller data blocks and review repeated Range.Copy and Paste calls; where appropriate, transfer values directly between equally sized ranges.