Task scheduler causes invalid page faults with DirectX

Ok here is what happened... I've been reading DirectX tutorials, and some of them have DirectX animations within the window (or it could be Java since this is a browser who knows) anyway, the reason I say DirectX is Because... when I started to read these is when I kept getting the Invalid Page Faults... in various DLL's. So at first I cleared all TSR's nothing then uninstalled-reinstalled still no luck... Now finally I noticed that it didn't matter what I did these IPF where timed. So There is this little Task Schedular Icon in the systray... IT DOES NOT SHOW UP ON THE TASK MANAGER! so I finally put it in pause mode... until I figure out what else to do with it. So now it's been well over an hour and so far not a one IPF... infact I have all my other stuff running in the background... So I strongly believe this was causing all my hearache. So next time you or some customer has IPF's you may wish to consider looking in to this... it is definately something that could affect all applications.

Let me quickly explain what *little* I know about IPF...

Windows Memory Management... allows memory to be movable and gives handles to all functions that call GlobalHandle(); Which is a 16bit array of pointers. When a program needs to access this memory it calls GlobalLock(); Keep in mind most Windows API's and DLL's will implicitly call these functions. So now something may happen during the moving memory around... conflicting libraries... conflicting tasks God knows what... that have caused the movable memory to be misrepresented... either the actual memory or the table of pointers is corrupt... and thus when the GlobalLock is called. Windows is unable to verify a valid pointer lock... and prompts the error. Keep in mind that movable memory uses the virtual memory functions... and that the virtual memory functions are a lower layer for more control of memory management... and that these function may also cause the fault... It seems like most applications would stick with the common memory API's... especially MFC developers ;)

Well now that W2k has been released, and I've been working with it... I have not seen any problems with IPF's.