This has happened to me on occasion in at work on WinXP pro with a very similar hardware configuration to your's. I've found that WinXP sucks.
A reboot usually solved the problem, but of course we use Centurion Guard at work which wipes a machine back to a clean slate every time you press reset. So a reboot meant a fresh installation of 1964.