Crash on Windows 11

Open 💬 3 comments Opened Jul 23, 2026 by BaxLi
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.12708.0

What subscription do you have?

PRO

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Problem description
The locally-installed Windows ChatGPT desktop application crashed while I was working on my local HEALTH with local folders project .
The crash occurred when the project started reading data from a LibreLink continuous glucose monitoring sensor through a shared Abbott WEB-link.
After the crash:

  • the ChatGPT/Codex desktop application disapeared from opened app list & couldn-t longer be started;
  • every attempt to launch it failed .

The only way to restore functionality was to use the Repair option from Windows Settings → Apps → Installed Apps. After running the repair, the application started normally again.

This problem has occurred at least 3 times, making it reproducible.

To investigate the issue, I asked Codex to analyze the crash in an isolated local sandbox using the generated crash dump and related diagnostic data.

The following summary was obtained from that analysis:

The root cause has been identified.

Historically, the crash occurred in ChatGPT.exe from the older Codex version 26.707.12708.0.

The minidump points to the native module serialport.node.

The exception 0xc06d007f with lastError=127 indicates that the DLL was successfully loaded, but the required exported function could not be found (GetProcAddress / ERROR_PROC_NOT_FOUND). This behavior is consistent with the Microsoft documentation.

This was not an out-of-memory condition caused by the LibreView report. The isolated Chrome instance reached a maximum of 665.8 MB while running under a 1.2 GB memory limit and did not crash.

LibreView did not return any medical data because Cloudflare Turnstile detected the environment as automated and returned CAPTCHA error 600010. LibreView subsequently displayed error 437. According to Cloudflare, 600* error codes indicate that the Turnstile verification failed due to bot-like behavior.

The system is now running the newer Codex version 26.715.10079.0. In this version, the old serialport.node module has been replaced with bindings.node. No similar crashes have been observed for the new version in the Windows Event Log so far. Therefore, the original native defect has likely already been fixed, although a direct relationship with LibreView cannot be conclusively proven without another reproducible crash.
Sandbox: R:\Claude_Cowork\Projects\BejenariProject\99_staging\libreview-sandbox\README.md
Main script: R:\Claude_Cowork\Projects\BejenariProject\99_staging\libreview-sandbox\run.ps1
Final anonymized report: R:\Claude_Cowork\Projects\BejenariProject\99_staging\libreview-sandbox\reports\2026-07-23T11-37-56-698Z\report.json
reports.zip
README.md

What steps can reproduce the bug?

start codex project and read librelink web link

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 1 month ago

English translation:

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.12708.0

What subscription do you have?

PRO

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Problem description
The locally-installed Windows ChatGPT desktop application crashed while I was working on my local HEALTH with local folders project .
The crash occurred when the project started reading data from a LibreLink continuous glucose monitoring sensor through a shared Abbott WEB-link.
After the crash:

  • the ChatGPT/Codex desktop application disapeared from opened app list & couldn-t longer be started;
  • every attempt to launch it failed .

The only way to restore functionality was to use the Repair option from Windows Settings → Apps → Installed Apps. After running the repair, the application started normally again.

This problem has occurred at least 3 times, making it reproducible.

To investigate the issue, I asked Codex to analyze the crash in an isolated local sandbox using the generated crash dump and related diagnostic data.

The following summary was obtained from that analysis:

The cause has been identified.
Historically, it was ChatGPT.exe itself from the old Codex version 26.707.12708.0 that crashed.
The minidump points to the native module serialport.node.
Exception 0xc06d007f, lastError=127 means that the DLL loaded, but the required function was not found in it (GetProcAddress / ERROR_PROC_NOT_FOUND). This is confirmed by the Microsoft documentation.
This was not a memory overflow caused by the LibreView report: the isolated Chrome instance reached a maximum of 665.8 MB with a 1.2 GB limit and did not crash.
LibreView did not provide the medical data: Cloudflare Turnstile identified the automated environment and returned CAPTCHA 600010, after which LibreView displayed error 437. Cloudflare classifies 600* as a verification failure due to bot-like behavior — Turnstile error codes.
A new version of Codex, 26.715.10079.0, is currently installed. The old serialport.node has been replaced with bindings.node; there have been no similar crashes from the new version in the Windows log so far. Therefore, the previous native defect has probably already been fixed, although the connection specifically to LibreView cannot be proven without a new crash.
Sandbox: [README.md](R:\\Claude_Cowork\\Projects\\BejenariProject\\99_staging\\libreview-sandbox\\README.md)
Main script: [run.ps1](R:\\Claude_Cowork\\Projects\\BejenariProject\\99_staging\\libreview-sandbox\\run.ps1)
Final anonymized report: [report.json](R:\\Claude_Cowork\\Projects\\BejenariProject\\99_staging\\libreview-sandbox\\reports\\2026-07-23T11-37-56-698Z\\report.json)

reports.zip

README.md

What steps can reproduce the bug?

start codex project and read librelink web link

What is the expected behavior?

_No response_

Additional information

_No response_

<!-- codex-issue-translator -->

github-actions[bot] contributor · 1 month ago

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

  • #34311
  • #33710
  • #34119

Powered by Codex Action

BaxLi · 1 month ago

I din't observe such detailed crash report as it is.
So it maybe a duplicated - but with more technical details provided and sandbox tests performed to deeply understand the issue.