FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST

Page 4 of 6 FirstFirst ... 23456 LastLast

  1. Posts : 101
    Microsoft Windows 10 Education 64-bit 14393 Multiprocessor Free
    Thread Starter
       #31

    In device manager its rt640x64.sys (see attached) picture. Clicking update driver couldn't find an update, but I followed that link in your reply and updated manually to the newest driver.

    Attachment 146481
      My Computers


  2. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #32

    How are things today?
      My Computer


  3. Posts : 101
    Microsoft Windows 10 Education 64-bit 14393 Multiprocessor Free
    Thread Starter
       #33

    Hasn't BSOD since I updated that network driver. Hopefully that is the correct fix and thanks for your help. Shame it took so long because I was using only some of the settings in verifier.
      My Computers


  4. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #34

    Your welcome.

    I'm glad we got the bsod fixed.

    Which drive had the clean install (deleting partitions, formatting)?

    Which drive is only used for storage?

    Which drive had the posting of this command: fsutil dirty set %systemdrive%

    Let's double check a few things, continue monitoring, and have you send an updated zip in a few days.

    Perform windows updates. If there are any failed kb# or error code post it in the thread.

    Open administrative command prompt on each drive and type or copy and paste these commands:
    1) fsutil dirty query c:
    2) sfc /scannow
    3) dism /online /cleanup-image /checkhealth
    4) dism /online /cleanup-image /scanhealth
    5) dism /online /cleanup-image /restorehealth
    6) 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


    On the HD if it is not marked dirty run chkdsk /x /f /r overnight and post the results.
      My Computer


  5. Posts : 101
    Microsoft Windows 10 Education 64-bit 14393 Multiprocessor Free
    Thread Starter
       #35

    Here is everything

    C: is my SSD which has my OS on it
    D: is a HDD used for storage

    I did the clean install on C and never formatted D

    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.


    C:\Windows\system32>fsutil dirty query c:
    Volume - c: is NOT Dirty


    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 /checkhealth


    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0


    Image Version: 10.0.15063.0


    No component store corruption detected.
    The operation completed successfully.


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


    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0


    Image Version: 10.0.15063.0


    [==========================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.15063.0


    Image Version: 10.0.15063.0


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


    C:\Windows\system32>chkdsk D: /x/f/r
    The type of the file system is NTFS.
    Volume dismounted. All opened handles to this volume are now invalid.
    Volume label is Second Disk.


    Stage 1: Examining basic file system structure ...
    805120 file records processed.
    File verification completed.
    823 large file records processed.
    0 bad file records processed.


    Stage 2: Examining file name linkage ...
    812730 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.


    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    3806 data files processed.
    CHKDSK is verifying Usn Journal...
    35993680 USN bytes processed.
    Usn Journal verification completed.


    Stage 4: Looking for bad clusters in user file data ...
    805104 files processed.
    File data verification completed.


    Stage 5: Looking for bad, free clusters ...
    392273959 free clusters processed.
    Free space verification is complete.


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


    2861458 MB total disk space.
    1359793364 KB in 575626 files.
    248768 KB in 3807 indexes.
    0 KB in bad sectors.
    996047 KB in use by the system.
    65536 KB occupied by the log file.
    1569095836 KB available on disk.


    4096 bytes in each allocation unit.
    732533503 total allocation units on disk.
    392273959 allocation units available on disk.


    C:\Windows\system32>
      My Computers


  6. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #36

    Nice, That is much improved.
    Run chkdsk /x /f on the SSD drive overnight and report results into the thread.
    It everything is fine on the chkdsk plan to make a new restore point and make a fresh backup image with Macrium.
      My Computer


  7. Posts : 101
    Microsoft Windows 10 Education 64-bit 14393 Multiprocessor Free
    Thread Starter
       #37

    Log Name: Application
    Source: Microsoft-Windows-Wininit
    Date: 8/3/2017 12:52:14 PM
    Event ID: 1001
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-2UMU17L
    Description:




    Checking file system on C:
    The type of the file system is NTFS.




    A disk check has been scheduled.
    Windows will now check the disk.


    Stage 1: Examining basic file system structure ...
    667392 file records processed.


    File verification completed.
    7584 large file records processed.


    0 bad file records processed.




    Stage 2: Examining file name linkage ...
    796284 index entries processed.


    Index verification completed.
    0 unindexed files scanned.


    0 unindexed files recovered to lost and found.




    Stage 3: Examining security descriptors ...
    Cleaning up 56 unused index entries from index $SII of file 0x9.
    Cleaning up 56 unused index entries from index $SDH of file 0x9.
    Cleaning up 56 unused security descriptors.
    Security descriptor verification completed.
    64447 data files processed.


    CHKDSK is verifying Usn Journal...
    40106752 USN bytes processed.


    Usn Journal verification completed.


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


    233916415 KB total disk space.
    63626988 KB in 573791 files.
    273604 KB in 64448 indexes.
    0 KB in bad sectors.
    782867 KB in use by the system.
    65536 KB occupied by the log file.
    169232956 KB available on disk.


    4096 bytes in each allocation unit.
    58479103 total allocation units on disk.
    42308239 allocation units available on disk.


    Internal Info:
    00 2f 0a 00 f8 bc 09 00 fa f4 11 00 00 00 00 00 ./..............
    b4 00 00 00 5f 00 00 00 00 00 00 00 00 00 00 00 ...._...........


    Windows has finished checking your disk.
    Please wait while your computer restarts.


    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-08-03T17:52:14.170113800Z" />
    <EventRecordID>6770</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-2UMU17L</Computer>
    <Security />
    </System>
    <EventData>
    <Data>


    Checking file system on C:
    The type of the file system is NTFS.




    A disk check has been scheduled.
    Windows will now check the disk.


    Stage 1: Examining basic file system structure ...
    667392 file records processed.


    File verification completed.
    7584 large file records processed.


    0 bad file records processed.




    Stage 2: Examining file name linkage ...
    796284 index entries processed.


    Index verification completed.
    0 unindexed files scanned.


    0 unindexed files recovered to lost and found.




    Stage 3: Examining security descriptors ...
    Cleaning up 56 unused index entries from index $SII of file 0x9.
    Cleaning up 56 unused index entries from index $SDH of file 0x9.
    Cleaning up 56 unused security descriptors.
    Security descriptor verification completed.
    64447 data files processed.


    CHKDSK is verifying Usn Journal...
    40106752 USN bytes processed.


    Usn Journal verification completed.


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


    233916415 KB total disk space.
    63626988 KB in 573791 files.
    273604 KB in 64448 indexes.
    0 KB in bad sectors.
    782867 KB in use by the system.
    65536 KB occupied by the log file.
    169232956 KB available on disk.


    4096 bytes in each allocation unit.
    58479103 total allocation units on disk.
    42308239 allocation units available on disk.


    Internal Info:
    00 2f 0a 00 f8 bc 09 00 fa f4 11 00 00 00 00 00 ./..............
    b4 00 00 00 5f 00 00 00 00 00 00 00 00 00 00 00 ...._...........


    Windows has finished checking your disk.
    Please wait while your computer restarts.
    </Data>
    </EventData>
    </Event>
      My Computers


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

    Nice progress.
    How long has windows driver verifier been run since the last bsod?
    If it has been 36 hours or more windows driver verifier can be turned off.
    Let's have you use the computer (typical use) for the rest of the week.
    If there are no more bsod then we will have completed the troubleshooting and preventative maintenance.

    Please make a brand new restore point.
    And please make a backup image of the drive using Macrium.
    Place the backup image on another drive and update it once per month or as needed.
    Backup files to another drive or to the cloud.
    You will now have multiple layers of backup should anything unexpected happen to the drive.
      My Computer


  9. Posts : 101
    Microsoft Windows 10 Education 64-bit 14393 Multiprocessor Free
    Thread Starter
       #39

    Woops guess I spoke too soon. Got another one today which showed PFN_List_Corrupt on the BSOD. Uploaded the dump.
      My Computers


  10. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #40

    There was no definitive misbehaving driver in the latest bsod mini dump file.

    Code:
    BugCheck 4E, {2, 3f1a99, 41efff, 1}Probably caused by : memory_corruption
    Please restart windows driver verifier with these customized settings and update the zip when there are new bsod:

    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    BSOD - Posting Instructions - Windows 10 Forums
      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 18:27.
Find Us




Windows 10 Forums