Jump to content

eset windows 10 memory integrity bug


Recommended Posts

hello eset community does anyone expeirencing DPC watchdog violation after installing eset internet i have been struggling with this bug my pc would boot up after dpc watchdog violation but after windows loading device security memory integrity is disabled i am pretty sure eset has some bugs that need to be fixed right away

Link to comment
Share on other sites

  • Administrators

Please elaborate more on the issue, it's not clear what you mean by "DPC watchdog" and provide step-by-step instructions with screenshots for illustration. However, check first if the issue is gone after temporarily uninstalling ESET.

Link to comment
Share on other sites

Hello dear admin marcos right after installing eset i am expierencing bsod with code dpc watchdog violation my pc would restart and booted succesful but after checking memory integrity it is now disable i never expierencing this before i had eset it always crashed my pc boot up i am sure it is bug as i completed wipe every thing in my pc and re installs windows no crack up no untrusted unverified application were installed in my pc

Link to comment
Share on other sites

  • Administrators

Does BSOD not occur if you temporarily uninstall ESET and occurs only after you've installed it? If so, please open a support ticket and provide a complete memory dump that should be generated during a crash. If necessary, configure Windows to generate complete memory dumps as per https://support.eset.com/en/kb380.

Link to comment
Share on other sites

DPC Watchdog Violation BSOD is usually caused by misbehaving drivers; most notably nVidia graphics card ones: https://learn.microsoft.com/en-us/answers/questions/349623/bsod-dpc-watchdog-violation-windows-10?page=2#answers .

This also could be the reason HV Memory Integrity is not enabling. However, there are a number of other reasons it won't enable. In my case, I had intentionally altered my motherboard memory timings to run my installed 1600 Mhz memory from its default 1333 Mhz setting. Once memory timing was reset to 1333 Mhz default, I could enable HV Memory Integrity.

Additional DPC Watchguard Violation causes are listed here: https://www.howtogeek.com/742322/how-to-fix-a-dpc-watchdog-violation-in-windows-10/ and here: https://windowsreport.com/dpc-watchdog-violation-windows-8/ .

To date, I have never seen Eset per se being the cause of this issue,

Edited by itman
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...