Windows 10: Explorer.exe Keeps Crashing

I concur with @calendon Ken about an in-place upgrade repair install. That said, I did find some info at answers.ms.com on your specific error condition:
problem event name BEX64 windows explorer has stopped working - Microsoft Community
Windows Explorer has stopped working - Microsoft Community
--Ed--

 

I need help to figure out what is causing my explorer.exe to keep crashing. Happens mostly when closing a window.

From the event viewer,
Code: Faulting application name: Explorer.EXE, version: 10.0.16299.248, time stamp: 0x18ee648b Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000032c0fae Faulting process id: 0x1530 Faulting application start time: 0x01d3d77bceb35122 Faulting application path: C:\WINDOWS\Explorer.EXE Faulting module path: unknown Report Id: 6761ce56-d516-47f2-8ea5-84f1ac0b6e98[/quote]
Things I have tried to fix this,

• Ran sfc /scannow
• Ran CCleaner cleaning

Processes using explorer.exe,




:)

 

Windows 10 Explorer keeps crashing

Since yesterday explorer.exe keeps on crashing and I can't get anything.

 

my windows 10 keep crashing

my windows 10 keep crashing 7 times today showing blue screen saying critical system failure sometimes explorer.exe crashed also any help

 

If it's crashing, you can try running the Reliability Monitor and look at the detail info in there, too. Might shed a little more light on the topic. Here's a snip from the recently-revealed blocking bug in Settings from Build 17134, for example:



HTH,
--Ed--

 

Gave me some more info but Im not sure what it means...

Code: Description Faulting Application Path: C:\Windows\explorer.exe Problem signature Problem Event Name: BEX64 Application Name: Explorer.EXE Application Version: 10.0.16299.248 Application Timestamp: 18ee648b Fault Module Name: StackHash_baa9 Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: PCH_93_FROM_ntdll+0x00000000000A0E14 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 10.0.16299.2.0.0.768.101 Locale ID: 1033 Additional Information 1: baa9 Additional Information 2: baa9ca92bccf5da1d131f62b82f5c318 Additional Information 3: c0d3 Additional Information 4: c0d3e39baca81c811ab3055dfc7bce19[/quote]

 

If sfc found nothing I think I would do an inplace repair / upgrade. Assuming you are on V1709 this will be a repair.

Repair Install Windows 10 with an In-place Upgrade

I always recommend having a full data backup even through the process is supposed to be non-destructive.

Another alternative would be to try a clean boot to see if this is being caused by third party software.

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts