Memory Corruption

The chkdsk fixed errors in the volume bitmap.
The HD tune passed.
The memtest86+ version 5.01 test passed with 16GB ram with 8 passes.

Windows error reporting indicating that the Nvidia graphics card was related to the bsod.
This may be confirmed in the memory dumps.

Post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

And post a memory dump using a one drive or drop box share link:

memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP


Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

Code:

9/25/2017 3:43 AM    Windows Error Reporting    Fault bucket BAD_DUMPFILE, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: aef994ea-6575-4dda-b329-4685e926d3fd

Problem signature:
P1: 141
P2: ffff8f8cf8689270
P3: fffff8017619f44c
P4: 0
P5: 2ac
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2138.dmp
\\?\C:\Windows\Temp\WER-692355500-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C98.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CAC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CEC.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_862ae42fdb78c430f1bfbc45ed2f12c5b6b5e6_00000000_cab_1a66ec3a

Analysis symbol: 
Rechecking for solution: 0
Report Id: af2a67e7-eca8-4f9c-a08a-2e3e92a8612b
Report Status: 268435556
Hashed bucket:9/25/2017 3:35 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 7dd5ba3f-4b70-4fb6-8446-ab5fc4a83b38

Problem signature:
P1: 141
P2: ffff8f8cf9a074a0
P3: fffff8017619f44c
P4: 0
P5: 2ac
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2134.dmp
\\?\C:\Windows\Temp\WER-692167250-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADEA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADEA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAE59.tmp.txt
\\?\C:\Windows\Temp\WER5B13.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4fafbdb044df1ac0ee96bd317afaf87afb6256_00000000_cab_b76e5bfd

Analysis symbol: 
Rechecking for solution: 0
Report Id: b25275f9-f64a-47ed-bd72-800c9d829a9e
Report Status: 268435456
Hashed bucket:
9/25/2017 3:27 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 8de148a4-4f81-44dd-bc68-2c9f7fd6ae8d

Problem signature:
P1: 141
P2: ffff8f8cf9b914a0
P3: fffff8017619f44c
P4: 0
P5: 37e28
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2127.dmp
\\?\C:\Windows\Temp\WER-691731906-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER89F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8AF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8DF.tmp.txt
\\?\C:\Windows\Temp\WER4943.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_958d347cfec487bbe64f4bb2cc344e0c538e6c8_00000000_cab_afff49de

Analysis symbol: 
Rechecking for solution: 0
Report Id: 7283ca0a-e642-4f88-ad8f-6be8de51b42e
Report Status: 268435456
Hashed bucket:
9/25/2017 3:32 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 97471d2d-2300-41c9-b018-4dc531c509ae

Problem signature:
P1: 141
P2: ffff8f8ce05e44a0
P3: fffff8017619f44c
P4: 0
P5: 39f48
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2130.dmp
\\?\C:\Windows\Temp\WER-691929796-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73C6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7500.tmp.txt
\\?\C:\Windows\Temp\WERC2E9.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_114382d540bef6aef1b7c83c1b403a2a98fe68ca_00000000_cab_88e2f90b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 25d7c322-ebc5-4707-b549-b080faac3e59
Report Status: 268435456
Hashed bucket:
9/25/2017 3:28 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: dceb8a31-10cb-4121-9ddc-8db56af392ea

Problem signature:
P1: 141
P2: ffff8f8cf992d4a0
P3: fffff8017619f44c
P4: 0
P5: 2ac
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2128.dmp
\\?\C:\Windows\Temp\WER-691765968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A71.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A73.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A94.tmp.txt
\\?\C:\Windows\Temp\WERDA38.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_211b6cd1fba98749679594e5a436f34c96127e7_00000000_cab_b33bdad4

Analysis symbol: 
Rechecking for solution: 0
Report Id: 918aeee4-21e1-4901-a08d-3c5304d7b080
Report Status: 268435456
Hashed bucket:
9/25/2017 3:29 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: e4967517-4538-4db8-b33d-51cf86b1f6d4

