Well the patch is out there and I tested it (but since this patch hasn’t officially been published in the open forums I can’t give any details on where it is and how to apply it.
But one point that was made on my successful test was how they would apply it (program update of other means) as it doesn’t appear to be widespread.
Now the comment about those of us that use the full Outpost Firewall Pro have experienced this problem (but we didn’t in the past with the beta builds) but there were changes in the aswTDI.sys file which as far as I’m aware has some outpost firewall elements. So there may be a possible conflict if the user has outpost firewall pro installed.
However, when I checked BlueScreenView aswTDI.sys was listed in the faulting processes/file name, but there were no outpost firewall pro processes/files listed.
So I don’t really know if this is showing a connection/conflict between the two.
Another point of note is that the patch was for win 7 both 32bit and 64bit, no other OS catered for in this patch.