Sfc /scannow issue

[Justworkdamnit]

I just did a clean reinstall of windows 10 pro (because originally i would get BSOD randomly like 3x a day). first thing i do is sfc /scannow. No issues. 6 hours later after I download things such as: office, warcraft, drivers, Kodi, etc, i scan again and it says that there are corrupt files and that it successfully repaired them, but after each scan its telling me the exact same thing. It's kinda driving me crazy and if anyone could offer insight Id much appreciate it. The cbs log is telling me
"2017-06-10 22:00:53, Info CSI 0000aeff Error - Overlap: Duplicate ownership for directory \??\C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys in component Microsoft-Windows-Crypto-keys, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-10 22:00:53, Info CSI 0000af00 Error - Overlap: Duplicate ownership for directory \??\C:\ProgramData\Microsoft\Crypto\Keys in component Microsoft-Windows-Crypto-keys, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-10 22:00:53, Info CSI 0000af01 Error - Overlap: Duplicate ownership for directory \??\C:\ProgramData\Microsoft\Crypto\DSS\MachineKeys in component Microsoft-Windows-Crypto-keys, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-10 22:00:53, Info CSI 0000af02 Warning - Overlap: 3 directory duplicate ownerships detected.
2017-06-10 22:00:53, Info CSI 0000af03@2017/6/11:05:00:53.982 Primitive installers committed for repair
2017-06-10 22:00:53, Info CSI 0000af04@2017/6/11:05:00:53.989 Primitive installers committed for repair
2017-06-10 22:00:53, Info CSI 0000af05 [DIRSD OWNER WARNING] Directory [l:31]'\??\C:\Windows\System32\catroot' is not owned but specifies SDDL in component Microsoft-Windows-CryptBase, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-06-10 22:00:53, Info CSI 0000af06 [DIRSD OWNER WARNING] Directory [l:70]'\??\C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}' is not owned but specifies SDDL in component Microsoft-Windows-CryptBase, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}"

I'm also getting a BSOD error "PAGE_FAULT_IN_NONPAGED_AREA" whenver i run Norton

 

[Colif]

PAGE_FAULT_IN_NONPAGED_AREA is normally a driver error, can sometimes be ram but I would lean towards the driver
can you remove norton until we work out cause? MY guess would be its the lan driver causing it,

can you upload your memory.,dmp file to onedrive and share the link here? (it should be in the root of C drive)

 

[Karadjgne]

When you did the clean reinstall of windows, did you also run the full updates too? Or did you finish windows, then add everything else?

 

[Justworkdamnit]

PAGE_FAULT_IN_NONPAGED_AREA is normally a driver error, can sometimes be ram but I would lean towards the driver
can you remove norton until we work out cause? MY guess would be its the lan driver causing it,

can you upload your memory.,dmp file to onedrive and share the link here? (it should be in the root of C drive)

I guess the problem was that norton didnt install as the most updated version. and im pretty new to this so could you teach me the steps to get my memory dmp file

 

[Justworkdamnit]

When you did the clean reinstall of windows, did you also run the full updates too? Or did you finish windows, then add everything else?

