Windows 10: BSOD Page Fault after downloading Win 10, ver 1709 Update

Discus and support BSOD Page Fault after downloading Win 10, ver 1709 Update in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi All, The BSOD script was "Page Fault in non page area". Occurred after I downloaded Win 10 Update ver 1709. After clicking restart, the computer... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Russ85, Nov 20, 2017.

  1. Russ85 Win User

    BSOD Page Fault after downloading Win 10, ver 1709 Update


    Hi All,
    The BSOD script was "Page Fault in non page area".

    Occurred after I downloaded Win 10 Update ver 1709. After clicking restart, the computer restarts without installing the update. I ran the Update Troubleshooter and it found several items and "fixed" them. Tried again with same result. Ran Disk Cleanup and then re-downloaded the update this morning with the same result.

    System dump file attached. Thanks in advance for the assistance!

    :)
     
    Russ85, Nov 20, 2017
    #1
  2. FilippGIT Win User

    BSOD PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl.exe

    Have you found a solution of the problem? I think i have exactly the same problems on HP Clients with Win 10 1709 ... when i shutdown the clienst i receive a BSOD (ba pool caller or page fault in non paged area)
     
    FilippGIT, Nov 20, 2017
    #2
  3. apers0n Win User
    Getting error 0x80246010 when updating Windows 10 home ver 1709 os 16299.192

    2018-01 Cumulative update for wins 10 ver 1709 for x64 based sys' (KB4058258) - Error 0x80246010

    Original subject: have win 10 home ver 1709 os 16299.192
     
    apers0n, Nov 20, 2017
    #3
  4. zbook New Member

    BSOD Page Fault after downloading Win 10, ver 1709 Update

    Hi Russ85,

    Welcome to Ten Forums BSOD forum.
    The bug check 50 was seen in prior dumps but there was no new dump as crash dumps had failed.
    The bug check 50 Page fault in a non paged area indicates that invalid system memory has been referenced. Typically the memory address is wrong or the memory address is pointing at freed memory. This could be caused by faulty hardware (RAM, drive, etc.)
    The logs indicated problems with the drive: bad blocks, chkdsk repair, and paging errors.
    There were problems noted with hibernation.
    The upgrade to 1709 failed and that can be evaluated later after fixing the BSODs.

    1) Please update the system specs in the "My Computer" section:
    How To Fill Out Your System Specs System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums General Tips Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums


    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

    For all tests please post images into the thread.
    If there are any problems posting images please use one drive or drop box share links.

    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /restorehealth
    5) 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

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

    7) Sometimes there are problems in the bios that produce bsod.
    The BIOS: Version/Date Dell Inc. A11, 7/9/2015
    8) Open the Dell website > enter the computer's serial or product number > please check to see that this is the most up to date edition.
    9) Post into the thread the URL or hyperlink for the computer's drivers.

    10) To ensure that there are no improper bios settings please reset the bios.
    11) Sometimes there can be failure to boot after resetting the bios.
    12) So please make sure your files are backed up.
    13) Please make a backup image with Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    13) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    14) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.
    Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool
    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM BSOD Tutorials

    15) Run HDTune: (check all drives)
    HD Tune website
    to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.
    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 General Tips Tutorials

    16) Open administrative command prompt and type or copy and paste:

    17) Powercfg -h off

    18) chkdsk /x /f /r (check all drives/partitions) (use syntax chkdsk /x /f /r C: and change C: to the drive letter)
    This may take many hours to run so plan to run it overnight.
    19) Post the chkdsk results into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

    20) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab under startup and recovery click settings > post an image into the thread

    21) In the left lower corner search type: clean > open disk cleanup > use the scroll feature and post images of the rows with checked and un-checked boxes.

    22) If you use Ccleaner > click Windows tab > scroll down to system and advanced > post images into the thread

    23) If you use other cleaning software please post that information into the thread.


    These are some of the tests that can be performed overnight:
    1) HD Tune drive error scans
    2) Memetest86+ version 5.01
    3) chkdsk /x /f /r



    Code: Event[14255]: Log Name: System Source: volmgr Date: 2017-09-08T18:35:36.869 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Dump file creation failed due to error during dump creation.Event[14256]: Log Name: System Source: volmgr Date: 2017-09-08T18:35:36.869 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Crash dump initialization failed![/quote] Code: Event[16721]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-10-13T04:00:01.727 Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: Windows failed to resume from hibernate with error status 0xC0000001.[/quote] Code: Event[19839]: Log Name: System Source: Virtual Disk Service Date: 2017-11-18T07:55:40.785 Event ID: 9 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Unexpected provider failure. Restarting the service may fix the problem. Error code: 8007001F@02000014Event[19840]: Log Name: System Source: Virtual Disk Service Date: 2017-11-18T07:55:40.985 Event ID: 9 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Unexpected provider failure. Restarting the service may fix the problem. Error code: 8007001F@02000014[/quote] Code: Event[20177]: Log Name: System Source: volmgr Date: 2017-11-19T10:14:42.555 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Dump file creation failed due to error during dump creation.Event[20178]: Log Name: System Source: volmgr Date: 2017-11-19T10:14:42.555 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Crash dump initialization failed![/quote] Code: Event[20430]: Log Name: System Source: volmgr Date: 2017-11-19T10:58:04.478 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Dump file creation failed due to error during dump creation.Event[20431]: Log Name: System Source: volmgr Date: 2017-11-19T10:58:04.478 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Crash dump initialization failed![/quote] Code: Event[19197]: Log Name: System Source: Application Popup Date: 2017-11-12T16:43:51.103 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: Application popup: Windows - Virtual Memory Minimum Too Low : Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help.[/quote] Code: Event[9746]: Log Name: System Source: Disk Date: 2017-08-17T15:21:23.900 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[9747]: Log Name: System Source: Disk Date: 2017-08-17T15:21:23.900 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[9748]: Log Name: System Source: Disk Date: 2017-08-17T15:21:23.900 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.[/quote] Code: Event[2036]: Log Name: System Source: Disk Date: 2017-05-22T18:18:11.709 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: The device, \Device\Harddisk1\DR1, has a bad block.[/quote] Code: Event[10331]: Log Name: System Source: Disk Date: 2017-09-02T09:41:25.573 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: The device, \Device\Harddisk7\DR24, has a bad block.[/quote] Code: Event[19756]: Log Name: System Source: Disk Date: 2017-11-16T15:22:44.350 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: The device, \Device\Harddisk6\DR6, has a bad block.[/quote] Code: Event[14846]: Log Name: System Source: Display Date: 2017-09-13T15:34:13.545 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: XPS8700 Description: Display driver amdkmdap stopped responding and has successfully recovered.[/quote] Code: Event[3934]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-06-08T12:09:12.294 Event ID: 98 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: Volume C: (\Device\HarddiskVolume5) needs to be taken offline for a short time to perform a Spot Fix. Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.[/quote] Code: Event[3935]: Log Name: System Source: Ntfs Date: 2017-06-08T12:09:22.553 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.Event[3936]: Log Name: System Source: Ntfs Date: 2017-06-08T12:11:28.289 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.Event[3937]: Log Name: System Source: Ntfs Date: 2017-06-08T12:11:36.720 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.Event[3938]: Log Name: System Source: Ntfs Date: 2017-06-08T12:11:36.721 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.Event[3939]: Log Name: System Source: Ntfs Date: 2017-06-08T12:13:58.933 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.Event[3940]: Log Name: System Source: Ntfs Date: 2017-06-08T12:13:58.946 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.Event[3941]: Log Name: System Source: Ntfs Date: 2017-06-08T12:13:58.947 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.Event[3942]: Log Name: System Source: Ntfs Date: 2017-06-08T12:13:58.949 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: XPS8700 Description: The file system structure on volume C: has now been repaired.[/quote] Code: 10/13/2017 9:01 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff805e89cde47 P4: ffffa98061b7b438 P5: ffffa98061b7ac80 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\101317-27187-01.dmp \\?\C:\Windows\Temp\WER-69843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2361.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER23FE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER240E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_8848ee3b2388761221794b3c6dfbaeb08cda_00000000_cab_37ed51c4 Analysis symbol: Rechecking for solution: 0 Report Id: 41def32d-ed28-4377-999f-44b65ec29b7e Report Status: 2049 Hashed bucket:10/13/2017 9:01 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff805e89cde47 P4: ffffa98061b7b438 P5: ffffa98061b7ac80 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\101317-27187-01.dmp \\?\C:\Windows\Temp\WER-69843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2361.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER23FE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER240E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_8848ee3b2388761221794b3c6dfbaeb08cda_00000000_01d5240d Analysis symbol: Rechecking for solution: 0 Report Id: 41def32d-ed28-4377-999f-44b65ec29b7e Report Status: 4 Hashed bucket:[/quote]
     
    zbook, Nov 20, 2017
    #4
  5. Hi there,

    all dumps show the AMD driver as culprit:
    Code: 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (2017-10-13 09:58:15) [Windows 10] CAUSED BY: atikmdag.sys [2017-04-25] * ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) * => AMD Support and Radeon Software Driver Download atikmpag.sys [2017-04-25] * ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) * => AMD Support and Radeon Software Driver Download ExceptionCode: c0000005 (Access violation) PROCESS: System[/quote] Code: 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (2017-08-13 09:08:29) [Windows 10] CAUSED BY: atikmdag.sys [2017-04-25] * ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) * => AMD Support and Radeon Software Driver Download atikmpag.sys [2017-04-25] * ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) * => AMD Support and Radeon Software Driver Download ExceptionCode: c0000005 (Access violation) PROCESS: System[/quote] Code: 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (2017-06-29 09:06:13) [Windows 10] CAUSED BY: atikmdag.sys [2017-04-25] * ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) * => AMD Support and Radeon Software Driver Download atikmpag.sys [2017-04-25] * ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) * => AMD Support and Radeon Software Driver Download ExceptionCode: c0000005 (Access violation) PROCESS: System[/quote] Code: 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA (2017-06-15 12:48:38) [Windows 10] CAUSED BY: NO INFORMATION FOUND PROCESS: atiesrxx.exe Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS[/quote]
    1) Please Remove/Install the newest AMD graphics driver using DDU

    BSOD Page Fault after downloading Win 10, ver 1709 Update [​IMG]
    Display Driver Uninstaller: How to use
    Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.

    2) Your Harddisk is also broken:
    Code: 2017-08-01 09:26:19 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\000000a5) was retried. 2017-08-03 07:30:47 Error: The device, \Device\Harddisk1\DR8, has a bad block. 2017-08-06 13:23:05 Error: The device, \Device\Harddisk1\DR10, has a bad block. 2017-08-06 13:42:20 Error: The device, \Device\Harddisk1\DR10, has a bad block. 2017-08-07 18:58:49 Error: The device, \Device\Harddisk1\DR12, has a bad block. 2017-08-11 18:59:51 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000092) was retried. 2017-08-13 16:40:15 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-08-13 17:22:41 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-08-14 09:48:21 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-08-14 19:01:11 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-08-16 08:19:46 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-08-17 15:21:23 Warning: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. 2017-08-17 15:21:23 Warning: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. 2017-08-17 15:21:23 Warning: An error was detected on device \Device\Harddisk2\DR2 during a paging operation. 2017-08-17 15:24:29 Error: The device, \Device\Harddisk1\DR8, has a bad block. 2017-08-18 19:01:41 Error: The device, \Device\Harddisk1\DR8, has a bad block. 2017-08-19 15:18:04 Error: The device, \Device\Harddisk1\DR8, has a bad block. 2017-08-20 19:01:21 Error: The device, \Device\Harddisk1\DR10, has a bad block. 2017-08-21 08:00:13 Warning: The IO operation at logical block address 0x622950 for Disk 1 (PDO name: \Device\000000d2) was retried. 2017-08-22 07:28:52 Error: The device, \Device\Harddisk1\DR15, has a bad block. 2017-08-23 07:31:51 Error: The device, \Device\Harddisk1\DR15, has a bad block. 2017-08-24 07:31:53 Error: The device, \Device\Harddisk1\DR15, has a bad block. 2017-08-24 10:44:44 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-08-24 19:00:18 Error: The device, \Device\Harddisk1\DR15, has a bad block. 2017-08-26 06:25:20 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\000000dd) was retried. 2017-08-26 15:18:34 Error: The device, \Device\Harddisk1\DR15, has a bad block. 2017-08-27 15:18:43 Error: The device, \Device\Harddisk1\DR15, has a bad block. 2017-08-28 09:45:39 Warning: The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\000000f7) was retried. 2017-08-28 09:46:03 Warning: The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\000000f9) was retried. 2017-09-02 09:41:25 Error: The device, \Device\Harddisk7\DR24, has a bad block. 2017-09-05 13:19:07 Error: The device, \Device\Harddisk1\DR10, has a bad block. 2017-09-06 09:52:20 Error: The device, \Device\Harddisk1\DR12, has a bad block. 2017-09-06 15:18:06 Error: The device, \Device\Harddisk1\DR12, has a bad block. 2017-09-07 08:38:27 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-09-07 15:44:43 Error: The device, \Device\Harddisk1\DR12, has a bad block. 2017-09-09 07:27:05 Warning: Reset to device, \Device\RaidPort1, was issued. 2017-09-09 07:27:05 Warning: The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-09-09 07:27:05 Warning: The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-09-09 07:27:28 Warning: Reset to device, \Device\RaidPort1, was issued. 2017-09-09 15:18:19 Warning: Reset to device, \Device\RaidPort2, was issued. 2017-09-09 15:18:21 Warning: The IO operation at logical block address 0x22 for Disk 2 (PDO name: \Device\00000045) was retried. 2017-09-10 15:18:37 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-13 16:00:37 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-14 15:19:05 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000047) was retried. 2017-09-16 07:13:26 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-17 07:36:00 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-18 07:01:28 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-19 07:33:35 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-20 09:47:24 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-09-21 07:13:09 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-23 07:24:35 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-09-24 07:27:32 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-24 10:30:40 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-09-24 15:18:43 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-25 17:57:25 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-09-26 07:23:45 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-26 21:27:04 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-09-27 07:10:52 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-28 07:28:53 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-09-29 06:21:23 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-01 15:18:17 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-02 19:00:24 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-03 19:00:15 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-05 07:22:14 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-06 06:40:03 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-07 07:23:36 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-07 18:20:42 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-09 06:57:56 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-09 10:56:57 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-10-10 07:23:38 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-10 16:56:41 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-11 15:18:36 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-12 18:30:46 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-10-30 22:20:51 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-10-31 14:48:55 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-10-31 15:57:11 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-01 15:30:45 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-02 16:06:24 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-11-03 15:29:11 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-11-04 06:44:26 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-11-04 15:30:41 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-05 15:40:46 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-06 15:40:09 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-07 14:26:02 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-11-07 15:43:43 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-08 15:18:43 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-09 15:18:42 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-11-10 15:18:48 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-11-11 15:18:41 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-12 10:47:09 Warning: Reset to device, \Device\RaidPort0, was issued. 2017-11-12 15:18:43 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-13 15:21:44 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-11-13 16:59:14 Warning: The IO operation at logical block address 0x22 for Disk 1 (PDO name: \Device\00000044) was retried. 2017-11-14 15:31:12 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-15 17:17:11 Error: The device, \Device\Harddisk6\DR6, has a bad block. 2017-11-16 15:22:44 Error: The device, \Device\Harddisk6\DR6, has a bad block. 2017-11-18 19:00:23 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-19 15:18:15 Error: The device, \Device\Harddisk1\DR1, has a bad block. 2017-11-20 15:18:41 Error: The device, \Device\Harddisk1\DR1, has a bad block.[/quote] Please make a backup!:

    1. Back Up ALL your data on an external device
    2. Create System Image Backup with Macrium Reflect
     
    BSODHunter, Nov 21, 2017
    #5
  6. zbook New Member
  7. Russ85 Win User
    Thank you zbook and BSOD Hunter for your assistance.

    OK, so upgrading the AMD graphics driver seems easy enough. Regarding my HDD, sounds like I need to replace it. Any recommendations/sources? Do I have to find an identical drive as a replacement?

    Also, I have my data backed up weekly using Acronis True Image 2016 on a external drive.
     
    Russ85, Nov 21, 2017
    #7
  8. Russ85 Win User

    BSOD Page Fault after downloading Win 10, ver 1709 Update

    I ran the SCANNOW and RESTOREHEALTH commands and here are the results;

    Microsoft Windows [Version 10.0.15063]
    (c) 2017 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 did not find any integrity violations.
    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>

    Additionally, I checked the Dell website and I appear to be running the latest BIOS version for my config. (A11).
     
    Russ85, Nov 21, 2017
    #8
  9. zbook New Member
    With a SSD you will enjoy the faster boot times.

    Please indicate the progress with each of the steps in post # 2.
     
    zbook, Nov 21, 2017
    #9
  10. Russ85 Win User
    Russ85, Nov 22, 2017
    #10
  11. zbook New Member
    For Memtest86+ version 5.01 see post #2 step 14
    The Dell website displays 2 new drivers in November.
    Download and install the latest drivers.
     
    zbook, Nov 22, 2017
    #11
  12. I got quite a few of those errors after i upgraded to 1709 - using 'WhoCrashed' i found out that it was my nVidia video drivers. I actually had to DOWNGRADE my legacy driver, using one from 2013 rather than the one i was using from Jan/15. After using DDU to uninstall the video driver i tried to reinstall the '15 driver & it wouldn't take. Tried the '13 driver which installed & so far have had no BSOD.

    If i have any more PFINPA errors, i'll test my RAM. If that passes, i'll downgrade back to 15063.674 - at least i didn't have any BSOD with the 1703 build.
     
    AthanasianCreed, Nov 22, 2017
    #12
  13. Russ85 Win User

    BSOD Page Fault after downloading Win 10, ver 1709 Update

    Update:

    Since my last post I have created a Macrium image of the C: drive and I created a new restore point. I don't have much faith in restore points as the last one I created failed to load when I tried to use it...

    Also, I updated the two November issued Dell drivers. I reset the BIOS to the default setting. I used DDU software to uninstall my AMD display driver. I installed AMD driver ver 17.11.1 without issue (so far). Finally, I am in the process of running MEMTEST86 v5.01. It has made two passes and no errors yet.

    I have not seen any BSOD's since the initial report... *Smile

    Happy Thanksgiving All!! and thanks again for your comments and support.
     
    Russ85, Nov 23, 2017
    #13
  14. Russ85 Win User
    I ran Memtest86 v5.01 for 12 passes. I ran Chkdsk and performed the DOS command Powercfg -h off. See attached logs for these tests as well as CCleaner and Spy Bot scans. I did not perform cleaning (analyze only) with Disk Cleanup, CCleaner or Spy Bot as I do not want to erase some of the memory dump files until we are done with them...

    I ran everything on zbook
    's list EXCEPT HdTune. The reason being my trial subscription has expired. Also, with all the re-starts, the Windows update (Fall Creators release) still has not installed.
     
    Russ85, Nov 24, 2017
    #14
  15. zbook New Member
    1) HD Tune has a free version.
    See if you can run the free version with tests for health, benchmark, and full error scan.
    2) In case that is not possible please use HD Sentinel which has a free or 30 day free trial.
    If you use this software please post into the thread reports for Overview, SMART, disk performance, and disk surface test
    3) For startup and recovery > system failure > change from kernel to automatic and un-check automatic restart
    4) For Ccleaner > system > un-check memory dumps and windows log files
     
    zbook, Nov 24, 2017
    #15
