Jump to content

Search the Community

Showing results for tags 'bsod'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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)
    • WeLiveSecurity.com
  • 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
    • Other ESET business products
  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Interests

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: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8018e7d5c88, address which referenced memory Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPagedPoolEnd unable to get nt!MmNonPagedPoolStart unable to get nt!MmSizeOfNonPagedPoolInBytes 0000000000000010 CURRENT_IRQL: 2 FAULTING_IP: nt!IopInsertRemoveDevice+5c fffff801`8e7d5c88 488b01 mov rax,qword ptr [rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: services.exe TRAP_FRAME: fffff60d18698710 -- (.trap 0xfffff60d18698710) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000010 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8018e7d5c88 rsp=fffff60d186988a0 rbp=fffff60d18698950 r8=0000000000000000 r9=ffffe380dc4c1910 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po cy nt!IopInsertRemoveDevice+0x5c: fffff801`8e7d5c88 488b01 mov rax,qword ptr [rcx] ds:00000000`00000010=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8018e859c29 to fffff8018e84dc00 STACK_TEXT: fffff60d`186985c8 fffff801`8e859c29 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff60d`186985d0 fffff801`8e857e16 : 00000000`00000000 00000000`00000000 fffff801`8e991eb8 ffffd20b`e3d6b5d0 : nt!KiBugCheckDispatch+0x69 fffff60d`18698710 fffff801`8e7d5c88 : ffffd20b`00000000 ffffd20b`e39084b0 ffffd20b`ef14ea60 ffffd20b`e86793f0 : nt!KiPageFault+0x256 fffff60d`186988a0 fffff801`8e7d5af9 : 00000000`00000000 ffffd20b`e86793f0 00000000`0000001a fffff801`00000000 : nt!IopInsertRemoveDevice+0x5c fffff60d`186988d0 fffff801`8e7d58b6 : 00000000`00000000 ffffd20b`ef0b3400 ffffd20b`ef14ea60 ffffd20b`ef0b34b0 : nt!IopCompleteUnloadOrDelete+0x99 fffff60d`18698990 fffff80e`c4371cd8 : ffffd20b`e6cfc078 00000000`00000000 00000000`00000000 ffffd20b`e6cfc078 : nt!IoDeleteDevice+0x76 fffff60d`186989c0 ffffd20b`e6cfc078 : 00000000`00000000 00000000`00000000 ffffd20b`e6cfc078 ffffd20b`e6cfc078 : em018k_64+0x21cd8 fffff60d`186989c8 00000000`00000000 : 00000000`00000000 ffffd20b`e6cfc078 ffffd20b`e6cfc078 fffff80e`c4371c88 : 0xffffd20b`e6cfc078 STACK_COMMAND: kb FOLLOWUP_IP: em018k_64+21cd8 fffff80e`c4371cd8 488b4308 mov rax,qword ptr [rbx+8] SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: em018k_64+21cd8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: em018k_64 IMAGE_NAME: em018k_64.dll DEBUG_FLR_IMAGE_TIMESTAMP: 5a1c223d FAILURE_BUCKET_ID: X64_AV_em018k_64+21cd8 BUCKET_ID: X64_AV_em018k_64+21cd8 Followup: MachineOwner --------- Since that I have deleted the previous build files, I'm totally stucked with this new build and I'll probably remove ESET and wait for an update. ESET Smart Security Version: 10.1.235.1
  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 Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time MEMORY.DMP 30/10/2017 21:47:39 BAD_POOL_CALLER 0x000000c2 00000000`00000004 00000000`00000000 00000000`00000000 ffffc787`c176cdb8 x64 C:\Windows\MEMORY.DMP 8 15 16299 2.698.196.132 30/10/2017 21:49:16
  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 samsumg magician start to load @ 100€ , freeze and bsod samsung magician 4.9.5 an up use rapid share (a sort of ram cache) and they are used to updade the firmware could you fixed? i have the bsod but they are 3.4GB ,hard to upload this did happen on 4 computer , 3 desktop and 1 laptop , all of them have samsung ssd and eset thanks
  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 uninstalled ESS and rebooted. I then reinstalled ESS 8.0.319 from the offline installer and rebooted. Windows 10 booted successfully and ESS seems to be working fine. I have seen a few other reports of this on the Internet, therefore I suggest people remove ESS before upgrading to Windows 10 and then reinstall it afterwards.
  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 FIle Services
  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 blue screen or issue since. This was definitely the cause of my blue screen issue. I would like someone from Eset customer services to either tell me how to rectify this issue as i've trawled the internet for answers for the past 2 weeks and am yet to find a soloution other than uninstall and dont use again. Secondly if eset staff cannot provide a solution I would like a full refund. I had no issues whilst using the 30 day free trial and so decided to pay for the licence. As soon as I did, i had the blue screen issues. Please help in some way Kind regards Swatson738
  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 SDK performance recording tool and set it to record the boot sequence and restarted the PC. Windows failed to boot twice (UNEXPECTED KERNEL MODE TRAP) and went into the auto diagnostic repair mode. Restore just spins until I lose patience. I did manage to boot in safe mode and disable the recording. It did not help.Running sfc/scannow "did not find any integrity violations". I also managed to uninstall the Windows SDK/Perf Rec (by restarting the MSI service) - to no avail. I ran the Windows memory test, but when it's done it reboots, the reboot fails, and I never did see the results. I replaced the new RAM with the original ones, but this did not make any difference (BIOS setting are as they were originally). After further investigation, it turned out the ESET driver eamonm.sys might be a factor. Code: BugCheck 1000007F, {8, ffff84001fc88b30, ffff840020108000, fffff8019ea3b196} *** WARNING: Unable to verify timestamp for *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys I think I also remember a software update done by ESET at about the same time as the above. I uninstalled ESET in Safe Mode (barely and partially) and the computer booted properly. I then went on to freshly reinstall ESET NOD32. When I restarted the computer, I got the same dreaded "UNEXPECTED KERNEL MODE TRAP" BSOD again. Please advise!
  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.2012.0 dated 5/23/2016 Does anyone have another solution for this issue? I have 40+ machines and would like to not need to fix the BSOD on each individual case.
  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 planned on doing the Win10 upgrade, eSet refused to start on Win7 even after multiple reboots. After upgrading to Win10, eSet has installed and run without incident.
  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 surprise I might add as I've never had any problems with ESET before. Disabling the ESET service on boot makes the BSOD disappear and the system seems to run stable just fine. Enable it, and windows goes back to crashing into the 0x00000124 BSOD on boot. Tried a full removal and re-install of ESET, but that didn't seem to help. Any ideas? I've been using ESET for at least 4-5 years now, never had any issue with it whatsoever. No signs of any problems related to either software or hardware up until earlier today either.
×
×
  • Create New...