Vista - Interesting TCPIP problem

Hello Friends, I have an event that I would like to learn more about and Microsoft Technet nor google has helped me in this one. Event ID: 4228 Source: TCPIP Message: TCP/IP has chosen to restrict the scale factor due to a network condition. This could be related to a problem in a network device and will cause degraded throughput. Could this be a driver issue?

What were you doing or attempting to do when this happened? Details son, we require details.

Ok, the only way I know this event happened was because I check my event viewer on a daily basis to see any abnormalities. I tried to think back to what I was doing at the time of the event and it was just browsing the internet. pidgin was open connecting to aim, yahoo, and MSN. Thats al I can think of, if it happens again i will try and have more specific details

... ok...

Might I make a suggestion?

Smoke a bone; twist a fatty; lite one up; drink not one but two pints of Jack Daniels; see the sun; roller skate.... I know it sounds like a joke, but honestly, with (literally) millions of lines of code, stuff is going to go wrong; it's the nature of the beast.

I've, on occaision, just because I was wondering the correct path to guide someone else to, found that "errors" had occured, unbeknownst to me. Seriously, Vista is pretty good at self-repair, and, I can't imagine checking the Event Viewer evey day.

If you have a question about TCP/IP, I've got the Microsoft Published, Vista Inside Out, book, and I'd be happy to look up answer any question you have, but... c'mon... there are some things which I, nor anyone can explain; afterall, "I dont' know" is a perfectly acceptable answer, right?

I dont know is a great answer and i dont need a specific answer to every question I ask. The only reason I post on these, or any message board, is to see if anyone had a similar situation and is more knowledgable than me to solve it. THe only reason I check the event viewer every day is because I had vista go bad on me on my 1st install and it was because I didnt check the event viewer that it went so badly.

I had that error about a month ago and haven't had it again and I don't know what is was that made the error.