its already mentioned …
there was a conflict reported, starting ten years ago, where a specific network driver caused a possible conflict which results in a “none paged pool” mem-leak.
If users not see here strange high values, then I assume there is no need to try these
