Recurrent Explorer Crashes

I'm not getting BSODs. Just recurrent Explorer crashes. Is this the right place for that?

If so, I'll proceed to submit the information requested in the Posting Instructions.

In this Video, i will show you how to fix the slow right-click issues and File Explorer Crashing problems in Windows.

Thanks, but context menu handlers do not seem to be relevant.

I had probably better describe the problem before we try to identify solutions.

Per the Posting Instructions, I've attached the .zip file produced by the V2 Log Collector.

In case it helps, here are the problem details for the most recent crash, as produced by perfmon /rel:


Source
Windows Explorer

Summary
Stopped working

Date
‎3/‎28/‎2025 8:02 PM

Status
Report sent

Description
Faulting Application Path: C:\Windows\explorer.exe

Problem signature
Problem Event Name: BEX64
Application Name: Explorer.EXE
Application Version: 10.0.26100.3323
Application Timestamp: 98a027e7
Fault Module Name: Explorer.EXE
Fault Module Version: 10.0.26100.3323
Fault Module Timestamp: 98a027e7
Exception Offset: 000000000007b5d8
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.26100.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 3c81
Additional Information 2: 3c81df0a588e59f1fcb20e01e506af1e
Additional Information 3: d240
Additional Information 4: d240ef0243f7ce4449186b0f1d24f933

Extra information about the problem
Bucket ID: a948b03ffc73336db7caeae4f7732518 (1714440877292856600)


Thanks in advance for your assistance.

There were non-explorer findings in the log files.

Please open a second thread to evaluate possible drive problems so you can continue to get help for explorer problems.

a screenshot would be nice.

Does windows explorer always crash or does it stay open for a while and what partition/file do you access to cause it to crash?

Not sure how to proceed with the suggestion. I mean, I understand what a separate thread is, but not sure what I'd be asking about in it.

Screenshot. You mean, of Explorer? Not much to see: sessions of File Explorer open one minute, gone the next.

It stays open most times. But then once in a while, apropos of nothing in particular that I've noticed, it shuts down: the open File Explorer sessions disappear; the taskbar goes blank and then restores. I'm not plugging in USB devices or doing anything that has (so far) cued me to a particular culprit.

raywood said:

Not sure how to proceed with the suggestion. I mean, I understand what a separate thread is, but not sure what I'd be asking about in it.

Screenshot. You mean, of Explorer? Not much to see: sessions of File Explorer open one minute, gone the next.

It stays open most times. But then once in a while, apropos of nothing in particular that I've noticed, it shuts down: the open File Explorer sessions disappear; the taskbar goes blank and then restores. I'm not plugging in USB devices or doing anything that has (so far) cued me to a particular culprit.

Click to expand...

Nice machine you got there.
Yes.
one question at a time:
Does explorer always crash when you open it?

second question: are you doing anything to explorer, like looking for a file, when it crashes, or are you using some other app like a browser.

since big delay here: third question: since you have a 13th gen cpu I have to check that you are on the very latest BIOS release.

raywood said:

Not sure how to proceed with the suggestion. I mean, I understand what a separate thread is, but not sure what I'd be asking about in it.

Click to expand...

Thread title: Work up some event viewer entries:

An error was detected on device \Device\Harddisk3\DR19 during a paging operation.
An error was detected on device \Device\Harddisk3\DR24 during a paging operation.
An error was detected on device \Device\Harddisk3\DR23 during a paging operation.
An error was detected on device \Device\Harddisk3\DR21 during a paging operation.
An error was detected on device \Device\Harddisk5\DR7 during a paging operation.
An error was detected on device \Device\Harddisk4\DR5 during a paging operation.
{Delayed Write Failed} Windows was unable to save all the data for the file \:$I30:$INDEX_ALLOCATION. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
{Delayed Write Failed} Windows was unable to save all the data for the file \$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: P:, DeviceName: \Device\VeraCryptVolumeP.

Failure status: A device which does not exist was specified.
The default transaction resource manager on volume P: encountered a non-retryable error and could not start. The data contains the error code.
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
The previous system shutdown at 1:15:57 PM on ?3/?25/?2025 was unexpected.
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{aae20b56-3001-4042-8080-6bf48c7965ca}, DeviceName: \Device\HarddiskVolume7.
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\000000d3) was retried.

BIOS release is a good question. I reboot rarely - lots of stuff running. But I will look, next time I do. I did download the latest BIOS, back in December. That probably but not definitely means I actually installed it.

So far, I haven't noticed any particular event or activity triggering Explorer crashes. You asked for a screenshot. Here's one that may illuminate. The crashes are relatively infrequent:



As in the highlighted example, most of the Application Failures shown in this image do feature an Explorer crash at some time of day, not necessarily linked to any other listed Application Failures.

Separate thread on possible drive issues: I've made a stab at it.

first things: D/L the latest BIOS from ASUS. Boot to BIOS (del or F2) and see what version you have installed and if not the latest, install the BIOS.
13th and 14th gen Intel cpus can cause serious random problems if the correct microcode is not in the BIOS.(manufacturing prob)
(For ASUS you do this by unzipping the BIOS, clicking on the rename thing and then copying the renamed module to a new root folder on your C: drive so you can easily find it in the flashing section in the ASUS BIOS.)