Submitted by Anonymous (not verified) on Sun, 2018/02/25 - 20:14
Looks like the pool header was overwritten. Retrying with special pool would make sense.
Alternatively, dumping the memory before the problematic allocation might give an indication of the problem. E.g. `x 0xE15DAA00 L 32` in the example (2nd bugcheck parameter rounded down)