Windows 10: Speratic BSODs mainly while playing games. 0xc0000005

Hello guys! I recently been getting BSODS randomly. It all started yesterday as I was playing some Human: Fall Flat on steam. I figured the BSOD with from my controller but after randomly browsing it happened again. It also happened when playing overwatch. I have a newer graphics card and had no issues with it for the several months I had it. It's a 1060. In this post I posted the logs. I hope they are useful and would love to get some help. Thank you all so much. W7F_03-01-2018.7z

:)

 

multiple bsods while playing games

hoping for help.... i recently have had multiple crashes only while playing games. i'm wondering if it might have been due to a graphic driver (which ive updated after the most recent crash), have run memory diagnostic and check disk.

On Fri 8/11/2017 2:19:47 AM your computer crashed

crash dump file: C:\WINDOWS\Minidump\081117-10343-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)

Bugcheck code: 0x7F (0x8, 0xFFFFAF000554ABF0, 0xFFFFAF0005541F50, 0xFFFFF803BDC07C50)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 8/11/2017 1:09:08 AM your computer crashed

crash dump file: C:\WINDOWS\Minidump\081117-10234-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)

Bugcheck code: 0x7F (0x8, 0xFFFFA6005034ABF0, 0xFFFFA60056C52F20, 0xFFFFF80183DF4354)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 8/9/2017 2:54:35 PM your computer crashed

crash dump file: C:\WINDOWS\Minidump\080917-8140-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)

Bugcheck code: 0x7F (0x8, 0xFFFFAA007BB4ABF0, 0xFFFFAA008634D010, 0xFFFFF801D6379C40)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

multiple bsods while playing games

Hi,

The UNEXPECTED_KERNEL_MODE_TRAP or commonly know as Bug Check 0x7F indicates that the CPU generated a trap and the kernel failed to catch this trap. To help resolve the issue, refer on this article:
Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP. This article contains information about
the bug check's cause and its resolution.

Update us with the outcome so we can provide further assistance.

 

Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions .

There is a lot more data we need collected.

Thanks.

 

My apologize, here you go!ESAV-Wed_01_03_2018__04701_16.zip

Note: Upon sending this message my computer randomly shut down without warning and reset. Not sure why that happened. Perhaps it's a Mobo or PCU issue?

 

The last dump at 1/3 12:02AM shows a problem with nvlddmkm.sys.
Code: ffffcd80`34af9d50 fffff806`e6503ce0Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x5c3ce0[/quote] You have driver version 338.13 dated 0/26/2017. There is a newer one available from Nvidia:
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.

The oldest dump from 1/2 3:05 PM shows a hardware machine check (CPU failure):
Code: 6: kd> !errrec ffff930cdf311028 =============================================================================== Common Platform Error Record @ ffff930cdf311028 ------------------------------------------------------------------------------- Record Id : 01d3840435968fca Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 1/2/2018 20:04:50 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff930cdf3110a8 Section @ ffff930cdf311180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Instruction Execute Flags : 0x00 Level : 1 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff930cdf3110f0 Section @ ffff930cdf311240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : 20 0f 60 00 00 08 08 06 - 0b 32 98 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffff930cdf311240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff930cdf311138 Section @ ffff930cdf3112c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 6 Bank 1) Status : 0xb080000000040151[/quote] ===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

See if that shows you have a definite CPU problem or not.

 

You have driver version 338.13 dated 0/26/2017. There is a newer one available from Nvidia:
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.

The oldest dump from 1/2 3:05 PM shows a hardware machine check (CPU failure):
Code: 6: kd> !errrec ffff930cdf311028 =============================================================================== Common Platform Error Record @ ffff930cdf311028 ------------------------------------------------------------------------------- Record Id : 01d3840435968fca Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 1/2/2018 20:04:50 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff930cdf3110a8 Section @ ffff930cdf311180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Instruction Execute Flags : 0x00 Level : 1 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff930cdf3110f0 Section @ ffff930cdf311240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : 20 0f 60 00 00 08 08 06 - 0b 32 98 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffff930cdf311240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff930cdf311138 Section @ ffff930cdf3112c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 6 Bank 1) Status : 0xb080000000040151[/quote] ===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

See if that shows you have a definite CPU problem or not.[/quote] Okay! I'll start removing the Graphics drivers now and will start that CPU test momentarily. I'll keep you updated with what I find.

 

You have driver version 338.13 dated 0/26/2017. There is a newer one available from Nvidia:
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.

The oldest dump from 1/2 3:05 PM shows a hardware machine check (CPU failure):
Code: 6: kd> !errrec ffff930cdf311028 =============================================================================== Common Platform Error Record @ ffff930cdf311028 ------------------------------------------------------------------------------- Record Id : 01d3840435968fca Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 1/2/2018 20:04:50 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff930cdf3110a8 Section @ ffff930cdf311180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Instruction Execute Flags : 0x00 Level : 1 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff930cdf3110f0 Section @ ffff930cdf311240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : 20 0f 60 00 00 08 08 06 - 0b 32 98 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffff930cdf311240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff930cdf311138 Section @ ffff930cdf3112c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 6 Bank 1) Status : 0xb080000000040151[/quote] ===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

