Sequoiahealth 7 Posted August 1, 2017 Posted August 1, 2017 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.
Administrators Marcos 5,468 Posted August 1, 2017 Administrators Posted August 1, 2017 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.
Sequoiahealth 7 Posted August 1, 2017 Author Posted August 1, 2017 Sadly I am not that computer savy.
Administrators Marcos 5,468 Posted August 1, 2017 Administrators Posted August 1, 2017 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.
Sequoiahealth 7 Posted August 1, 2017 Author Posted August 1, 2017 I have not updated to Eset10.1 I suspect that was the problem. Lots of work to get back running again.
Administrators Marcos 5,468 Posted August 1, 2017 Administrators Posted August 1, 2017 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.
Sequoiahealth 7 Posted August 1, 2017 Author Posted August 1, 2017 Where is the link to the KB you mentioned?
Administrators Marcos 5,468 Posted August 1, 2017 Administrators Posted August 1, 2017 8 minutes ago, Sequoiahealth said: Where is the link to the KB you mentioned? Here it is: http://support.eset.com/kb380/
Sequoiahealth 7 Posted August 2, 2017 Author Posted August 2, 2017 Tried to set-up dump file. Was not there. Tried loading ESET 10.1 and comouter crashed again. Going to try and find dump file and send it.
Sequoiahealth 7 Posted August 2, 2017 Author Posted August 2, 2017 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?
Sequoiahealth 7 Posted August 3, 2017 Author Posted August 3, 2017 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
Administrators Marcos 5,468 Posted August 3, 2017 Administrators Posted August 3, 2017 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.
Sequoiahealth 7 Posted August 3, 2017 Author Posted August 3, 2017 Not sure why I would be getting this log info. This is a one person computer.
Recommended Posts