This appears to be a delay-load “procedure not found” failure in the ARM64 SerialPort native addon. The built-in
browser starts around the same time, but clearing its cache and attempting to disable it does not change the crash.
Could OpenAI disable CodexMicro for affected ARM64 builds or ship a corrected win32-arm64 native module?
You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex.
I had ChatGPT look for the closest related issue and it identified:
That appears to be a hot issue with other leaving comments in the last few hours.
If that issue matches your problem, consider adding a reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.
If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.
Subject: Windows ARM64/Snapdragon: Codex Desktop crashes on startup (0xC06D007F)
Codex Desktop crashes immediately on startup on a Windows ARM64 (Snapdragon) device.
Crash exception code: 0xC06D007F.
It appears to occur while delay-loading @serialport/bindings-cpp, a dependency of device-kit, where the Node-API export symbol napi_module_register cannot be found.
Please confirm whether this is caused by an ARM64 build issue or a server-side feature flag, and provide a fix or temporary work around.
The same crash happens on Windows x64 — but with a different surface symptom that may help narrow the cause.
Environment
Windows 11 x64 (build 26200)
OpenAI Codex 26.707.9981.0 x64
NVIDIA GeForce RTX 4060 Laptop GPU
App was stable for several weeks before July 15
Behaviour
Unlike the ARM64 report where the app dies immediately, on x64 the app stays open but the UI freezes for 2–5 seconds at a time — clicking a conversation, typing, even hovering buttons all stall. The freezes repeat in a loop. Each one lines up with a silent ChatGPT.exe background crash.
Over 24 hours this produced 30+ crash dumps, each ~12 MB, totalling roughly 360 MB of disk writes that made the UI lag even worse.
Crash details
Everything matches the ARM64 report except the platform:
same here on my HP windows 11. mine started after i gave it quite a tough prompt and i felt like i overloaded it but not sure, i go to open codex and after a couple seconds it crashes. tried repairing, terminating and resetting yet still nothing.