[Windows] Repeated ChatGPT.exe crashes with 0xc06d007f cause system-wide micro-freezes

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #33518
• #33529
• #33494
• #33538
• #33466

Powered by Codex Action

Additional sanitized reproduction on the same current Windows x64 package:

• Codex package: OpenAI.Codex 26.707.12708.0.
• OS: Windows NT 10.0.26200.8875 x64 (25H2).
• Windows Application log contained 201 Event ID 1000 failures for ChatGPT.exe within 24 hours.
• All 201 events reported exception code 0xc06d007f.
• The failures involved 5 distinct faulting process IDs.
• First observed: 2026-07-15 23:54:59 +08:00.
• Last observed: 2026-07-16 17:11:34 +08:00.
• The latest event points to package OpenAI.Codex_26.707.12708.0_x64__<redacted-package-family>; faulting module is reported as unknown.

A controlled MCP A/B test was also performed:

• All 15 currently configured remote MCP servers were set to enabled=false.
• Two local MCP servers remained enabled.
• Codex was fully restarted.
• The Windows-wide lag still reproduced, so remote MCP startup/network overhead does not appear to be the primary cause.

Other exclusions from the local snapshot:

• WSL_DISTRO_NAME was absent at User and Machine scope.
• Two git.exe processes had accumulated 0 CPU seconds during the diagnostic snapshot.
• The local Node/Node REPL family had accumulated about 1.42 CPU seconds.
• During active diagnostics (not an idle benchmark), 9 ChatGPT.exe processes used about 1358.5 MB combined working set, and 2 codex.exe processes used about 345.1 MB.

The current package still contains the built-in native dependency chain:

CodexMicroService -> @worklouder/device-kit-oai -> @worklouder/wl-device-kit -> serialport.node

Sanitized binary details:

• Size: 229,376 bytes
• SHA-256: 2D5D112E2E57054034FA9454E9C33DC306377455D989644F7D4C1B43027EB006

After a later app restart, the user still experienced lag even though no new Event ID 1000 entry had appeared yet. This may indicate two related paths: the repeated native crash/WER loop and a renderer or Windows-shell degradation path that does not always generate a formal crash event.

No configuration files, databases, session files, raw logs, screenshots, workspace paths, prompts, credentials, or personal documents are attached or included.

Facing same issue. App is unusable on windows.

Same issue app now unusable, It was fine last night. I ran the update this morning and now crashes constantly with Not Responding

I can reproduce the same system-wide micro-freezes on a newer AppX build.

Environment

• AppX package: OpenAI.Codex_26.715.3651.0_x64__2p2nqsd0c76g0
• Architecture: x64
• Installed package version: 26.715.3651.0
• Install location:

C:\Program Files\WindowsApps\OpenAI.Codex_26.715.3651.0_x64__2p2nqsd0c76g0

• Windows desktop application with Codex open

Observed behavior

When the ChatGPT Windows application is open, the entire Windows UI periodically becomes severely unresponsive:

• mouse movement becomes frame-by-frame;
• input and window interaction lag;
• the freezes are irregular but frequent;
• sometimes they occur every few minutes;
• sometimes several events occur in a short cluster.

The problem starts after opening the application and stops after fully closing it. This makes the desktop application effectively unusable for sustained work.

Process Explorer shows short CPU spikes corresponding to the freezes, but there is no obvious process with continuously high CPU usage. Several ChatGPT.exe child processes remain visible, as expected for the Electron application.

Crash dump evidence

%LOCALAPPDATA%\CrashDumps contains repeated ChatGPT.exe dumps.

Ten dumps were generated between approximately 10:29:50 and 10:35:13 on July 16, 2026. Each dump is approximately 11 MB.

Example timestamps:

10:29:50
10:29:52
10:32:56
10:34:47
10:34:49
10:34:51
10:34:53
10:34:56
10:35:11
10:35:13

Seven dumps were generated within approximately 26 seconds during one cluster.

Example files:

ChatGPT.exe.35952.dmp
ChatGPT.exe(1).35952.dmp
ChatGPT.exe(2).35952.dmp
ChatGPT.exe(3).35952.dmp
...
ChatGPT.exe(9).35952.dmp

The dump sizes range from approximately 11,047,792 to 11,113,104 bytes.

Event log result

The following PowerShell query returned no matching Application Error 1000 or Windows Error Reporting 1001 events for ChatGPT.exe or Codex.exe:

Get-WinEvent -FilterHashtable @{
    LogName   = "Application"
    Id        = 1000, 1001
    StartTime = $since
} -ErrorAction SilentlyContinue |
Where-Object {
    $_.Message -match "ChatGPT\.exe|Codex\.exe"
}

However, the repeated local crash dumps confirm that ChatGPT.exe is repeatedly entering the Windows crash-dump path.

Regression information

The application worked normally before several recent updates. This behavior appeared only in recent versions and has persisted through multiple updates.

The issue is not related to a permanently high system load: when the ChatGPT application is closed, the system immediately returns to normal.

This may be the same native-module crash loop described in #33518, but I have not yet analyzed the dump in WinDbg, so I cannot independently confirm the exception code or faulting module.

I can provide one of the crash dumps to OpenAI through a private upload channel if requested. I would prefer not to attach it publicly because a process dump may contain data from application memory.

Update from me after having theses issues: I have been having the same problem after hours of pulling my hair out it turned out to be my K55 corsair keyboard causing the issues. I unplugged it and plugged in a wireless keyboard and no hang or crash in 2 hours (this only started happening after the latest update for me) May help someone, may help no one but its fixed the issue for me

Wow, unplugging the keyboard fixed the issue. But this is only issue with Codex app. This must be fixed.