Jump to content

Recommended Posts

Mr. Aryeh Goretsky,


I'm not an IT guy, I have no idea what you are asking me to do. Can you give me directions how to get that info to you?  and just give me your e mail adresss or a phone # I can call you at?


What is a private message? and a Macro?

Link to post
Share on other sites

Any news on this please ?


I also have three licences.  It took me a frustrating week to track down the issue (plus no paths to applications in interactive mode) to Cyber Security Pro.  I find it difficult to believe that ESET would leave me alone in the dark (thinking I had three infected machines) struggling to find the problem when they know already know it is an issue.

Link to post
Share on other sites

Mr. Aryeh Goretsky,


I'm not an IT guy, I have no idea what you are asking me to do. Can you give me directions how to get that info to you?  and just give me your e mail adresss or a phone # I can call you at?


What is a private message? and a Macro?


Hi SANman,

i wanted to send you a quick reply on behalf of Aryeh.

What he means by his statement of upload to a server is simply generalized and not implicit.

You can visit a decent site which will host your files for free and provide you with web addresses to get your files when you need them.

Example : hxxp://www.firedrive.com/

Add the samples you need ESET to investigate and then send them a private message using these forums and give them access to your files via "http download link".


Hope this helps you.

Link to post
Share on other sites


What is a private message? and a Macro?


Add the samples you need ESET to investigate and then send them a private message using these forums and give them access to your files via "http download link".


Hope this helps you.


Put your cursor on for example Aryeh's name here on the forum then a menu will popup and from there you chose "Send message" (write the message and/or add a link and send) that way the "private/personal message" will be sent only to that person. And when you get a reply you will see a red square with a digit on it at the very top of the forum close to the login area in the "messenger/inbox" it's the first icon from the left, then you click on the red square, then on the message and it will open up.


You can also send the message directly from the messenger if you want, both ways works the same.

Edited by SweX
Link to post
Share on other sites

For the second time in 3 months,  I find myself uninstalling Eset again.  Add me the the list of people with the kernel panics.


This happen on version 5,  I didn't reinstall until version 6.  Poor QA


Are you saying that you had Eset 5, installed 6, then went back to 5 (when you experienced the Kernel Panic issues), and STILL had Kernel Panics with 5 installed thereafter?





I was going to walk away from using Eset completely... We'll see how this goes...


I like your candor, however not giving ESET a chance to fix or repair, would be counter-productive. ( You would end up with a less protective solution (my opinion :) )



I went from v5, to 6, then back to 5. Have had it installed for a week now without any Kernel Panics. Appreciate your comment, and yes I'll give

them a chance... It's the least I can do, but if this happens again I'm gone for good. I can't deal with the downtime, there must be good quality

assurance across the board before releases are issued. This is the same thing that just happened with PS4 users this week. A major firmware update

was released for the console and it has bugs. Thousands downloaded it just to see their consoles go completely black on screen, game crashes,

no network connectivity, and screen flickering. While others had no issues whatsoever apparently. Again this means that coders, techs, and the like

must test software out across the board continuously on different hardware (or scenarios in general). Just to triple check there not being any compatibility issues.

Link to post
Share on other sites

We experience the same issues. We switched from ESET 5 to ESET 6 and had 3-5 kernel panics a day, with esets_proxy being the issue. However, the kernel panics only occurred on our MacBook Pros, not on the iMacs running ESET 6. The iMacs are still running ESET 6 without problems. The MacBook Pros are 15” and 17” machines, running several OS X flavours, from 10.6.8 up to the latest version of Mavericks.
The kernel panics were eliminated when we returned to ESET 5, but obviously that is only a temporary solution.

Attached is a partial panic log.

Panic Log 1.rtf

Link to post
Share on other sites

I just installed ESET 6 on my macbook pro (2.3ghz; OSX 10.6.8)  yesterday and it has crashed five times within an afternoon. Each time I was using firefox or chrome.


Like others, my Mac was getting HOT and the fan was kicking in.


This is very unlike my mac so I thought I'd do a search to see if there was an issue with ESET. And that's what brought me here.


I have legal registered versions of Microsoft Office Business 2011 (crashes frequently but is a separate issue) and Adobe Creative Suite.


I have uninstalled ESET and it hasn't crashed yet. Back to normal.  I don't think I'm going to bother re-installing it. Judging by how ESET has brushed off the the issue from the people that have brought this up months ago I've come to the conclusion that they're not taking this seriously.

