NVDA Application Crash - Memory Access Error on Windows

[ajay-EY-1859]

Brief summary

NVDA crashes with a memory access error: 'The instruction at 0x00007FF88975F844 referenced memory at 0x0000000000000000. The memory could not be read.'

Steps to reproduce

1. Launch NVDA application
2. Error dialog appears with access violation message
3. Click OK to terminate the program

Actual behavior

NVDA crashes immediately with an access violation error dialog:

Error message: 'nvda.exe - Application Error'
'The instruction at 0x00007FF88975F844 referenced memory at 0x0000000000000000. The memory could not be read.'

The application terminates when the user clicks OK.

Expected behavior

NVDA should launch successfully without any application errors or crashes. The screen reader should start normally and be ready for use.

NVDA logs, crash dumps and other attachments

Please attach any nvda_crash.dmp files if available in %appdata%/nvda directory. Include NVDA logs from the session if possible.

NVDA type

installed copy

NVDA version

Latest stable version

Have you tried any other versions of NVDA? If so, please report their behaviors.

No response

Windows version

Windows (latest - please provide exact version from System Information)

Name and version of other software in use when reproducing the issue

Not specified - please provide versions of any software that might be installed on this system

Other information about your system

This appears to be a critical startup crash affecting the application immediately upon launch.

Does the issue still occur after restarting your computer?

I have not restarted my computer

If NVDA add-ons are disabled, is your problem still occurring?

I do not have any NVDA add-ons installed

Does the issue still occur after you run the System Accessibility Repair Tool (COM Registration Fixing Tool in older versions) in NVDA's tools menu?

I have not run the System Accessibility Repair Tool

[ABuffEr]

Hi @ajay-EY-1859,
first of all, fully restart your computer. Errors like this could be NVDA independent, due to OS memory issues or changes (memory pressure, virtual memory/pagefile management, etc).
If error persist, try to disable fast startup from energy settings and restart again (you can re-enable that option later).
If this not solve, please specify the real NVDA and Windows version ("latest" is not a useful version).

[SaschaCowley]

Welcome @ajay-EY-1859 ,

We are unable to process this issue as it stands.

• Please fill out the issue template fully.

Kind Regards,
NV Access Software Developers

[saisharan0103]

The repro details point to a startup-time null read: NVDA is an installed copy, the dialog appears immediately after launch, and the referenced memory address is 0x0000000000000000. For a PR, I would start by using the crash dump and session log to identify the failing startup component, then narrow it to a missing guard or initialization ordering issue. Is an nvda_crash.dmp from %appdata%/nvda available for this run?

[makhlwf]

The repro details point to a startup-time null read: NVDA is an installed copy, the dialog appears immediately after launch, and the referenced memory address is 0x0000000000000000. For a PR, I would start by using the crash dump and session log to identify the failing startup component, then narrow it to a missing guard or initialization ordering issue. Is an nvda_crash.dmp from %appdata%/nvda available for this run?

Is this an AI agent؟

[SaschaCowley]

@saisharan0103 that is abundantly clear. If you have anything that is not surface-level to report, please feel free. Otherwise, please refrain from making these comments, they are not a good use of your or our time.