[deleted][deleted]

Question

[deleted]

[deleted]

[deleted]

[deleted]

[deleted]

[deleted]

Answer 1

I have a similar problem that is on my 2 computers. The same errors and system behavior. I can't find a solution for a long time.

Answer 2

There are several suspicions. We can compare the installed programs. Now I suspect the drivers and software of the Brothers printer or the Microsoft Visio 2021 pro. Do you have any of these installed?

Answer 3

There are several suspicions. We can compare the installed programs. Now I suspect the drivers and software of the Brothers printer or the Visio 2021 pro. Do you have any of these installed?

Answer 4

Hello

Sorry, the forum does not have permission to analyze your dump file.

For the dump file, you can open the start menu and search for feedback, then open the Feedback Hub application and submit a bug report and attach the dump file there:

Send feedback to Microsoft with the Feedback Hub app - Microsoft Support

Or consider purchasing a Microsoft online support ticket:

Contact Us - Microsoft Support

According to the details you provided, there were two distinct events:

1. Event on 07/06/2024 at 02:24

Problem Event Name:** BEX64

Faulting Application:** Explorer.EXE (Path: C:\Windows\explorer.exe)

Exception Code:** c0000409

Exception Offset:** 00000000000d2700

2.Event on 08/29/2024 at 22:27

Problem Event Name:** APPCRASH

Faulting Application:** Explorer.EXE (Path: C:\Windows\explorer.exe)

Faulting Module:** KERNELBASE.dll ... Exception:** e0434e49

Exception Offset:** 000000000005fabc

Based on this information, here are some things you can try to resolve the issue:

1.Reinstall or Repair Windows Explorer:

you can use PowerShell to reinstall Windows Explorer and other default Windows applications. Run PowerShell as an administrator and use the command:

Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

2.Check Installed Programs:

Some third-party applications may conflict with Windows Explorer. Consider uninstalling recently installed or rarely used applications, or try running it in safe mode to see if that resolves the issue.

3.Check Faulting Modules:

In the first event, the faulting module is Explorer.EXE itself, suggesting a possible internal problem. In the second event, the faulting module is KERNELBASE.dll, which is a critical Windows module. It may be necessary to re-register KERNELBASE.dll. In the Command Prompt (administrator), run:

cmd

regsvr32 KERNELBASE.dll

Answer 5

Hello

Sorry, the forum does not have permission to analyze your dump file.

For the dump file, you can open the start menu and search for feedback, then open the Feedback Hub application and submit a bug report and attach the dump file there:

Send feedback to Microsoft with the Feedback Hub app - Microsoft Support

Or consider purchasing a Microsoft online support ticket:

Contact Us - Microsoft Support

According to the details you provided, there were two distinct events:

1.Event on 07/06/2024 at 02:24

Problem Event Name:** BEX64

Faulting Application:** Explorer.EXE (Path: C:\Windows\explorer.exe)

Exception Code:** c0000409

Exception Offset:** 00000000000d2700

2.Event on 08/29/2024 at 22:27

Problem Event Name:** APPCRASH

Faulting Application:** Explorer.EXE (Path: C:\Windows\explorer.exe)

Faulting Module:** KERNELBASE.dll ... Exception:** e0434e49

Exception Offset:** 000000000005fabc

Based on this information, here are some things you can try to resolve the issue:

1.Reinstall or Repair Windows Explorer:

you can use PowerShell to reinstall Windows Explorer and other default Windows applications. Run PowerShell as an administrator and use the command:

Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

2.Check Installed Programs:

Some third-party applications may conflict with Windows Explorer. Consider uninstalling recently installed or rarely used applications, or try running it in safe mode to see if that resolves the issue.

3.Check Faulting Modules:

In the first event, the faulting module is Explorer.EXE itself, suggesting a possible internal problem. In the second event, the faulting module is KERNELBASE.dll, which is a critical Windows module. It may be necessary to re-register KERNELBASE.dll. In the Command Prompt (administrator), run:

cmd

regsvr32 KERNELBASE.dll