I am running the latest build (0621) of the AV. I was running the V3 suite, but had too many issues with it so I wanted to see if just the AV runs any better. It has been running fairly well until last night. My ISP started having email POP3 server problems. I currently check about 8 different accounts on 3 different domains. The 2 accounts on my ISP would not receive mail. I noticed my CPU was at 100% on all 4 cores. Not a good sign on a Q6600 with 4GB RAM and Vista Ultimate. I look in task manager and it says ekrn.exe is the culprit. I reboot and all is fine. Open Outlook and check mail. The 2 accounts from my ISP fail so I cancel all send and receive tasks. I notice my CPU usage is 30-40%. I redo send/recevie and my CPU usage goes to 80-85%. I cancel send/receive and usage stays at 85%. I do another send/receive. Now 100% CPU. Cancel the hung send/receive and CPU usage stays 100%. Again and as expected ekrn.exe is the problem. I try to kill ekrn from task manager to see what it will do. It does not stop (good thing), but CPU usage drops back to 0. This morning my ISP is still having issues. Again my CPU usage went to 35-40% even though I cancel the tasks. I remvoed those 2 accounts from being checked. Rebooted and now everything is working perfectly again. I see at least 3 issues here. Why does ekrn.exe hang waiting for response from a pop3 server? Why does ekrn.exe not recover or detect when the mail checking operation is canceled? Why does ekrn.exe not at least timeout and cancel the failed mail operation and keep eating more CPU each time the operation is repeated? I know that people have seen the ekrn.exe 100% problem in the past. Maybe this information may give people something else to look at when they see this. Eset - any ideas or reasons for this behavior?