I can not even start Winamp !

pioneercezl · 18th June 2009, 09:37

I have installed winamp5552_full_emusic-7plus_en-us in my notebook that have Windows XP SP2 and each time when I try to start winamp a Visual Studio Just-In-Time Debugger window appear the messange "An unhandled win32 exception occurred in winamp.exe [4792]" I have a month with this problem.

I have try to install and unistall Winamp and also try to download a new executable from the website and Install again. What can I do? Help please !!!

ahwm · 13th August 2009, 17:09

I've got the same problem... Only I'm using 5.56 Pro. I tried to rip a CD this morning and it said it couldn't find the encoder. So I reinstalled and now I get this...

Unhandled exception at 0x01ca1221 in winamp.exe: 0xC0000005: Access violation reading location 0x00000000.

Visual Studio shows the disassembly and points to this as the problem:

01CA1221 mov eax,dword ptr [ecx]

Any ideas? I haven't yet tried uninstalling, but that will probably be my next move unless someone has any other ideas...

rkstar · 13th August 2009, 21:30

Quote:

Originally posted by ahwm
I've got the same problem... Only I'm using 5.56 Pro. I tried to rip a CD this morning and it said it couldn't find the encoder. So I reinstalled and now I get this...

Unhandled exception at 0x01ca1221 in winamp.exe: 0xC0000005: Access violation reading location 0x00000000.

Visual Studio shows the disassembly and points to this as the problem:

01CA1221 mov eax,dword ptr [ecx]

Any ideas? I haven't yet tried uninstalling, but that will probably be my next move unless someone has any other ideas...

Winamp's previous version was running fine for me with Vista SP1, 64 bit. Then I installed the 5.56 update and it only gets as far as the skin-selection before crashing. I tried uninstalling and re-installing, and during the installation it said some of the dlls were broken and couldn't be used.

rkstar · 13th August 2009, 21:37

Quote:

Originally posted by rkstar
Winamp's previous version was running fine for me with Vista SP1, 64 bit. Then I installed the 5.56 update and it only gets as far as the skin-selection before crashing. I tried uninstalling and re-installing, and during the installation it said some of the dlls were broken and couldn't be used.

I deleted old plugin files and this (so far) is fixed. Though I couldn't remove some of the files and this annoys me. I need to figure out how to unlock permissions to delete them.

ahwm · 13th August 2009, 23:09

I uninstalled, rebooted, reinstalled and now it seems to be working fine, so hopefully that fixed it. Still curious why the error came up, though...

18th June 2009, 09:37	#1
pioneercezl Junior Member Join Date: Jun 2009 Posts: 1	I can not even start Winamp ! I have installed winamp5552_full_emusic-7plus_en-us in my notebook that have Windows XP SP2 and each time when I try to start winamp a Visual Studio Just-In-Time Debugger window appear the messange "An unhandled win32 exception occurred in winamp.exe [4792]" I have a month with this problem. I have try to install and unistall Winamp and also try to download a new executable from the website and Install again. What can I do? Help please !!!

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

13th August 2009, 17:09	#2
ahwm Junior Member Join Date: Aug 2009 Location: Idaho Posts: 7	I've got the same problem... Only I'm using 5.56 Pro. I tried to rip a CD this morning and it said it couldn't find the encoder. So I reinstalled and now I get this... Unhandled exception at 0x01ca1221 in winamp.exe: 0xC0000005: Access violation reading location 0x00000000. Visual Studio shows the disassembly and points to this as the problem: 01CA1221 mov eax,dword ptr [ecx] Any ideas? I haven't yet tried uninstalling, but that will probably be my next move unless someone has any other ideas...

13th August 2009, 23:09	#5
ahwm Junior Member Join Date: Aug 2009 Location: Idaho Posts: 7	I uninstalled, rebooted, reinstalled and now it seems to be working fine, so hopefully that fixed it. Still curious why the error came up, though...