Ok so after playing songs to and from work today, it reported 0000.51 Sigkill err and rebooted shortly ater startup... I noticed after it does this and reboots the visual goes away and the display changes to track after track info mode... once in this mode, the error seems to occur a lot less frequently if at all. So I pulled it out of the dash and did a cold reboot and the visual came back as it is the default but again produced the error fairly quickly. So I cold booted again and changed the visual to the simple o-scope from the previous 3d cube (not sure if that was the name) and it has not happened so far. I do wonder if some visuals use more memory and it could be possibly related to memory explaining why it seems to fail more frequently with complex visuals as opposed to simpler or none at all.
Just thinking out loud.
_________________________
12Gb MKII 080000516 Blue
20Gb MKII 010101303 Green
20Gb MKII 090001020 Green
30Gb MKII 10101980 Blue