I try to find a memory corruption of my driver. What I already did:
1. Verifier with pool checking and all other flags
2. checked build xp sp1
3. Analyzing the pool with !pool and !poolval
The corruption error occurs in a completely unrelated part of the OS.
It seems that the command !poolval does not work correctly. It displays
an invalid page for ALL allocations (for the first allocation of my
driver as well). Like this:
kd> !poolval 83856f68
Pool page 83856f68 region is Special pool
Validating Pool headers for pool page: 83856f68
Pool page [ 83856000 ] is INVALID.
Analyzing linked list...
[ 83856000 ]: invalid previous size [ 0x98 ] should be [ 0x0 ]
[ 83856000 --> 83856010 (size = 0x10 bytes)]: Corrupt region
Scanning for single bit errors...
None found
Is there a debugger command for analyzing the pool allocations of the
hole system?
Any ideas?
Marc