Last updated September 18, 2005


As this FAQ gradually build up from questions and answers in the ... NewsGroup, the answers were ordered by subject. This has lead to the current 'sub-obtimal' situation, where Q+A's about 'Error-messages' are scattered all over the FAQ.

To make searching for answers to 'Error-messages' somewhat easier, I made up this list of 'errors', that point to the specific FAQ-item. Furthermore, I added an error-message that didn't seem to fit into any of the other main-subjects.

back to top

Error message: SCHDPL32 caused an invalid page fault in module MSSPC32.DLL at 0137:6c20eecf.
Error message: MAPISP32 has made an invalid page fault in module KERNEL32.DLL at 015f:bff7b997.

Both the program-file (mosttimes a '.DLL'-file) and the 'memory-address' that are mentioned in the message can be different. These errors can occur when you start the program, while working with it, or when you exit.
When you ask Windows to show some extra information, it will turn up a something like:

EAX=0000000c CS=0137 EIP=6c20eecf EFLGS=00010206
EBX=00000000 SS=013f ESP=0062f5f4 EBP=0062f65c
ECX=0062f65c DS=013f ESI=006207cd FS=1207
EDX=006532ac ES=013f EDI=00000000 GS=0000
Bytes at CS:EIP:
66 8b 10 66 3b f2 76 07 b8 ff ff ff ff eb 3c 73
Stack dump:
0062f650 00000000 6c269b90 0000000c 0062f65c 006531d4 00000007 0062f650
1a0a07cd 006531d4 6c269ad9 0062f650 00000007 0062f6d0 00000000 006531d4

Error-messages that mention 'invalid page faults' are quite difficult to trouble-shoot (with one exception).

The 'registers', the 'stack' and the 'pages' mentioned in the error-mesage, are specific area's in the RAM-memory. What this message means, is that Schedule+ attempted to write to a piece of the RAM, that some other program had been writing to. From this error-message one can't see, which of the two programs is 'the bad guy'.
To explain a bit more: Windows hands out a piece of the (RAM-)memory to each program, in which it can do it's work. If a program starts using RAM that's outside 'it's own area', it can get in the way of another program. Either of the two programs can crash, depending on who tries to use the messed-up memory-area first.
Then you can get problems like the error-messages above.

Would re-installing Schedule+ be a likely solution?
Actually, not really ...
As you might understand from the short explanation above, it might turn out to be necessary to re-install an entirely different program, to get rid of the Schedule+ error-message. But it's often very difficult to tell what program that would be.

Hmmm... , now what?
First question would be: do you have this error often?
If not: keep things like they are. You might mess up more, then you fix.
If so: you might try, whether re-installing Schedule+ helps. Schedule+ may very well not be the culprit, but re-installing it is not so much work, and it might help.
Should this not help (which might well be the case), you could think about re-installing Windows and all programs. REMEMBER TO BACK UP ALL OF YOUR DATA FIRST.
(If this sounds too much like a nightmare to you, you can leave it at the point of just thinking about it ... ;-) )

As a conclusion: this is actually more a general 'Windows'-problem, than a specific 'Schedule+' error. So the solution may not be in Schedule+ either.

back to top

<- back to menu