Welcome to the Anandtech forums, Paul. Since this question is about a specific computer problem, it would be better answered in the Software, or Troubleshooting forums. The highly technical forum is normally reserved for questions about specific technologies or how things work. In addition, aside from being off-topic, this forum has a fairly low traffic count and your question will get more views in one of the other forums.
Having said this, it could be argued that memory paging is a highly technical subject.
Invalid page faults are generally a bad sign. Memory is divided up by an operating system into sections, called pages - usually a page is assigned to a specific application. A page fault is a problem accessing a page - which can be as simple as the page not being in the stored in the right cache (don't go technical on me all of you other HT'ers and correct me, I'm trying to keep it simple) and doesn't necessarily mean that there's a real problem - page faults don't always crash programs. OTOH, an invalid page fault is a bad thing since it means there's a problem finding the right page, or the page in being accessed can't be accessed. It is a sign that something is fundamentally wrong with the system. Usually the problem is that something has overwritten the translation area where the table that sets up the map from this paged form of memory to the physical memory that's actually present in the chip (since pages are software constructs, not a reflection of the actual memory). So usually the error means that the translation got blown away by some program that shouldn't have been overwriting the translation at all.
This could be hardware, or an OS problem, but it's nearly always a driver problem.
If there is a hardware error like a bad memory chip, or something, you could get a corrupted page table which could lead to page faults. Or if the OS is corrupted - like a key file like the virtual memory device loader - this could do this. But in this case, I doubt the previous two explanations... it's usually a driver conflict problem.
My advice is to:
a. reset all of the relevant sound and video drivers to the latest versions, and grab the latest DirectX release.
b. upgrade to a newer OS - like WinXP Home or Windows 2000 Professional. It is much harder for a bad driver to cause problems in XP or 2k.