Considering the first parameter is an invalid pointer, it sounds like a bug. I wouldn't be surprised if this was tcpview's fault, considering that sysinternals' software uses device drivers to do the dirty work. I'd recommend you to download the latest version of tcpview if you're using an old version, since pre-sp2 "hack" tools are likely to do stupid things on sp2 as the kernel has changed a little...
