You're right: It's only recent hijacks that show the error. The error isn't caused by hijack, it's just reporting them now.

I agree that locked up player software sucks because of that speaker-pop. Sometimes, even when the player software is locked up, you can still make the Hijack menu appear and select the "reboot machine" option to get the player to reboot nicely without needing to pull it and make the pop happen.

So. Back to the problem at hand: sigbus and segfault errors. These can be caused by:

- Running alpha software. Your best bet is to stick with 2.0 final or 2.0 beta 13.

- A specific bad MP3 file that screws up the decoder.

- Disk drive, IDE header, or disk cable trouble.

- RAM trouble.

- Other hardware trouble.

I'm guessing that the fact you're specifically getting a "sigbus" error indicates a certain kind of hardware trouble that others might be able to diagnose. But first give us a full boot log and a RAM test log. Instructions on how to do this are in the FAQ, search for Hyperterminal.