No, I'm saying that it was in one of the reports (Debug session time: Fri Jun 19 21:27:03.889 2009 (GMT-4)). I searched for it in the remaining reports, and it doesn't show in the first couple of reports, then shows in the middle reports, then doesn't show in the last reports. But that doesn't mean that it's gone - just that it's not listed as being loaded when that particular process crashed.
The remaining errors tend towards networking type of issues, but we'll need a new memory dump to see what's happening.
If the kl1.sys issue is fixed (and you can find this out by seeing if it's still on your system), then we can proceed with checking the networking stuff.
As the drivers
appear current, our possibilities will most likely be that either the driver
is corrupted or the device is malfunctioning. There are other possibilities (such as Windows 7 compatibility, firmware updates, Windows OS issues, malware, etc). But I need to do more research on the networking component (not just the drivers) - and that's why I'd like to see another memory dump.