MSTASK cause invalid page fault

symon · #1 June 9th, 2004, 12:28 AM

On booting up Win98se I get a warning; "MSTASK caused an invalid page fault in module MSTASK.EXE at 016f:01008f7b, if problem persists contact the vendor" Well the vendor is Microsoft and I thought someone here at cybertech help could come up with a more concise and succint solution.
I'd really like to get rid of the task scheduler all together but am leary about any collateral damage that might occur if I delete anything that Microsoft puts in the code.
What causes this? It doesn't seem to affect anything after I continue on.
Thanks

TJolly · #2 June 9th, 2004, 12:30 AM

Go here and download Spybot Search&Destroy:
http://www.safer-networking.org/inde...&page=download

Check for updates before running the program. A tutorial can be found under help. You can safely delete what it finds.

Do likewise with Adaware 6 that can be found here:

http://lavasoft.element5.com/software/adaware/

Download CW Shredder:
http://www.spywareinfo.com/~merijn/files/cwshredder.zip
Unzip, run and hit the fix tab to fix all found problems

symon · #3 June 9th, 2004, 01:44 AM

I have Spybot search and destroy and it gives me many missing DLL entries as well as many "usage track" entries. Is it safe to delete all these entries without deleting something that is used by another program?

TJolly · #4 June 9th, 2004, 01:45 AM

Delete evrything marked red.

symon · #5 June 9th, 2004, 02:01 AM

No immediate treats found is what I get but the rest have red exclamation marks preceeding the little check box, but the entries are all in a stylish aquamarine colour.

On a different track; do you no anything about Spooler Sub System Process, Spool32.exe. I found it in "Running tasks" in MSINF 32.

symon · #6 June 9th, 2004, 02:18 AM

Hi again, never mind the Spooler Sub System question. It's part of the printer programing. I should have been able to figure that out. Thanks for the info on the MSTASK problem

TJolly · #7 June 9th, 2004, 10:48 AM

Re Spybot.

You can delete the ones marked aquamarine.

symon · #8 June 10th, 2004, 05:36 AM

Thanks, I was wondering about that. I also discovered that I had two MSTASK.exe file running. One from 1999 and another from 2004. I renamed one and ran it and the problem continued; I renamed the other while restoring the original name to the previous one and voila no error message on boot up.
Thanks for the info on the spy bot I'll give it a go.