Doesn't look pirated.
Not W10
?recent updates? Maybe a new ntoskrnl.exe that someone forgot to enter into the symbol server?
I've had some issues with symbols recently - but nothing that was worth noting until this came up.
nt!_KPRCB would use one of the variants that form ntoskrnl - I can't recall all of them, but seem to recall that there were 4 that could be renamed to ntoskrnl (ntkrnlpa and ntkrnlmp were 2 of them) during installation depending on the processor involved.
Still no idea about the symbols. It's either a problem with the server, or with the file(s).
