Windows 10: FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST

Discus and support FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST in Windows 10 BSOD Crashes and Debugging to solve the problem; Uninstalled that program and the computer sat for 2 days with driver verifier running. I remoted into it last night and started google drive and then... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by jag213, May 15, 2017.

  1. jag213 Win User

    FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST


    Uninstalled that program and the computer sat for 2 days with driver verifier running. I remoted into it last night and started google drive and then the computer BSOD (don't know if drive caused it). Since I was out of office I didn't see the error on the screen and when I got in this morning the computer screen was blank, so I just rebooted. Whocrashed says a microsoft driver, but not which. Attached the dumps.
     
    jag213, Jul 30, 2017
    #31
  2. zbook New Member

    There was 1 bsod mini dump file debugged and it displayed the misbehaving driver: rt640x64.sys (Realtek RT640 NT Driver)
    The reference table that we use has different information about this driver than what is displayed about the driver within the msinfo32. The reference table displays: Realtek NICDRV 8169 PCIe GBE Family Controller driver
    So when you open device manager make sure that you click properties then driver details and confirm that it is the Realtek driver rt640x64.sys
    Then report into the thread the name used for this driver on device manager.
    When you see this driver within device manager > right click properties > driver > update driver



    Code: BugCheck C4, {9200d, fffff806264705f0, ffff9d0396c44d80, ffff9d0396c44df8}*** WARNING: Unable to verify timestamp for rt640x64.sys*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys Probably caused by : rt640x64.sys ( rt640x64+1b66a )[/quote] rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver
    http://www.realtek.com.tw/downloads/...&GetDown=false


    Code: rt640x64 Realtek RT640 NT Drive Realtek RT640 NT Drive Kernel Manual Running OK TRUE FALSE 4,096 897,024 0 10/7/2016 4:24:19 AM C:\Windows\system32\drivers\rt640x64.sys 8,192[/quote]
     
    zbook, Jul 30, 2017
    #32
  3. jag213 Win User
    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.


    FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST [​IMG]
     
    jag213, Jul 30, 2017
    #33
  4. jag213 Win User

    FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST

    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.
     
    jag213, Aug 1, 2017
    #34
  5. zbook New Member
    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.
     
    zbook, Aug 1, 2017
    #35
  6. jag213 Win User
    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>
     
    jag213, Aug 1, 2017
    #36
  7. zbook New Member
    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.
     
    zbook, Aug 1, 2017
    #37
  8. jag213 Win User

    FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST

    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>
     
    jag213, Aug 2, 2017
    #38
  9. zbook New Member
    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.
     
    zbook, Aug 3, 2017
    #39
  10. jag213 Win User
    Woops guess I spoke too soon. Got another one today which showed PFN_List_Corrupt on the BSOD. Uploaded the dump.
     
    jag213, Aug 6, 2017
    #40
  11. zbook New Member
    zbook, Aug 7, 2017
    #41
  12. jag213 Win User
    So I realize this is kinda a dead thread due to my absence. However, I've been still getting BSOD every now and then but I've been trying to troubleshoot on my own. Driver verifier showed that "Intel Smart Connect" (which shouldn't even be installed in win10) was causings and I've since uninstalled it and "Intel Rapid Start". Today though I got another BSOD when I tried to remote into the computer, so it may be a network driver again. However, driver verifier doesn't seem to be triggering any BSOD anymore.
     
    jag213, Oct 29, 2017
    #42
  13. jag213 Win User

    FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST

    So I upgraded to windows 1709 and attached all the results you asked for. The HD sentinel only lets you run the self and surface tests if you register the program and I think the only way to register is to buy it, so I couldn't get those.

    No errors seemed to have popped up in the tests.
     
    jag213, Nov 9, 2017
    #43
  14. zbook New Member
    zbook, Nov 9, 2017
    #44
  15. jag213 Win User
    Somehow my dump folder is empty. I don't know if its due the windows update or the check disk. I don't think the computer has BSOD in the past week, but previously I gone weeks without seeing a BSOD only for it to pop up again.
     
    jag213, Nov 9, 2017
    #45
Thema:

FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST

Loading...
  1. FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST - Similar Threads - FAULTY_HARDWARE_CORRUPTED_PAGE BSOD errors

  2. Faulty_Hardware_Corrupted_Page BSOD

    in Windows 10 BSOD Crashes and Debugging
    Faulty_Hardware_Corrupted_Page BSOD: This BSOD occurred. It took the bluescreen an alarmingly long time for it to finish collecting error data the better part of an hour before it finally reached 100%.Possibly useful information:Log from C:\Windows\Minidump created 7:21...
  3. BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

    in Windows 10 Gaming
    BSOD FAULTY_HARDWARE_CORRUPTED_PAGE: Minidump 072023-7593-01.dmp / Облако Mail.ruHere two scenarios of this failure are described, depending on whether parameters 3 and 4 are equal to 0 or not.FAULTY_HARDWARE_CORRUPTED_PAGE parametersThere are two scenarios where the memory manager raises...
  4. BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

    in Windows 10 Software and Apps
    BSOD FAULTY_HARDWARE_CORRUPTED_PAGE: Minidump 072023-7593-01.dmp / Облако Mail.ruHere two scenarios of this failure are described, depending on whether parameters 3 and 4 are equal to 0 or not.FAULTY_HARDWARE_CORRUPTED_PAGE parametersThere are two scenarios where the memory manager raises...
  5. BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

    in Windows 10 Gaming
    BSOD FAULTY_HARDWARE_CORRUPTED_PAGE: I've been having fairly regular issues for a couple of years with this system. As I only use it for gaming, and I'm pretty bad at gaming, I just suck it up and restart and occasionally run a utility to try to help. I'm attaching the log files from the system. I have a few...
  6. Recurring FAULTY_HARDWARE_CORRUPTED_PAGE BSOD

    in Windows 10 BSOD Crashes and Debugging
    Recurring FAULTY_HARDWARE_CORRUPTED_PAGE BSOD: Hi guys, I've been getting at least a BSOD daily, for the past 2-3 months, ever since I've purchases my current laptop. For few months, I had ThrottleStop installed, and up until a few weeks ago, I was undervolting the CPU (started with -150mV, ended at about -30mV, was still...
  7. BSOD FAULTY_HARDWARE_CORRUPTED_PAGE (12b)

    in Windows 10 BSOD Crashes and Debugging
    BSOD FAULTY_HARDWARE_CORRUPTED_PAGE (12b): Hi, Link includes minidump and msinfo32. https://1drv.ms/f/s!AlnwRVD5MUqdiBZaU2_G1mPB62GZ -Tommi https://answers.microsoft.com/en-us/windows/forum/all/bsod-faultyhardwarecorruptedpage-12b/e11370b2-a90a-4cd0-b273-5c16b6fd7984
  8. Bsod faulty_hardware_corrupted_page

    in Windows 10 BSOD Crashes and Debugging
    Bsod faulty_hardware_corrupted_page: Please check my upload. 86740
  9. Random BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD FAULTY_HARDWARE_CORRUPTED_PAGE: Hello there. I getting BSOD randomly on windows 10 on my ASUS K550JK. I tried the ASUS forum but, with respect, they suck on support. I've tried the new drivers and the original ones (Windows 8). Whocrashed logs keeps telling me that it may be a memory hardware problem but...
  10. BSOD with various games, Error: FAULTY_HARDWARE_CORRUPTED_PAGE

    in Windows 10 BSOD Crashes and Debugging
    BSOD with various games, Error: FAULTY_HARDWARE_CORRUPTED_PAGE: Hello, I am having this problem. This is a new pc, The first three days, it went fine, untill saterday. Thats when crashes started to happen. I tested with battlefield 4 and PUBG. I tried so far: Recovering to an early point (when I first got the PC, and played some games...