Sounds like a memory bug. Overflowing allocated memory can signal a malicious attack. However, in this case it would be an accident, not malicious. (unless you have a virus)
Can you reproduce the problem?
Hi Matt,
I just wanted to let you know that something had changed in that build and caused this to be triggered. Yes, I could recreate it, but only that build. So far 148 is fine.
By the way, this is enabled by default on all SP2 installs. If you have a supported AMD chip, it is hardware DEP. If not, software DEP is used. My system is an INtel, so it is software DEP
"Data Execution Prevention (DEP) is a set of hardware and software technologies that perform additional checks on memory to help prevent malicious code from running on a system. In Microsoft Windows XP Service Pack 2 (SP2) and Microsoft Windows XP Tablet PC Edition 2005, DEP is enforced by hardware and by software.
The primary benefit of DEP is to help prevent code execution from data pages. Typically, code is not executed from the default heap and the stack. Hardware-enforced DEP detects code that is running from these locations and raises an exception when execution occurs. Software-enforced DEP can help prevent malicious code from taking advantage of exception-handling mechanisms in Windows."