Jump to content

Eset 10 Caused Debug Assertion Failure on Windows 7 Machine


Sequoiahealth
 Share

Recommended Posts

Did a normal update 7/31/2017 of Eset Nod 32 that caused a Debug Assertion failure. Had to to restore computer to an earlier set point. Eset inactive need assistance updating without computer shutdown. 

Link to comment
Share on other sites

  • Administrators

If you can reproduce the crash, please configure Windows to generate complete memory dumps as per the instructions at http://support.eset.com/kb380 and then reproduce it. Afterwards upload the generated dump in a compressed form to a safe location and pm me the download link. It's usually a 3rd party driver or unpatched system which causes BSOD in conjunction with ESET.

Link to comment
Share on other sites

  • Administrators

Are you able to reproduce the crash? I've added a link to a KB with instructions how to configure Windows to generate complete memory dumps.

Link to comment
Share on other sites

  • Administrators

I'm not aware of any case with v10 when ESET was the culprit of BSOD. Crashes that we've been reported were caused by 3rd party drivers. Unfortunately, without a memory dump we can't tell what caused the crash.

Link to comment
Share on other sites

I set up the memory dump file but don't see it after I restore the computer. To use the computer after the crash I have to go the a restore point. Is the dump file being wiped out by the restore point?

Link to comment
Share on other sites

Did get this on a system scan today...

Boot sector of disk C: - error opening
Boot sector of disk D: - error opening
Boot sector of disk E: - error opening
Boot sector of disk H: - error opening
C:\1ffadd0f70cdd2fdb4c237995292206a\Windows6.1-KB3138612-x64-pkgProperties.txt - error opening
C:\1ffadd0f70cdd2fdb4c237995292206a\Windows6.1-KB3138612-x64.cab - error opening
C:\1ffadd0f70cdd2fdb4c237995292206a\Windows6.1-KB3138612-x64.xml - error opening
C:\1ffadd0f70cdd2fdb4c237995292206a\WSUSSCAN.cab - error opening
C:\85726c2fa25d0103619d3e0f8480\Windows6.1-KB3138612-x86-pkgProperties.txt - error opening
C:\85726c2fa25d0103619d3e0f8480\Windows6.1-KB3138612-x86.cab - error opening
C:\85726c2fa25d0103619d3e0f8480\Windows6.1-KB3138612-x86.xml - error opening
C:\85726c2fa25d0103619d3e0f8480\WSUSSCAN.cab - error opening
C:\fe88e2e56e66bfd16ce7f3a678c0cb\Windows6.1-KB3138612-x64-pkgProperties.txt - error opening
C:\fe88e2e56e66bfd16ce7f3a678c0cb\Windows6.1-KB3138612-x64.cab - error opening
C:\fe88e2e56e66bfd16ce7f3a678c0cb\Windows6.1-KB3138612-x64.xml - error opening
C:\fe88e2e56e66bfd16ce7f3a678c0cb\WSUSSCAN.cab - error opening
C:\hiberfil.sys - error opening

Link to comment
Share on other sites

  • Administrators

Boot sectors can be scanned only if a scan is run with administrator rights. Hiberfil.sys is exclusively used by the system so other applications can't access it. As for the other files, it could be that the current user doesn't have permissions to read them or they are exclusively being used by the system.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

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