I have a problem with IE crashing when running my swf player

From glancing through the forum, it appears that Internet Explorer's flash
plugin is having issues with respect to sound. From reading some of the
comments in this forum, people are thinking perhaps it is hardware sound card
issues. From the behavior of my actionscript code, i am thinking that perhaps
it is an issue with the ActiveX plugin.

I have created a flash player that I have running in both firefox(Mozilla) and
Internet Explorer. This player dynamically loads swf, flv and mp3 files on the
fly. The player loads swf files. Each loaded swf file can then load associated
sound and video files.
My code has no problems when running in mozilla based browsers. Unfortunately
this is not true with IE which most of my audience will most likely be using.

My player has a sound button from which i can turn my sound on and off. When i
turn my sound off, Internet Explorer runs fine.I can traverse all of my swf
content. No crashing occurs. If the button is turned on, after 50-55 swf files
have been loaded with their associated mp3 files, the browser crashes. This
implies to me that the sound object and its associated properties and methods
are malfunctioning in some manner. From programming in another scripting
language(TCL/TK),
I have run into this problem when buffer areas have gotten corrupted when code
writes to areas that they shouldn't and blows away necessary information which
appears to be the case here.

I am running my IE browser in a windows XP professional operating system at
work. The browser version is IE 6.0.2900.2180.... with service pack 2 updates.
Flash player version 7.0.19.0 plugin as well. At home, i am running windows xp
pro without the service pack 2 updates and the same version of IE without
service pack 2 updates. I can get IE to crash on both platforms.

I know from reading other comments that Bentley Wolfe from macromedia has
escalated the problem to macromedias development team, I would like to know
what is the current status of this bug. OR has anyone found a workaround to
deal with this problem?