Thanks for this thread. A google search with that error link today brought me to this thread.
I really hope it's as simple as a new chipset driver, its unfortunate that the ones I've been using are the ones direct from ASUS.
They're massively outdated for such a prevelent bug (nor did I know...