Troubleshooting Adobe Crash Reporter Loops in Windows Event Viewer

An Adobe Crash Reporter loop occurs when AdobeCrashReporter.exe or CRWindowsClient.exe repeatedly crashes, restarts, and re-logs errors in the Windows Event Viewer. Instead of gathering a single crash dump and closing, the reporting tool gets trapped in a cycle. This behavior spikes CPU usage, fills your storage drives with dump files, and can cause target applications like Premiere Pro, After Effects, or Photoshop to hang indefinitely on launch.

Fast Fix

Press Ctrl + Shift + Esc to open Task Manager, right-click any instances of Adobe Crash Reporter or CRWindowsClient, and select End Task. Then, press Win + R, paste %LocalAppData%\Adobe\CrashReporter, hit Enter, and delete all contents within that directory to stop the loop.

---

Windows Event Viewer: Identifying the Fault Signature

To resolve a crash reporter loop, you need to identify which module crashed first. The crash reporter only runs because another component failed, but a second failure occurs when the reporter itself crashes while generating the dump.

Open the Windows Event Viewer by pressing Win + R and entering eventvwr.msc. Expand Windows Logs and select Application. Look for pairs of events labeled Error with the sources Application Error (Event ID 1000) and Windows Error Reporting (Event ID 1001).

[Event Log Timeline]
10:00:01 AM - Event 1000: Photoshop.exe crashes (Faulting module: D3D12Core.dll)
10:00:02 AM - Event 1000: AdobeCrashReporter.exe launches
10:00:04 AM - Event 1000: AdobeCrashReporter.exe crashes (Faulting module: ntdll.dll)
10:00:05 AM - Event 1001: Windows Error Reporting captures CrashReporter crash
10:00:06 AM - AdobeCrashReporter attempts relaunch -> Infinite Loop Begins

Inspect the Event ID 1000 record for AdobeCrashReporter.exe. Review the following two fields:

• Faulting Module Name: Indicates what caused the crash (e.g., ntdll.dll, vcruntime140.dll, or CrashReporterIPC.dll).
• Exception Code: Indicates the underlying system error (e.g., 0xc0000005 for an access violation or 0xc0000409 for a stack buffer overrun).

If the original exception code in the log is 0xc0000005, read How to Fix ‘The Application was Unable to Start (0xc0000005)’.

---

Common Root Causes

Faulting Module in Event Viewer	Diagnostic Meaning	Next Logical Step
ntdll.dll / kernelbase.dll	Permission failure writing dump files or corrupted memory space.	Clear the CrashReporter directory and repair storage permissions.
vcruntime140.dll / msvcp140.dll	Corrupted or mismatched Visual C++ redistributable packages.	Reinstall the Microsoft Visual C++ 2015–2022 redistributables.
CoreSync.dll / AdobeIPC.dll	Creative Cloud background sync services crashed while communicating.	Clear the OOBE runtime cache and check UI helper processes.
Specific GPU driver (nvldumdx.dll, amdxx64.dll)	GPU driver crashed during the initial failure, breaking the crash window render.	Perform a clean GPU driver installation.

---

Step-by-Step Resolution

Step 1: Purge the Dump Queue

When the crash reporter encounters an existing, corrupted .dmp file in its target path, it can fail when attempting to append new crash trace data.

1. Terminate all Adobe processes via Task Manager.
2. Press Win + R, paste the following path, and press Enter:
   %LocalAppData%\CrashDumps
3. Delete any .dmp files starting with Adobe, Photoshop, Premiere, or CrashReporter.
4. Next, press Win + R, navigate to:
   %LocalAppData%\Adobe\CrashReporter
5. Delete all files in this directory, including crash_dump_submitted.xml and any temporary storage files.

Step 2: Resolve Microsoft Visual C++ Runtime Conflicts

When AdobeCrashReporter.exe logs 0xc0000409 alongside vcruntime140.dll, its shared C++ libraries are likely damaged.

1. Press Win + R, type appwiz.cpl, and hit Enter.
2. Scroll to the Microsoft Visual C++ Redistributable entries.
3. Locate the 2015–2022 packages (both the x86 and x64 versions).
4. Click each entry, select Change, and then click Repair.
5. Restart your computer once both installations have been repaired.

Step 3: Address Creative Cloud Helper and UI Process Crashes

If the crash reporter loops whenever the Creative Cloud desktop window opens, the Chromium Embedded Framework (CEF) helper layer is usually failing to initialize its off-screen canvas. If you suspect this is the trigger, work through the steps in Fixing Creative Cloud UI Helper Crashes on Startup.

Step 4: Clear Corrupted Local AppData Configuration

A corrupted user profile or application workspace state can trigger an immediate crash on startup, while simultaneously breaking the crash reporter’s error-collection process.

Clear the temporary application configurations:

1. Close all Adobe programs.
2. Open Win + R and browse to:
   %AppData%\Adobe
3. Locate the folder for the specific crashing program (for example, Premiere Pro or Photoshop).
4. Append .old to the directory name (e.g., Premiere Pro.old).
5. Open Cleaning Hidden Appdata/Local/Adobe Folders for a Fresh Start to identify and clear any remaining orphaned cache files safely.

---

Advanced Workaround: Halting the Reporter Binary

If you need to finish an urgent project and an app runs fine after an initial transient crash, but the Crash Reporter loop continues to consume CPU cycles and cause input lag, you can disable the reporter temporarily.

1. Navigate to the root directory of the affected application. For example:
   C:\Program Files\Adobe\Adobe Premiere Pro 2026
2. Locate AdobeCrashReporter.exe (or CRWindowsClient.exe).
3. Right-click the file and select Rename.
4. Change the extension to AdobeCrashReporter.bak.

Important: This is a temporary diagnostic workaround. Renaming the reporter prevents the loop from consuming system resources, but it does not fix the underlying software error that caused the crash in the first place.

---

Hard Stops

Stop local troubleshooting and review your core system setup if:

• The Faulting Module is consistently ntdll.dll across multiple programs: This indicates operating system file corruption or unstable system memory, rather than an isolated Adobe error. Run sfc /scannow and test your RAM.
• The loop occurs only inside video projects at specific points: The crash is likely caused by a hardware decode failure or corrupt footage rather than the application itself. If the failure occurs during video rendering or timeline scrubbing, see How to Fix “A Low-Level Exception Occurred in: Adobe Player”.