Speratic BSODs mainly while playing games. 0xc0000005

Page 2 of 2 FirstFirst 12

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

    The latest BSOD mini dump file debugging displayed Nvidia graphics driver as the misbehaving driver.
    This was bugcheck 3B
    This is a recurrent misbehaving hardware driver.
    There are now 2 different misbehaving Nvidia drivers.
    The driver numbers need to be recorded to see which drivers are unstable /stable in the current computer environment.

    The current driver:
    nvlddmkm nvlddmkm.sys Fri Dec 15 16:17:15 2017 (5A3449EB)
    nvlddmkm.sys (23.21.13.8871)

    Prior:
    nvlddmkm nvlddmkm.sys Fri Oct 27 10:49:39 2017 (59F35593)
    Driver Version 23.21.13.8813

    The logs displayed event problems related to the drive: paging errors, and possible corruption.

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

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

    5) chkdsk /x /f /r use the syntax chkdsk /x /f /r C: or chkdsk /x /f /r D: changing the driver letter so that all drives/partitions are tested
    This may take many hours so plan to run overnight
    6) Use the information in this link to find the chkdsk reports in the event viewer. Copy and past the report and post into the thread using a one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    7) Run HDTune: http://www.hdtune.com/
    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

    8) To ensure that there are no improper bios settings please reset the bios.
    9) Sometimes there can be failure to boot after resetting the bios.

    10) Make sure your files are backed up to another drive or to the cloud

    11) Make a backup image with Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    12) Place the backup image onto another drive or into the cloud

    13) 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) Uninstall Vbox
    15) Unisntall Malwarebytes
    16) Uninstall cbfs64.sys EldoS Corp - Callback File System Driver (can reinstall after the troubleshooting process) (if it is needed then uninstall and reinstall)
    17) Uninstall AsIO.sys Asus PCProbe Utility (can reinstall after the troubleshooting process) (if it is needed then uninstall and reinstall)

    18) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller.
    19) For re-installation use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller Download version 17.0.7.2
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA

    20) During the troubleshooting period to complete the testing on the other hardware components you may be able to remove the Nvidia graphics card and use the motherboard graphics. This way you would not risk having BSOD interrupting the testing.

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

    22) Ensure the GPU is free from dust build up and that the fan is working correctly
    23) Reseat the GPU and check all connections are securely made

    24) What are the BIOS 3.3, 5 and 12 voltage values?
    25) What are the CPU voltage and frequency?

    26) See if you can find a friend, neighbor, relative, or local computer store to swap the Nvidia graphics card.
    There should be two different tests:
    The problematic computer graphics card should be tested in another computer.
    A replacement card should be tested in this computer.

    27) Update the system specs in the "My Computer" section:
    How To Fill Out Your System Specs How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Site Use 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.)

    28) The computer has Windows 10 version 1703.
    What are your plans for Windows 10 version 1709?
    Had the computer failed to upgrade? If so what were the error messages and code?

    These are tests that can be run overnight:
    chkdsk /x /f /r
    HD Tune full error scan
    Memtest86+ version 5.01

    Code:
    Event[17814]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-12-31T14:32:54.307  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: ESAV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume9.(A device which does not exist was specified.)
    Code:
    Event[17809]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.306  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17810]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.306  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17811]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.307  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17812]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.307  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17813]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.307  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
    Code:
    Event[17170]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-12-25T15:07:27.029  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: ESAV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume9.(A device which does not exist was specified.)
    Code:
    Event[17160]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.028  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17161]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.028  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17162]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.028  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17163]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17164]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17165]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17166]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17167]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17168]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17169]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
    Code:
    Event[17719]:  Log Name: System  Source: cdrom  Date: 2017-12-30T08:18:18.849  Event ID: 7  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: The device, \Device\CdRom0, has a bad block.

    These were boot-start drivers that had failed to load:

    cbfs64.sys EldoS Corp - Callback File System Driver http://www.eldos.com/support/




    VBoxNetLwf.sys Oracle VirtualBox NDIS 6.0 Lightweight Filter Driver http://www.virtualbox.org/wiki/Downloads


    esprotectiondriver.sys Malwarebytes

    Code:
    PNP Device ID    PCI\VEN_10DE&DEV_1C03&SUBSYS_85B61043&REV_A1\4&23984C36&0&0058INF File    oem8.inf (Section136 section)Name    NVIDIA GeForce GTX 1060 6GBAdapter Description    NVIDIA GeForce GTX 1060 6GBColor Planes    Not AvailableIRQ Channel    IRQ 32Adapter Type    GeForce GTX 1060 6GB, NVIDIA compatibleInstalled Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dllDriver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvlddmkm.sys (23.21.13.8871, 16.24 MB (17,028,552 bytes), 1/4/2018 2:54 PM)Color Table Entries    4294967296Bits/Pixel    32Driver Version    23.21.13.8871Resolution    1920 x 1080 x 144 hertzMemory Address    0xFD000000-0xFE0FFFFFMemory Address    0xD0000000-0xD1FFFFFFMemory Address    0xC0000000-0xD1FFFFFFMemory Address    0xA0000-0xBFFFFI/O Port    0x0000E000-0x0000EFFFI/O Port    0x000003C0-0x000003DFI/O Port    0x000003B0-0x000003BBAdapter RAM    (1,048,576) bytes
    Last edited by zbook; 08 Jan 2018 at 19:21.
      My Computer


  2. Posts : 165
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter
       #12

    zbook said:
    The latest BSOD mini dump file debugging displayed Nvidia graphics driver as the misbehaving driver.
    This was bugcheck 3B
    This is a recurrent misbehaving hardware driver.
    There are now 2 different misbehaving Nvidia drivers.
    The driver numbers need to be recorded to see which drivers are unstable /stable in the current computer environment.

    The current driver:
    nvlddmkm nvlddmkm.sys Fri Dec 15 16:17:15 2017 (5A3449EB)
    nvlddmkm.sys (23.21.13.8871)

    Prior:
    nvlddmkm nvlddmkm.sys Fri Oct 27 10:49:39 2017 (59F35593)
    Driver Version 23.21.13.8813

    The logs displayed event problems related to the drive: paging errors, and possible corruption.

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

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

    5) chkdsk /x /f /r use the syntax chkdsk /x /f /r C: or chkdsk /x /f /r D: changing the driver letter so that all drives/partitions are tested
    This may take many hours so plan to run overnight
    6) Use the information in this link to find the chkdsk reports in the event viewer. Copy and past the report and post into the thread using a one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    7) Run HDTune: http://www.hdtune.com/
    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

    8) To ensure that there are no improper bios settings please reset the bios.
    9) Sometimes there can be failure to boot after resetting the bios.

    10) Make sure your files are backed up to another drive or to the cloud

    11) Make a backup image with Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    12) Place the backup image onto another drive or into the cloud

    13) 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) Uninstall Vbox
    15) Unisntall Malwarebytes
    16) Uninstall cbfs64.sys EldoS Corp - Callback File System Driver (can reinstall after the troubleshooting process) (if it is needed then uninstall and reinstall)
    17) Uninstall AsIO.sys Asus PCProbe Utility (can reinstall after the troubleshooting process) (if it is needed then uninstall and reinstall)

    18) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller.
    19) For re-installation use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller Download version 17.0.7.2
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA

    20) During the troubleshooting period to complete the testing on the other hardware components you may be able to remove the Nvidia graphics card and use the motherboard graphics. This way you would not risk having BSOD interrupting the testing.

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

    22) Ensure the GPU is free from dust build up and that the fan is working correctly
    23) Reseat the GPU and check all connections are securely made

    24) What are the BIOS 3.3, 5 and 12 voltage values?
    25) What are the CPU voltage and frequency?

    26) See if you can find a friend, neighbor, relative, or local computer store to swap the Nvidia graphics card.
    There should be two different tests:
    The problematic computer graphics card should be tested in another computer.
    A replacement card should be tested in this computer.

    27) Update the system specs in the "My Computer" section:
    How To Fill Out Your System Specs How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Site Use 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.)

    28) The computer has Windows 10 version 1703.
    What are your plans for Windows 10 version 1709?
    Had the computer failed to upgrade? If so what were the error messages and code?

    These are tests that can be run overnight:
    chkdsk /x /f /r
    HD Tune full error scan
    Memtest86+ version 5.01

    Code:
    Event[17814]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-12-31T14:32:54.307  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: ESAV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume9.(A device which does not exist was specified.)
    Code:
    Event[17809]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.306  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17810]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.306  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17811]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.307  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17812]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.307  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17813]:  Log Name: System  Source: Disk  Date: 2017-12-31T14:32:54.307  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
    Code:
    Event[17170]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-12-25T15:07:27.029  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: ESAV  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume9.(A device which does not exist was specified.)
    Code:
    Event[17160]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.028  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17161]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.028  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17162]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.028  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17163]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17164]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17165]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17166]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17167]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17168]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[17169]:  Log Name: System  Source: Disk  Date: 2017-12-25T15:07:27.029  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
    Code:
    Event[17719]:  Log Name: System  Source: cdrom  Date: 2017-12-30T08:18:18.849  Event ID: 7  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ESAV  Description: The device, \Device\CdRom0, has a bad block.

    These were boot-start drivers that had failed to load:

    cbfs64.sys EldoS Corp - Callback File System Driver http://www.eldos.com/support/




    VBoxNetLwf.sys Oracle VirtualBox NDIS 6.0 Lightweight Filter Driver http://www.virtualbox.org/wiki/Downloads


    esprotectiondriver.sys Malwarebytes

    Code:
    PNP Device ID    PCI\VEN_10DE&DEV_1C03&SUBSYS_85B61043&REV_A1\4&23984C36&0&0058INF File    oem8.inf (Section136 section)Name    NVIDIA GeForce GTX 1060 6GBAdapter Description    NVIDIA GeForce GTX 1060 6GBColor Planes    Not AvailableIRQ Channel    IRQ 32Adapter Type    GeForce GTX 1060 6GB, NVIDIA compatibleInstalled Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumd.dllDriver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvlddmkm.sys (23.21.13.8871, 16.24 MB (17,028,552 bytes), 1/4/2018 2:54 PM)Color Table Entries    4294967296Bits/Pixel    32Driver Version    23.21.13.8871Resolution    1920 x 1080 x 144 hertzMemory Address    0xFD000000-0xFE0FFFFFMemory Address    0xD0000000-0xD1FFFFFFMemory Address    0xC0000000-0xD1FFFFFFMemory Address    0xA0000-0xBFFFFI/O Port    0x0000E000-0x0000EFFFI/O Port    0x000003C0-0x000003DFI/O Port    0x000003B0-0x000003BBAdapter RAM    (1,048,576) bytes
    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>
      My Computer


  3. Posts : 13,950
    Windows 10 Pro X64 21H1 19043.1503
       #13

    Latest dump point to Nvidia card or driver.

    You have version 388.71 dated 12/14/2017. There is a newer one available:
    GeForce Game Ready Driver



    Version: 390.65 WHQL
    Release Date: 2018.1.8
    Operating System: Windows 10 64-bit
    Language: English (US)
    File Size: 430.81 MB

    Remove and install latest Nvidia drivers:

    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

    Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    See if that gets rid of the problem.
      My Computers


  4. Posts : 165
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter
       #14

    Ztruker said:
    Latest dump point to Nvidia card or driver.

    You have version 388.71 dated 12/14/2017. There is a newer one available:
    GeForce Game Ready Driver



    Version: 390.65 WHQL
    Release Date: 2018.1.8
    Operating System: Windows 10 64-bit
    Language: English (US)
    File Size: 430.81 MB

    Remove and install latest Nvidia drivers:

    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

    Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    See if that gets rid of the problem.
    I've been trying to update my drivers but whenever I have use DDU to uninstall the outdated ones shortly after drivers are automatically installed. Kind of puzzled on why that's happening. I haven't even been able to update to my latest drivers
      My Computer


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

    Windows by default will update non-Microsoft drivers.
    So any driver can be installed when offline.
    Then when Windows updates the driver may change.
    There are options in this link which can be used to modify the default settings.
    Some of the options have been lost when Windows was upgraded from 1703 to 1709.
    You may need to start with option #3 in this link:
    Enable or Disable Driver Updates in Windows Update in Windows 10 Windows Update Activation Tutorials
      My Computer


  6. Posts : 165
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter
       #16

    zbook said:
    Windows by default will update non-Microsoft drivers.
    So any driver can be installed when offline.
    Then when Windows updates the driver may change.
    There are options in this link which can be used to modify the default settings.
    Some of the options have been lost when Windows was upgraded from 1703 to 1709.
    You may need to start with option #3 in this link:
    Enable or Disable Driver Updates in Windows Update in Windows 10 Windows Update Activation Tutorials
    Thank you for the pointer! I got the latest Nvidia Drivers installed and I guess it's time to play the waiting game again
      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 06:06.
Find Us




Windows 10 Forums