According to your cmd-prompt, you seem to be using local-kernel debugging?
For windbg falls back to exported symbols for ntkrnlmp.exe, I assume also ntkrnlmp.pdb is not loaded.
When doing a !sym noisy .reload /f nt
does windbg look for image-file?
Then probably it is a matter of paged-out memory.
Also you may try for more info !lmi ntkrnlmp.exe !lmi ntdll.dll (though for this one I would expect 'not found' according to your error message)
Sometimes during local-kernel-debugging (which I do not use very often) I have to switch to a user process to load symbols for ntdll.dll
PROCESS 84fcf9a8 SessionId: 1 Cid: 0c5c Peb: 7ffd9000 ParentCid: 060c
DirBase: 7c2beac0 ObjectTable: 94401af8 HandleCount: 76.
lkd> .process /r /p 84fcf9a8
Implicit process is now 84fcf9a8
Loading User Symbols
DBGHELP: c:\windows\symbols\dll\ntdll.pdb - file not found
DBGHELP: c:\windows\symbols\dll\dll\ntdll.pdb - file not found
DBGHELP: c:\windows\symbols\dll\symbols\dll\ntdll.pdb - file not found
DBGHELP: ntdll - public symbols
Besides, have you already tried Sysinternals livekd, though it seems to be a little bit more restricted using a static snapshot.