Edge 155 repeatedly crashes with 0xC0000005 NX fault in History SQLite/ICU path

Question

Edge 155 repeatedly crashes with 0xC0000005 NX fault in History SQLite/ICU path

RickyJack 0

Microsoft Edge is intermittently terminating and closing all browser windows on my Windows 11 Pro system.

This has reproduced on multiple Edge builds, including:

154.0.4258.53
155.0.4283.45

The crashes are consistently:

0xC0000005
AV.Type: Execute
SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE

The latest full ProcDump was captured on Edge 155.0.4283.45 after I had already run Repair Microsoft Edge.

WinDbg reports:

Failure.Bucket:
SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE_c0000005_msedge.dll!sqlite3BtreeTableMoveto

Failure.Hash:
{0133c442-4058-8453-3eaf-45ed31f47f48}

The regular stack repeatedly shows:

msedge!sqlite3BtreeTableMoveto
msedge!sqlite3VdbeExec
msedge!sql::Statement::StepInternal
msedge!sql::Statement::Step
msedge!history::URLDatabase::GetUrlRowsByKeywords
msedge!history::HistoryBackend::QueryHistoryByKeywords

The hardware shadow stack additionally shows:

msedge!icuLikeFunc
msedge!sqlite3VdbeExec
msedge!sql::Statement::StepInternal
msedge!sql::Statement::Step
msedge!history::URLDatabase::GetUrlRowsByKeywords
msedge!history::HistoryBackend::QueryHistoryByKeywords

Across separate crashes, Edge has attempted to execute different non-code memory locations, including stack memory, heap URL/text data, ICU table data, read-only msedge.dll data, and near-null address 0x74.

The problem still occurs after:

rebuilding the Edge profile
clearing history
disabling History sync
disabling all sync categories
disabling extensions
disabling hardware acceleration
disabling Nahimic/A-Volute injection
updating Edge 154 → 155
running Edge Repair

Brave remains stable on the same Windows installation.

I have retained multiple:

Edge Crashpad dumps
full-memory ProcDump files
WinDbg !analyze -v outputs
hardware shadow-stack outputs

The full dumps are about 1 GB each and are available to Microsoft engineering if requested.

This appears reproducibly tied to:

History keyword query
→ SQLite
→ ICU LIKE/case-folding processing
→ invalid control transfer / NX fault

If a Microsoft moderator or Edge engineer can escalate this based on the failure bucket/hash above, I can provide the corresponding dumps privately.Microsoft Edge is intermittently terminating and closing all browser windows on my Windows 11 Pro system.

This has reproduced on multiple Edge builds, including:

154.0.4258.53
155.0.4283.45

The crashes are consistently:

0xC0000005
AV.Type: Execute
SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE

The latest full ProcDump was captured on Edge 155.0.4283.45 after I had already run Repair Microsoft Edge.

WinDbg reports:

Failure.Bucket:
SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE_c0000005_msedge.dll!sqlite3BtreeTableMoveto

Failure.Hash:
{0133c442-4058-8453-3eaf-45ed31f47f48}

The regular stack repeatedly shows:

msedge!sqlite3BtreeTableMoveto
msedge!sqlite3VdbeExec
msedge!sql::Statement::StepInternal
msedge!sql::Statement::Step
msedge!history::URLDatabase::GetUrlRowsByKeywords
msedge!history::HistoryBackend::QueryHistoryByKeywords

The hardware shadow stack additionally shows:

msedge!icuLikeFunc
msedge!sqlite3VdbeExec
msedge!sql::Statement::StepInternal
msedge!sql::Statement::Step
msedge!history::URLDatabase::GetUrlRowsByKeywords
msedge!history::HistoryBackend::QueryHistoryByKeywords

Across separate crashes, Edge has attempted to execute different non-code memory locations, including stack memory, heap URL/text data, ICU table data, read-only msedge.dll data, and near-null address 0x74.

The problem still occurs after:

rebuilding the Edge profile
clearing history
disabling History sync
disabling all sync categories
disabling extensions
disabling hardware acceleration
disabling Nahimic/A-Volute injection
updating Edge 154 → 155
running Edge Repair

Brave remains stable on the same Windows installation.

I have retained multiple:

Edge Crashpad dumps
full-memory ProcDump files
WinDbg !analyze -v outputs
hardware shadow-stack outputs

The full dumps are about 1 GB each and are available to Microsoft engineering if requested.

This appears reproducibly tied to:

History keyword query
→ SQLite
→ ICU LIKE/case-folding processing
→ invalid control transfer / NX fault

If a Microsoft moderator or Edge engineer can escalate this based on the failure bucket/hash above, I can provide the corresponding dumps privately.

0 comments

2 answers

Your answer

Answer 1

RickyJack 0

how do i submit it through support

0 comments

Answer 2

The supported next step is to collect the Edge crash data in the format Microsoft Support requests and submit it through Support.

For repeated Edge crashes or launch failures, the documented data to collect is:

Edge version: go to edge://version and record the full version.
Application Error events: open Event Viewer → Windows Logs → Application, filter for source Application Error together with faulting module msedge.exe, and export the matching entries.
Crash ID: go to edge://crashes and record the most recent crash ID.

Because the issue persists after Edge Repair and profile rebuild attempts, also collect the broader diagnostic set used for Edge performance/crash investigations:

Go to edge://settings/help and note the full version number.
Press Shift+Esc in Edge to open Browser Task Manager and capture one screenshot sorted by CPU and another sorted by Memory.
Go to edge://discards and save the output.

If crash reporting is enabled, crash dumps are stored locally and sent to Microsoft over an encrypted link. The local crash list can be viewed at edge://crashes. If local crash entries need to be cleared before reproducing, use the Clear all button on edge://crashes.

For enterprise-managed environments, crash and diagnostic data collection can also be managed by policy.

References: