I've never seen this problem after installing XP.
The difference is that a misbehaving program will only corrupt its own memory space.
Usually the problem is writing to memory you don't own.
For example, this could be an out of bounds array index or drawing outside the limits of a locked buffer.
The only advice I can offer is to find the source of the crash and fix it.
The difference is that a misbehaving program will only corrupt its own memory space.
Usually the problem is writing to memory you don't own.
For example, this could be an out of bounds array index or drawing outside the limits of a locked buffer.
The only advice I can offer is to find the source of the crash and fix it.