It's part of the DirectX stack, and may be indicative of a corrupt file (you can run sfc /scannow to check) or an out-of-date video driver, but most likely it was just a bug in the original ...