Thema:

BSOD Page Fault after downloading Win 10, ver 1709 Update

Loading...
  1. BSOD Page Fault after downloading Win 10, ver 1709 Update - Similar Threads - BSOD Page Fault

  2. BSOD Page Fault

    in Windows 10 Gaming
    BSOD Page Fault: Hi support,I have been getting a regular BSOD Page fault for a month now. I have updated NVIDIA drivers , AMD chipset drivers and removed things that were installed just before the fault started happening. I have done memory checks and error checking with no faults apparent....
  3. BSOD Page Fault

    in Windows 10 Software and Apps
    BSOD Page Fault: Hi support,I have been getting a regular BSOD Page fault for a month now. I have updated NVIDIA drivers , AMD chipset drivers and removed things that were installed just before the fault started happening. I have done memory checks and error checking with no faults apparent....
  4. BSOD Page Fault

    in Windows 10 BSOD Crashes and Debugging
    BSOD Page Fault: Hi support,I have been getting a regular BSOD Page fault for a month now. I have updated NVIDIA drivers , AMD chipset drivers and removed things that were installed just before the fault started happening. I have done memory checks and error checking with no faults apparent....
  5. Windows Update Page Fault BSOD

    in Windows 10 Installation and Upgrade
    Windows Update Page Fault BSOD: Hello, I purchased a Lenovo Legion Y520 a little over a year ago and I've had absolutely no problems...until 2 days ago. Windows pushed updates KB4506991 and KB4503308 ( a security update which Win10 won't allow me to uninstall) in the early morning hours. My machine now...
  6. Can't get updates past win 10 ver 1709 x64

    in Windows 10 Installation and Upgrade
    Can't get updates past win 10 ver 1709 x64: I am constantly bombarded with continuous updates for versions 1803 and 1809. I have run the update assistant, checked all my drivers and manually updated them and tried all the different suggestions for fixes I can find on the internet to no avail. I just keep getting 1803...
  7. BSOD page fault in no pages area

    in Windows 10 BSOD Crashes and Debugging
    BSOD page fault in no pages area: For a few weeks now I've been getting BSOD mostly while using internet browser (chrome). I've tried all the trouble shooting step including anti virus scans, registry clean ups, dusting out computer vents, changing settings for paging, adjusting chrome settings etc. I have...
  8. windows 10 update from ver.1709 to ver.1809

    in Windows 10 Installation and Upgrade
    windows 10 update from ver.1709 to ver.1809: can we update Windows 10 ver.1709 to ver.1809 directly using "Windows 10 Update Assistant"??? https://answers.microsoft.com/en-us/windows/forum/all/windows-10-update-from-ver1709-to-ver1809/891e2f3f-4120-495c-8e5a-c97032c032ff
  9. downgrade win 10 ver1803 to ver 1709 or 1703

    in Windows 10 Installation and Upgrade
    downgrade win 10 ver1803 to ver 1709 or 1703: I own a Lenovo y520 laptop which got it's win 10 upgraded to ver1803. Now I am experiencing a faster battery drainage issue and sometimes battery also drops to 0% from 67% suddenly. I am afraid this battery drainage and sudden shutdown of my laptop will harm the hardware in...
  10. AV Preventing Win 10 Ver 1709 Update Install

    in Windows 10 Updates and Activation
    AV Preventing Win 10 Ver 1709 Update Install: I am having trouble installing ver 1709 of Win 10. I get an error message part way through installation. The previous owner had Trend Micro Internet Security 2007 installed and had removed it with Windows uninstaller. I have run ALL the Trend Micro uninstallers and manually...