Hi:
I was checking around and found that the probable cause of the problem is in
the HP software, that may interfere with the DEP (Data execution
prevention). You can disable that as a workaround but just a temporal
solution. You need to get in contact with HP and get the latest version of
the software of your HP multifuntion.
--
Un saludo
Juan Perez
P.D.:
Also found this info:
Data Execution Prevention
What does data execution prevention do?
Data execution prevention (DEP) is a set of hardware and software
technologies
that perform additional checks on memory to help protect against malicious
code
exploits. In Windows XP SP2, DEP is enforced by both hardware and software.
Hardware-enforced DEP
Hardware-enforced DEP marks all memory locations in a process as
non-executable
unless the location explicitly contains executable code. There is a class of
attacks that attempt to insert and execute code from non-executable memory
locations. DEP helps prevent these attacks by intercepting them and raising
an
exception.
Hardware-enforced DEP relies on processor hardware to mark memory with an
attribute that indicates that code should not be executed from that memory.
DEP
functions on a per-virtual memory page basis, usually changing a bit in the
page
table entry (PTE) to mark the memory page.
The actual hardware implementation of DEP and marking of the virtual memory
page
varies by processor architecture. However, processors that support
hardware-enforced DEP are capable of raising an exception when code is
executed
from a page marked with the appropriate attribute set.
Both Advanced Micro DevicesT (AMD) and Intel® Corporation have defined and
shipped
Windows-compatible architectures that are compatible with DEP.
Beginning with Windows XP Service Pack 2, the 32-bit version of Windows
utilizes
the no-execute page-protection (NX) processor feature as defined by AMD or
the
Execute Disable bit feature as defined by Intel. In order to use these
processor
features, the processor must be running in Physical Address Extension (PAE)
mode.
The 64-bit versions of Windows XP uses the NX processor feature on 64-bit
extensions and certain values of the access rights page table entry (PTE)
field on
IPF processors.
It is hoped that all future 32-bit and 64-bit processors will provide
support for
hardware-enforced data execution prevention. Microsoft continues to work
with
processor vendors to encourage the adoption and development of DEP
technologies.
Software-enforced DEP
An additional set of data execution prevention security checks have been
added to
Windows XP SP2. These checks, known as software-enforced DEP, are designed
to
mitigate exploits of exception handling mechanisms in Windows.
Software-enforced
DEP runs on any processor which is capable of running Windows XP SP2. By
default,
software-enforced DEP only protects limited system binaries, regardless of
the
hardware-enforced DEP capabilities of the processor.
Who does this feature apply to?
Application and driver developers should be aware of data execution
prevention and
the requirements of software running on a supporting platform. Applications
that
perform just-in-time (JIT) code generation or execute memory from the
default
process stack or heap should pay careful attention to DEP requirements.
Driver developers are encouraged to be aware of PAE mode on platforms
supporting
hardware-enforced DEP. PAE mode behavior on Windows XP Service Pack 2
systems is
changed to improve driver compatibility.
For More information
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx
--
Un saludo
Juan Perez
Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no
otorga ningún derecho.
