And according to M$ was this problem solved! If you run XP SP1 this should have been fixed, now it appears not to be...
http://support.microsoft.com/default.aspx?scid=kb;en-us;322857
Shame.
Then again this is according to AMDZone, but it seems to me as they are right (allthough the KB article referred to relates only partly to this problem).