# Windows Codex Desktop 26.707.62119 repeatedly bugchecks host (0x13A / 0xC2) when starting tasks, then loses project/sidebar mappings

Windows Codex Desktop 26.707.62119 repeatedly bugchecks host (0x13A / 0xC2) when starting tasks, then loses project/sidebar mappings

Codex app version

26.707.62119 (latest client version observed in local Codex logs)

Older client versions also present in the log history: 26.707.61608, 26.707.31428, 26.707.31123, 26.623.141536, 26.623.101652.

Platform

• Windows 11 Pro 25H2, build 26200.8655, x64
• Lenovo Legion 2025 laptop
• Intel Core Ultra 9
• 32 GB DDR5
• NVIDIA GeForce RTX 5070 Ti Laptop GPU
• NVIDIA driver 610.62
• Tested in both dedicated-GPU and Hybrid modes
• Tested in Balanced and Performance power modes
• Internal 2K display; some crashes occurred with an extended 4K TV, but the latest repro did not require multiple concurrent tasks

Summary

Codex Desktop is a reliable trigger for whole-machine Windows kernel bugchecks on this laptop. On 2026-07-13, Windows recorded six bugchecks while Codex was active. Five were 0x13A KERNEL_MODE_HEAP_CORRUPTION; one was 0xC2 BAD_POOL_CALLER.

The latest reproduction happened immediately after pressing Enter to run one Codex task. Earlier reproductions often occurred when starting a second task, but the latest crash demonstrates that multiple tasks are not required.

After the repeated crashes, Codex Desktop also lost its project/sidebar mappings: projects disappeared, some tasks became orphaned, and valid tasks were omitted from the local visible-thread catalog even though all conversation data remained intact.

This report does not claim a normal user-mode app directly writes kernel memory. It reports that this Codex Desktop build/workload is a repeatable trigger for a kernel-mode corruption path on this system and that the forced reboots also expose a Codex project-state durability bug.

Reproduction

1. Start Codex Desktop on Windows.
2. Open an existing local task or project.
3. Enter a prompt and press Enter to begin the task.
4. The external display may lose output first; the internal display then shows the Windows kernel crash text.
5. Audio freezes/repeats briefly and Windows automatically reboots.
6. Relaunch Codex.
7. Repeat with one or more tasks. The failure has reproduced six times in one day.
8. After the reboots, observe missing projects and/or tasks in the left sidebar even though the underlying local conversation records and rollout files still exist.

Windows bugcheck evidence

All times are local on 2026-07-13.

| Time | Bugcheck | Parameter 1 | Dump |
|---|---:|---:|---|
| 9:35:12 AM | 0x13A | 0x8 | C:\Windows\Minidump\071326-17453-01.dmp |
| 10:14:57 AM | 0x13A | 0x12 | C:\Windows\Minidump\071326-17906-01.dmp |
| 10:26:19 AM | 0x13A | 0x12 | C:\Windows\Minidump\071326-12421-01.dmp |
| 10:59:35 AM | 0xC2 | 0xD | C:\Windows\Minidump\071326-17078-01.dmp |
| 12:45:26 PM | 0x13A | 0x12 | C:\Windows\Minidump\071326-16625-01.dmp |
| 1:34:29 PM | 0x13A | 0x12 | C:\Windows\Minidump\071326-15375-01.dmp |

The latest WER report ID is 3e0fc8bd-eb3e-414c-bb9f-53e40e63d91e.

Codex local-state evidence after the crashes

A read-only recovery audit and verified backup found:

• %USERPROFILE%\.codex\state_5.sqlite: 29 intact thread records.
• Nine normal user-facing tasks after including the recovery task; 20 internal guardian/subagent records.
• All corresponding rollout/conversation JSONL files remained present under %USERPROFILE%\.codex\sessions.
• All examined SQLite databases passed PRAGMA integrity_check.
• .codex-global-state.json had been reduced to only a few saved workspace roots even though other valid project roots still existed in task metadata.
• sqlite\codex-dev.db.local_thread_catalog contained only seven visible tasks and omitted two valid normal user tasks.
• One missing Wall Decals task was still directly readable by thread ID with full prior context, proving this was a visibility/index failure rather than conversation deletion.
• A tested repair restored the catalog rows, but the running desktop shell rewrote the repaired global project registry from its stale in-memory copy. This matches public reports that the app must be completely closed before restoring .codex-global-state.json.

Expected behavior

• Starting a Codex task must not trigger a Windows kernel bugcheck.
• Codex Desktop should fail safely if a renderer, GPU, app-server, sandbox, or memory subsystem fails.
• Project/sidebar mappings should be written atomically and reconstructed from durable state_5.sqlite, session_index.jsonl, and rollout files after an unclean shutdown.
• The live app should not overwrite a newer, valid project registry with stale in-memory state.
• All valid unarchived local tasks should remain visible/searchable after restart.

Impact

• Six forced reboots in approximately four hours.
• Work interruption and risk of unrelated file corruption.
• Projects and task associations appeared to be lost after reboot.
• User cannot safely rely on Codex Desktop for normal work because even a single task can reproduce the host crash.

Related public reports

• openai/codex#19615 — projects and conversations missing after computer restart.
• openai/codex#19290 — Windows sidebar shows no chats/projects after update while search still finds them.
• openai/codex#19873 — project list lost after update; project grouping remains broken; live app can overwrite local repair.
• openai/codex#20254 — Windows sidebar hides valid local project threads while SQLite and rollout files are intact.
• openai/codex#24598 — Codex Desktop crash/stability report with WER and local log guidance.
• openai/codex#24998 — Windows desktop app crashes during use.
• Public Reddit report: Codex app triggering a Windows VIDEO_MEMORY_MANAGEMENT_INTERNAL (0x10E) BSOD.

Private diagnostics available to OpenAI Support

The following should be provided privately, not attached to a public GitHub issue, because they may include prompts, paths, or other sensitive context:

• Six Windows minidumps listed above.
• %USERPROFILE%\.codex\logs_2.sqlite
• %USERPROFILE%\.codex\state_5.sqlite
• Pre- and post-crash .codex-global-state.json
• session_index.jsonl
• Windows Event Viewer System events 41, 1001, and 162
• Timestamped recovery backup and SHA-256 manifests

Safety note for maintainers

Please request the dumps and raw Codex logs through a private support/upload channel. The public report intentionally contains no raw conversation text, authentication material, or dump contents.