Jump to content

Search the Community

Showing results for tags 'BSOD'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • ESET General Forums
    • ESET Announcements
    • General Discussion
    • Forum FAQ's and Rules
    • Submit a virus, website or potential false positive sample to the ESET lab
    • Quick questions by guests (registration not required)
  • ESET Home User Products
    • ESET Internet Security & ESET Smart Security Premium
    • ESET NOD32 Antivirus
    • ESET Cyber Security (for Mac)
    • ESET Cyber Security Pro (for Mac)
    • ESET NOD32 Antivirus for Linux Desktop
    • ESET Products for Mobile Devices
    • Web portals
  • Malware Detection and Cleaning
    • Malware Finding and Cleaning
    • ESET Standalone Malware Removal Tools
  • ESET Business User Products
    • ESET Cloud solutions
    • ESET Endpoint Products
    • ESET Products for Windows Servers
    • ESET Products for Linux Servers
    • ESET Products for Mobile Devices
    • Remote Management
    • ESET Enterprise Inspector (EDR)
    • ESET Products for Virtualized Environments
    • Encryption
    • ESET Licensing for Business
  • ESET Beta Products
    • ESET Beta Products for Home Users
    • ESET Beta Products for Business Users
  • Slovak and Czech forums
    • ESET NOD32 Antivirus, ESET Internet Security a ESET Smart Security Premium
    • Produkty pre mobilné zariadenia
    • Vírusy a iné hrozby
    • Ostatné

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL






Found 12 results

  1. %90 of the time I'm getting BSOD at Windows log in since the last 17063 Build. I've checked the Minidump and it's apperantly caused by ESET. I'm using Windows 10 Insider Preview and that's probably why it's happening Here is the information if anyone cares: IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000010, memory referenced Arg2: 000
  2. I've installed the latest ESet on my laptop 10 last week and 11 today. Both cause the machine to bugcheck regularly. The machine is rock stable after uninstalling and switching back to Windows Defender. I can share a dump file. Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor
  3. hi with the lastest updates (i'm at 16388 right now) , (but i guess it 's related to prev update ,2 or 3 days ago) and samsung magician 4.9.5 and up there is an issue that generate BSOD i got 3 BSOD ,under w10 and w7 ,with eset smart secuity 8 ,9 and 11 i guess it's not related to the version of eset but to the lastest update when i run samsung magician the cpu jump @ 100€ and my comptures start to freeze & i had 3 BSOD on w7 and 2 on w10 i have restored an image ,created 1 month ago and samsumg magician work perfectly , i pushed the update on eset , reboot and s
  4. I updated Eset Smart Security to 8.0.319 in Windows 8.1 Pro (x64) and rebooted. Everything was working well. I performed an in place upgrade of Windows 8.1 to Windows 10 Pro (x64). After the upgrade had completed successfully ESS seemed to be working OK. I rebooted and every time that Windows 10 started it crashed due to a "DRIVER: IRQL_NOT_LESS_OR_EQUAL" error in epfwwfp.sys, the Eset Personal Firewall driver. I eventually fixed the problem by booting into safe mode and deleting epfwwfp.sys from C:\Windows\System32\drivers. Windows 10 then booted successfully. I uninstalle
  5. Our Domain Controller Server has been crashing with a BSOD off and on for a few months now. Every time it happens Eset updates the virus signature database. I have checked the Event Logs in Windows as well as the AV Logs and the exact time the system shutdown error is logged, the ASDB update is logged. I have checked the dump file and this appears "PROCESS_NAME: ekrn.exe". I can submit the dump files to a tech or admin as needed. AV: ESET File Security Version: 4.5.12017.0 OS: Windows Server 2008 R2 Standard (64-bit) Server Roles: AD Domain, DHCP, DNS, Application and FI
  6. Since around 20/09/2017 I have been experiencing multiple blue screen errors, attributing themselves to all manner of fault, from "paged fault in non paged area" through to eamon.sys. None of which occurred before I installed Eset smart internet security premium. I assumed paying £55 for 2 licences, one on my partners machine and one on mine, this would work as it stated it was compatible with Windows 10. I currently run Windows 10 Pro 64 bit and as I said, have had no issues up until I installed Eset product. I have since uninstalled Eset and have not experienced another b
  7. Hi, I have a desktop Windows 10 x64 machine that's been working fine for months/years. It was automatically updated from Win7 last year. A couple days ago I replaced the 2x4GB DDR3 memory with 2x8GB DDR3. This seemed to work though for some reason it works at 800MHz instead of the 1600MHz that the memory supports. The BIOS shows mem freq 1600 as expected. But this is the smaller issue. The PC worked booted fine.When everything seemed to working as expected, I was still bothered by the slow startup and login times. Now with 16GB I had expected these times to improve.I installed Windows S
  8. version 6.4.2014.0 During the automatic update to windows 10 x64 anniversary edition (1607) KB3199209 we have been receiving the error IRQ_NOT_LESS_OR_EQUAL on epfwwfpr.sys. Using the windows 10 recovery, command prompt we rename the driver in the system32/drivers folder and allow the update to install. We then install the cumulative updates for 1607. When that update has completed epfwwfpr.sys is restored and no further issues occur. Our initial response was to remove epfwwfpr.sys, deinstall eset, allow the updates to run, reinstall eset. epfwwfrp.sys is version 6.4.201
  9. Recently upgraded from Win 7 64-bit to Win 10 64-bit. I have eSet installed along with the Comodo firewall. After reinstallation, I've been occasionally seeing BSOD on boot in inspect.sys (Comodo). Working with the Comodo team analyzing memory dumps and they are suspicious that there's some type of interaction issue w/eSet. After uninstalling Comodo, I got one BSOD that the Comodo team reviewed and said was in eSet (ekrnAmon.dll). I'm running Win 10 (10.0.10586 and eSet 9.0.381.0). I have a memory dump if anyone from eSet would like inspect it. One other point. The evening I plann
  10. I use a MSI GS60-2QE with Windows 10. Last saturday it gave a BSOD all of a sudden and restarted. After reboot it still gave BSOD within seconds of Windows opening. Error messages changed from security kernel failure to IRQL not less or equal. Windows started fine under safe mode. Then I restored the notebook to factory settings, updated from Windows 8 to Windows 10 again and let Windows install all updates. When I tried installing Endpoint Security it gave a BSOD during install process. Is there a particular problem with the latest install Endpoint Security? How should I proceed?
  11. Just to let you know and ask if you are aware of the problem? If you upgrade to build 14271 with the latest eset endpoint antivirus installed or install it after upgrading you get a BSOD after rebooting. The blue screen mentions the file edevmon.sys which is of eset. Do you have a fix/workaround?
  12. Good day, Earlier today, my new (8-ish weeks old) computer suddenly crashed into a persistant BSOD whenever I boot. A bit of troubleshooting later, it turns out to be a BSOD code related to detection of general hardware problems. Booting into safe mode (win7 64bit) worked fine, so I ran some general hardware checks and stresstests: no problems detected. Doing a clean boot also works fine. Ran more test, again no hardware issues detected. Lastly, I tried booting my pc with more and more services enabled at start-up to see if I could figure out the culprit. Turns out it's ESET, much to my
  • Create New...