Problem signature:
P1: 141
P2: ffff8f8cf8d164a0
P3: fffff8017619f44c
P4: 0
P5: 4
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2129.dmp
\\?\C:\Windows\Temp\WER-691836812-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA112.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA127.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA157.tmp.txt
\\?\C:\Windows\Temp\WERB17.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b86c562de2ebcacc3e2f54d344c451a3b53446a_00000000_cab_ae690bb2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 806f8092-8846-479b-96aa-2dac1b91b79d
Report Status: 268435456
Hashed bucket:
9/25/2017 3:43 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: f3e24553-fee4-4c2b-a4a7-4b2f4db67df1

Problem signature:
P1: 141
P2: ffff8f8cf8689270
P3: fffff8017619f44c
P4: 0
P5: 2ac
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170924-2138.dmp
\\?\C:\Windows\Temp\WER-11203-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3895.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3896.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38A7.tmp.txt
\\?\C:\Windows\Temp\WER237A.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_862ae42fdb78c430f1bfbc45ed2f12c5b6b5e6_00000000_cab_1a672404

Analysis symbol: 
Rechecking for solution: 0
Report Id: b1c9c051-3296-4241-8235-25e2a2e4b8e3
Report Status: 268435556
Hashed bucket:
9/17/2017 3:19 AM    Windows Error Reporting    Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_0000_DEV_0000_REV_0000, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 2782298a-bff2-4db8-bfd3-b092d61c874f

Problem signature:
P1: 144
P2: 3003
P3: ffffb6811c546838
P4: 4001001a
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\USBHUB3\USBHUB3-20170916-2118.dmp
\\?\C:\Windows\Temp\WER-18375-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52B3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52B3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52C4.tmp.txt
\\?\C:\Windows\Temp\WER7CF1.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_bad67c51211e52b607df28f9081d56f1639884_00000000_cab_1a787e28

Analysis symbol: 
Rechecking for solution: 0
Report Id: 85582bfc-59cf-45d7-9f6f-e14c705da31c
Report Status: 268435456
Hashed bucket:
8/14/2017 7:51 PM    Windows Error Reporting    Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_0000_DEV_0000_REV_0000, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 4ae59d7c-18de-481b-b131-b003da190055

Problem signature:
P1: 144
P2: 3003
P3: ffff8b81021f0838
P4: 40010000
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\USBHUB3\USBHUB3-20170814-1350.dmp
\\?\C:\Windows\Temp\WER-5703-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2470.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2470.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24B1.tmp.txt
\\?\C:\Windows\Temp\WER76AB.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_cb7975a9ddd566407a3a8a6369f7a936ef9d27_00000000_cab_19907733

Analysis symbol: 
Rechecking for solution: 0
Report Id: bfdded85-27cb-498a-af2a-46824ceae386
Report Status: 268435456
Hashed bucket:
8/14/2017 7:51 PM    Windows Error Reporting    Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_0000_DEV_0000_REV_0000, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: b7b03f69-75ad-4e9d-91d4-d63c615b5da1

Problem signature:
P1: 144
P2: 3003
P3: ffff8b81021f0838
P4: 40010000
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\USBHUB3\USBHUB3-20170814-1350.dmp
\\?\C:\Windows\Temp\WER-5468-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2471.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2471.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24B0.tmp.txt
\\?\C:\Windows\Temp\WER59C9.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_cb7975a9ddd566407a3a8a6369f7a936ef9d27_00000000_cab_19905a83

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6be44746-bfab-40ff-b24d-51b7e4cb6ead
Report Status: 268435456
Hashed bucket:
9/2/2017 3:43 AM    Windows Error Reporting    Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_05E3_DEV_0610_REV_9223, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 95aef282-e3c6-4d1a-a3d8-a041e19b4086

Problem signature:
P1: 144
P2: 3003
P3: ffffb28009375838
P4: 40010000
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\USBHUB3\USBHUB3-20170901-2143.dmp
\\?\C:\Windows\Temp\WER-286533421-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DF4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DF4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E14.tmp.txt
\\?\C:\Windows\Temp\WER4D93.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_e1b15f12f1cc54cdffbd1b7b7ca0e039de78ad_00000000_cab_644c4e5d

