WMP 11 Buffer Overflow Detected when playing 2nd Music File

WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the second
song you attempt to play.

This causes the app to Hang and it must be killed via the control panel.

Here is a link to the error:
http://www.craddockfamily.com/images...PonWMAfile.JPG

What files cause this? Is it a specific file format or file... ?
Where are these files coming from?

--
Windows Media Development Team (speaking for myself only)
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Jim Craddock" <JimCraddock@discussions.microsoft.com> wrote in message
news:227D659C-52A6-4DBA-9CFD-8BC10FE0214D@microsoft.com...
> WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the
> second
> song you attempt to play.
>
> This causes the app to Hang and it must be killed via the control panel.

All files seem to cause it. WMA's that I download from URGE and old MP3's I
burn myself. It is being detected by the on-access scan of McAfee as a
Buffer Overflow attempt.

"zachd [MSFT]" wrote:

>
> What files cause this? Is it a specific file format or file... ?
> Where are these files coming from?
>
> --
> Windows Media Development Team (speaking for myself only)
> See http://zachd.com/pss/pss.html for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> "Jim Craddock" <JimCraddock@discussions.microsoft.com> wrote in message
> news:227D659C-52A6-4DBA-9CFD-8BC10FE0214D@microsoft.com...
> > WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the
> > second
> > song you attempt to play.
> >
> > This causes the app to Hang and it must be killed via the control panel.
>
>
>

This happens to me too. Although it happens every time that I double-click a
song name in Urge to play it or if I attempt to download a song in Urge.

If I disable Buffer Overflow Protection in McAfee, the problem goes away.
But our network guys won't let me leave that disabled (with good reason). We
use McAfee VirusScan Enterprise 8.0.

I tried excluding the wmplayer.exe file with "GetProcAddress" entered as the
API. When I do that, I don't get the error anymore, but it does lock up WMP11
when I attempt to do either of the things mentioned above.

Anyone know how to fix this?

-Mike

"Jim Craddock" wrote:

> All files seem to cause it. WMA's that I download from URGE and old MP3's I
> burn myself. It is being detected by the on-access scan of McAfee as a
> Buffer Overflow attempt.
>
> "zachd [MSFT]" wrote:
>
> >
> > What files cause this? Is it a specific file format or file... ?
> > Where are these files coming from?
> >
> > --
> > Windows Media Development Team (speaking for myself only)
> > See http://zachd.com/pss/pss.html for some helpful WMP info.
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > --
> > "Jim Craddock" <JimCraddock@discussions.microsoft.com> wrote in message
> > news:227D659C-52A6-4DBA-9CFD-8BC10FE0214D@microsoft.com...
> > > WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the
> > > second
> > > song you attempt to play.
> > >
> > > This causes the app to Hang and it must be killed via the control panel.
> >
> >
> >

Yeah, I'm in the same boat. Our network guys have a policy administrator.
Even though I'm Admin on my box and can change it to Disable OnAccessScan,
the policy Administrator executes every 5 minutes and turns it back on.

This is huge, MS guys. Basically, I cannot use WMP. However, possibly due
to one of these lockups, my whole library now is gone from the WMP11 and
refuses to get readded, so I'm not sure it matters anyway.

"Mike Z" wrote:

> This happens to me too. Although it happens every time that I double-click a
> song name in Urge to play it or if I attempt to download a song in Urge.
>
> If I disable Buffer Overflow Protection in McAfee, the problem goes away.
> But our network guys won't let me leave that disabled (with good reason). We
> use McAfee VirusScan Enterprise 8.0.
>
> I tried excluding the wmplayer.exe file with "GetProcAddress" entered as the
> API. When I do that, I don't get the error anymore, but it does lock up WMP11
> when I attempt to do either of the things mentioned above.
>
> Anyone know how to fix this?
>
> -Mike
>
> "Jim Craddock" wrote:
>
> > All files seem to cause it. WMA's that I download from URGE and old MP3's I
> > burn myself. It is being detected by the on-access scan of McAfee as a
> > Buffer Overflow attempt.
> >
> > "zachd [MSFT]" wrote:
> >
> > >
> > > What files cause this? Is it a specific file format or file... ?
> > > Where are these files coming from?
> > >
> > > --
> > > Windows Media Development Team (speaking for myself only)
> > > See http://zachd.com/pss/pss.html for some helpful WMP info.
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > --
> > > "Jim Craddock" <JimCraddock@discussions.microsoft.com> wrote in message
> > > news:227D659C-52A6-4DBA-9CFD-8BC10FE0214D@microsoft.com...
> > > > WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the
> > > > second
> > > > song you attempt to play.
> > > >
> > > > This causes the app to Hang and it must be killed via the control panel.
> > >
> > >
> > >

Is there any update on this issue? I'm having the same exact problem and
would like to know if there's a solution.

Mike wrote:
> Is there any update on this issue? I'm having the same exact problem and
> would like to know if there's a solution.

