winamp crashes after every 1-2 songs

[metashdw]

So I've searched around the site a bunch and haven't found anybody with the same problem as me. My winamp works, and I can play any song/video just fine, but after playing a couple in a row, winamp unexpectedly crashes.

I have no plugins, and I've already tried reinstalling, and every different skin. Also, I've had winamp for years and have never had any problems. The only thing that changed was today I started using a new keyboard, mouse, and moniter, and I installed a new internet driver.

I have Windows XP, SP2, DirectX 9, Pentium 4, 1.75 GB RAM, and Winamp 5.52. My sound card is the one that came with this computer (it's about 3.5 years old), Creative SB Live! or something like that.

Also: I just realized that my equalizer isn't working either. The sound wont change at all.

[aussieraider007]

Yeah it's happening to me man, i've tried every single skin and used defaults,re-installed all my Codec's for songs and only played Mp3's and .wav's on winamp and about 1-3 songs it just freezes. My whole pc frigen crashes! It gets to 0:00 and plays about 0.5 sec of a song then Winamp and my pc freezes then leads to a restart.

I haven't done anything to my pc in the last month, been using winamp a long time.

Pentium 4 3.0 MhZ
2 Gig of Ram
7600 Nividea GT
80 Gb HDD
Logitech g15 Keyboard
Mx 518 Logitech keyboard
Icematt Black (headset)
XP Sp2

[J_Darnley]

Both of you please read the sticky FAQ thread and then post the information we require. Error details (if any), list of plugins, hijack this log, dxdiag log.

[metashdw]

Here's dxdiag, Like I said I don't have any plugins, and I don't have hijackthis but I keep my computer pretty clean. I think it might have to do with the audio drivers because the equalizer doesn't work either.
It hasn't given me error details.. just the standard "send error report" box that windows gives when anything crashes. I looked at the error report and it looked like a bunch of code and nothing really useful, is that what you need?

[J_Darnley]

Well if you don't have any plugins then what are you going to do with Winamp? Winamp has no functions without plugins.

The error details can be accessed through that crash report dialog, "To see what this report contains, Click Here" and then copy the bit that says...

Why the hell am I retyping what's in the FAQ?
http://forums.winamp.com/showthread....d=161361#specs

Please include all relevant Winamp & System specs, including:
-A List of Plugins (see below for full details) <-- this is the most important log!
-PC or Motherboard make/model
-CPU & RAM
-Sound card or chip
-Videocard
-Windows OS (including Service Pack, eg. WinXP sp2)
-DirectX version (start > run > dxdiag)
-Winamp version (eg. 5.52)
-Confirmation of the Winamp installation type (Pro, Full, Bundle, Lite)
-We will also need further information for any video playback issues

If relevant, also attach a HijackThis log (alt download)
to show all concurrently running processes and startup items.
Instructions for attaching the HJT log to your post can be found below.
Make sure you've got HJT v1.99.1 or newer (logs from older versions are useless).
Further HJT instructions & alt download sites: (1) | (2) | (3) | (4).

Please also include full details of any error messages
eg. in WinXP Error message, you'll see it say something like:
"To see what data this report contains, click here"
which will then reveal the following required information:
AppName: Winamp.exe | AppVer: ? | ModName: ? | ModVer: ? | Offset: ?

Also include any other information relevant to the problem at hand, eg.
-internet connection type/speed (if related to playing streams)
-filetypes played when the problem occurs (mp3, m4a, wma, ogg, etc)
-internet browser+version
-firewall details (if related to any internet/online features)
-cd-rom drive make/model (if related to playing/ripping/burning cd's)
-a link to a zipped sample file which causes the problem
..(if the file is too big to attach, upload it to one of stashbox.org or sendspace.com or mediafire.com)
-a link to a specific stream url which causes the problem

As I can't see any glaring problems in the dxdiag log all I can suggest you do is a clean install.
http://forums.winamp.com/showthread....d=161361#clean

[SandmanX]

Attached is my dxdiag.

Have attempted everything stated in FAQs, Tech Support and in this thread here but to no avail.

This bug really needs to be ironed out. It has worked fine before and I have no idea why this issue has suddenly cropped up.

Seems like i'm not alone.

[J_Darnley]

Again I can't see anything wrong from your dxdiag log but if you want a suggestion other a clean install you will have to provide the other information we need to help diagnose the problem, that is the list of plugins and a hijack this log.

If you genuinely think it is a bug then you will need to give much more information about how to reproduce it. I think that if Winamp was really crashing because it changes track someone might have noticed it before now.

[LongBow986]

doing the same stuff to me, its a 'virgin' install of winamp, havent installed any 3rd party plugins, no additional skins, nor have i caught any virus/spyware/malware as of late. i am running windows vista. it happened when i installed the latest winamp 5.531. im lucky for it to be running right now
-edit- if i had fraps id show you

[J_Darnley]

There is an easier way to show me than installing fraps to record a video of you doing it.

[DJ Egg]

What's with all the dxdiag logs?
The FAQ says we only need a dxdiag log for problems with video.

For all other problems we need a 'List Of Plugins', HijackThis log and details of the crash/error message. Without those 3, we can't help.

The 'List of Plugins' isn't just for showing if there's any 3rd-party plugins present, it also shows which 1st-party plugins are present (and whether they're the latest versions), the path to your Winamp settings folder, your Windows OS, what skin and lang pack you're using (if any), which output & dsp plugins are active, amongst other useful info.

The HJT log shows us startup items and what processes are currently running, which helps us determine if there's any possible conflicts going on.