The reason racoon_boy found it referencing so many different things is that the error is the result of something trying to read or write to an incorrect address (this can be caused by bad RAM or faulty connections but is usually the result of non-MS products being bitched at by the OS)
I'm going to guess that the stop BSD is referencing the stop code: 0xA and the third error parameter is 0x0. If so, it's almost certainly due to one of the sound drivers trying to access the wrong address; that happens a lot with properitary drivers on XP. Crazy as it sounds, it's often a successful workaround to swap a couple of DIMMs around, I don't know why it works but it often does. Try that one first.
Assuming that's no use you might want to set XP up to do full kernel dumps and find the driver responsible.
no subject
I'm going to guess that the stop BSD is referencing the stop code: 0xA and the third error parameter is 0x0. If so, it's almost certainly due to one of the sound drivers trying to access the wrong address; that happens a lot with properitary drivers on XP. Crazy as it sounds, it's often a successful workaround to swap a couple of DIMMs around, I don't know why it works but it often does. Try that one first.
Assuming that's no use you might want to set XP up to do full kernel dumps and find the driver responsible.