Winamp has stopped working..


Recommended Posts

I just recently upgraded to windows 7 ultimate 64-bit from 32-bit, and I have this problem with winamp. Whenever I open it up and play any radio station, after about 30sec I get the error message "Winamp has stopped working" and it closes. In WMP it plays fine. I also like to listen to some other internet radio stations which are in .asx format and WMP doesn't play those.

Any suggestions? Thanks.

Link to comment
Share on other sites

.asx files are extremely dangerous. Don't ever, ever use them.

Winamp has multiple issues with W7 - and understandably, the audio system in W7 has changed a fair bit since vista.

I run 5.55 fine on W7 7200 RC 1 64-bit.

Anything newer should work fine on any version you are running.

Link to comment
Share on other sites

^-- Are you trolling... ?

Why doesn't WMP play those ASX files... ? What happens?

What's the fault data for the WinAMP crash?

When I open an asx file in WMP I can't press play for it to work. I have to fast forward a bit then it starts to play.

How do I access the fault data? All it gives me is a "winamp has stopped working" window and I only have the option to close it and nothing else.

Link to comment
Share on other sites

.asx files are extremely dangerous. Don't ever, ever use them.

Don't be stupid. Pretty much all online content that streams in Windows Media uses ASX. I'm sure your security patch there is useful for all the people out there running Windows 98 though.

As to why WinAmp crashes, it's just because it doesn't support the new Windows 7 codecs. It happens to lots of people.

Link to comment
Share on other sites

Don't be stupid. Pretty much all online content that streams in Windows Media uses ASX. I'm sure your security patch there is useful for all the people out there running Windows 98 though.

Who cares about windows media? If you're going to stream, it should be done properly or not at all.

It appears that over 3/4 of ASX procedure handling software STILL has this exploit, just Google "ASX Exploit" to see a list of 10 odd different softwares just on the first page of results.

I've seen ASX files exploit WMP 10 and 11, up until M$ releases the security patch ALL versions of WMP were vulnerable.

FYI, WMP 6 (The ver this patch was released for) actually comes bundled in XP.

As to why WinAmp crashes, it's just because it doesn't support the new Windows 7 codecs. It happens to lots of people.

That's not possible. There's no "New" Windows 7 codecs and Winamp doesn't use them.

The only way to get winamp to play non-standard codecs to enable FLV's and many others is to install custom plugins specifically for winamp.

The rest is hardcoded.

Link to comment
Share on other sites

Pro-tip:

Using M$ as an abbriviation for Microsoft makes you look like a tool.

On topic: You said you did an upgrade....did you try uninstalling then reinstalling the most recent Winamp?

<--- oops nevermind...dont think you can do an upgrade from 32 to 64 bit

Link to comment
Share on other sites

Who cares about windows media? If you're going to stream, it should be done properly or not at all.

It is one of the most popular streaming formats on the planet, and until the advent of flash video it completely dominated streaming. It's cute for you to sit there and say "who cares", but the reality is that WM is extremely popular. You can sit here and whine about ten year old exploits that are no longer relevant, but it's a complete derail.

That's not possible. There's no "New" Windows 7 codecs and Winamp doesn't use them.

The only way to get winamp to play non-standard codecs to enable FLV's and many others is to install custom plugins specifically for winamp.

The rest is hardcoded.

What? There are new codecs, and nothing is "hardcoded" in Winamp apart from MP3 and OGG. It just builds a default DirectShow graph with whatever filters have the highest merit. When it encounters many of the Microsoft ones, it will simply crash.

Link to comment
Share on other sites

Really? prove it. Unless you can, i suggest you quit trolling. Because that is very obviously what you are doing.

The exploit may be 10 years old, true, i don't really care, it's still 100% relevant.

90% of my customers who had virii got it from either internet explorer, LimeWire or an asx exploit in WMPlayer while trying to watch porn.

Link to comment
Share on other sites

Prove what...?

And no, the exploit most certainly is not relevant on any modern system. Either your customers have systems that haven't been updated in half a decade, or more likely, they get viruses (the plural of virus) by being idiots. The onus is on you to prove that any such bugs exist in any currently shipping Microsoft software (or even third party software like Winamp). It doesn't. They've been fixed long ago.

Link to comment
Share on other sites

Err are you a complete retard? I linked the MS Patch not long ago.

It's not listed in Windows Update, it's a manual patch to apply.

