Hi,
I have been getting this too, and contrary to expectations, I suspect that it is *not* a hardware or memory problem, particularly because I've started getting the same problem, and at roughly the same time. I suspect that there is something in Windows 10 which is doing something nasty to memory, and it seems specifically to be shown up as corrupted pages in the FS cache. I found it tends to happen quite a lot when using readyboost / superfetch, which caches quite a lot of FS data in kernel memory.
My solution was to not use USB drive for readyboost (which you won't be doing), disable the superfetch service (My Computer > Manage > Services),, and wait for windows 10 to be a bit more stable. It looks like a H/W problem, but I suspect it isn't - there's probably some random driver somewhere that occasionally writes garbage over bits of kernel memory. You'll see it in filesystem caching components first because they have the biggest memory footprint.
Unfortunately I don't have a spare machine here otherwise I'd connect a kernel debugger. I'm looking at a full size dump file to see if I can see what the nature of the corruption is, but trawling through page tables in a pain in the backside.
MH.
.
