Sequoiahealth

Not sure why I would be getting this log info. This is a one person computer.

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

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?

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.

thx

Where is the link to the KB you mentioned?

I have not updated to Eset10.1 I suspect that was the problem. Lots of work to get back running again.

Sadly I am not that computer savy.

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.