When i encounter the issue, i patch the system and the patch is in my list of bare minimum softwares/updates to install on a system when i do a format.

I've already proven myself, it's not my fault if you know so little about the state of the I.T industry that you don't even know this patch isn't included in the "Essential" security patches list on WU.

Link to comment
Share on other sites

Err are you a complete retard? I linked the MS Patch not long ago.

It's not listed in Windows Update, it's a manual patch to apply.

Windows Media Player 6.4 Security Patch: ASX Processor Contains Unchecked Buffer

[...]

System Requirements

* Supported Operating Systems: Windows 2000; Windows 95; Windows 98; Windows NT

* Windows Media Player 6.4

You do realize that it's 2009 now, right? You're not writing this through a tear in the fabric of time, are you? I can't be bothered with this nonsense. If you want to go on claiming that a known ten year old bug in one of the most widely used playlist formats in the world hasn't been fixed and that you need to go and download an ancient patch to fix it, then so be it. Live your delusion.

Link to comment
Share on other sites

Buddy, Windows Media Player 6.4 comes with windows xp. You might want to mark it down as a typo that it's not listed on the MS site.

EDIT: I shouldn't have to mention, windows XP *IS* 10 years old almost. It was released in 2000.

Finally, "Ancient patch" or not, it's still relevant, not having it still enables people to install custom dll's on your system via the ASX exploit.

Link to comment
Share on other sites

Buddy, Windows Media Player 6.4 comes with windows xp. You might want to mark it down as a typo that it's not listed on the MS site.

It isn't a typo. The version that ships with XP is already fixed. Even if it hadn't been (it is), you'd have to be high beyond belief to think that a critical vulnerability would remain unpatched for the entire lifetime of the OS unless you went and manually installed a patch.

XP was released in late 2001, and has been updated continuously since. Even if we for argument's sake say that other bugs have also cropped up over the years, they've all been fixed long ago and the only people still affect are those running extremely old and unpatched (by WU) systems. You are now in a thread about Windows 7 and the latest version of Winamp.

Link to comment
Share on other sites

You are now in a thread about Windows 7 and the latest version of Winamp.

So why are you trolling the application of security fixes and WMP versions 6-10 topic then?

The exploit exists and i've seen it happen with my own eyes on WMP 10 and 11.

If you don't beleive that, i don't particularly care, your raather rediculous comments prove you don't know what you're doing and i'm over this debate.

I've already said i have no problems with winamp 5.55 on W7, perhaps you should get with the program and test it on the version YOU are running, if you actually have any desire to be contributing to this thread.

Link to comment
Share on other sites

So why are you trolling the application of security fixes and WMP versions 6-10 topic then?

The exploit exists and i've seen it happen with my own eyes on WMP 10 and 11.

You are the "troll". You barged into the thread and told the guy "DON'T USE ASX!!! IT'S BAD!!! DON'T USE IT!!!" and then started referencing an ancient bug in products that predate even XP. I'm sorry, but your (completely unverified) claim that a critical bug from the 1990s is still present in Windows and remains unfixed is ludicrous. Whatever you think you've seen has been something else.

I've already said i have no problems with winamp 5.55 on W7, perhaps you should get with the program and test it on the version YOU are running, if you actually have any desire to be contributing to this thread.

I run it and have had many problems with it randomly crashing, particularly when dealing with Windows Media. I believe I already commented on this.

Link to comment
Share on other sites

Or search for "MP3 exploit"... your point is centered around problems in random client rendering applications, and specifically ignores current versions of WMP or WinAMP. The 2001 WMP reference you make has been folded into the basic Windows code for years now, to my knowledge, and that fix is part of XPSP2, to my knowledge. So: probably not generally relevant any more than old MP3 buffer overruns in WinAMP might be.

If you know of some extant (current) BO with WMP10/11 whatever, please provide specific details.

But this digression seems largely unhelpful, since getting WinAMP working would seem to be first on "our" list. :)

When I open an asx file in WMP I can't press play for it to work. I have to fast forward a bit then it starts to play.

How do I access the fault data? All it gives me is a "winamp has stopped working" window and I only have the option to close it and nothing else.

Click this link:

* http://zachd.com/pss/pss.html#bucket

, which I had quietly linked to in my post.:))

Link to comment
Share on other sites

The 2001 WMP reference you make has been folded into the basic Windows code for years now, to my knowledge, and that fix is part of XPSP2, to my knowledge

