any update on the matter? had you another crash? is your hadware stable, any particular problems? i must confess to have seen a similar crash on one of our university machines. it was running 2.4.25 and this bug happened once. machine shouldn't have been under mem pressure, but had a quite long uptime. i guess it's a feature of the 2.4 vm. -- maks