Computer crashing after cursor update

Tomer_Z · April 5, 2026, 11:30am

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

after updating to cursor 3.
windows 11 is crashing with IRQL_NOT_LESS_OR_EQUAL (0xA).

attached dump log:

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

– Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.218 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Loading Dump File [C:\Windows\Minidump\040526-11500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff8009be00000 PsLoadedModuleList = 0xfffff8009ccf50c0
Debug session time: Sun Apr 5 13:52:53.912 2026 (UTC + 3:00)
System Uptime: 0 days 0:03:14.712
Loading Kernel Symbols
…
…
…
…
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000fb23735018). Type ".hh dbgerr001" for details Loading unloaded module list ............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8009c2fb990 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffca098b6cf000=000000000000000a 9: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ...................................... Loading User Symbols PEB is paged out (Peb.Ldr = 000000fb23735018). Type “.hh dbgerr001” for details
Loading unloaded module list
…

                   Bugcheck Analysis                                    *

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000000c5, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8009c01df2b, address which referenced memory

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 812

Key  : Analysis.Elapsed.mSec
Value: 809

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 1

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 328

Key  : Analysis.Init.Elapsed.mSec
Value: 17034

Key  : Analysis.Memory.CommitPeak.Mb
Value: 81

Key  : Analysis.Version.DbgEng
Value: 10.0.29547.1002

Key  : Analysis.Version.Description
Value: 10.2602.27.2 amd64fre

Key  : Analysis.Version.Ext
Value: 1.2602.27.2

Key  : Bugcheck.Code.LegacyAPI
Value: 0xa

Key  : Bugcheck.Code.TargetModel
Value: 0xa

Key  : Dump.Attributes.AsUlong
Value: 0x21808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 0

Key  : Failure.Bucket
Value: AV_nt!MiCompletePrivateZeroFault

Key  : Failure.Exception.IP.Address
Value: 0xfffff8009c01df2b

Key  : Failure.Exception.IP.Module
Value: nt

Key  : Failure.Exception.IP.Offset
Value: 0x21df2b

Key  : Failure.Hash
Value: {da77f906-0950-e1c7-5aba-d57356ac6e7e}

Key  : Faulting.IP.Type
Value: Paged

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key  : Hypervisor.Flags.Phase0InitDone
Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 1

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 55185662

Key  : Hypervisor.Flags.ValueHex
Value: 0x34a10fe

Key  : Hypervisor.Flags.VpAssistPage
Value: 1

Key  : Hypervisor.Flags.VsmAvailable
Value: 1

Key  : Hypervisor.RootFlags.AccessStats
Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key  : Hypervisor.RootFlags.Value
Value: 1015

Key  : Hypervisor.RootFlags.ValueHex
Value: 0x3f7

Key  : WER.System.BIOSRevision
Value: 5.27.0.0

BUGCHECK_CODE: a

BUGCHECK_P1: c5

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8009c01df2b

FILE_IN_CAB: 040526-11500-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffe1055d15c080

WRITE_ADDRESS: fffff8009cdc44c8: Unable to get MiVisibleState
00000000000000c5

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Cursor.exe

IP_IN_PAGED_CODE:
nt!MiCompletePrivateZeroFault+beb
fffff800`9c01df2b 97 xchg eax,edi

STACK_TEXT:
ffffca098b6ceff8 fffff8009c4bece9 : 000000000000000a 00000000000000c5 0000000000000002 0000000000000001 : nt!KeBugCheckEx
ffffca098b6cf000 fffff8009c4b9fa8 : ffff828018e97090 0000000000000000 ffffca098b6cf7f8 fffff8009c01edb6 : nt!KiBugCheckDispatch+0x69
ffffca098b6cf140 fffff8009c01df2b : 0000000000000000 ffffb49556039e58 0000000000000011 ffffdb6605560001 : nt!KiPageFault+0x468
ffffca098b6cf2d0 fffff8009c0fe6ce : ffffe1055bec6000 ffffca098b6cf420 0000000000000001 ffffca0900002010 : nt!MiCompletePrivateZeroFault+0xbeb
ffffca098b6cf3e0 fffff8009c0fc846 : 0000000000000009 0000000000000000 ffffffffffffffff ffffe1055d146480 : nt!MiResolvePrivateZeroFault+0x65e
ffffca098b6cf5a0 fffff8009c01489e : ffffca098b6cf8e0 ffffca098b6cf840 ffffb49556039e58 ffffb4ffffffffff : nt!MiResolveDemandZeroFault+0x246
ffffca098b6cf740 fffff8009c016976 : 00002aac073ca000 ffff800000000004 00002aac073cb008 0000000000000000 : nt!MiDispatchFault+0x5ee
ffffca098b6cf8b0 fffff8009c4b9ecb : 00007ff74a1f1b80 00002aac07101f00 00002aac07680948 000000fb2a7ff128 : nt!MmAccessFault+0x226
ffffca098b6cfa20 00007ff7423a58a0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x38b
000000fb2a7fee70 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff7`423a58a0

