Jump to content

BSOD on Dell Pc's


onetwothree

Recommended Posts

Hi

I have been pushing out update to the latest version of ESET (10.1.2058.0) to our clients.  However i have got a call from 2 clients to report that their pcs blue screened and crashed.  

I have the ESET logs from one of the pcs attached, i do not have access to the other pc yet.  

Can you please check this for me as i am now afraid to push out the update to our other clients in case they have issues

Edit:  i have added the error that i got on the pc after running WhoCrashed on it.

 

 

ees_logs.zip

premeng error.png

Edited by onetwothree
Link to comment
Share on other sites

  • Administrators

Please provide the dump from the crash compressed in an archive which should be created in c:\windows\memory.dmp by default.

Link to comment
Share on other sites

  • Administrators

This is just a minidump that will not help much. Are you able to reproduce the crash? If so, please configure Windows to generate complete memory dumps as per https://support.eset.com/en/kb380. After making the necessary changes in the registry, reboot the machine and reproduce the crash.

Link to comment
Share on other sites

Hi

i am not reproducing the crash as it may cause the user to lose data.  

this previously happened to us in August with a number of clients and on contacting our supplier i was told this has never happened before but on reading different eset forums i can see that ESET has caused BSOD after updating.

I would appreciate if you could check the eset logs from the 2 different pcs that i have supplied to see what caused this issue.

Thanks

 

 

Link to comment
Share on other sites

FYI: https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/debugger/bug-check-0xd1--driver-irql-not-less-or-equal.md

As the article states, Driver Verifier utility analyzing epfw.sys might be able to shed additional info on what is going on here.

In this article: https://answers.microsoft.com/en-us/windows/forum/all/bsod-kernel-mode-driver-attempted-to-access/dc240524-45d9-4219-bd03-184b2725953c , an update of PC manufacturer motherboard chipset drivers fixed the problem.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...