no, installed everything first but nothing came up. system restored it to the point where there were no problems and i kept most of the downloads, then i redownloaded everything that was removed. Did a rescan and it was fine up until like 2 hours later where it started saying things were corrupt again(now instead of constantly telling me its corrupt and was fixed, everytime i sfc scan, its telling me its corrupt and somethings cant be fixed.

BTW, this hasnt affected any of my use of windows so far. Everything pretty much runs fine, I just dont want to be running on a faulty OS that can screw me if i dont fix it now.

 

[Karadjgne]

When it comes to win10 you are fighting several different scenarios, least of which is a new OS. There's regular win10, it's a little older and does things 1 way. That got updated, and updated again to the Creator edition, which has a tendency to do things slightly different. Both Nvidia and Symantec (just to name 2) got caught up in that with drivers. If you tried using the latest edition drivers, on an older version of win10, you got errors as the drivers were trying to access stuff that wasn't there yet. Using old drivers on new Creators had the same affect, the drivers trying to access something that was no longer there. Only answer was to match up the software with the OS, use older drivers with older version OS, or update both. Unfortunately, because Creators is just released, you'll find some software that previously worked perfectly, now has some stability bugs, or runs slower, or just doesn't run at all. So my only suggestion is to make sure, if you have the Creators win10 OS is to make sure that everything you have, from mobo drivers and software, to actual app software is at the latest revision/update, and not just a disc/download copy from a while back that never needed fixing.

 

[Colif]

firstly, sfc scans on a fresh install can show corruption. I don't know why but its a common thing.

You can try this to repair it
open command prompt (admin)
copy/paste this into window (if you type it, spacing needs to match):
DISM /Online /Cleanup-Image /RestoreHealth and press enter

DISM cleans the image file which is what SFC uses to compare and fix system files, once its complete, re run SFC /scannow and see if you get same results. Restart PC after doing both scans.

 

[axe0axe0]

firstly, sfc scans on a fresh install can show corruption. I don't know why but its a common thing.

That is usually because some updates haven't been released, or not yet installed, that update file hashes SFC uses to check whether a file is corrupted or not.

SFC compares the file hashes against the hashes present in hives, which I believe is why some Windows Update analysts request hives, to make sure that the files they replace the corrupted with are the right onces.

 

[Justworkdamnit]

firstly, sfc scans on a fresh install can show corruption. I don't know why but its a common thing.

You can try this to repair it
open command prompt (admin)
copy/paste this into window (if you type it, spacing needs to match):
DISM /Online /Cleanup-Image /RestoreHealth and press enter

DISM cleans the image file which is what SFC uses to compare and fix system files, once its complete, re run SFC /scannow and see if you get same results. Restart PC after doing both scans.

Idk why but at first DISM was saying that i needed to change the source or something, now its giving me the restore completed successfully and SFC is now saying everything is good.
On a side note, after updating, sfc says no integrity violations but 30 mins later corruption again. Restarted the computer, no violations for awhile and then corruption again but the same thing where it keeps saying files its been repaired every time i scan until i did the DISM like you said.

Also mdsched.exe is telling me there are hardware problems, but my ram doesnt seem affected at all? cpu z is telling me my ram is running where its supposed to be. I did change it from default 1333mhz to 2400mhz so idk if that could be it? theyre corsair vengeance 8gb 2400mhz sticks.

Computer specs: msi z97MB, i7 4790k, corsair vengeance 2x 8gb 2400mhz, MSI r9 390, samsung evo ssd 250, WD 1tb, then a bunch of fans

starting to feel like windows loves dicking people around.

 

[Justworkdamnit]

When it comes to win10 you are fighting several different scenarios, least of which is a new OS. There's regular win10, it's a little older and does things 1 way. That got updated, and updated again to the Creator edition, which has a tendency to do things slightly different. Both Nvidia and Symantec (just to name 2) got caught up in that with drivers. If you tried using the latest edition drivers, on an older version of win10, you got errors as the drivers were trying to access stuff that wasn't there yet. Using old drivers on new Creators had the same affect, the drivers trying to access something that was no longer there. Only answer was to match up the software with the OS, use older drivers with older version OS, or update both. Unfortunately, because Creators is just released, you'll find some software that previously worked perfectly, now has some stability bugs, or runs slower, or just doesn't run at all. So my only suggestion is to make sure, if you have the Creators win10 OS is to make sure that everything you have, from mobo drivers and software, to actual app software is at the latest revision/update, and not just a disc/download copy from a while back that never needed fixing.

How do i know i have creators version? it seems like corrupt files is sometimes not a big deal?

 

[axe0axe0]

Run winver in search, if it says "Version 1703" you have Creators version.

Also mdsched.exe is telling me there are hardware problems, but my ram doesnt seem affected at all? cpu z is telling me my ram is running where its supposed to be. I did change it from default 1333mhz to 2400mhz so idk if that could be it? theyre corsair vengence 8gb 2400mhz sticks.

When memtest detects errors it means a small portion on a stick could be bad, nothing else.
Windows and other utilities will still detect the RAM like normally since it is only a small portion.

 

[Karadjgne]

Only time you'll ever have to worry about ram issues is when you get a bluescreen telling you that there is an error in the first 64Kb.