In my Organization we had this issue with a number of SQL2005 64 Clusters.

I went through every posting on the net.

We updated NIC drivers, disabled TCP/IP offload. We checked Storage adapters and SAN provider bugs. It was getting to the point where we were considering some rather drastic measures regards RAID layout when on the 5th or 6th call to Microsoft PSS a tech mentioned these settings as a possible resolve.

As we were getting to the point where we might have to ask the client to blow away their LUNS to test a theory, we thought we would give the registry edits a try. They worked and continue to work. I got to thinking about all the hours of trolling through online postings I did and decided to post the info so someone else’s life could be more fulfilling.

Hope it works out for you. On the upside I now know more about SQL architecture than I ever really wanted to know (I am an OS guy primarily)

BTW what process would you use to generate the error?