It's a beta, so really your short-term choices are 1. roll-back to the
previous version of WMP; or 2. wait for the release version.

Same thing here, basically. I was running on WMP 10, getting bo:heaps
seemingly randomly, also detected by McAfee VirusScan Enterprise 8.0.0 - I
thought upgrading to WMP11 beta a few weeks ago might help, but no suck luck,
I still get them just as much as before. I also tried the exclusion, which
resulted in the same lockups, so I went back to having no exclusion in place.
I'm not on Urge (just MSN Music), but it happens either on songs I ripped
from CDs as WMA or MP3, as well as downloaded WMAs. Doesn't seem to happen
with video files that I can tell, but I'm not playing many video files - I'll
post again after I try some. Unfortunately, it's not that consistent in my
case (might happen on the first or second song, might happen on the fifth),
but I'd say it is usually within 10 songs of the first one I start playing.
I'd take a screen shot next time it happens, but it would look almost
exactly like Jim's; it's the same bo:heap occurring in C:\Program
Files\Windows Media Player\wmplayer.exe::GetProcAddress. I'd really rather
not have to delete WMP and all my songs and re-rip my whole library, but at
this point, it's so annoying that I'm definitely considering it...

-Rich


"Mike Z" wrote:

> This happens to me too. Although it happens every time that I double-click a
> song name in Urge to play it or if I attempt to download a song in Urge.
>
> If I disable Buffer Overflow Protection in McAfee, the problem goes away.
> But our network guys won't let me leave that disabled (with good reason). We
> use McAfee VirusScan Enterprise 8.0.
>
> I tried excluding the wmplayer.exe file with "GetProcAddress" entered as the
> API. When I do that, I don't get the error anymore, but it does lock up WMP11
> when I attempt to do either of the things mentioned above.
>
> Anyone know how to fix this?
>
> -Mike
>
> "Jim Craddock" wrote:
>
> > All files seem to cause it. WMA's that I download from URGE and old MP3's I
> > burn myself. It is being detected by the on-access scan of McAfee as a
> > Buffer Overflow attempt.
> >
> > "zachd [MSFT]" wrote:
> >
> > >
> > > What files cause this? Is it a specific file format or file... ?
> > > Where are these files coming from?
> > >
> > > --
> > > Windows Media Development Team (speaking for myself only)
> > > See http://zachd.com/pss/pss.html for some helpful WMP info.
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > --
> > > "Jim Craddock" <JimCraddock@discussions.microsoft.com> wrote in message
> > > news:227D659C-52A6-4DBA-9CFD-8BC10FE0214D@microsoft.com...
> > > > WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the
> > > > second
> > > > song you attempt to play.
> > > >
> > > > This causes the app to Hang and it must be killed via the control panel.
> > >
> > >
> > >

I have the same problem with WMP 10. Interestingly, it only appeared when I
cut over to my new Dell Latitude 620 - the old Latitude 600 never had this
problem. I have also seen it with video clips, but again, not watching many,
not very often.

Is this an MS issue...or a McAfee?

Re-ripping my whole library isn't an option - but a different player may be.
I'd rather not though...

"Rich H." wrote:

> Same thing here, basically. I was running on WMP 10, getting bo:heaps
> seemingly randomly, also detected by McAfee VirusScan Enterprise 8.0.0 - I
> thought upgrading to WMP11 beta a few weeks ago might help, but no suck luck,
> I still get them just as much as before. I also tried the exclusion, which
> resulted in the same lockups, so I went back to having no exclusion in place.
> I'm not on Urge (just MSN Music), but it happens either on songs I ripped
> from CDs as WMA or MP3, as well as downloaded WMAs. Doesn't seem to happen
> with video files that I can tell, but I'm not playing many video files - I'll
> post again after I try some. Unfortunately, it's not that consistent in my
> case (might happen on the first or second song, might happen on the fifth),
> but I'd say it is usually within 10 songs of the first one I start playing.
> I'd take a screen shot next time it happens, but it would look almost
> exactly like Jim's; it's the same bo:heap occurring in C:\Program
> Files\Windows Media Player\wmplayer.exe::GetProcAddress. I'd really rather
> not have to delete WMP and all my songs and re-rip my whole library, but at
> this point, it's so annoying that I'm definitely considering it...
>
> -Rich
>
>
> "Mike Z" wrote:
>
> > This happens to me too. Although it happens every time that I double-click a
> > song name in Urge to play it or if I attempt to download a song in Urge.
> >
> > If I disable Buffer Overflow Protection in McAfee, the problem goes away.
> > But our network guys won't let me leave that disabled (with good reason). We
> > use McAfee VirusScan Enterprise 8.0.
> >
> > I tried excluding the wmplayer.exe file with "GetProcAddress" entered as the
> > API. When I do that, I don't get the error anymore, but it does lock up WMP11
> > when I attempt to do either of the things mentioned above.
> >
> > Anyone know how to fix this?
> >
> > -Mike
> >
> > "Jim Craddock" wrote:
> >
> > > All files seem to cause it. WMA's that I download from URGE and old MP3's I
> > > burn myself. It is being detected by the on-access scan of McAfee as a
> > > Buffer Overflow attempt.
> > >
> > > "zachd [MSFT]" wrote:
> > >
> > > >
> > > > What files cause this? Is it a specific file format or file... ?
> > > > Where are these files coming from?
> > > >
> > > > --
> > > > Windows Media Development Team (speaking for myself only)
> > > > See http://zachd.com/pss/pss.html for some helpful WMP info.
> > > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > > --
> > > > "Jim Craddock" <JimCraddock@discussions.microsoft.com> wrote in message
> > > > news:227D659C-52A6-4DBA-9CFD-8BC10FE0214D@microsoft.com...
> > > > > WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the
> > > > > second
> > > > > song you attempt to play.
> > > > >
> > > > > This causes the app to Hang and it must be killed via the control panel.
> > > >
> > > >
> > > >

