Share via

I can't find memory diagnostic results in Event viewer.

Anonymous
2024-07-01T04:19:07+00:00

I ran the memory diagnostic. You are supposed to be able to find them in the event viewer. Is it the case that there is simply no output if the tool finds no errors? That does not seem very good, one would want to see "no errors found" or something like that.

I followed the documentation quite precisely:

After running the diagnostic the PC reboots. IN the event viewer i went to Windows logs/system. The i went to Action\Filter Current log. I checked all the boxes for Memory Diagnostics, including MemoryDisgnostics-Results, MemoryDiagnostics-Schedule, and MemoryDiagnostics-Task Handler.

The only events that were then found after the filter was applied were MemoryDiagnostics-Schedule events. Indeed the timestamp was precisely the time of the scan that i had scheduled. But, no "results". Did the scan complete?

Documentation says that there should be some MemoryDiagnostics-Results records, but there are none. Is there any way to actually retrieve the results of this memory diagnostic scan? (my PC is crashing and i'm trying to figure out why).

Thank you.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-06T11:24:49+00:00

    Hi Tom-Con.

    Thanks for your reply. The general filter I mentioned earlier refers to the find function, which doesn't strictly filter the search content. It looks like this

     

    In addition, we tested it on a test machine, and still the same thing happened as you, after executing the previous command, nothing happened.

    We determined that under normal circumstances, after entering that command, the system would find the relevant information in MemoryDiagnostics-Results and automatically record it in a text file, which would then be opened, just as the previous command opened the Event Viewer.

    Since we don't have any information in MemoryDiagnostics-Results in the Event Viewer as you do, it is indeed possible that there is no response after entering the command.

    So, please also check the information about the diagnostics in the blue Memory Diagnostics page, via the Status section, during the memory diagnostics process.

    Microsoft attaches great importance to user experience, you can submit your ideas and suggestions through the Feedback Hub, and the development team will regularly review submissions for ideas or fixes.

    Please share the feedback link here after submitting as it will allow others on the forum to vote for your submission, including me. More votes will lead to More votes will lead to more visibility and higher priority to the development team.

    Best regards,

    Zev - MSFT | Microsoft Community Support Specialist

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-07-03T06:03:39+00:00

    thank you for your reply. Here are some follow-up questions.

    #2-"you can also use the general filter". Can you explain how i access/use the general filter?

    #3. "Use the command line..." I typed those commands in the command window (as administrator). They just came back with a command prompt, no output. I show a screen shot. The first command opened the event viewer, so it was open in a different window when i typed the second command. Did i do this correctly, or do you need to explain further as to how i see a text format output?

    Thank you.

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-07-02T11:00:02+00:00

    Hi Tom-Con,

    Welcome to Microsoft Community.

    In your description, you don't see anything related to memory diagnostics in the event viewer after you try them.

    When you memory diagnostic, you will go to a blue memory diagnostic page and you can see the information about the diagnostic through the status section.

    Typically, the Windows Memory Diagnostic tool will indeed post an event in the Event Viewer under 'Windows Logs' > 'System' with a source of 'MemoryDiagnostics-Results' after completing a scan, regardless of whether it found errors or not. If you do not see any 'Results' entries, it might indicate that the test did not complete properly or there was an issue in logging the results.

    Here are a few steps you can take to troubleshoot this issue:

    1. Re-run the Memory Diagnostic: Sometimes, re-running the diagnostic can help if the previous attempt was somehow interrupted or did not complete. Restart your computer and during boot-up, press F8 to trigger the diagnostic tool again.
    2. Check Alternative Log Views:
      • Although you've already checked the System logs, sometimes entries can be misfiled. Check other sections in Event Viewer such as 'Application' and 'Setup'.
      • You can also use the general filter to search for terms like 'memory' instead of using the pre-set filters to see if any related logs appear elsewhere.
    3. Use Command Line to View Results:
      • You can also try to view the memory diagnostic results using the Command Prompt. Open Command Prompt as an administrator and type the following command:
      • eventvwr.msc
      • This opens Event Viewer directly. Then use:
      • wevtutil qe System "/q:*[System[(Provider/@Name='Microsoft-Windows-MemoryDiagnostics-Results')]]" /f:text
      • This command queries the System logs for entries from the Memory Diagnostics tool and displays them in a text format.
    4. System File Checker: Since your PC is crashing, it might be helpful to run the System File Checker tool to ensure all system files are intact and not corrupted.

    Run Command Prompt as administrator and type:

          DISM /Online /Cleanup-Image /ScanHealth

      DISM /Online /Cleanup-Image /CheckHealth

      DISM /Online /Cleanup-Image /RestoreHealth

      SFC /Scannow

        This will scan all protected system files, and replace corrupted files with a cached copy.

    If you continue experiencing problems and cannot isolate the issue through software diagnostics, it may be necessary to consider physical memory issues or other hardware tests. Tools like Memtest86 can be used to run more extensive tests on your RAM.

    If these steps do not help in retrieving the diagnostic results or resolving your PC's crashing issues, it may be advisable to seek professional technical support, possibly considering sending in your device for hardware diagnostics if it is still under warranty or taking it to a certified technician.

    Best regards,

    Zev - MSFT | Microsoft Community Support Specialist

    0 comments