Cursor keeps crashing with code '-1073741819'

[SeBsZ]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This bug has been occurring for a few weeks now and some days I hardly encounter it, on other days like today it happens over 10 times and it makes working with Cursor unbearable. This never used to be an issue, but I don’t know from which version it started.

The difficult part is that it happens randomly - while programming manually, or an agent is working through some things, or I’m just scrolling through a log file. Especially today I’ve had it crash in the middle of an agent working. Each time when it re-opens the IDE I have to ask the agent to continue where it left off and usually it does a good job continuing - that’s great at least.

The whole IDE turns black suddenly with a popup “The window terminated unexpectedly (reason: ‘crashed’, code: ‘-1073741819’)” - it’s extremely descriptive.

I’m willing to help as much as I can!

Steps to Reproduce

Very difficult to explain - it seems to happen mostly when either looking at a .log file or while an agent is working on something.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.4.31 (user setup)
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Any, GPT-5.1, 5.2, 5.3-Codex

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[SeBsZ]

2026-02-10 15:45:21.847 [error] [Main] CodeWindow: renderer process gone (reason: crashed, code: -1073741819)
2026-02-10 15:45:21.854 [info] [Main] Extension host with pid 5564 exited with code: 0, signal: unknown.
2026-02-10 15:45:21.857 [info] [Main] Extension host with pid 26212 exited with code: 0, signal: unknown.

This is all I see in the logs. I also seem to be able to reproduce this by moving the window, resizing it, snapping it.

[ani-anysphere (Ani Betts)]

Hey @SeBsZ, this error code is just 0xc0000005 (segfault). There are lots of reasons why this could happen but I would try running a memory testing tool like MemTest86+ first, to make sure your RAM isn’t faulty

[SeBsZ]

Hey, thanks, but I have in fact run MemTest86+ for a whole night just the other day as my Google search for this code also pointed at memory. No issues were found at all. No other applications have issues except for some Chrome tabs crashing rarely - nothing like Cursor.

Could it be anything else?

[ani-anysphere (Ani Betts)]

Given that it repros more when you resize the window, you could try disabling hardware acceleration, Cursor Screen Flickering bug - #10 by SamuraiCobra explains how to do it, or updating your video drivers