Make that three machines. They're all of the same config. This identical hardware config runs fine under non-Xen. It also only occurs when a domain is being destroyed, so I wouldn't suspect this is a driver issue or memory corruption given the pattern. Xen is most suspect, in my mind.

Will you provide me with some debugging code that'll make these occurrences more useful in tracking down the problem the next time it triggers?