SYMBOL_NAME: nt!MiCompletePrivateZeroFault+beb

MODULE_NAME: nt

IMAGE_VERSION: 10.0.26100.8036

STACK_COMMAND: .process /r /p 0xffffe1055d146080; .thread /r /p 0xffffe1055d15c080 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: beb

FAILURE_BUCKET_ID: AV_nt!MiCompletePrivateZeroFault

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {da77f906-0950-e1c7-5aba-d57356ac6e7e}

Followup: MachineOwner

Steps to Reproduce

launch it

Operating System

Windows 10/11

Version Information

unable to launch app

Does this stop you from using Cursor

Yes - Cursor is unusable

deanrie · April 5, 2026, 11:39am

Hey, thanks for the detailed crash dump.

The crash happens in nt!MiCompletePrivateZeroFault, which is part of the Windows kernel memory management subsystem. IRQL_NOT_LESS_OR_EQUAL usually means some driver is touching invalid memory at a raised IRQL. Cursor (as an Electron app) can trigger it, but the root cause is more likely a driver or hardware issue.

A similar case was reported here, and updating the GPU driver fixed it: Cursor crashes Windows11

Here’s what to try:

Run Cursor with cursor --disable-gpu from the command line. If the BSOD stops, it’s likely a GPU driver issue.
Update your GPU drivers to the latest version (both the dedicated GPU and the integrated one, if you have both).
- Intel: https://www.intel.com/content/www/us/en/download-center/home.html
- NVIDIA: Download The Latest Official NVIDIA Drivers
If --disable-gpu doesn’t help, check RAM using Windows Memory Diagnostic mdsched.exe. MiCompletePrivateZeroFault can sometimes point to RAM issues.

Also, please share which GPU you have (and whether you have integrated graphics) and what GPU driver version you’re on. That’ll help narrow it down.

Tomer_Z · April 5, 2026, 2:57pm

Thank you for your reply.

i have installed 2.6 again and everything works fine.
2. GPU: AMD Radeon RX 7900XTX, drivers are up to date 26.3.1,
integrated GPU Intel UHD Graphics 770, driver 32.0.101.6129

deanrie · April 5, 2026, 3:03pm

Glad to hear everything’s stable on 2.6. Thanks for the GPU info.

If you ever want to try Cursor 3 again, run cursor --disable-gpu from the command line. That turns off GPU acceleration and will probably prevent the BSOD. You can also go to Windows Settings > System > Display > Graphics and force Cursor to use the AMD GPU instead of the built-in Intel one. Sometimes Windows defaults to the iGPU, and that’s what causes the conflict.

Let me know if you decide to try it.

Topic		Replies	Views
Cursor crashes Windows11 Bug Reports crashes , windows	3	69	March 20, 2026
Green screen in Windows 11 Bug Reports crashes , windows	4	72	February 24, 2026
Constant crashing in v2 due to GPU handoffs - switching to CLI Bug Reports cli , java	2	74	November 29, 2025
Cursor stuck at waiting for extension,Keep crashing,ai Agent is completely unusable even after disabling all extension Bug Reports chat , installation , crashes , windows	8	907	March 26, 2026
Cursor 1.7.4x crashes when GPU is enabled (renderer code 5) Bug Reports	11	311	November 15, 2025