Different bug. The one Phoenix is apparently going around patching was fixed before XP was even released. Regardless, the point is like you say that all the patches for bugs that have been released for XP and Vista over the years are actually already part of 7.

Link to comment
Share on other sites

Windows Media Format ASX Parsing Vulnerability - CVE-2006-6134:

A remote code execution vulnerability exists in Windows Media Format Runtime due to the way it handles certain elements contained in Advanced Stream Redirector (ASX) files. An attacker could exploit the vulnerability by constructing a specially crafted ASX file that could allow remote code execution if a user visits a malicious Web site, where specially crafted ASX files are used to launch Windows Media player, or if a user clicks on a URL pointing to a specially crafted ASX file. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

What causes the vulnerability?

The processing code within Windows Media Format Runtime which handles certain URLs included in ASX files.

http://www.securiteam.com/cves/2006/CVE-2006-4702.html

This means that even if you are running Firefox and you think that you are secure, by simply opening an ASX media file, you expose yourself to all kinds of IE vulnerabilities.
Those of your who have Media Player 11 are sort of protected. Upon execution you will see a confirmation box.

http://www.gnucitizen.org/blog/backdooring...ws-media-files/

http://www.fortiguard.com/encyclopedia/vul...p.overflow.html

http://www.microsoft.com/technet/security/...n/MS06-078.mspx

You got ONE thing right out of all the crap you've spewed over the last page hdood - i linked the wrong resolution earlier.

That is all.

Tested Software and Security Update Download Locations:

Affected Software:

?

Microsoft Windows Media Format 7.1 through 9.5 Series Runtime on the following operating system versions:

?

Microsoft Windows 2000 Service Pack 4 - Download the update (KB923689)

?

Microsoft Windows XP Service Pack Microsoft Windows XP Service Pack 3 3 - Download the update (KB923689)

Link to comment
Share on other sites

You got ONE thing right out of all the crap you've spewed over the last page hdood - i linked the wrong resolution earlier.

That is all.

Wrong bug, you mean. Thanks for your update though, I'm sure he's running out to get to get the XP patch for a bug that was fixed before Vista was even released to install on his Windows 7. I hope it's not too late for him.

Link to comment
Share on other sites

It's nothing inherent in the (simple XML) ASX format: you're simply referencing old fixed coding errors in the text parser, much like the WinAMP PLS exploit .

If you know of any ACTIVE security bugs/holes in WMP/Win7, point them ASAP so the right people can take care of them if they haven't already. If not: why fearmonger? There's enough actually wrong in this world.

I would love to get information about the actual WinAMP crash here. Or get that information to WinAMP's team so they can take a look. Either way. :) Jihads against any given format might be interesting in a new and unrelated thread. Getting Your Software Working is *my* priority here. :)

edit: Reviewed the 2006 articles that were linked to: those seem to have been previously addressed back in the Vista era or earlier. Not sure of the relevance to Windows 7. *Active* security issues would seem to be the most interesting... and still largely beside the point of helping ATOMIK getting his system working. Let's sort that out FIRST and THEN go tangential. :)

edit2: Ah-ha. Saw in another thread that Phoenix is an IT admin for a net cafe running XP machines. As much as we might laud XP, the 2002 security standdown between XPSP1 and XPSP2 is critical to understanding MS security. XP doesn't reap the full benefits of that, but Vista and Windows 7 both have much much improved security design. If you're XP-centric, you're probably going to be having many more security concerns, which the MS security team(s) would handle & fix, than you would on Vista/Windows 7. If you know of any active exploits, point those out. Otherwise: there have been exploits against most every file format renderer at this point, and at least MS seems committed to ensuring ongoing patching. And please let's stop the jihad at least in this thread until we can get the crash data here. :)

Edited by zachdms
Link to comment
Share on other sites

There's no guarantee it's fixed on Windows 7.

As it was said in one of those pages, Microsofts "Fix" for the bug was to add a confirmation box in WMP11.....

That's a different issue. That's regarding the fact that WMP embeds IE to show web content, so that you could accidentally be exposing yourself to an IE bug that you thought you were safe from (because you Firefox or whatever) by opening a playlist that contains URLs which would then be opened in the embedded IE. Get it? Earlier versions would simply show the web page automatically, whereas the last few versions will prompt you first. This is a completely separate issue from the earlier overflow bugs in the playlist parser.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.