That's a fairly obscure scenario. Plus, if that allocation was within a service or driver then both Windows 7 hibernation and Windows 8 Fast Startup would have to page it to the Hibernation file.

"Interesting" was my main point; the non-paged pool comment was mostly kidding. Interesting in that it could indicate a "de-hibernation" process that's nothing like the "inverse of hibernation" one might naively think it should be: while hibernation must write 100% of allocated physical RAM to disk, "de-hibernation" need only restore non-paged pool plus whatever else is necessary to reinitialize the virtual memory subsystem (including whatever drivers are necessary to support it, of course). This done, the balance of the hibernation file could effectively be treated as a page file.