intermittent BEX64 explorer.exe crash

Hello folk,

Would very much like some thoughts on the following. Hopefully anyone has clues or tips.

On a fully updated and legally activated system with careful installation of 3rd party software there is an intermittent crash of explorer.exe in both Windows 10 Pro as in Windows 10 Home, which is the present OS. As far as my logic goes it can only be caused by 3rd party software, unless Windows 10 is inherently buggy?
The good news is Explorer recovers instantly without any actions needed. Can continue working.

Happens when:
Unclear but seems random. Last crash was when opening a folder.

Already done:
sfc /scannow (ok)
Dism /online /cleanup-image /restorehealth (ok)

Unlikely cause:
Several context menu entry removals (from Brink's tutorials)


Here the event info in Dutch which is exactly the same in the 3 crashes this month:

Naam van probleemgebeurtenis: BEX64
Naam van de toepassing: Explorer.EXE
Versie van toepassing: 10.0.18362.145
Tijdstempel van toepassing: 8a1c1adf
Naam van foutmodule: StackHash_9147
Versie van foutmodule: 0.0.0.0
Tijdstempel van foutmodule: 00000000
Uitzonderingsmarge: PCH_D0_FROM_ntdll+0x000000000009CBB4
Uitzonderingscode: c0000005
Uitzonderingsgegevens: 0000000000000008
Versie van besturingssysteem: 10.0.18362.2.0.0.768.101
Landinstelling-id: 1043
Aanvullende informatie 1: 9147
Aanvullende informatie 2: 9147ad64d9a57077d2f68e2ed750d935
Aanvullende informatie 3: ac8e
Aanvullende informatie 4: ac8e188d77783fc278a3c9493613cb54

Extra informatie over het probleem
Bucket-id: 9ef693b93a331a7d9b1b305a45affaef (1953208027669592815)


Thank you
dm

Hi dinkymau, Welcome to 10F!

BEX refers to Buffer Overflow Exception, see:
http://technet.microsoft.com/en-us/l...83(WS.10).aspx

And you're right it most likely has to do with your 3rd party programs. I'm trying to think which way would be the easiest to check this.

• You could try running in safe mode to see if bex shows up or
• You could disable your 3rd parties one by one to see who the offender is or
• You put you 3rd parties on the DEP whitelist or
• If you find the offender reinstall it with win 7 compatibility mode.

One thing for sure, make sure everything, everything is up-to-date!

It would be very helpful if you could fill in your System Specs: System Specs - Fill in at Ten Forums

Thank you for the helpful answers. Had hoped the event information would point to the cause more precise.

I never considered DEP exceptions before. I know and trust my 3rd parties so adding some seems useful.
The safer route is to start disabling or exchanging 3rd party action least familiar with. Here goes !

Thanks for working on your system specs dinkymau.

There's a couple of items you need to know about if you're going to use event viewer.
First you need to make sure WER (windows error reporting) is enabled, you can check that using this tutorial: Enable or Disable Windows Error Reporting in Windows 10
You may only have to check to see if it is enabled, I believe it's default is enabled.

Then, even though you may get event viewer to load there has been some problems reported using it. You haven't listed the build and version of your win10 OS but this started with June's Tuesday's updates:

Event Viewer may close or you may receive an error when using Custom Views
When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close.

See details > OS Build 18362.175 June 11, 2019 KB4503293 Mitigated June 13, 2019 02:21 PM PT

And lastly: If you're unsure how to open event viewer you can use this tutorial to open event viewer: Read Chkdsk Log in Event Viewer in Windows 10
Yes, it is designed to check the logs for CHKDSK but you would still have to follow the steps in Option One to check the logs for your 3rd parties but instead of looking for CHKDSK you're looking for your programs.

Thanks goes to dalchina for mentioning appcrashview, I hope it works for you.

One culprit maybe the comodo. Do u tried without it?

Good eye there boombastik, for a test dm could turn off comodo and just run defender with firewall and see if things improve.