Just to add to my last item, after posting, I reinstalled WMP10 from the
website, and the problem SEEMS to have gone away. This was before I installed
the new security update for WMP (which may have addressed the same issue - I
don't know). For what it's worth...

"Paul E." wrote:

> I have the same problem with WMP 10. Interestingly, it only appeared when I
> cut over to my new Dell Latitude 620 - the old Latitude 600 never had this
> problem. I have also seen it with video clips, but again, not watching many,
> not very often.
>
> Is this an MS issue...or a McAfee?
>
> Re-ripping my whole library isn't an option - but a different player may be.
> I'd rather not though...
>
> "Rich H." wrote:
>
> > Same thing here, basically. I was running on WMP 10, getting bo:heaps
> > seemingly randomly, also detected by McAfee VirusScan Enterprise 8.0.0 - I
> > thought upgrading to WMP11 beta a few weeks ago might help, but no suck luck,
> > I still get them just as much as before. I also tried the exclusion, which
> > resulted in the same lockups, so I went back to having no exclusion in place.
> > I'm not on Urge (just MSN Music), but it happens either on songs I ripped
> > from CDs as WMA or MP3, as well as downloaded WMAs. Doesn't seem to happen
> > with video files that I can tell, but I'm not playing many video files - I'll
> > post again after I try some. Unfortunately, it's not that consistent in my
> > case (might happen on the first or second song, might happen on the fifth),
> > but I'd say it is usually within 10 songs of the first one I start playing.
> > I'd take a screen shot next time it happens, but it would look almost
> > exactly like Jim's; it's the same bo:heap occurring in C:\Program
> > Files\Windows Media Player\wmplayer.exe::GetProcAddress. I'd really rather
> > not have to delete WMP and all my songs and re-rip my whole library, but at
> > this point, it's so annoying that I'm definitely considering it...
> >
> > -Rich
> >
> >
> > "Mike Z" wrote:
> >
> > > This happens to me too. Although it happens every time that I double-click a
> > > song name in Urge to play it or if I attempt to download a song in Urge.
> > >
> > > If I disable Buffer Overflow Protection in McAfee, the problem goes away.
> > > But our network guys won't let me leave that disabled (with good reason). We
> > > use McAfee VirusScan Enterprise 8.0.
> > >
> > > I tried excluding the wmplayer.exe file with "GetProcAddress" entered as the
> > > API. When I do that, I don't get the error anymore, but it does lock up WMP11
> > > when I attempt to do either of the things mentioned above.
> > >
> > > Anyone know how to fix this?
> > >
> > > -Mike
> > >
> > > "Jim Craddock" wrote:
> > >
> > > > All files seem to cause it. WMA's that I download from URGE and old MP3's I
> > > > burn myself. It is being detected by the on-access scan of McAfee as a
> > > > Buffer Overflow attempt.
> > > >
> > > > "zachd [MSFT]" wrote:
> > > >
> > > > >
> > > > > What files cause this? Is it a specific file format or file... ?
> > > > > Where are these files coming from?
> > > > >
> > > > > --
> > > > > Windows Media Development Team (speaking for myself only)
> > > > > See http://zachd.com/pss/pss.html for some helpful WMP info.
> > > > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > > > --
> > > > > "Jim Craddock" <JimCraddock@discussions.microsoft.com> wrote in message
> > > > > news:227D659C-52A6-4DBA-9CFD-8BC10FE0214D@microsoft.com...
> > > > > > WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the
> > > > > > second
> > > > > > song you attempt to play.
> > > > > >
> > > > > > This causes the app to Hang and it must be killed via the control panel.
> > > > >
> > > > >
> > > > >

so what's the deal... is there no solution to this? seems like a pretty big
problem for the new WMP11.

"Jim Craddock" wrote:

> WMP 11 is getting a Buffer Overflow attempt blocked by McAfee on the second
> song you attempt to play.
>
> This causes the app to Hang and it must be killed via the control panel.