Link to post
Share on other sites


I'm on Cyber Security on recent iMac, osx 10.9.2.


I had a panic crash today:


Anonymous UUID:       C044987B-52E2-D9B4-4AE6-4561F1268C80

Sat May 10 12:11:15 2014
Panic(CPU 1): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff80361a7c10, spinlock owner: 0xffffff80364ea590, current_thread: 0xffffff80364ea590, spinlock_owner_cpu: 0x1
RAX: 0x00000000000000c5, RBX: 0xffffff8010fc4261, RCX: 0x0000000000000002, RDX: 0x0000000000000000
RSP: 0xffffff81e385be90, RBP: 0xffffff81e385beb0, RSI: 0x0000000000000001, RDI: 0xffffff8044511948
R8:  0x0000000000000002, R9:  0x0000000000000000, R10: 0xffffff81e385be20, R11: 0x00000000000016c0
R12: 0xffffff803ea438e8, R13: 0xffffff8035d16008, R14: 0xffffff8035d16008, R15: 0x0000000000000000
RFL: 0x0000000000000246, RIP: 0xffffff801101a2ac, CS:  0x0000000000000008, SS:  0x0000000000000010
Backtrace (CPU 1), Frame : Return Address
0xffffff81d8aacf50 : 0xffffff8010ce1f21 
0xffffff81d8aacf80 : 0xffffff8010cdb43f 
0xffffff81d8aacfd0 : 0xffffff8010cf3539 
0xffffff81e385beb0 : 0xffffff8010fc4261 
0xffffff81e385bf70 : 0xffffff8010fc4580 
0xffffff81e385bfb0 : 0xffffff8010cd7047 

BSD process name corresponding to current thread: esets_proxy

Mac OS version:

Kernel version:
Darwin Kernel Version 13.1.0: Wed Apr  2 23:52:02 PDT 2014; root:xnu-2422.92.1~2/RELEASE_X86_64
Kernel UUID: E9CF78E2-1E9F-3B6F-81A4-FEE6C6D0E4D5
Kernel slide:     0x0000000010a00000
Kernel text base: 0xffffff8010c00000
System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)

System uptime in nanoseconds: 279855163893724
last loaded kext at 278468021423285: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f932dc000, size 49152)
last unloaded kext at 278642779914864: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f932dc000, size 32768)
loaded kexts:
com.LaCie.ScsiType00 1.2.13
com.eset.kext.esets_kac 600.00.91f01
com.eset.kext.esets_pfw 600.00.91f01
com.oxsemi.driver.OxsemiDeviceType00 1.28.13
com.apple.filesystems.smbfs 2.0.1
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.3f10
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 2.6.0f1
com.apple.driver.AGPM 100.14.15
com.apple.driver.ApplePlatformEnabler 2.0.9d1
com.apple.driver.X86PlatformShim 1.0.0
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.3f10
com.apple.GeForce 8.2.4
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleIntelHD5000Graphics 8.2.4
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleMikeyDriver 2.6.0f1
com.apple.driver.AppleIntelFramebufferAzul 8.2.4
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.iokit.IOUSBAttachedSCSI 1.0.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBHub 666.4.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.5.1
com.apple.driver.AppleSDXC 1.5.2
com.apple.driver.AirPort.Brcm4360 831.21.63
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AppleAHCIPort 3.0.0
com.apple.driver.AppleUSBXHCI 670.4.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.IOBluetoothHIDDriver 4.2.3f10
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.6.0f1
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.5fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOBluetoothFamily 4.2.3f10
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.3f10
com.apple.iokit.IOAcceleratorFamily 98.14
com.apple.nvidia.driver.NVDAGK100Hal 8.2.4
com.apple.nvidia.driver.NVDAResman 8.2.4
com.apple.iokit.IOSurface 91
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.driver.AppleHDAController 2.6.0f1
com.apple.iokit.IOHDAFamily 2.6.0f1
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.IOPlatformPluginFamily 5.7.0d10
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.AppleGraphicsDeviceControl 3.4.35
com.apple.iokit.IOAcceleratorFamily2 98.14
com.apple.driver.AppleThunderboltEDMSink 2.1.3
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleUSBHIDKeyboard 170.15
com.apple.driver.AppleHIDKeyboard 170.15
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.driver.CoreStorage 380
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.6
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.2.7
com.apple.iokit.IO80211Family 630.35
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 675.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.pthread 1
panic(cpu 0 caller 0xffffff8010fc46d5): "Spinlock acquisition timed out: lock=0xffffff80361a7c10, lock owner thread=0xffffff80364ea590, current_thread: 0xffffff80341b06d0, lock owner active on CPU 0x1, current owner: 0xffffff80364ea590"@/SourceCache/xnu/xnu-2422.92.1/osfmk/i386/locks_i386.c:365
Backtrace (CPU 0), Frame : Return Address
0xffffff81e22f3650 : 0xffffff8010c22fa9 
0xffffff81e22f36d0 : 0xffffff8010fc46d5 
0xffffff81e22f3710 : 0xffffff801101b116 
0xffffff81e22f3750 : 0xffffff8010ed5a84 
0xffffff81e22f3b90 : 0xffffff8010ec8916 
0xffffff81e22f3be0 : 0xffffff8010ec8c12 
0xffffff81e22f3dc0 : 0xffffff8010eb6d7d 
0xffffff81e22f3de0 : 0xffffff8010e527b3 
0xffffff81e22f3e10 : 0xffffff8010e33b8e 
0xffffff81e22f3eb0 : 0xffffff8010e2b25c 
0xffffff81e22f3f60 : 0xffffff8010e32a79 
0xffffff81e22f3fb0 : 0xffffff8010cd7047 