See if that shows you have a definite CPU problem or not.[/quote] Okay so I did update my Graphics drivers and attempted to run a CPU test but I still got some BSODs. I'm not sure if the CPU test completed because most of the times the computer would Blue Screen in the middle of it. I did make a new dump and will provide the txt file from the test.

 

Did you use DDU to uninstall the Nvidia driver?
Did you install only the NVidia graphics driver and the PhysX driver?

The 1/4 3:05PM dump showed a problem with VBoxNetLwf.sys.
Code: ffffde01`f6b71098 fffff80a`7c6a20f4Unable to load image VBoxNetLwf.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VBoxNetLwf.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxNetLwf.sys VBoxNetLwf+0x20f4[/quote] Driver Description: Oracle VirtualBox NDIS 6.0 Lightweight Filter Driver

Are you at the latest Oracle VirtualBox version which is 5.1.30? If not upgrade to teh latest. VB will do that for you.

The 1/4 2:34PM dump showed a problem with MBAMChameleon.sys.
Code: ffffd400`ef6fa3a8 fffff807`25016e08Unable to load image MBAMChameleon.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for MBAMChameleon.sys *** ERROR: Module load completed but symbols could not be loaded for MBAMChameleon.sys MBAMChameleon+0x26e08[/quote] Driver Description: Malwarebytes Chameleon Protection Driver

Uninstall Malwarebytes antimalware for now, see if that makes any difference. Reinstall the latest once we're done debugging.

Are you over clocking at all? If yes, please set everything back to normal for now, see whatthat does.

Also, Please update your System Specs so they match your system as it is now.

See here: System Specs - Fill in at Ten Forums

The more information you can provide the better.

 

Driver Description: Oracle VirtualBox NDIS 6.0 Lightweight Filter Driver

Are you at the latest Oracle VirtualBox version which is 5.1.30? If not upgrade to teh latest. VB will do that for you.

The 1/4 2:34PM dump showed a problem with MBAMChameleon.sys.
Code: ffffd400`ef6fa3a8 fffff807`25016e08Unable to load image MBAMChameleon.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for MBAMChameleon.sys *** ERROR: Module load completed but symbols could not be loaded for MBAMChameleon.sys MBAMChameleon+0x26e08[/quote] Driver Description: Malwarebytes Chameleon Protection Driver

Uninstall Malwarebytes antimalware for now, see if that makes any difference. Reinstall the latest once we're done debugging.

Are you over clocking at all? If yes, please set everything back to normal for now, see whatthat does.

Also, Please update your System Specs so they match your system as it is now.

See here: System Specs - Fill in at Ten Forums

The more information you can provide the better.[/quote] I uninstalled Malwarebytes for now. I'm not overclocked but in my BIOS I did have the performance power setting enabled. I brought it back to the default power option. I was discussing these issues with a few friends of mine and they believe a possible issue is that the CPU is overheating. Turns out I haven't reapplied Thermal Paste in quite some time. Would the overheating explain the times the computer randomly reset without BSODs?

 

If the CPU is overheating then random shutdowns is entirely possible. New thermal paste sounds like an excellent idea.

You could also use a program like SpeedFan to monitor temps and see what they are.

 

So I thought it was in the clear since nothing has happened since I added the new thermal paste, reverted my bios performance settings and added the new Nvidia drivers but I just got another BSOD. I wasn't doing anything new or installed anything recently so not sure what's up.

 

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: 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

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.)[/quote] 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.[/quote] 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.)[/quote] 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.[/quote] 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.[/quote]
These were boot-start drivers that had failed to load:

cbfs64.sys EldoS Corp - Callback File System Driver /n software - A Bright Future for EldoS Products
AsIO.sys Asus PCProbe Utility Official Support | ASUS Global
VBoxDrv.sys VirtualBox Downloads – Oracle VM VirtualBox
VBoxNetAdp.sys VirtualBox network driver Downloads – Oracle VM VirtualBox
VBoxNetLwf.sys Oracle VirtualBox NDIS 6.0 Lightweight Filter Driver Downloads – Oracle VM VirtualBox
VBoxUSBMon.sys VirtualBox USB driver Downloads – Oracle VM VirtualBox
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[/quote]

 

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.[/quote] 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.)[/quote] 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.[/quote] 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.[/quote]
These were boot-start drivers that had failed to load:

cbfs64.sys EldoS Corp - Callback File System Driver /n software - A Bright Future for EldoS Products
AsIO.sys Asus PCProbe Utility Official Support | ASUS Global
VBoxDrv.sys VirtualBox Downloads – Oracle VM VirtualBox
VBoxNetAdp.sys VirtualBox network driver Downloads – Oracle VM VirtualBox
VBoxNetLwf.sys Oracle VirtualBox NDIS 6.0 Lightweight Filter Driver Downloads – Oracle VM VirtualBox
VBoxUSBMon.sys VirtualBox USB driver Downloads – Oracle VM VirtualBox
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[/quote] [/quote] 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>

 

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.