Reading driver verifier crash dump

Page 2 of 2 FirstFirst 12

  1. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit
       #11

    Windows reported malfunctioning RAM.
    Please check the warranty status for the RAM.

    1) Open administrative command prompt 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) bcdedit /enum {badmemory}

    10) 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

    11) Make sure that there is no over clocking while troubleshooting.

    12) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan


    13) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    14) Run Memtest86 version 8.2 (or newer version if available) for four passes.
    Repeat the test so that eight passes are performed.
    MemTest86 - Official Site of the x86 Memory Testing Tool
    Use a camera or smart phone camera to take pictures and post images into the thread.
    In case there are any problems uploading images use share links (one drive, drop box, or google drive)
    Memtest86 has a feature to produce a text report.
    Please post this in addition to the images.
      My Computer


  2. Posts : 6
    Windows 10 Enterprise
    Thread Starter
       #12

    Here is the latest logs / dumps with the verifier settings that you recommended enabled. System crashed during use this time. Redisabled driver verifier for now. All I keep seeing is mention of ntoskrnl.exe in the minidump. Not sure what that entails.

    Attachment 252994

    - - - Updated - - -

    zbook said:
    Windows reported malfunctioning RAM.
    Please check the warranty status for the RAM.

    ....

    Just saw this post, thank you. I will run all the test and post back with results ASAP.

    - - - Updated - - -

    here is everything so far, will update with the memtest results after I run it overnight.

    Code:
    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>dism /online /cleanup-image /scanhealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1
    
    Image Version: 10.0.18362.449
    
    [==========================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.18362.1
    
    Image Version: 10.0.18362.449
    
    [==========================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.
    
    Stage 1: Examining basic file system structure ...
      864768 file records processed.
    File verification completed.
      7312 large file records processed.
      0 bad file records processed.
    
    Stage 2: Examining file name linkage ...
      1297 reparse records processed.
      1140518 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
      1297 reparse records processed.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      137876 data files processed.
    CHKDSK is verifying Usn Journal...
      41323936 USN bytes processed.
    Usn Journal verification completed.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
     487725055 KB total disk space.
     197366960 KB in 675719 files.
        388548 KB in 137877 indexes.
             0 KB in bad sectors.
        990819 KB in use by the system.
         65536 KB occupied by the log file.
     288978728 KB available on disk.
    
          4096 bytes in each allocation unit.
     121931263 total allocation units on disk.
      72244682 allocation units available on disk.
    
    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\RAIDEN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Enterprise|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\RAIDEN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Enterprise|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.
    
    C:\Windows\system32>bcdedit /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
    badmemorylist           0x25b759
    
    C:\Windows\system32>
    Attachment 253161
    Attachment 253160
      My Computer


  3. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit
       #13

    When available please post images for ST2000 health and benchmark results.



    Code:
    C:\Windows\system32>bcdedit /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
    badmemorylist           0x25b759


    Windows has blocked the use of the above portion of the bad RAM.





    Remove all RAM modules.
    Re-seat one module and check computer stability / instability for several days.
    If there are BSOD change RAM modules and test in the same DIMM.
    Once a good RAM module is identified you can use the single module while shopping for RAM replacement.

    Run the crucial scanner to see replacement options.
    Crucial System Scanner | Crucial.com

    Make sure replacement RAM is on the motherboard's manufacturer Qualified Vendor List (QVL) and that there are matching SKU.
      My Computer


  4. Posts : 6
    Windows 10 Enterprise
    Thread Starter
       #14

    Here are the other two images:
    Ill try what you suggested, thank all of you for the help so far.


    Attachment 253170Attachment 253171
      My Computer


  5. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit
       #15

    In the above image there is a scroll bar on the right.
    Please post the images of the missing results.

    Also post for CT500.
      My Computer


 

  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 07:39.
Find Us




Windows 10 Forums