winamp 5.2 crashes when i try to open
 

i just downloaded the new installation just now and i installed it, and when i clicked "run winamp" it crashes and windows tells me it had to shut down and should i report it to microsoft ect....

i cleared my browser cache and uninstalled it and tried it again and it still crashes whenever i try to open winamp

im using windows XP SP2 all the latest windows updates, ect

I don't think clearing the cache would solve the problem... but I'm having the same difficulties.

I've noticed that Winamp is crashing due the the presence of AIM (at least version 5.9) in the background. If I have AIM minimized to the system tray, then maximize it again, Winamp crashes. If someone tries to get files from me and Winamp is open, Winamp crashes. There's a bug between these two programs... something's conflicting in memory, and it's really annoying. It could be that AIM is taking away some sort of critical modules when Winamp is open when AIM becomes the active window again, or is overwriting that module thus crashing Winamp. Whatever the case may be, FIX IT!

try a complete and total uninstallation
this means uninstalling and then deleting the entire winamp folder from program files
then install it again
it took me two times, but now it's working... let's hope it stays that way

The same problem happened to me. I had Winamp 5.12 or 5.13 or whatever the previous version was... and it worked perfectly. As soon as I updated to Winamp 5.2, it crashes each and every time I try to open it. And I don't have AIM on my computer, so I know that's not the problem.

This seems to be a different case on each computer. It could be that it was just released to early and it's still too buggy. I'm sure they'll fix it soon.

It must be different for each compy. My roommate also just installed it and it worked fine for him.

Same problem here... Crash when opening winamp 5.2 with dsp_stacker.dll DSP plugin [it has systray icon]

I just simply change dspplugin_name=dsp_stacker.dll to dspplugin_name= in winamp ini before running it, if i last time forgot to disable it before closing =)

