Windows 10: Graphics card crashing, nothing in Event Viewer

If there is a problem in my storage drive, can I simply disconnect it?

 

There was a problem in the event viewer with 1 of the drives that is being evaluated by hd tune and chkdsk. The external drive is going to be used for the backup of the internal drive. Once this troubleshooting is done you will use windows driver verifier and have secure backup knowing that you have already fixed the windows operating system (sfc /scannow) and any unknown drive problems.

If the graphics driver produces bsod and is replaced and there is no further bsod using windows driver verifier for an additional 36 - 48 hours troubleshooting will be completed with windows driver verifier.

If the graphics driver does not produce bsod then GPU stress testing may provide more information on the underlying problems.

If there is freezing, display artifacts, temperature problems with GPU stress testing then swapping graphics cards will be useful.

 

Sorry, these are from my main HD, I scanned the storage drive before

 

Nice progress.
Please post the chkdsk /x /f /r on the second drive.

Backup all files.
Create a backup image using Macrium.
Place the backup image onto another drive or into the cloud.
Create a brand new restore point.

Review the 3 methods to turn off Windows driver verifier:
1) windows advanced troubleshooting menu > startup options (not startup repair) > select #6 safe mode with command prompt > type:
verifier /reset
2) windows advanced troubleshooting menu > command prompt > type > verifier /bootmode resetonbootfail
3) windows advanced troubleshooting menu > system restore
The methods to turn off windows driver verifier should be used in the above order only going to the next one if the prior one failed.
The system restore leads to a loss of the bsod minidump and little progress is made in the troubleshooting.


Practice using the windows advance troubleshooting menu by opening administrative command prompt and typing: shutdown /r /o /f /t 00

Use the information in this link to set the testing parameters for windows driver verifier:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Use the information in this link for turning off windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

Run bluescreenview and whocrashed after each bsod > uninstall > reinstall or update each misbehaving driver
Post a new zip after each bsod and we will guide you through the process:
BSOD - Posting Instructions - Windows 10 Forums

 

I ran Driver Verifier and my graphics card crashed about 1 minute into a game of Heroes of the Storm.

Whocrashed did not report a BSOD, but since you seem to know a way to see them that I don't, here is a new ZIP...

 

It only seems to do this when I am playing something that makes significant use of my graphics card. It has happened when I have a game, Photoshop CC 2015, and/or Skype open and running.

Is it possible that my VRAM is faulty?

 

There was a crash but no dump to debug yet.
The last mini dump was the whocrashed test dump.

The bsod window was modified to un-check automatic restart.
When using Windows driver verifier a bsod will typically display a bugcheck driver verifier detected violation and sometimes it will display the misbehaving driver in the form *.sys.
If you see the misbehaving driver displayed on the bsod windows after the bugcheck please post that information into the thread.

Please install bluescreenview if not already installed and run each after each bsod:
Blue screen of death (STOP error) information in dump files.

Code: Event[11121]: Log Name: System Source: EventLog Date: 2017-10-01T19:56:35.494 Event ID: 6008 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-T9JLHFU Description: The previous system shutdown at 7:53:06 PM on ?10/?1/?2017 was unexpected.[/quote] Code: Event[11131]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-10-01T19:56:21.118 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-T9JLHFU Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote]

 

The problem is, the crash only occurs when I am doing something GPU-intensive. It will not happen if I am just sitting idle. Therefore, the only way to try and get it to crash is to sit idle, and that may not prove anything.

I looked up that VIDEO_TIMEOUT error you mentioned earlier and it is related to the "TDR timeout" functionality built into Windows. This exact same crash (freeze up for a few moments with buzzing sound, then quiet) happened when I disabled the TDR timeout functionality. When it was enabled, it would crash and restart my driver, allowing me to continue using the computer.

Do you know how to enable this?

 

When using windows driver verifier you commented that you had an immediate crash.
If you can create more crashes there should be some bsod mini dump files to debugg.
There are already known problems with graphics.
Windows driver verifier should produce bsod mini dump files and when debugged they should indicate whether the drivers are problematic or not.

 

I ran HD Tune again and this test looks alarming. What does this indicate?

 

The HD tune test results indicated pass for both drives.
HD Tune Help

Were you able to run Sea Tools on each drive (post 7, #22)?
If so please post images of the results into the thread for SMART, short, and long generic for each drive.
Take Screenshot in Windows 10 General Tips Tutorials

Were you able to complete the chkdsk /x /f /r on the 2nd drive?
If available please post using the information in this link:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials



Have you been using Windows driver verifier?
Were there more bsod mini dump files?

Please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

And whenever there is a new bsod please post a new zip.