Analysis symbol: 
Rechecking for solution: 0
Report Id: e7a275ae-b699-4a8d-929e-9b756580f4b1
Report Status: 268435456
Hashed bucket:
9/25/2017 3:43 AM    Windows Error Reporting    Fault bucket LKD_0x1A1_WIN32K_CALLOUT_WATCHDOG_nt!IopLiveDumpEndMirroringCallback, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 5a0d0043-3330-4a75-aa42-4e2a3978ac15

Problem signature:
P1: 1a1
P2: ffff8f8ceda9b040
P3: 0
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20170924-2136.dmp
\\?\C:\Windows\Temp\WER-11203-0.sysdata.xml
\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20170924-2136.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3865.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3875.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3885.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_4a7f804bb1412f51283238892e0cff1f25d6d4_00000000_cab_1a6713d7

Analysis symbol: 
Rechecking for solution: 0
Report Id: a92e62ab-b69a-4a6e-adcc-62800794d57d
Report Status: 268435556
Hashed bucket:

Code:

9/25/2017 3:43 AM    Windows Error Reporting    Fault bucket 0x133_DPC_bthport!HCI_IdleTimerDpc, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 2ae25653-291e-434b-a580-40ab6a00dded

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff803d27f6348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\092417-6968-01.dmp
\\?\C:\Windows\Temp\WER-11203-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38B5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38C7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38C8.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_a4a538952dbbc8bd916d7a68f5f169bf9d4351_00000000_cab_1a675778

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3c4029cf-5f4d-476c-b360-66f378725b15
Report Status: 268435456
Hashed bucket:9/29/2017 3:48 AM    Windows Error Reporting    Fault bucket 0x19_d_nt!ExDeferredFreePool, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 66dec8b2-f840-409a-a91b-bfe4827bc13f

Problem signature:
P1: 19
P2: d
P3: ffff930478d87fff
P4: 5c709521c2b91e67
P5: e45c709521c246e1
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\092817-5359-01.dmp
\\?\C:\Windows\Temp\WER-6375-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER275E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER276D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER27AD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_19_585935e258d2369e580dcc8ec165c92beda86_00000000_cab_056eff84

Analysis symbol: 
Rechecking for solution: 0
Report Id: 69e142b8-0e2f-4b45-b223-10a820d49f0d
Report Status: 268435556
Hashed bucket:
8/29/2017 8:10 PM    Windows Error Reporting    Fault bucket 0x19_d_nt!ExDeferredFreePool, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 81f41e24-e575-42be-8409-d3f25f33cc3c

Problem signature:
P1: 19
P2: d
P3: ffffe48f76042fff
P4: d3ba885f92f18f67
P5: c0d3ba885f92ee70
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\082917-134781-01.dmp
\\?\C:\Windows\Temp\WER-135812-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER265A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER266A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26B9.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_19_b168f25fbc970ffbedb98ca248cfd4bd8b5323_00000000_cab_18ba3e18

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1d0ad034-9607-4d0d-b86a-678e872d717e
Report Status: 268435456
Hashed bucket:
8/14/2017 7:51 PM    Windows Error Reporting    Fault bucket 0x1a_5200_nt!ExAllocatePoolWithTag, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 55646a85-95c7-4d4d-bdf1-06319819b427

Problem signature:
P1: 1a
P2: 5200
P3: ffffb80617defff0
P4: beb02013c4a4
P5: a2557650cfd550b3
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\081417-4765-01.dmp
\\?\C:\Windows\Temp\WER-5703-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24CE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24D1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24E2.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_3cfd67e3939688cd8f623614a435f23045ec98ea_00000000_cab_1990aaf5

