I have asked Kyhi about false positives with sfc /scannow in windows 10, because there are false positives in windows 8 and I'm unsure if the same files are false positive in windows 10.
The link he posted points to a tool he wrote that helps with the sfc and dism commands.
I have run the memtest for about 14 hours with the default settings, and there appears to be no errors.
On the other hand, sfc /scannow still cannot fix all the errors, even though I restarted at least 5 times, and some of them in safe mode too.
If DISM is meant to be replacing files from a system image, maybe I should just reinstall Win7Pro and then try to upgrade from there?
DISM is meant to fix problems when sfc can't.
DISM in windows 7 can only scanhealth, not restorehealth..
I had another go at upgrading to Windows 10 from my current system in case something was fixed somewhere, but no.. the same BSOD and error code again....
Any other ideas?
Check for any drivers that could cause trouble:
WarningPlease make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please read and run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
NoteYour system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
So far, it's ok. How long should I leave it running? Can I shut down my computer later tonight? Or leave it in standby mode?
You should run driver verifier for max 48 hours at a time, or until you get a bluescreen, which comes first.
You can leave the pc while driver verifier is running, but do not shut your pc down!
It's still ok..
I've decided to do a clean install, so thanks for your help anyway.
If driver verifier hasn't crashed then it is most likely a hardware problem with windows 10.
Before a clean install, would you mind to do a couple of hardware related tests?