First scannow:
Code:Windows Resource Protection found corrupt files and successfully repaired them.
Second scannow:
Code:Windows Resource Protection did not find any integrity violations.
The printable version has only one page rather than 30 pages.
The one who has advised the OP to print it out has to provide papers.
In the first post three questions were asked.
The tool is not new it has been around for a long time probably since Windows XP.So, is this memory diagnostic test
- new?
- done automatically on some random cycle?, or
- is there a trigger event somewhere?
If Windows detects a possible memory related problem it will automatically initiate the tool to run the next time you restart the PC. You can also start it manually - see this tutorial: Run Windows Memory Diagnostics Tool in Windows 10 | Tutorials (tenforums.com)
I am not sure what precisely triggers the automatic use of the tool - but it is probably a detected memory error that Windows was able to recover from rather than having to trigger a blue screen of death crash.
As the test did not find any errors I would suggest that you have nothing to worry about but if it keeps happening it could be a sign your RAM is failing.
There is another test you can run if you are concerned:
Diagnostic Test
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
Note
MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
see attached image, marked up to show page count.
Each page has a number on it at the top, took that for a page number. But those numbers did no0t match the actual printed page ranges - wasted a lot of paper.
21 sheets of paper are needed at my end. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬⇓
Hi all,
Thanks for the help. I take it (from the last posts by zbook and Philc43) that things are normal (again, even if they were briefly "must check this"). In so far as the RAM is concerned - that might be the actual processor RAM (2xCrucial 4gb PC12800 DDR3 sticks) that is as old as the m/b, ie nearly 5 years; or the C drive, which is a 250gb SSD (for C only, used 61.6gb, 161gb free), which is essentially RAM with a Sata interface on it, that is 26 months old (installed Jan 2019). Would that memory test report which one, or would just the test running indicate that?
Regarding the test log doco - comments made seem to have missed my point: I was quite happy to print the section pages involved, eg pages 16-18, I just could not identify which pages they were in the larger document that addressed a lot of other conditions: whenever I tried printing a page range - however I got that, either from the print page section or the numbers on the browser article - what was printed was the wrong data. The only way to get the log data accurately was to print the whole thing and throw away the parts not relevant - what a waste of paper! And thus my point about making those sort of instructions "standalone" - not only smaller, and thus easier to amend as needed, but also subject to the point and nothing else.
Zbook's extraction from the instructions that he posted after I made that remark were clear enough when read carefully.
Quote