Analysis symbol: 
Rechecking for solution: 0
Report Id: c2b185c0-9c0d-460e-aac6-1933a5fea48b
Report Status: 268435456
Hashed bucket:
9/11/2017 4:26 AM    Windows Error Reporting    Fault bucket 0x1a_5200_nt!ExAllocatePoolWithTag, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 970103fe-5c0e-4c98-aed8-d410e6ad9462

Problem signature:
P1: 1a
P2: 5200
P3: ffffc489ba023ff0
P4: 0
P5: fb5660b60bf623d4
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\091017-6234-01.dmp
\\?\C:\Windows\Temp\WER-7500-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EE0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EEF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2F2F.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_6e1ee273d134e59c91abefc6852e0ca26fd98_00000000_cab_17a45bac

Analysis symbol: 
Rechecking for solution: 0
Report Id: 46ff7c4b-b180-4fbb-8ffa-25763ecbd70e
Report Status: 268435456
Hashed bucket:
10/6/2017 4:29 AM    Windows Error Reporting    Fault bucket 0xc4_2000_VRF_MpKslf7900685!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 1df41156-f7ef-43fd-87a2-06884945014c

Problem signature:
P1: c4
P2: 2000
P3: fffff809d5d1a25c
P4: 0
P5: 444c534b
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100517-5546-01.dmp
\\?\C:\Windows\Temp\WER-6078-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CCC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CDC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CED.tmp.txt
\\?\C:\Windows\Temp\WERFC49.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_c417a135952442fa22f73ab9f7b6311ad7805129_00000000_cab_04f3327b

Analysis symbol: 
Rechecking for solution: 0
Report Id: aa106d5a-835b-4562-9cf4-cd372ad95fd2
Report Status: 268435556
Hashed bucket:
9/17/2017 2:01 AM    Windows Error Reporting    Fault bucket 0xCFFFFFFF_IMAGE_NTFS.sys, type 0
Event Name: AppTermFailureEvent
Response: Not available
Cab Id: 4c8bc9d2-b104-4bcf-ab1f-5218b7644dd7

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Windows\Temp\WERCB48.tmpatk.kdmp
\\?\C:\Windows\Temp\WERCB59.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBA8.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC65.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCC74.tmp.txt
\\?\C:\Windows\Temp\WERCC75.tmp.xml
\\?\C:\Windows\Temp\WERE27B.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_00000000_cab_34a5e42f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 46e6cb16-0c6e-48a3-a44d-73a4967fa47d
Report Status: 268570624
Hashed bucket:
9/17/2017 1:23 AM    Windows Error Reporting    Fault bucket 0xCFFFFFFF_nt!DbgkpLkmdSnapThreadInContext, type 0
Event Name: AppTermFailureEvent
Response: Not available
Cab Id: c54f0c6b-d4c9-4fe1-b9e5-b91df7107e1e

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Windows\Temp\WERFD5E.tmpatk.kdmp
\\?\C:\Windows\Temp\WERFD6F.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFD70.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFE0D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFE0C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFE1D.tmp.txt
\\?\C:\Windows\Temp\WERFE1E.tmp.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_00000000_cab_3a11ff14\memory.hdmp
WERGenerationLog.txt
\\?\C:\Windows\Temp\WER1F9D.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_00000000_cab_292e20f4

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8a02ff8f-4d86-4a06-963e-7cabd116f67f
Report Status: 268566528
Hashed bucket:

Link for memory dump: MEMORY.DMP - Google Drive

New BSOD zip:
Attachment 157113

The event logs also indicate that you have had had problems with the Nvidia graphics card:

Code:

Event[9731]:  Log Name: System  Source: Display  Date: 2017-09-24T21:27:41.129  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: FAMILY-PC  Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[9732]:  Log Name: System  Source: Display  Date: 2017-09-24T21:28:15.193  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: FAMILY-PC  Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[9733]:  Log Name: System  Source: Display  Date: 2017-09-24T21:28:28.485  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: FAMILY-PC  Description: Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

Event[9736]:  Log Name: System
  Source: Display
  Date: 2017-09-24T21:29:26.033
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: FAMILY-PC
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

Event[9745]:  Log Name: System
  Source: Display
  Date: 2017-09-24T21:38:04.718
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: FAMILY-PC
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.


Event[9746]:
  Log Name: System
  Source: Display
  Date: 2017-09-24T21:38:04.718
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: FAMILY-PC
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.


The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.


If you 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

Code:

Name    NVIDIA GeForce GT 730PNP Device ID    PCI\VEN_10DE&DEV_0F02&SUBSYS_8A9F1462&REV_A1\4&23E0F855&0&0008
Adapter Type    GeForce GT 730, NVIDIA compatible
Adapter Description    NVIDIA GeForce GT 730
Adapter RAM    (2,147,483,648) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumd.dll
Driver Version    22.21.13.8205
INF File    oem59.inf (Section002 section)
Color Planes    Not Available
Color Table Entries    4294967296
Resolution    1680 x 1050 x 59 hertz
Bits/Pixel    32
Memory Address    0xF6000000-0xF6FFFFFF
Memory Address    0xE8000000-0xEFFFFFFF
Memory Address    0xF0000000-0xF1FFFFFF
I/O Port    0x0000E000-0x0000E07F
IRQ Channel    IRQ 16
I/O Port    0x000003B0-0x000003BB
I/O Port    0x000003C0-0x000003DF
Memory Address    0xA0000-0xBFFFF
Driver    c:\windows\system32\driverstore\filerepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvlddmkm.sys (22.21.13.8205, 13.79 MB (14,456,912 bytes), 5/19/2017 6:04 PM)

Please update the computer 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 General Tips 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

I built the computer, so there isn't a manufacturer to go to. I can reinstall the nvidia drivers though. I just checked and it says I have the latest driver. But if you think it will help I can reinstall them. What does this have to do with the memory corruption? That event didn't happen on one of the days that the computer crashed.

Where are you seeing memory corruption? In the windbg debugging?

Please update the system specs including psu, cooler, case, peripherals or anything attached to the computer by wireless or wired (mouse, keyboard, printer, headset, xbox, etc.)

Yes, when I looked at the dumps in windbg it said there was system memory corruption.

That is very common to see as so many dumps are related to memory.

The memory dump debugging has displayed a misbehaving driver

Code:

10/6/2017 4:29 AM    Windows Error Reporting    Fault bucket 0xc4_2000_VRF_MpKslf7900685!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 1df41156-f7ef-43fd-87a2-06884945014c

Problem signature:
P1: c4
P2: 2000
P3: fffff809d5d1a25c
P4: 0
P5: 444c534b
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100517-5546-01.dmp
\\?\C:\Windows\Temp\WER-6078-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CCC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CDC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CED.tmp.txt
\\?\C:\Windows\Temp\WERFC49.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_c417a135952442fa22f73ab9f7b6311ad7805129_00000000_cab_04f3327b

Analysis symbol: 
Rechecking for solution: 0
Report Id: aa106d5a-835b-4562-9cf4-cd372ad95fd2
Report Status: 268435556
Hashed bucket:

Our database of drivers indicate that this misbehaving driver(MpKslf7900685+0xa25c) and is related to Microsoft security essentials.

MpKslf0642d99.sys	May be dynamic update driver for Microsoft Security Essentials	Unknown driver from this post: http://www.sevenforums.com/crashes-d...riends-pc.html or Windows Update
MpKslf2699e70.sys	May be dynamic update driver for Microsoft Security Essentials	Unknown driver from this post: http://www.sevenforums.com/crashes-d...-7-32-bit.html or Windows Update
MpKslf75fbf8c.sys	May be dynamic update driver for Microsoft Security Essentials	Unknown driver from this post: http://www.vistax64.com/crashes-debu...-warcraft.html or Windows Update
MpKslfc8f3df7.sys	May be dynamic update driver for Microsoft Security Essentials	Unknown driver from this post: http://www.sevenforums.com/crashes-d...ml#post1215803 or Windows Update
MpKslfdeeb78f.sys	May be dynamic update driver for Microsoft Security Essentials	Unknown driver from this post: http://www.sevenforums.com/crashes-d...-problems.html or Windows Update

