Hi All!
I’m debugging a problem with kernel-mode memory corruption on the system running Windows 10 x64 Build 17763.107. I’m using latest Windbg version 10.0.17763.132 AMD64.
I’m executing under Verifier and I’m using Special pool with granularity 0x20
Whenever I’m trying to use !pool command, I’m receiving a message “Failed to read heap key”. For example:
3: kd> !vm 0x20
************ NO PAGING FILE *********************
Physical Memory: 1048284 ( 4193136 Kb)
...
NonPagedPool Usage: 0 ( 0 Kb)
NonPagedPoolNx Usage: 1425 ( 5700 Kb)
NonPagedPool Max: 4294967296 (17179869184 Kb)
PagedPool 0: 0 ( 0 Kb)
PagedPool 1: 0 ( 0 Kb)
PagedPool 2: 0 ( 0 Kb)
PagedPool 3: 0 ( 0 Kb)
PagedPool 4: 0 ( 0 Kb)
PagedPool Usage: 0 ( 0 Kb)
PagedPool Maximum: 4294967296 (17179869184 Kb)
...
System Region Base Address NumberOfBytes
UltraZero : ffff828000000000 100000000000
...
PagedPool : ffffc30000000000 100000000000
...
SpecialPoolPaged : ffffde8000000000 8000000000
NonPagedPool : ffffdf0000000000 100000000000
...
SpecialPoolNonPaged : fffffd0000000000 8000000000
3: kd> !pool fffffd0000000000
Failed to read heap key
3: kd> !pool ffffdf0000000000
Failed to read heap key
Do I miss something? How else can I enforce verification of the Non-Paged (special) pool at the WinDbg break?
Thank you in advance,
Alex