Hi ItsTheYoshi ,
Welcome to Ten Forums BSOD forum.
The BSOD mini dump files were partially debugged.
Some of the Windbg commands are not working during this Windows upgrade period.
The debugging indicated that the GPU drivers were misbehaving.
In addition the debugging displayed video TDR failure.
For all tests please post images into the thread.
In case there is any difficulty posting images please use one drive or drop box share links.
Perform the following steps:
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
This may take many hours so plan to run overnight.
Use the information in this link to find the report in the event.vwr and post the report into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
6) 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
7) Uninstall everything AMD using Display driver uninstaller and install new drivers from the AMD website.8) Be sure the "clean install" box is checked and only install the graphics 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
AMD Support and Radeon Software Driver Download
AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
9) 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
10) What are the BIOS 3.3, 5 and 12 voltage values?
What are the CPU voltage and frequency?
PSU - Test DC Output Voltage - Windows 7 Help Forums
11) 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
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
Code:
Event[36939]: Log Name: System Source: Display Date: 2017-10-26T15:01:20.668 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered. GPU drivers were misbehaving.
In addition they indicated TDREvent[36940]: Log Name: System Source: Display Date: 2017-10-26T15:01:22.951 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[36941]: Log Name: System Source: Display Date: 2017-10-26T15:01:27.258 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[36942]: Log Name: System Source: Display Date: 2017-10-26T15:01:29.561 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[36943]: Log Name: System Source: Display Date: 2017-10-26T15:01:33.859 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[36944]: Log Name: System Source: Display Date: 2017-10-26T15:01:36.162 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[36945]: Log Name: System Source: Display Date: 2017-10-26T15:01:40.455 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.
Code:
Event[36946]: Log Name: System Source: Display Date: 2017-10-26T15:01:42.744 Event ID: 4109 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Application chrome.exe has been blocked from accessing Graphics hardware.
Code:
Event[37291]: Log Name: System Source: Display Date: 2017-10-27T22:51:47.978 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37292]: Log Name: System Source: Display Date: 2017-10-27T22:51:50.615 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37293]: Log Name: System Source: Display Date: 2017-10-27T22:51:53.074 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37294]: Log Name: System Source: Display Date: 2017-10-27T22:52:01.374 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37295]: Log Name: System Source: Display Date: 2017-10-27T22:52:04.757 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37296]: Log Name: System Source: Display Date: 2017-10-27T22:52:13.064 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37297]: Log Name: System Source: Display Date: 2017-10-27T22:52:16.594 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37298]: Log Name: System Source: Display Date: 2017-10-27T22:52:24.836 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[37299]: Log Name: System Source: Display Date: 2017-10-27T22:52:28.530 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-GKV5H8I Description: Display driver amdkmdap stopped responding and has successfully recovered.
Code:
VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: ffffd888391ad010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff8001cc0f948, The pointer into responsible device driver module (e.g. owner tag).Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.Arg4: 000000000000000d, Optional internal context dependent data.