No. Within each process there are sections of memory that either hold code or data. So maybe he is trying to change a code section, that's why it gives that error.
But well, now that I think about it. CE will take care of that problem by changing the permissions of that section. Thus it means it was a protected memory he tried to access.
The Following User Says Thank You to Jabberwock For This Useful Post: