I disabled WIA as a workaround, but I want to fix problem underlying i
I am a new member. I am looking for suggestions for cleaning up the source of a Data Execution Prevention action triggered by Generic Host Process that when interrupted says EventType BEX in the accompanying message (see below for detail).
What I have seen on the web is that the most likely cause is HP printer driver or other software. I plan to reinstall HP software for an OfficeJet 7310xi unless others might know more and suggest otherwise. Thanks in advance if you know something about this kind of issue.
The symptoms of the problem were on startup the appearance of multiple Data Execution Prevention (DEP) messages from the previous Win XP session with a request to send info to MS and also that Windows Explorer took a very long time to find disk drives, folders and files when started up.
I have a workaround for the symptoms in disabling WIA (Windows Image Acquisition) in Services. That stops the DEP messages at the next login and makes Windows Explorer fast again.
Here is more of the detail from the message I get if I leave WIA on automatic or manual rather than disabled:
EventType : BEX P1 : svchost.exe P2 : 5.1.2600.2180 P3 : 41107ed6
P4 : unknown P5 : 0.0.0.0 P6 : 00000000 P7 : 009a9eec
P8 : c0000005 P9 : 00000008
Error report will include files
When I open appcompat.txt I see the following except that I deleted the additional information beyond the SIZE data:
<?xml version="1.0" encoding="UTF-16"?>
<EXE NAME="SYSTEM INFO" FILTER="GRABMI_FILTER_SYSTEM">
<MATCHING_FILE NAME="advapi32.dll" SIZE="616960"
<MATCHING_FILE NAME="gdi32.dll" SIZE="282112"
<MATCHING_FILE NAME="kernel32.dll" SIZE="984576"
<MATCHING_FILE NAME="ntdll.dll" SIZE="708096"
<MATCHING_FILE NAME="ole32.dll" SIZE="1285120"
<MATCHING_FILE NAME="oleaut32.dll" SIZE="549376"
<MATCHING_FILE NAME="shell32.dll" SIZE="8454656"
<MATCHING_FILE NAME="user32.dll" SIZE="577536"
<MATCHING_FILE NAME="wininet.dll" SIZE="824832"
<MATCHING_FILE NAME="winsock.dll" SIZE="2864"
The good news is that the message is always the same. The better news is that I now have a less annoying experience witheout the messages. The great news would, of course, be fixing the underlying problem.