0

I have tried to run a .net core 8 code that worked for me 3 days ago. But now it crashes with error related to access violation

Same code works on another computer

So i tried to look for the cause and figured that my cmd 32 bit crashes with dllhost.exe crashing

It might be after the antivirus update but pausing it did not helped Maybe installing the core 8 sdk Was thinking maybe the EDR is blocking, but it did not

Powershell gives same error

the first time the error for dllhost.exe show on event viewer is 06/3/2024 on 10:37 with this log:

Faulting application name: DllHost.exe, version: 10.0.22621.1, time stamp: 0x05e70ed3
Faulting module name: combase.dll, version: 10.0.22621.3085, time stamp: 0x9c05761b
Exception code: 0xc0000005
Fault offset: 0x00000000000a76ae
Faulting process id: 0x0x13504
Faulting application start time: 0x0x1DA6FA09BB91C5C
Faulting application path: C:\WINDOWS\system32\DllHost.exe
Faulting module path: C:\WINDOWS\System32\combase.dll
Report Id: 2bdfaa34-7b82-44aa-8a97-750a0f4c6c1c
Faulting package full name: EsetContextMenu_11.0.2032.0_neutral__f55j32bkf4yvt
Faulting package-relative application ID: ESET

the first error before that is this one:

The program explorer.exe version 10.0.22621.3155 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

How can that be checked, fixed without installing the whole computer?

And what could cause it

Improve this question
6
  • What error messages do you get and what do they say? What "access violation" message and dllhost errors do you actually see? Why do you believe this might be antivirus related? Have you had trouble with this particular machine in the past? When including error messages it is helpful to show the full text of the message. You can edit your question to add more details.
    – Mokubai ♦
    Commented Mar 8 at 8:46
  • Process exited with code 3221225477 (0xc0000005)
    – Y.G.J
    Commented Mar 8 at 9:55
  • Faulting application name dllhost.exe
    – Y.G.J
    Commented Mar 8 at 9:56
  • Try to test Windows integrity by running the commands Dism /Online /Cleanup-Image /RestoreHealth and then sfc /scannow. (Add to your comment @harrymc for me to be notified.)
    – harrymc
    Commented Mar 8 at 10:31
  • 1
    You need a stronger method for ensuring that Windows is in a consistent state - Repair Install.
    – harrymc
    Commented Mar 9 at 10:11

2 Answers 2

Reset to default
-1

It's ESET. It's been causing issues for several days now. Try disabling HIPS detection within ESET and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds, which I see you did.

Improve this answer
2
  • Do you have any sources that confirm your claim that it is ESET? Besides the Faulting package-relative application ID: ESET is there some authoritative source on the internet confirming this issue?
    – Mokubai ♦
    Commented Mar 9 at 19:18
  • it was ESET! their DEEP INSPECTION
    – Y.G.J
    Commented Mar 10 at 9:06
-1

Had very similar issue with this error code, and yes, it was ESET, the DEEP BEHAVIORAL INSPECTION under the HIPS toggle. Disable it and everything will work fine.

Improve this answer
1
  • Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.
    – Community Bot
    Commented Mar 15 at 11:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .