INTERACT FORUM

More => Old Versions => Media Center 11 (Development Ended) => Topic started by: GHammer on December 09, 2004, 03:35:45 pm

Title: DEP Violation?
Post by: GHammer on December 09, 2004, 03:35:45 pm
I've never seen any program get shutdown by XP until now.
Doing nothing special, playing an APE file, had Options open and unchecked 'Run Remote Server on port:' Clicked Ok and got this:

(http://ghammer.net/147Error.jpg)
Title: Re: DEP Violation?
Post by: JimH on December 09, 2004, 03:50:56 pm
Sounds like an SP2 improvement.  Did you try the Microsoft site?

Title: Re: DEP Violation?
Post by: Alex B on December 09, 2004, 04:02:27 pm
Microsoft Help and Support:

You receive a "Data Execution Prevention" error message in Windows XP Service Pack 2 or in Windows XP Tablet PC Edition 2005 (http://support.microsoft.com/kb/875351)

A detailed description of the Data Execution Prevention (DEP) feature in Windows XP Service Pack 2 and Windows XP Tablet PC Edition 2005 (http://support.microsoft.com/kb/875352)
Title: Re: DEP Violation?
Post by: Omni on December 09, 2004, 04:23:27 pm
Sounds like an SP2 improvement.  Did you try the Microsoft site?
Apparently, MC is doing something that AMD's onchip microcode deems inappropriate.  Microsoft provides a way to "ignore" the suspicious behavior, but it is an MC issue, not a Microsoft issue.
Title: Re: DEP Violation?
Post by: JimH on December 09, 2004, 04:38:21 pm
MC does a lot with the registry and sometimes a lot with ports, so it isn't surprising that Microsoft might object.

A better description of exactly what triggers it might help us understand what the possibilities are.

Why do you think it's an AMD chip?
Title: Re: DEP Violation?
Post by: Matt on December 09, 2004, 05:13:07 pm
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?
Title: Re: DEP Violation?
Post by: GHammer on December 09, 2004, 10:20:29 pm
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."