Someone complained to me that they get DEP errors in XP when running PDFCreator. I have never had such an issue. I looked on the sourceforge forum for PDFCreator and it seems some people do have this problem. I've yet to see a specific cause, or an example of the developer responding to these complaints. Does anyone know what the cause of the issue is?
Well, the basic idea of DEP implies the fundamental cause: PDFCreator is trying to execute code in a memory segment that XP thinks is data. One reason that this might be happening to others and not to you is that your DEP policy is probably the default
OptIn, and theirs might be set to a more-restrictive
The more specific reason why DEP is being triggered is a matter of some deep debugging in PDFCreator.