BSOD while watching Youtube and on Second Life

Hi,

BSOD dumps show bugcheck 0x116, this means theres a problem with GPU driver or GPU itself:

Code:

0x00000116:    VIDEO_TDR_FAILURE (3.06.2017 21:14:51) [Windows 10] 
 
CAUSED BY:     nvlddmkm.sys [1.05.2017] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
               dxgkrnl.sys [28.04.2017] * DirectX Graphics Kernel (Windows System File) 
 
PROCESS:       System 
 
Usual causes:  Video driver, overheating, bad video card, ?BIOS, ?Power to card (see Significant Posts section below)

0x116

VIDEO_TDR_ERROR

A VIDEO_TDR_ERROR always relates to the system's graphics card (TDR = Timeout Detection Recovery). This could be down to a number of reasons including drivers, heat, power to the card, a faulty PCI-e slot or simply a defective GPU. It's in your best interests to employ common sense trouble shooting techniques in these situations.

• Try later and/or earlier drivers
• Measure the GPU's temperatures at idle and under load
• Ensure the GPU is free from dust build up and that the fan is working correctly
• Reseat the GPU and check all connections are securely made
• Check PSU voltages in BIOS
• Try a different card in the system

Diagnostic Test

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

There are a bunch of tools u are using which are known for causing bluescreens. Some of these tools are used for overclocking. Please remove them to see if it helps. If you overclocked your system please revert back to stock to see if that helps.

MSI Afterburner
Corsair Link 4
Asus AI Suite III

Ok, so, I updated the video card drivers to the latest and, as it was on my hit list, updated the bios from something that came from the factory to the latest since I preordered the motherboard. Though that kinda screwed up my mild overclock, I was running at 3.8ghz now I am running at 3.6ghz, it crashes at 3.8ghz. >.<

Code:

BugCheck 124, {0, ffffa702b3c868f8, 0, 0}Probably caused by : AuthenticAMD

Code:

BugCheck 116, {ffffbe002af43010, fffff802936e7880, 0, d}Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2a6e383a1adc0e24\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.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+157880 )

Code:

BugCheck 116, {ffffac8dfca2b010, fffff80a5e9ef44c, 0, d}Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a2b0acab06663645\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.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+15f44c )

Code:

BugCheck 133, {1, 1e00, 0, 0}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+d33e )

Code:

The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_&Prod_Patriot_Memory&Rev_PMAP#070B650499ABF818&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Code:

File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T08:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy3'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.

Code:

Windows failed fast startup with error status 0xC00000D4.

Code:

The driver \Driver\WudfRd failed to load for the device USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android\7&19ede046&0&0000.

Code:

File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T09:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy5'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.

Code:

Windows failed fast startup with error status 0xC00000D4.

Code:

File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T09:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy2'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.

Code:

File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T09:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy8'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.

Code:

The VMware Input Filter and Injection Driver (vmkbd) service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Code:

The driver \Driver\WudfRd failed to load for the device USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android\7&19ede046&0&0000.

Code:

The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{9d57014f-3871-11e7-b436-6045cb9a054e}#0000000008100000.

Code:

{Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Lee Lloyd\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.

Code:

{Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Lee Lloyd\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.

Code:

The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

Code:

The device, \Device\Harddisk2\DR2, has a bad block.

1) The AMD bsod was from approximately 3 months ago.
2) Nvidia drivers need to be uninstalled and the installed
3) There were several windows failed fast startup: Turn fast start up off
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials
4) There is a bad block on the HD
Run chkdsk /x /f /r (it may take many hours, plan to run overnight)
Run HD sentinel: Hard Disk Sentinel - HDD health and temperature monitoring
Run Sea Tools for Windows: SMART, short, and long generic:
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows

Open administrative command prompt and type or copy and paste these commands:
sfc /scannow
dism /online /cleanup-image /restorehealth


Please report the results of each scannow and restorehealth

For the chkdsk report:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials


get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

Or use eventvwr find menu and enter 26226

CHKDSK: What is it and how do I run it? - Ask Leo!
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

Please post images from HD sentenial and results of seatools SMART, short and long generic tests

1 - Not sure what you mean, the BSOD I am referring to happened the night I posted this.
2 - Already done, the nVidia video drivers have been updated.
3 - Done, Fast Start has been disabled
4 - Which drive? I have 4 physical drives internally and 1 external USB 3 drive. One 640gb C: for booting, 2 2tb, a 4tb, and a 4tb USB 3 external. Umm...

C: WDC WD6401AALS 640gb
D: Seagate ST32000644NS 2tb
E: WDC WD40003FZEX 4tb
F: Seagate ST2000DM001 2tb
G: Seagate Expansion Desk 4tb USB 3

Ok, odd...

E:\>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is New Volume.


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


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


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


Stage 4: Looking for bad clusters in user file data ...
Windows replaced bad clusters in file 754452
of name \PROGRA~1\Steam\STEAMA~1\common\oblivion.rar.
2181104 files processed.
File data verification completed.
An unspecified error occurred (75736e6a726e6c2e 4f8).


E:\>

What error is that? O.o

On March 14, 2017 you had a bsod related to AMD. This was an old bsod so we did not make any new changes.
Have there been any bsod since 6/8?
When you uninstalled the NVIDIA drivers did you use the Display Driver Uninstaller?
Display Driver Uninstaller Download version 17.0.6.6
If you have another bsod please use this tool to uninstall all NVIDIA drivers.
And when you reinstall NVIDIA drivers from the NVIDIA web site make sure you check the "clean install box" only install the Graphics driver and the PhysX driver.

Run Sea Tools on all of your non SSD drives: SMART, short and long generic testing
Run HD tune, HD Sentinel, or Crystal Disk on all of your drives: SMART testing
This way you will have a baseline and find the problems with the drive reported in the event log.
The later three will provide images and data. Please post in the forum.

Yeah, my Steam drive, that's the 4tb, it's having issues, going to buy another when I am able to, copy off the 4tb onto the new drive, then RMA the 4tb and ship it back to Western Digital. Took two tries but I finally got it to complete a chkdsk, even after I still have two warnings in the SMART table.

C5 200 200 __0 000000000001 Current Pending Sector CountC6 200 200 __0 000000000001 Uncorrectable Sector Count

And, so far, no new BSODs, so we'll see, I hate to mark this as solved then have it BSOD again. >.<

Glad to hear that your problem is now fixed. Let us know if there are any other problems.

At least the root cause for your problem was with high probability something with the GPU and/or GPU driver.
In most cases the bsod dump show the right direction to the culprit:

Code:

0x00000116:    VIDEO_TDR_FAILURE (3.06.2017 21:14:51) [Windows 10] 
 
CAUSED BY:     nvlddmkm.sys [1.05.2017] * nVidia Video drivers * => NVIDIA  
 
Usual causes:  Video driver, overheating, bad video card, ?BIOS, ?Power to card (see Significant Posts section below)