BSD process name corresponding to current thread: kernel_task
Link to post
Share on other sites

I am having same kernel panic issue.  I bought four new licencese to the upgraded Cyper Security Pro.  I had the earlier version 5 with no problem so I confidently renewed and added it to my lap top and my kids' laptops.  Then my desktop mac started having kernel crashes.  I kept losing data and the downtime from work was a pain.  Imagine, I am in the middle of a phone call accessing client data and my computer crashes.  I have to tell the client that I will call them back.  Ridiculous!  I googled it and felt like maybe it was a memory issue as my desktop is a few years old (ancient for computers).  I took it in for an evaluation at a local Mac specialist.  Came home and began using my laptop (I do not use my laptop except when I travel.)  KERNEL CRASH!  I wised up and realized it had to be ESET which was the only recent addition to my laptop.  Sure enough, googled it and here we are. 


So, I am out the $79 for the evaluation.  I called the computer store and told them I had figured out the problem on my own but they had already been running diagnostics on it so not really fair to ask them not to charge.    I was able to re-install the 5 version but only as a trial version since I have no clue what my version 5 password was or whether it will work - probably not since it was only good for a year.  Now what do I do with my other computers.  Go back to Norton?  Who is going to reimburse me my $79 and refund me the money for the four licensce. 


This is not a good situation. 

Link to post
Share on other sites

Has anyone had a reply from Eset regarding these 'Panics'. The reason for asking is that I sent 'Marcos' a message and the output of running ls -l /Applications on the 5th of this month and up to now there has there been no response and according to the status of the message it has not even been read.


I would have thought that Eset would have placed some urgency on this problem but apparently not or else, if they are being proactive they are not communicating the fact very well.

Link to post
Share on other sites

if they are being proactive they are not communicating the fact very well.


I have pointed this out to ESET before that a response is better than no response at all, just a "yes we are aware" or "Yes we are working on it" anything is better than getting silence as the answer. It only takes 10sec to send an answer like that.


But yes they are proactive even if they don't talk a lot about it. So hang in there   :)

Edited by SweX
Link to post
Share on other sites
  • ESET Moderators



we are testing fixed binaries, which should resolve the issue, but could take a while.

Is somebody experiencing the panics on a regular basis or is able to reproduce it on demand?


Thank you for your patience, we are really sorry for the inconvenience.

Link to post
Share on other sites
  • Most Valued Members

Just had my fourth kernel panic related to ESET minutes ago. Updated to 10.9.3 less than twelve hours ago, was watching a video with Adobe Flash Player in Safari 7.0.3 when panic occurred. This time it was caused by esets_daemon.

Link to post
Share on other sites
  • ESET Moderators



@Cos - please provide us with crash log (there are more issues, that could be the root cause) so we need to find out which one causes you the troubles.


@Planet I will reply you on Monday regarding the "NMIPI for spinlock acquisition timeout issue" we need to gather more info.

Link to post
Share on other sites

