Office Apps Crashing

How to Fix Excel and Word Crashes with Ntdll.dll Errors

Algirdas JasaitisAlgirdas Jasaitis Nov 3, 2026 871 views

Question details

The user is experiencing persistent crashes across Microsoft Office applications, accompanied by an ntdll.dll error and exception code 0xc0000374.

Fix Excel, Word, Outlook, and PowerPoint Crashes with Ntdll.dll Errors
Product
Microsoft Office
Device & OS
Windows
Scenario
Opening and working within Microsoft Excel, Word, Outlook, or PowerPoint.
Observed behavior
The applications crash unexpectedly and display an ntdll.dll error code 0xc0000374, indicating potential issues with system file corruption or damaged user profiles.
Before you start

Ensure that you are logged into Windows with an account that has Administrator privileges, as you will need elevated permissions to create new user profiles and run system-level scans.

Solution 1Recommended

Test with a New Windows User Profile

Creating a fresh Windows user profile can help determine if the ntdll.dll crashes are caused by localized corruption within your current account's registry or app data.

Often, application crashes are tied to specific user profile configurations rather than the application itself. Testing in a clean environment isolates the issue.

1
Access Windows Settings

Press the Windows key + I on your keyboard to open Settings, then navigate to Accounts.

2
Add a New User

Click on 'Family & other users' in the left pane, then click 'Add someone else to this PC'.

3
Create a Local Account

Select 'I don't have this person's sign-in information', then choose 'Add a user without a Microsoft account'. Enter a new username and password.

4
Test Office Apps

Log out of your current Windows session, log into the newly created profile, and open Excel or Word to see if the crash persists.

Test with a New Windows User Profile
Profile Migration: If Office works perfectly on the new profile, your old profile is corrupted. You may need to migrate your personal files to the new local account to permanently avoid the crash.
Free Microsoft Office alternative

Switch to WPS Office to Avoid System-Level Office Crashes

If persistent ntdll.dll errors and 0xc0000374 exceptions keep interrupting your workflow, consider switching to WPS Office. As a free and lightweight alternative, WPS Office bypasses many deep-rooted Windows registry conflicts that plague traditional Microsoft Office setups, ensuring a stable, fast, and crash-free experience with seamless transition.

  1. 1. Download the Installer: Visit the official WPS Office website and click 'Download' to get the free installation package.
  2. 2. Install the Software: Run the downloaded executable file and follow the quick setup wizard to install WPS Office on your PC.
  3. 3. Open Your Files: Launch WPS Office and directly open your existing Excel, Word, or PowerPoint files to continue your work without crashes.
Free, fully featured, and lightweight alternative to Microsoft OfficeExcellent format compatibility with Microsoft Word, Excel, and PowerPoint (.docx, .xlsx, .pptx)Independent architecture that is far less prone to system-level ntdll.dll and registry crashesFamiliar user interface ensuring a seamless migration with zero learning curve
microsoft office alternative - wps office

Frequently Asked Questions

What is the ntdll.dll file and why does it cause Office to crash?

The ntdll.dll file is a core Windows system file that handles internal kernel functions. When Office applications crash and reference this file along with exception 0xc0000374, it usually means there is a heap corruption issue, a conflict with a third-party add-in, or localized corruption within your Windows profile interacting poorly with Microsoft Office.

Will reinstalling Microsoft Office fix the ntdll.dll 0xc0000374 exception?

Reinstalling Office or performing an Online Repair can fix the issue if the corruption is strictly within the Office program files. However, because ntdll.dll is a Windows component, the crash often stems from a damaged Windows user profile or corrupted Windows system files. Testing a new Windows user profile or running an SFC scan is generally more effective.

How long does an SFC scan take to complete?

A System File Checker (SFC) scan typically takes between 10 to 30 minutes, depending on the speed of your hard drive and the overall health of your system files. You should leave the Command Prompt window open and avoid restarting your PC until the verification process reaches 100%.