Explorer Crash on Opening. Faulting application name: Explorer.EXE, version: 10.0.22621.4541, time stamp: 0x5136cabe

Question

I have many drives (6+) on my computers and access to external drives and network location. Western Digital Red for the most part (Everything is Western Digital and now using NVME + Red). Drives are sleeping unless requested.

When i copy data from one disk to the other, if i close all my Explorer windows while leaving the "Running Actions" window opened.

If i start Explorer (Windows+E for instance), Explorer will freeze and then crash and restart and thus cancelling my file transfer right in the middle of it

Since Windows 7 Ultimate, then Windows 10 Pro and Windows 11 Pro.

With different hardware/computers

Multiple Windows reinstallation (20+) through the years and happening even after installing drivers but before installing extra software such as Bulk Rename or an Anti-Virus

Can this issue be reproduced; Yes, I'd tend to say every time

The Event Viewer log is the following:

Faulting application name: Explorer.EXE, version: 10.0.22621.4541, time stamp: 0x5136cabe

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0000000003940fd8

Faulting process id: 0x0x3358

Faulting application start time: 0x0x1DB4F7F92F0F544

Faulting application path: C:\Windows\Explorer.EXE

Faulting module path: unknown

Report Id: d30cfbe4-ea93-49f4-8630-1f57f3b3bf28

Faulting package full name: 

Faulting package-relative application ID: 

Now, one thing that i have tried today was to launch a command prompt and open Explorer from there; No issue

This raises the question, what is the difference between launching Explorer from a command prompt and one using the Windows launch whether from the Windows+E shortcut or the icon...

Please escalate this ticket to support

Please refrain from asking me to run checks on my computer; I've already said that reinstalling windows did not solve the issue and the issue was present with a clean Windows installation so it would be pointless to do so and a waste of my time. You could try to reproduce the issue in your own lab environment with the bases that i have provided.

Thank you

***Moved from Windows / Windows 11 / Files, folders, and storage***

Answer 1

I've crashed like 8 times for the past two week during file transfer

Today, I've crashed without even doing file transfer, nothing was running, launched explorer, it froze and restarted automatically. This doesn't happen often, most of the time it is during file transfer. I heard at the same time one of my WD red which started to spin right after the crash as it was waking up...

I wonder if it tried to read data from my "recent" folder to generate for instance thumbnails...and failed to do so in a timely manner since the disk was sleeping...

Faulting application name: Explorer.EXE, version: 10.0.22621.4541, time stamp: 0x5136cabe

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0000000002d00fd8

Faulting process id: 0x0x26D0

Faulting application start time: 0x0x1DB5317310D1A02

Faulting application path: C:\Windows\Explorer.EXE

Faulting module path: unknown

Report Id: b6896e43-315b-4321-b033-2e4875aa2548

Faulting package full name: 

Faulting package-relative application ID: