Windows 10: Graphics card crashing, nothing in Event Viewer

I did it on the larger drive. C: and D: are on it, and E: is on the smaller drive as a storage disk.

 

The HD Tune displays the results for Model WDC WD3200AAJS-65VWA0.
Can you also display the results for Model WDC WD30EFRX-68EUZN0
Run chkdsk /x /f /r on every drive c, d, e, etc. so that all partitions are scanned/fixed. (This can be done overnight)

 

I am working on it now, but it is an old drive so it is going extremely slow.

 

I downloaded and ran Whocrashed, but it did not find any dump files or detect any BSODs.

 

Please post an image of the startup and recovery settings before the changes.
Post the whocrashed results after the test crash dump.
And post a new zip after the crash dump test.
BSOD - Posting Instructions - Windows 10 Forums
These steps are to troubleshoot the setup of the crash dumps,

 

The bios version is 2501 from 2014.
Please check to see if there is an update.
If so please update the bios.

Please post an image of the startup and recovery settings before the modification.
Or report what were the prior settings and the changes.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials


Code: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: deaddead P2: 0 P3: 0 P4: 19a2a199 P5: 3c2a58ed P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\093017-24312-01.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA04.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA08.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA18.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_deaddead_e5ee701e776c6d5488e95de732e578f3c757d_00000000_cab_16490133 Analysis symbol: Rechecking for solution: 0 Report Id: 95b6e66a-a3cf-4c55-9d29-13e736d6d4b1 Report Status: 2049 Hashed bucket:10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffa00f249b8010 P3: fffff806c434f640 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170922-1121.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9A5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9B7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9C8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_6866b3e4fd9bb15bdd3c5ed552aab66da2d67ed6_00000000_cab_16490059 Analysis symbol: Rechecking for solution: 0 Report Id: d8d65d3e-7123-4e68-b3eb-49b092488001 Report Status: 2049 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffe38b84f60010 P3: fffff8037818f7f8 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2019.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF936.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF938.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF949.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4efb305bba85d7433f69a8919b6ce6bf479f9e7e_00000000_cab_1648ffbc Analysis symbol: Rechecking for solution: 0 Report Id: 1a9e0e68-cd74-4891-8270-5a178289f026 Report Status: 2049 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 117 P2: ffffdb05da057010 P3: fffff8063e4bf7f8 P4: 0 P5: 424 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2204.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF899.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8AA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8BA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_163a7b1251a6a21b82d10e3d91c3b5289ae32aa_00000000_cab_1648fef1 Analysis symbol: Rechecking for solution: 0 Report Id: 4cda707c-e20b-4161-a328-2483f646ca6a Report Status: 2049 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffdf08291a2450 P3: fffff8004a86f7f8 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2205.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF78F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7EC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF80D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e74ac0a85febe93a5b24957ba5651eba4c6a6d_00000000_cab_1648fd0d Analysis symbol: Rechecking for solution: 0 Report Id: 88f45091-619b-4e3d-958c-c7f89c405293 Report Status: 2049 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: deaddead P2: 0 P3: 0 P4: 19a2a199 P5: 3c2a58ed P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\093017-24312-01.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA04.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA08.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA18.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_deaddead_e5ee701e776c6d5488e95de732e578f3c757d_00000000_0354fa1f Analysis symbol: Rechecking for solution: 0 Report Id: 95b6e66a-a3cf-4c55-9d29-13e736d6d4b1 Report Status: 4 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffa00f249b8010 P3: fffff806c434f640 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170922-1121.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9A5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9B7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF9C8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_6866b3e4fd9bb15bdd3c5ed552aab66da2d67ed6_00000000_0354f9d1 Analysis symbol: Rechecking for solution: 0 Report Id: d8d65d3e-7123-4e68-b3eb-49b092488001 Report Status: 4 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffe38b84f60010 P3: fffff8037818f7f8 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2019.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF936.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF938.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF949.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_4efb305bba85d7433f69a8919b6ce6bf479f9e7e_00000000_0354f944 Analysis symbol: Rechecking for solution: 0 Report Id: 1a9e0e68-cd74-4891-8270-5a178289f026 Report Status: 4 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 117 P2: ffffdb05da057010 P3: fffff8063e4bf7f8 P4: 0 P5: 424 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2204.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF899.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8AA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8BA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_163a7b1251a6a21b82d10e3d91c3b5289ae32aa_00000000_0354f8b7 Analysis symbol: Rechecking for solution: 0 Report Id: 4cda707c-e20b-4161-a328-2483f646ca6a Report Status: 4 Hashed bucket: 10/1/2017 12:40 AM Windows Error Reporting Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 141 P2: ffffdf08291a2450 P3: fffff8004a86f7f8 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2205.dmp \\?\C:\Windows\Temp\WER-47515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF78F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7EC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF80D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_e74ac0a85febe93a5b24957ba5651eba4c6a6d_00000000_0354f80c Analysis symbol: Rechecking for solution: 0 Report Id: 88f45091-619b-4e3d-958c-c7f89c405293 Report Status: 4 Hashed bucket:[/quote]

 

I did post the image, it is on the last page

 

Were those the settings before the changes?
What modifications did you make?
There was only 1 new dump with Whocrashed and you ran it twice?
Were there any spontaneous crashes?

 

Are you sure the problem is not with my graphics card?

 

1)Yes
2)I turned off automatic restart
3)Yes
4)No

 

One of the problems is with the graphics card and that was indicated in post#5.
The problem will be troubleshooted.

The logs are displaying
141
117
Watchdog violations
etc.

 

Would it help to try a different graphics card?

 

Not yet.
The plan is
1) to fix and tune up the drives.
2) update the bios
3) backup all files
4) make a backup image using Macrium
Macrium Software | Your Image is Everything
5) place the backup image onto another drive or into the cloud
6) create a brand new restore point
7) use windows driver verifier to find misbehaving drivers
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials
8) fix misbehaving drivers by uninstalling/installing or updating
9) This will likely produce bsod related to the AMD graphics drivers
10) reevaluate the computer environment with new/updated drivers
11) possibly stress test GPU using Furmark
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials

So hd tune, chkdsk /x /f /r, on all drives, and bios update, need to be completed first.

Please read the above links on windows driver verifier so that you know 3 methods to turn off windows driver verifer using the Windows advanced troubleshooting menu.