Has anyone else experienced this: After leaving my PC while it was downloading several files with a download manager, I returned to find my PC had rebooted. I messed around trying to figure out what happened, at first to no avail. So I re-queued the downloads and watched to see what happened. This time I noticed that as the NOD32 scanner opened to scan each completed download, my computer locked up, and I had to reboot. After messing with it a while longer, I ultimately came to this conclusion: if more than one instance of NOD32 is opened (in this case to auto-scan files after download), and the instances are executed in quick succession (as would happen if the files being downloaded were approx. the same size), NOD32 freezes or reboots my PC. The multiple-instance-reboot can be duplicated here by double-clicking the "Run NOD32" button on the NOD32 screen in Control Center. Double-clicking that button has the same effect as if I hit my restart button. It startled me at first, but I was able to reproduce the behavior several times in a row (glutton for punishment, I guess ). I've not experienced this with other AVs, nor do I recall it happening with pre- "December Update" NOD. Maybe I just didn't have the opportunity to notice with the latter as I haven't used NOD32 much in the last six months. I think what I notice with other AVs is a longer delay between scan windows opening...maybe that delay is what keeps things from crashing. Tested on WIN98 PC. I haven't installed NOD on my XP PC yet. Thanks.