ah right... it started to crash since some 3xx beta update and so is in 5.2 (39x beta? don't remember numbers x.x)

I've had the same problem ever since I upgraded to Winamp 5.2. It usually crashes when I change the player skin, open DSP stacker with more than two DSP plugin and playing a song all at the same time. When I restarted winamp, it crashes again asking me to debug. I think that's the scenario here.

My workaround is to delete the winamp.ini located at C:\Program Files\Winamp and rerun winamp. Winamp should then run with no problems but all your settings will be lost, so you would have to configure winamp again. The best way is to make a backup copy of winamp.ini and rename it to winamp.ini.bak or something similar.

Nullsoft - get this fixed
 

Yeh, my 5.2 crashes on attempting to start.
BUT - I do not have the time or patience to go through all these fixes above - just reverted back to 5.13
I have about five skins installed and I think a few plug-ins - must be old ones tho' 'cos I haven't installed a new plug-in for years
Nullsoft folk - please fix whatever is causing this
:mad:

Mcyrhul - I've got the same problem, I've tried all the fixes above, but nothing seems to have helped!

hmm... i deleted the winamp folder after uninstalling, and it works at the moment. Ill see if i can tell what crashes it

EDIT: it seems to be something with plugins that is making winamp crash (at least for me). I completly uninstalled it and it worked fine, then i installed "64th note" plugin and it works fine then i installed "SNESamp" plugin and it crashes.

my custom skin works as well

Modern Skin causes the crash on my machine?
 

If I start with the classic skin, it seems to work ok.

Dell Optiplex GX620
Pentium D 2.80 GregaHertz
Unknown sound device
ATI Radeon X600
Windows XP Pro x64
DirectX 9.0c
Winamp 5.2 Pro

Re: Modern Skin causes the crash on my machine?
 

Update:

Here's some info from my logs:

Faulting application winamp.exe, version 5.1.3.387, faulting module gen_ff.dll, version 0.0.0.0, fault address 0x00074736.

Faulting application winamp.exe, version 5.1.3.387, faulting module winamp.exe, version 5.1.3.387, fault address 0x0005213c.

Faulting application winamp.exe, version 5.2.0.473, faulting module icm32.dll, version 5.2.3790.2476, fault address 0x00004500.

As you can see, I'm having trouble with both 5.1.3, and 5.2.

Thanks!!!!!

Just tried loading with the 'Classic' skin, and still no joy :(

Me too!
 

Crashes for me too. I wouldn't really say crashes - more like "hangs" for longer than 10 minutes without loading. I just deleted my old copies - anyway I can get an old 5.13 version of pro?

Another iteration...

I've never had a problem with downloading and running winamp prior to this... I've tried everything mentioned above and in the other threads, etc... checked all the usual suspects, but these days I'm not that up on XP Home to know what might be causing this... it might be something else altogether. 5.13 worked just fine until 5.2 was downloaded. Now I can't get EITHER version to work, even after 5.2 was scrubbed off. It crashes right after I try to start it.

Dudes, don't tell me that I'm going to have to re-format my hard drive just to get this new version of winamp working!

You guys should NEVER have made a deal with AOL... lol

Yeah 5.2 is bad news for now. They made a deal with AOL, what does that entail? I swear if I see ONE ad I'm going to use a different player.

I've just isloated the cause of my crash: the in_CDReader.dll file (can't even remember what this is for).

@Panda76
in_cdreader.dll is an old 3rd-party plugin (which has never been included with the default winamp distro) and was required in versions of Winamp prior v2.90 to enable Digital Audio Extraction method for CD playback. Of course, since v2.90 Winamp's in_cdda.dll supports DAE by default, and therefore the old in_cdreader plugin is no longer required. Having both plugins installed/active can certainly cause conflicts.


@all

Looks like old 3rd-party plugins are causing all/most of your problems.

http://forums.winamp.com/showthread....d=161361#specs

If you would've all read that first (Sticky: FAQ) and attached a my_plugin_list.txt to your post, then we could've diagnosed the cause of your problems much easier/sooner.

Alas, it's always the case that whenever there's a major Winamp update (eg. 2.70, 2.80, 2.90, 5.0, 5.10. 5.20) then there's always some old 3rd-party plugins which will break and will need fixing by the relevant 3rd-party authors to make them compatible with the new version of Winamp... ie. there's nothing to be fixed at our end.

Either remove 3rd-party plugins, and restore them one at a time until the problem reoccurs (thus revealing which plugin was the guilty party), or go for a clean install

Winamp 5.2 loads instantly and with no crashes on all the test machines we've run it on, and it runs perfectly ok on my own personal comp, and that's with a fair few 3rd-party plugins installed too (but yeah, even I had to remove a couple of problematic plugins).

Other than that, there could be some conflicts going on, maybe with the new Portable Media Player support plugins (ml_pmp, pmp_ipod, pmp_njb, pmp_p4s), especially if you were using a different plugin previously (eg. ml_ipod, or ml_zen). But of course, again, a plugin list would've told us this, and then there would have been no need for us to try guess the cause/solution.


Re: old versions (5.13)
They're all available here, but note that they are no longer supported.

Thanks for the info!
 

Egg:

Just wondering if you're also testing on Win64 dual core boxes?

We've had a number of issues with some drivers and hardware -- that's why I'm asking (Winamp has been crashing on shut down, for example).

In fact, the Winamp installer complains that CD burning/ripping may not work, but I've had no problems with ripping at least.

Thanks again for the info -- I'll be better about providing better info in the future!

Thanks!
Go

thanks

When I upgraded the old version it did not start! Then i uninstalled winamp and also deleted the folder in program files. Then I reinstalled winamp 5.2 and it works! I think that there is a problem with a plug-in or sth. like that! I hope i've been helpful!

All right,

I removed ml_ipod.
My Winamp (5.2) crashes when my iPod is plugged in.
It works fine when it isn't plugged in.

Try unplugging your iPod before you open Winamp.

DJ, my problem found at http://forums.winamp.com/showthread....hreadid=238931 doesn't have anything to do with Winamp, since I deleted EVERY SINGLE third-party plugin (in fact, I did a TOTAL CLEAN INSTALL, which is for me to uninstall Winamp AND delete the Winamp folder completly. I stress to make sure you know that they only plugin I had were the ones that came WITH the player install, no third party or any added plug-in's what-so-ever), and it STILL crashes anytime I try to play ANY OTHER FILE AT ALL other than the MP3 that was installed with 5.2.

My problem seems to have absolultly nothing to do with any sort of plug-ins (and I even double-checked in ALL the plug-in sections in the Preferences dialog box just to be sure), with no luck. It STILL crashes.