Winamp 5.8 installation error

[Wolverine71]

... nobody seems to have the same error, not anybody...

[Wolverine71]

I really don´t know about these things you´re telling me. I´m really angry with this because it work for a few days and now it crushed again. I don´t know how to fix it and anyone seems to have the same error as me. Thank you so much for your lines. I´ll have to wait to another version. Meanwhile, I´ll hate Windows Media Player...

[Stella764]

What the Internet tells me about these DirectSound errors is either that they are old drivers, or about restarting the Windows Audio service.

WASAPI has been only introduced in 5.8, but are you getting an issue using the DirectSound driver on 5.8? That would be a fair comparison to see if the bug is because of WASAPI, or if it was a regression.

WASAPI seems to work fine for me, but I have newer hardware and drivers.

[Wolverine71]

Thanks

[NJK]

https://www.google.com/search?source=hp&ei=BfbRW9fJL5DYwAL895TIBg&q=Access+Violation+%280xc0000005%29&oq=Access+Violation+%280xc0000005%29&gs_l=psy-ab.3..35i39k1.963.963.0.2184.3.2.0.0.0.0.54.54.1.2.0....0...1.1.64.psy-ab..1.2.142.6...89.SeQPE_4CznE

[Wolverine71]

Hi, I was happy when i knew that Winamp was back. I used a lot in other devices, and now I´m trying the installation in a Windows 7 Home Premium with 64 bits, everything it´s ok until the running, when appears an error that my computer sends to "Nullsoft Bug Reporting".

The subject is: "Winamp Error Report [3A2E47B11EAE4DB98216F461A394E08]"

And the main text:

"Winamp client version: 5.8 Build 3660
winamp caused an Access Violation (0xc0000005)
in module winamp.exe at 0023:050a6be7.

Exception handler called in Winamp."

The software was downloaded today from Winamp´s site.

Does anybody knows what can be happening? Thank you,