Windows memory diagnostic tool - auto runs?

Page 1 of 4 123 ... LastLast

  1. Posts : 72
    windows10/2010
       #1

    Windows memory diagnostic tool - auto runs?


    I've been running win10 home for some 8 months now, currently updated to 20h2.
    My normal boot cycle involves a wait counter at the boot manager stage - to allow for safe starts or other things if I choose. If not, I can cut the timer short and/or when the timer runs out, windows boots.
    Today, started the PC and slipped away for a few seconds, expected the boot manager to be doing it's thing. Coming back, a windows memory diagnostic tool is running on a blue screen, bulky text: 2 passes. Status of test and publication of results after windows starts was part of the screen info. Let it run to the end, no errors reported on the test screen, then the boot manager came up; interesting that this test started without any manual intervention before that stage.
    After windows started there was nothing on the desktop wallpaper screen, but as soon as the 1st app was started, a notification appeared (briefly) - diagnostic showed no errors.

    So, is this memory diagnostic test
    - new?
    - done automatically on some random cycle?, or
    - is there a trigger event somewhere?
      My Computer


  2. Posts : 38,426
    windows 10 professional version 1607 build 14393.969 64 bit
       #2
      My Computer


  3. Posts : 72
    windows10/2010
    Thread Starter
       #3

    Attaching images (jpg files) to posts understood, done many times. But the rest - too cryptic, not understood.
    Clarify please.
      My Computer


  4. Posts : 38,426
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    See Ten Forum's webpage for log collector description and threads in the forum room.
      My Computer


  5. Posts : 72
    windows10/2010
    Thread Starter
       #5

    Well, IMHO, still to cryptic. But I poked around and eventually found what I think you wanted.

    V2 allegedly newer and better than VM, the latter surrounded in red by warnings. So I ran v2 only. The output file attached.
    Windows memory diagnostic tool - auto runs? Attached Files
      My Computer


  6. Posts : 38,426
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    DM allows a substantially longer look back period.
    V2 looked back 30 days.
    The logs were unremarkable.

    Windows Error Reporting (WER) had recorded a fault bucket on 03/28/2021 related to memory diagnostics.


    Please perform the following steps:


    1) Run:

    Tuneup_plus_log.bat Click here to go to the BSOD batch repository to download and run this batch file.


    2) The BIOS: Version/Date American Megatrends Inc. F6, 21/04/2015
    Identify the motherboard version
    Upgrade the BIOS to the most up to date non beta BIOS: F6 > F7
    GA-H97M-D3H (rev. 1.0) Overview | Motherboard - GIGABYTE U.S.A.
    GA-H97M-D3H (rev. 1.1) Support | Motherboard - GIGABYTE U.S.A.





    Code:
    Event[7725]:
      Log Name: System
      Source: Microsoft-Windows-MemoryDiagnostics-Results
      Date: 2021-03-28T15:57:01.6190000Z
      Event ID: 1101
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Hains-PC
      Description: 
    The Windows Memory Diagnostic tested the computer's memory and detected no errors
    
    Event[7726]:
      Log Name: System
      Source: Microsoft-Windows-MemoryDiagnostics-Results
      Date: 2021-03-28T15:57:01.6190000Z
      Event ID: 1201
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Hains-PC
      Description: 
    The Windows Memory Diagnostic tested the computer's memory and detected no errors


    Code:
    28/03/2021 5:57 AM    Windows Error Reporting    Fault bucket 373533579, type 5
    Event Name: MemDiagV1
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 4097
    P2: BootManager
    P3: Immediate
    P4: Pass
    P5: Standard
    P6: 0
    P7: 0
    P8: 330
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BC3.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_4097_d2b6c8cbe390788d2d8d2e78114cdea71623aef_00000000_8c40aab6-c196-4aeb-b8bc-dbd92961c761
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 8c40aab6-c196-4aeb-b8bc-dbd92961c761
    Report Status: 268435552
    Hashed bucket: 4d21575f292d399fc0b943438de776de
    Cab Guid: 0
    Code:
    Windows Error Reporting:
    +++ WER0 +++:
    Fault bucket 373533579, type 5
    Event Name: MemDiagV1
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 4097
    P2: BootManager
    P3: Immediate
    P4: Pass
    P5: Standard
    P6: 0
    P7: 0
    P8: 330
    P9: 
    P10: 
    
    
    +++ WER1 +++:
    Fault bucket , type 0
    Event Name: MemDiagV1
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 4097
    P2: BootManager
    P3: Immediate
    P4: Pass
    P5: Standard
    P6: 0
    P7: 0
    P8: 330
    P9: 
    P10:

    Code:
    Version=1
    EventType=MemDiagV1
    EventTime=132613846218023447
    Consent=1
    UploadTime=132613846336629887
    ReportStatus=268435552
    ReportIdentifier=8c40aab6-c196-4aeb-b8bc-dbd92961c761
    Wow64Host=34404
    OriginalFilename=RelPost.exe
    AppSessionGuid=00001754-0000-0220-a180-da2b9723d701
    TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!0000e78d010c9f068709f495a31d319568330a1781fc!RelPost.exe
    TargetAppVer=2009//01//12:17:55:46!3a13c!RelPost.exe
    BootId=4294967295
    TargetAsId=123
    IsFatal=4294967295
    EtwNonCollectReason=1
    Response.BucketId=4d21575f292d399fc0b943438de776de
    Response.BucketTable=5
    Response.LegacyBucketId=373533579
    Response.type=4
    Sig[0].Name=Range of memory size
    Sig[0].Value=4097
    Sig[1].Name=Launch type
    Sig[1].Value=BootManager
    Sig[2].Name=Schedule type
    Sig[2].Value=Immediate
    Sig[3].Name=Completion type
    Sig[3].Value=Pass
    Sig[4].Name=Test type
    Sig[4].Value=Standard
    Sig[5].Name=Failed tests
    Sig[5].Value=0
    Sig[6].Name=Number of bad pages
    Sig[6].Value=0
    Sig[7].Name=Test duration in seconds
    Sig[7].Value=330
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.19042.2.0.0.768.101
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=3081
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    OsInfo[0].Key=vermaj
    OsInfo[0].Value=10
    OsInfo[1].Key=vermin
    OsInfo[1].Value=0
    OsInfo[2].Key=verbld
    OsInfo[2].Value=19042
    OsInfo[3].Key=ubr
    OsInfo[3].Value=870
    OsInfo[4].Key=versp
    OsInfo[4].Value=0
    OsInfo[5].Key=arch
    OsInfo[5].Value=9
    OsInfo[6].Key=lcid
    OsInfo[6].Value=3081
    OsInfo[7].Key=geoid
    OsInfo[7].Value=12
    OsInfo[8].Key=sku
    OsInfo[8].Value=101
    OsInfo[9].Key=domain
    OsInfo[9].Value=0
    OsInfo[10].Key=prodsuite
    OsInfo[10].Value=768
    OsInfo[11].Key=ntprodtype
    OsInfo[11].Value=1
    OsInfo[12].Key=platid
    OsInfo[12].Value=10
    OsInfo[13].Key=sr
    OsInfo[13].Value=0
    OsInfo[14].Key=tmsi
    OsInfo[14].Value=221020383
    OsInfo[15].Key=osinsty
    OsInfo[15].Value=3
    OsInfo[16].Key=iever
    OsInfo[16].Value=11.789.19041.0-11.0.1000
    OsInfo[17].Key=portos
    OsInfo[17].Value=0
    OsInfo[18].Key=ram
    OsInfo[18].Value=8037
    OsInfo[19].Key=svolsz
    OsInfo[19].Value=223
    OsInfo[20].Key=wimbt
    OsInfo[20].Value=0
    OsInfo[21].Key=blddt
    OsInfo[21].Value=191206
    OsInfo[22].Key=bldtm
    OsInfo[22].Value=1406
    OsInfo[23].Key=bldbrch
    OsInfo[23].Value=vb_release
    OsInfo[24].Key=bldchk
    OsInfo[24].Value=0
    OsInfo[25].Key=wpvermaj
    OsInfo[25].Value=0
    OsInfo[26].Key=wpvermin
    OsInfo[26].Value=0
    OsInfo[27].Key=wpbuildmaj
    OsInfo[27].Value=0
    OsInfo[28].Key=wpbuildmin
    OsInfo[28].Value=0
    OsInfo[29].Key=osver
    OsInfo[29].Value=10.0.19041.870.amd64fre.vb_release.191206-1406
    OsInfo[30].Key=buildflightid
    OsInfo[30].Value=5AFFFB9B-FB87-4242-B66A-4ECEEB1CF75F.1
    OsInfo[31].Key=edition
    OsInfo[31].Value=Core
    OsInfo[32].Key=ring
    OsInfo[32].Value=Retail
    OsInfo[33].Key=expid
    OsInfo[34].Key=fconid
    OsInfo[35].Key=containerid
    OsInfo[36].Key=containertype
    OsInfo[37].Key=edu
    OsInfo[37].Value=0
    FriendlyEventName=Memory test results reported
    ConsentKey=MemDiagV1
    AppName=Windows Memory Diagnostic
    AppPath=C:\Windows\System32\RelPost.exe
    ReportDescription=The results of running the Windows Memory Diagnostic were submitted to Microsoft for analysis and product improvement
    ApplicationIdentity=00000000000000000000000000000000
    MetadataHash=-1187671916
      My Computer


  7. Posts : 72
    windows10/2010
    Thread Starter
       #7

    Several things . .
    I've downloaded the tune-up file, but the operating instructions are another story. They are part of a much larger file with many choices. According to the data in the download, at least 30 pages. And the page count in the browser image is nowhere near the actuals when trying to print the instructions out - which is seems reasonable to do, since generally, running diagnostics with no other software alive or backgrounded/minimized is generally advised. The tune up instructions in the browser download are just 2 pages, but a) the page division in the browser file don't match printable sections - more properly, the pages covering tune up printed are about re-boot with UEFI and further on, adjusting page numbers I wind up with pages about powercfg. So, I've just about given trying to find which 2 pages, lots of wasted paper so far, and I see no point in printing the whole file . . . .

    So as a strong suggestion - instructions for specific tools like tune up (and all the others in that collage) should be a stand alone file.
    As for now - which printable A4 pages in that tools collage actually apply to tune up???

    Regarding the BIOS . . my twitchy topic
    Updating BIOS in my experience - long ago and in a universe far far away - has been a process fraught with 'cannot go back' issues. If anything - anything at all - happens to the update, the PC is stuffed, unable to start to even look at it. So I have avoided BIOS updates: the one that came with the technology has worked fine without any issues for me..
    Of the versions available, and you cite the 2 involved, the motherboard is a rev1.1 item and that would apply.

    But for this unscheduled and uncommanded memory diagnostic run - which apparently has reported no errors, and you said the result was unremarkable - just how would updating the BIOS affect it??
      My Computer


  8. Posts : 38,426
    windows 10 professional version 1607 build 14393.969 64 bit
       #8

    1) Open administrative command prompt (ACP) and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
    12) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
    11) bcdedit /enum {badmemory}


    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    Use this link as needed when posting results:
    How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com



    This was displayed on the Gigabyte website for F7:
    Code:
    Better system compatibility for Intel® 5th Generation Core™ Processors
    The computer has Intel 3rd Generation Core so the upgrade is not required.
      My Computer


  9. Posts : 72
    windows10/2010
    Thread Starter
       #9

    I hope this has worked . .
    Microsoft Windows [Version 10.0.19042.870]
    (c) 2020 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc/scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19042.870

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844

    Image Version: 10.0.19042.870

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is SYSTEM64.

    Stage 1: Examining basic file system structure ...
    616448 file records processed.
    File verification completed.
    Phase duration (File record verification): 6.68 seconds.
    6207 large file records processed.
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 3.85 milliseconds.

    Stage 2: Examining file name linkage ...
    2309 reparse records processed.
    881592 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 11.86 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 3.72 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 1.37 milliseconds.
    2309 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 11.27 milliseconds.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 164.20 milliseconds.
    132573 data files processed.
    Phase duration (Data attribute verification): 0.83 milliseconds.
    CHKDSK is verifying Usn Journal...
    34799832 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 308.84 milliseconds.

    Windows has scanned the file system and found no problems.
    No further action is required.

    233845628 KB total disk space.
    71043004 KB in 388251 files.
    174368 KB in 132574 indexes.
    0 KB in bad sectors.
    750620 KB in use by the system.
    65536 KB occupied by the log file.
    161877636 KB available on disk.

    4096 bytes in each allocation unit.
    58461407 total allocation units on disk.
    40469409 allocation units available on disk.
    Total duration: 22.78 seconds (22785 ms).

    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\HAINS-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\HAINS-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\WINDOWS\system32>wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
    Updating property(s) of '\\HAINS-PC\ROOT\CIMV2:Win32_ComputerSystem.Name="HAINS-PC"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE


    C:\WINDOWS\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\WINDOWS\system32>

    Please advise
      My Computer

  10. Matthew Wai's Avatar
    Posts : 5,113
    Windows 10 Home 20H2
       #10

    Davidk said:
    I've downloaded the tune-up file, but the operating instructions are another story. They are part of a much larger file with many choices. According to the data in the download, at least 30 pages.
    Do you mean you have downloaded the following webpage and the download contains at least 30 pages?

    Batch files for use in BSOD debugging
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:53.
Find Us




Windows 10 Forums