Skip to content

ChatGPT Desktop (Codex) repeatedly freezes after sending prompts and generates recurring MoAppCrash reports (StackHash_0000) #33466

Open

Description

@novita

Hello OpenAI Support,
I would like to report what appears to be a reproducible issue with the ChatGPT Desktop application (Codex integration).
Environment
ChatGPT Desktop (Microsoft Store)
Package: OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0
Windows 11 24H2
OS Version: 10.0.26200.2.0.0.256.48
ASUS Zenbook Pro 16X
NVIDIA GeForce RTX 4080 Laptop GPU
NVIDIA Studio Driver
Discrete GPU mode enabled (Intel iGPU disabled through ASUS settings)
Symptoms
The application frequently becomes temporarily unresponsive.
Typical behavior:
I type a prompt and press Enter.
Immediately afterward, the ChatGPT Desktop UI freezes for several seconds.
During the freeze:the window sometimes becomes slightly grayed out,
mouse movement becomes sluggish,
even Windows Task Manager feels temporarily less responsive.

The application usually recovers after a few seconds.
In most cases, the application does not completely exit.
The issue occurs multiple times per hour.
Important observations
I investigated the issue extensively.
CPU
Actual CPU usage remains around 30–40%.
Verified using:
Process Explorer
Resource Monitor
PowerShell Get-Counter
CPU is not saturated.
GPU
GPU usage remains around 20%.
Interestingly, during the freeze the GPU usage often drops, rather than increases.
Disk
Disk activity remains very low.
Memory
Memory usage is around 75–80%, but there is still available RAM.
Hardware interrupts
Hardware Interrupts / DPC remain low (approximately 2%).
No indication of a driver interrupt storm.
Reliability Monitor
Windows Reliability Monitor records repeated application failures.
Every crash reports essentially the same information:
Problem Event Name:
MoAppCrash
Application:
OpenAI.Codex
Fault Module:
StackHash_0000
Exception Code:
c06d007f
Example Bucket ID:
fe840c3ed30ba850ddeac7488b0e9f2e
The reports are generated repeatedly within a few minutes.
Reproducibility
Initially I suspected the issue was caused by long sessions.
However, after a complete Windows reboot:
I launched only ChatGPT Desktop and a web browser.
No heavy applications were running.
The freezes still occurred immediately after startup.
Therefore the issue does not appear to depend on long uptime or accumulated system load.
Additional notes
I have already attempted:
Windows reboot
ChatGPT "Repair" from Windows Apps settings
Monitoring CPU/GPU usage
Checking Windows Reliability Monitor
Process Explorer investigation
None of these changed the behavior.
My observation
The freezes appear to happen most frequently immediately after pressing Enter to submit a prompt, especially when using Codex with a local project.
This suggests that the issue may be related to the Desktop application's renderer process, Electron UI, or Codex local workspace processing rather than overall CPU or GPU utilization.
If additional logs or crash dumps would be useful, I would be happy to provide them.
Thank you for your assistance.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    on Jul 16, 2026
  2. zhuaixiaoniu commented on Jul 16, 2026

    @zhuaixiaoniu

    Independent Windows confirmation (sanitized):

    • Product: Codex Desktop MSIX OpenAI.Codex_26.707.9981.0 on Windows 11 x64.
    • On 2026-07-16, between 09:44 and 09:50 China Standard Time (UTC+8), Windows recorded repeated MoAppCrash events for ChatGPT.exe.
    • Within the most acute 09:47–09:50 interval, there were at least nine Application Error Event ID 1000 records.
    • Every crash had the same fingerprint: exception 0xC06D007F, faulting module unknown, WER signature StackHash_0000.
    • The visible client repeatedly flashed/restarted. The current process tree later stabilized briefly, but this was not a one-off failure.
    • No concurrent System-log critical/warning/error or graphics-driver event was recorded in the same time window.

    No session contents, project paths, prompt text, or logs are attached. This appears to match the MoAppCrash/StackHash_0000 class rather than the separate chrome.dll browser access-violation crash.

  3. Respect08 commented on Jul 16, 2026

    @Respect08

    +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingperformancewindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions