"Milhouse Van Houten" <firstname.lastname@example.org> wrote in message
> "Jon" <Email_Address@SomewhereOrOther.com> wrote in message
>> "Milhouse Van Houten" <email@example.com> wrote in message
>>> The Internet seems to have a grand total of one question about this
>>> Vista error message, and the answer doesn't suit me since I don't have
>>> iTunes installed.
>>> I've seen bouts of this error message happen on two separate occasions
>>> now, most recently tonight.
>>> Apropos of nothing, running IE7 yielded that message -- you have to OK
>>> it 3 or 4 times before it goes away and allows IE to run. Eventually I
>>> noticed that Task Manager showed a task I was not used to seeing: media
>>> foundation protected pipeline (mfpnp.exe). When that task was examined
>>> with Process Explorer, it didn't even have any DLLs associated with it,
>>> so it was impossible to tell what spawned it. So I ended task on it and
>>> the Bad Image problem vanished.
>>> EventID: 26
>>> Application popup: EVR Fullscreen Window: Windows - Bad Image :
>>> Exception Processing Message 0xc000007b Parameters 0x762A023C 0x762A023C
>>> 0x762A023C 0x762A023C
>> There's a few more results with Google, if you google for mfpmp.exe
>> (the 'm' makes all the difference). DRM related, by the looks of it
> Yes, I made a typo there, but what I didn't find is any connection between
> mfpmp.exe and the error message I was getting. At least I know how to get
> rid of the error message should it ever recur, but I'm a little puzzled by
> mfpmp.exe running at all because I don't even have any protected content
> that I know of. I do use WMP, so I expect it resulted from that.
> Fortunately, mfpmp.exe didn't seem to cause any overuse of the CPU, which
> looks like one of the main complaints about it.
There's another suggestion in a thread called,
EVR Fullscreen error
which didn't work for the OP, but might for you, or perhaps spark of an
Looks like the site is temporarily unavailable as I write, but you can get
the idea from the Google cached version (click on 'cache' with the following
Or if not then here is the resolution that was posted.
"RESOLVED!...Got this solution while googling around..in some of the forums,
it is also mentioned that disabling any enhacements for the sound device (in
playback devices-->properties in volume control) can also resolve the issue.
A VST plugin which I had enabled in WMP 11 caused the problem. Disabling the
plug-in in WMP 11 resolves the issue!!"