nadriel

Oh, regarding finding the driver, it shouldn't be that hard, the stop code ought to have four parameters at the end, the first is the address that couldn't be referenced, the second in the request level, the third is read/write (0/1) and the fourth is the referencing address. I haven't looked at a kernel dump recently but I seem to recall the loaded drivers being listed, along with the memory they've allocated. Comparing that to the last parameter of the stop code should tell you which driver is going tits up.