Guru Meditation & Multiple Winamp Crashes

[vagranted]

Specs:
Winamp 5.531 Clean Install (No 3rd Party Stuff)
Windows Vista SP1 running as Admin
Intel Quad Core 6700
Intel DG33TL with 2GB pc-6400 RAM
Intel GMA 3100
IDT High Definition Audio Codec
DirectX 10
AV/AS: Kaspersky and Adaware (scanned and clean)

Issues:
1st: Winamp was closing out on me as soon as I started it up. Gave the "Windows is finding a solution" screen. This happened many times.

2. Winamp, when it did start up, would do the same as above if I clicked play, clicked on a song title, or if I added anything to the playlist.

3. When I had Winamp running, I tried to change the skin on it before it would turn off. When I tried to change it from Classic to Modern, it gave me a Guru Meditation that said:

Script failure. Press left mouse button to continue. Guru Medtation #0021.001402C3.8 Script Fatal Error scripts/configtarget.maki

So, any help at all would be awesome. The Guru Meditation threw me off. I thought that was an Amiga thing.

[Wildrose-Wally]

Guru Meditation come as something is wrong with the skin. What skin are you using?

[vagranted]

It happened when I was switching from the Classic skin to the Modern skin. As in Right-click > Skins...

[Wildrose-Wally]

Check a minute if the configtarget.maki is still in the scripts folder of your modern skin. If it is missing, it would bring up that Guru thingy.

[DJ Egg]

Windows Vista SP1 running as Admin

There's only one true Admin account on Vista, and that's the super hidden one:
http://www.computerperformance.co.uk...r_activate.htm

Please post your "List Of Plugins" (as explained in the FAQ, it's not just a list of plugins). A HijackThis log might also reveal something....
http://forums.winamp.com/showthread....d=161361#specs

Have you maybe manually deleted/disabled your paths.ini file?
By default, %ProgramFiles%\Winamp\paths.ini makes Winamp save its settings in %AppData%\Winamp.
If paths.ini doesn't exist then it will attempt to write to the Install Dir instead.
Vista doesn't allow writing to Program Files by default, and this includes so called Admin profiles.

Other than corruption of (or missing) files, I can't think of any other possible reasons for the problem - though the logs might reveal more....