You can add me as another data point for just had my first kernel panic crash due to 'esets_proxy' — I've got ESET Cyber Security installed & current on my late '11 MacBook Pro, and installing yesterday's OS X Update 10.9.3 seems to have kicked it over into being a problem; I would occasionally see little bursts of high CPU activity that seemed to be associated with ESETS before that, but not to the point where it would cause system-level problems. However, when my computer was rebooting after the system update installation yesterday, I got a gray screen flashing over my desktop after logging in that I had to manually shut down my laptop to escape, and I strongly suspect this morning's kernel panic crash means that problem yesterday was also likely caused by an issue with ESETS.


Very frustrating + disconcerting; have filed a Customer Care support request, but seeing that this has been an issue for people going as far back as a year ago does not fill me with confidence that it will be fixed promptly now.

Link to post
Share on other sites

@Peter Randziak — do you want me to send along my crash log somewhere as followup to my just-filed Customer Care support request?

Edited by jbold
Link to post
Share on other sites

Is there a solution to this problem yet?  I started having crashes and restarts a month or so ago when eset updated to 6 on my MacBook Pro.  I communicated with eset and Apple.  Around the time the moderator posted on 4/16/14, the Genius Bar erased my hard drive and re-installed Mavericks.  I've been afraid to download eset 6 since I don't know if I will start having crashes again.  If it is a conflict with another app, I might.  However, I also wanted to mention that Apple could not run their usual tests for Mavericks because, they said, "whatever operating system" I was running would not allow the tests.  Has anyone else had that problem?  I had downloaded Mavericks when it first came out, and I always installed all updates as soon as they came out.  Somehow, it seems maybe Mavericks never fully installed properly.  I'm wondering now if other people might have had the same problem.  Since eset 5 is supposed to run with earlier versions of OSX, and eset 6 is supposed to work with Mavericks, I'm just wondering if people are getting crashes because they aren't completely running Mavericks.  Also wondering if eset might have impacted the download and installation of Mavericks and the updates way back when.  Anyway, is it safe now to download eset 6 again?

Link to post
Share on other sites
  • Most Valued Members

@Planet I will reply you on Monday regarding the "NMIPI for spinlock acquisition timeout issue" we need to gather more info.


Just had my fifth Kernel Panic, this time the usual esets_proxy. Was playing music in iTunes, browsing a website in Safari with just text.

Reading the panic file; "NMIPI for spinlock acquisition timeout".

Link to post
Share on other sites
  • ESET Moderators



@jbold: Yes we need a crash log in order to investigate the issue 


@Leonida50: Please provide us with the crash log so we can investigate which issue caused you the crash.  


@Planet: Try to enlarge timeout for kernel spinlock to avoid crash by command: "sudo nvram slto_us=0xffffffff" and restart for apply.

In case you experience kernel panic please provide us with logs as described on the end of this post.
You may return everything to normal by running command "sudo nvram -d slto_us" and restart to apply



@ALL: To get all required logs please use this Info_get script, password is "clean".

Just run the script, upload the output archive to safe location and provide me with direct download link and encryption password via Private message. 

We will check the logs and provide you with further instructions.


We are sorry for any inconvenience caused by these issues and I would like to assure everybody that we are still working on resolving them.

Link to post
Share on other sites

I recently downloaded and a few days later I had my first panic crash.  They are coming more often now and only while I am reading a webpage.

Since It took a few times before I started thinking it might be Eset, I did not come to this forum until tonight and this has confirmed it for me.  Also, it happened while on this forum and I actually looked at the log and indeed it is Eset proxy.

I think some of you are right. There are probably thousands out there with the same problem but have not made the connection yet.

Link to post
Share on other sites
  • ESET Insiders

Hi @peter randziak,


These issues were initially reported +/- 21 March. Today it's 2 MONTHS later and there is still no bug fixes update for this? This can't be true..... Could you please provide a timeframe from within we customers can expect that ESET wil FIX this issue for all users by simply updating their ESET CS Pro? Did the recent OS X update to 10.9.3 (13D65) resolve any of these terrible crashes?


Thanks in advance.

Link to post
Share on other sites
  • ESET Moderators



could you please provide me with the crash log?

I can check it, we maybe already have an workaround for it.

As we said it is not one issue, but more resulting in one observable behavior, which makes this quite complicated.

Link to post
Share on other sites
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...