[Latest update BSOD.]

I have win 10 2004 Insider built, may be this info will help in some way

[Latest update BSOD.]

6 minutes ago, itman said:

I assume you mean you're using Windows Defender. As such, you want to keep "Launch of anti malware protection" enabled so the WD ELAM driver loads. With Eset uninstalled, there will be no launching of its ELAM driver at boot time.

I don't want my ESET to be uninstalled. WD is working fine. ESET's driver eamonm.sys causing BSOD. Disable earlier Launch of anti malware protection to boot my laptop is temporary.

[Latest update BSOD.]

1 hour ago, itman said:

For those whom have received this boot screen due to eamonm.sys, someone opened another thread that they were getting,  Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION, from it: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception .

Is this what is being displayed on your blue screen?

ohh, yaa this is the Exception when i got BSOD. Installation of ESET Internet Security 13.1.16.0 version won't make any problem but updating its modules of 155MB  makes BSOD. 

Now I have Disabled earlier Launch of  anti malware protection to boot my windows and using Microsoft Security

[Latest update BSOD.]

1 hour ago, Marcos said:

Please supply me with c:\windows\memory.dmp, ideally in a compressed form.

Get this link to resolve the issue

Memory Dump

[Latest update BSOD.]

37 minutes ago, itman said:

In regards to the original posting reference to disabling early launch anti-malware driver via boot startup option, a quick review on what it does:

https://www.top-password.com/blog/disable-early-launch-anti-malware-protection-in-windows/

Since the majority of Eset ver. 13.1.16 upgraded devices have no issues in this regard, it would appear that on a few select Eset installations its ELAM driver is detecting an existing driver as malicious. The key to resolution is to find out which driver is being detected as malicious.

eamonm.sys is a root cause of BSOD

[Latest update BSOD.]

Hello,

I have exactly the same problem.I've updated Eset Security to the latest version and instant BSOD.I've restarted and the same.

I've uninstalled Eset in Safe mode and no BSOD.Installed Eset again and BSOD continued.

Windows 10 works fine when boot with Special options F8 then Disable earlier startup of anti malware protection.

eamonm.sys is a root cause of BSOD.