Since you are using Windows 10 it has Windows defender and it is currently unclear how this could relate to Microsoft security essentials.
And in most cases Windows updates fixes misbehaving Microsoft drivers.

So you could perform an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

First though perform the following steps:
1) perform windows updates and post any failed KB# with error code.
2) Open administrative command prompt and type or copy and paste:
3) sfc /scannow
4) dism /online /cleanup-image /restorehealth
5) 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


In the earlier posts there was 1 HD tune and 1 chkdsk result.
Please post HD tune results and chkdsk /x /f /r for all of the drives.

Please make images and post the results into the thread.

Run Sea tools for windows on your drive using SMART, short and long generic tests:


How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
http://www.seagate.com/support/downloads/seatools/

Yeah, I'm still working on the other hard drives, the second one hasn't finished yet. I did ask a question regarding them though, hdtune only reports them as 2199G, but they are larger than that. So, is it going to help if it doesn't look at the whole drive? Since I'm in the middle of still running hdtune, I'm not going to be able to do all the other things you requested. I'm only on my second drive, and it has been running for over 2 hours and still has quite a bit to go. So, that, plus the rest of my drives are going to take a long time. Since updates might require a reboot, I'm going to have to at least wait until the current one will finish. Which of all these things is more helpful to run first? You just requested me to do quite a few things, if there is an order that is more preferred, please let me know.

What specifically are you looking for? This doesn't feel very directed to what is in the minidmps. I'm just trying to figure out how everything you're asking me to do is related.

There is nothing critical in the order as you are having infrequent dumps.
Sometimes unexpected bsod can interfere with testing.
As long as that does not happen you can proceed as you are with the troubleshooting steps.
For the HD Tune I am not familiar with that particular issue and will await the results.

It is very common that windbg displays memory corruption.
Many times we will run RAM testing to rule in/rule out hardware problems.
There are no memory problems with the RAM as per Memtest86+ version 5.01 testing.
The Windbg has found a misbehaving driver.
Sometimes our database is incompleted and needs to be updated.
So at this time it is unknown what it is and how to fix it.

Code:

10/6/2017 4:29 AM    Windows Error Reporting    Fault bucket 0xc4_2000_VRF_MpKslf7900685!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 1df41156-f7ef-43fd-87a2-06884945014c

Problem signature:
P1: c4
P2: 2000
P3: fffff809d5d1a25c
P4: 0
P5: 444c534b
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100517-5546-01.dmp
\\?\C:\Windows\Temp\WER-6078-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CCC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CDC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CED.tmp.txt
\\?\C:\Windows\Temp\WERFC49.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_c417a135952442fa22f73ab9f7b6311ad7805129_00000000_cab_04f3327b

Analysis symbol: 
Rechecking for solution: 0
Report Id: aa106d5a-835b-4562-9cf4-cd372ad95fd2
Report Status: 268435556
Hashed bucket:

Code:

0: kd> lmvm MpKslf7900685start             end                 module name
fffff809`d5d10000 fffff809`d5d1e000   MpKslf7900685   (no symbols)           
    Loaded symbol image file: MpKslf7900685.sys
    Image path: \??\C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{4F5AA15D-E7F5-4906-80BF-4878992A0727}\MpKslf7900685.sys
    Image name: MpKslf7900685.sys
    Timestamp:        Tue May 19 20:50:37 2015 (555BE86D)
    CheckSum:         0000D1AA
    ImageSize:        0000E000
    File version:     1.2.1003.0
    Product version:  1.2.1003.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Malware Protection
    InternalName:     KSLDriver
    OriginalFilename: KSLDriver.sys
    ProductVersion:   1.2.1003.0
    FileVersion:      1.2.1003.0
    FileDescription:  KSLDriver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

I just checked for updates, the only update it shows is:
2017-09 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4040724)

I've got it downloading.