Jump to content

Momber

Members
  • Posts

    10
  • Joined

  • Last visited

Kudos

  1. Upvote
    Momber gave kudos to itman in Blue Screen after uninstalling Nod32   
    @Marcos post the regsvr32.exe command to unregister the service associated with edevmon.sys; believe that is edevmon. Then OP can run this from the command line option in Win 7 recovery environment.
    Hopefully Eset self-protections will not be in effect in recovery mode?
  2. Upvote
    Momber gave kudos to Marcos in Blue Screen after uninstalling Nod32   
    I'm afraid this wouldn't work since it would not affect the upperfilter and lowerfilter values of other filters registered in a filter chain in the system which is what causes BSOD if edevmon.sys (or another filter with its driver) is missing on the disk or if the driver is corrupt.
  3. Upvote
    Momber gave kudos to itman in Blue Screen after uninstalling Nod32   
    Wishfully thinking on my part as far the as the above is concerned.
    Regedit is all that can be used in Win 7 recovery environment and the applicable registry hive must be loaded. Then service settings modified accordingly. Procedure is detailed here: https://support.microsoft.com/en-us/help/927525/after-you-install-a-device-or-update-a-driver-for-a-device-windows-vis
  4. Upvote
    Momber gave kudos to itman in Blue Screen after uninstalling Nod32   
    Seems to me this still could be useful.
    Load the HKLM registry hive and navigate to Services key per Microsoft linked article. Open it up and determine if the following Eset services entries exist;
    eamonm ehdrv ekbddflt ekrn ekrnEpfw epfw epfwwfp epfwlwf ? Then do a; cd C:\Windows\System32\drivers. Then enter, dir.
    Next for all the above Eset services present in the Services key, verify that a corresponding .sys file exists in C:\Windows\System32\drivers.
    At least this will show what Eset driver is missing from C:\Windows\System32\drivers if that is indeed the issue.
  5. Upvote
    Momber gave kudos to itman in Blue Screen after uninstalling Nod32   
    @Marcos if the problem is in the Registry as you seem to be indicating, how about restoring the registry from its backup?
    This article is for Win 10 but the author indicates it should work for Win 7: https://pureinfotech.com/restore-registry-backup-windows-10/
    Further confirmed in this Microsoft TechNet discussion:
    -EDIT and Important- Ignore the Repair option given below. Repair on Win 7 is anything but straightforward as I recollect. The installation media version must match what ver. of Win 7 you have installed; e.g. SP2 media if Win 7 SP2 is installed..
    https://social.technet.microsoft.com/Forums/windows/en-US/50c51ee9-f25a-4286-9c8c-657b1c6f9868/recovering-windows-7-registry-hivesfiles
  6. Upvote
    Momber gave kudos to itman in Blue Screen after uninstalling Nod32   
    Since you haven't been able to successfully boot that device, did you try the "Last known good configuration" option?
    Ref.: https://www.sevenforums.com/tutorials/666-advanced-boot-options.html
    If that doesn't work, did you try the "System Restore" option from the Win 7 Repair screen?
  7. Upvote
    Momber gave kudos to itman in Blue Screen after uninstalling Nod32   
    Have you tried to perform a Win 7 Start Up Repair?
    Ref: https://www.technorms.com/33940/startup-repair-windows-7
     
×
×
  • Create New...