AName

I have only had my Mac a few days and had 2 kernel panics all of which mention “Spinlock acquisition timed out” and ESET Proxy!! Any news on when the test version will make its way into the beta channel or normal updates?? %%%% Extract from the last one %%%% Tue Jul 22 14:50:42 2014 Panic(CPU 2): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff801cc73568, spinlock owner: 0xffffff801d284000, current_thread: 0xffffff801d284000, spinlock_owner_cpu: 0x2 RAX: 0x0000000000000005, RBX: 0x0000000000000000, RCX: 0xffffff801c69bef8, RDX: 0xffffff801c69bef8 RSP: 0xffffff81256dbd00, RBP: 0xffffff81256dbdb0, RSI: 0xffffff801c69bf30, RDI: 0x0000000000000000 R8: 0x0000000000000000, R9: 0x000000000000018b, R10: 0x0000000000000000, R11: 0xffffffffffffffff R12: 0x0000000000000000, R13: 0xffffff801c69bee8, R14: 0xffffff801cc73560, R15: 0xffffff801cc73560 RFL: 0x0000000000000202, RIP: 0xffffff8007bc65e9, CS: 0x0000000000000008, SS: 0x0000000000000010 BSD process name corresponding to current thread: esets_proxy Mac OS version: 13E28 Kernel version: Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64 Kernel slide: 0x0000000007600000 Kernel text base: 0xffffff8007800000 System model name: MacBookPro11,2 panic(cpu 0 caller 0xffffff8007bc6ca5): "Spinlock acquisition timed out: lock=0xffffff801cc73568, lock owner thread=0xffffff801d284000, current_thread: 0xffffff801b5da280, lock owner active on CPU 0x2, current owner: 0xffffff801d284000"@/SourceCache/xnu/xnu-2422.110.17/osfmk/i386/locks_i386.c:365 %%%% Extract End %%%% Thanks

Thanks that solved everything.

For some unknown reason Windows recognises ESET SS Firewall and spyware/ PUA but not the actual virus module. As seen in the screenshot. Unfortunately I am not sure how long this has been happening but it wasn’t like this when I first installed ESET on the machine. I only noticed when Defender was asking for permission through the HIPS. I turned defender off and tried these instructions (hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN217) but still getting the error in the screenshot. Computer info: Windows 8.1 Pro- All Critical Updates. ESET Version: 7.0.302.26 Current Signature: 9241

I have the same problem on Windows 8. For some unknown reason it attempts to open up the editing software for the camera which just crashes. Not the actual software for the webcam.