Windows 10 BSOD's - Driver problem or Hardware failure?

Hey there,

Ive been having blue screens for quite a while now and been trying to fix them myself but Ive decided it might be easier with some assistance.

Ive ran memtest86+ for a whole day and found no errors.
I ran prime95 and furmark for a couple of hours with no errors.

Ive also tried using Driver Verifier a long while back and removed any drivers that i saw causing problems but it still persisted. I was going to try Driver Verifier again but while i do that i thought it'd be wise to see if anyone can see something obvious or offer some assistance.

My debug file is attached.
[Removed]

Thanks.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Code:

2: kd> k
Child-SP          RetAddr           Call Site
ffffd001`c90f6788 fffff800`e917ca67 nt!RtlSplay+0x90
ffffd001`c90f6790 fffff800`e90b5e56 NTFS!NtfsFullDeleteLcb+0x47
ffffd001`c90f67c0 fffff800`e917cd1c NTFS!NtfsTeardownFromLcb+0x146
ffffd001`c90f6860 fffff800`e90aca80 NTFS!NtfsTeardownStructures+0xdc
ffffd001`c90f68e0 fffff800`e9164b5b NTFS!NtfsDecrementCloseCounts+0xd0
ffffd001`c90f6920 fffff800`e91a0182 NTFS!NtfsCommonClose+0x40b
ffffd001`c90f69f0 fffff802`7c4616a9 NTFS!NtfsFspCloseInternal+0x1a6
ffffd001`c90f6b80 fffff802`7c4f35a5 nt!ExpWorkerThread+0xe9
ffffd001`c90f6c10 fffff802`7c557626 nt!PspSystemThreadStartup+0x41
ffffd001`c90f6c60 00000000`00000000 nt!KiStartSystemThread+0x16


1: kd> k
Child-SP          RetAddr           Call Site
ffffd000`211ccd38 fffff801`bab74196 nt!KeBugCheckEx
ffffd000`211ccd40 fffff801`bab6b0c2 nt! ?? ::FNODOBFM::`string'+0x5396
ffffd000`211cd420 fffff801`bab697a1 nt!KiExceptionDispatch+0xc2
ffffd000`211cd600 fffff801`9ee937d3 nt!KiPageFault+0x221
ffffd000`211cd790 fffff801`9ee9292a NTFS!NtfsCreateScb+0xc23
ffffd000`211cd870 fffff801`9ee8fa23 NTFS!NtfsBreakBatchOplock+0xaa
ffffd000`211cd8e0 fffff801`9ee8f058 NTFS!NtfsOpenExistingAttr+0x93
ffffd000`211cd9b0 fffff801`9ee73ed6 NTFS!NtfsOpenAttributeInExistingFile+0x138
ffffd000`211cdb70 fffff801`9ee7638d NTFS!NtfsOpenExistingPrefixFcb+0x416
ffffd000`211cdc60 fffff801`9ee770c5 NTFS!NtfsFindStartingNode+0x45d
ffffd000`211cdd20 fffff801`9ee75efd NTFS!NtfsCommonCreate+0x425
ffffd000`211cdf50 fffff801`bab63047 NTFS!NtfsCommonCreateCallout+0x1d
ffffd000`211cdf80 fffff801`bab6300d nt!KxSwitchKernelStackCallout+0x27
ffffd000`eb9aaf30 fffff801`baa2fa61 nt!KiSwitchKernelStackContinue
ffffd000`eb9aaf50 fffff801`baa2f7d6 nt!KiExpandKernelStackAndCalloutOnStackSegment+0x131
ffffd000`eb9aafd0 fffff801`baa2f69f nt!KiExpandKernelStackAndCalloutSwitchStack+0xa6
ffffd000`eb9ab030 fffff801`9ee7a949 nt!KeExpandKernelStackAndCalloutInternal+0x2f
ffffd000`eb9ab080 fffff801`9d587895 NTFS!NtfsFsdCreate+0x1d9
ffffd000`eb9ab2a0 fffff801`9d5b62d7 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a5
ffffd000`eb9ab330 fffff801`bae33d68 FLTMGR!FltpCreate+0x347
ffffd000`eb9ab3e0 fffff801`bae2a6d6 nt!IopParseDevice+0x7c8
ffffd000`eb9ab5b0 fffff801`bae290dc nt!ObpLookupObjectName+0x776
ffffd000`eb9ab750 fffff801`bae16580 nt!ObOpenObjectByNameEx+0x1ec
ffffd000`eb9ab870 00000000`00000000 nt!NtQueryAttributesFile+0x180


1: kd> k
Child-SP          RetAddr           Call Site
ffffd000`22cf2108 fffff800`eb166196 nt!KeBugCheckEx
ffffd000`22cf2110 fffff800`eb15d0c2 nt! ?? ::FNODOBFM::`string'+0x5396
ffffd000`22cf27f0 fffff800`eb15b57d nt!KiExceptionDispatch+0xc2
ffffd000`22cf29d0 fffff800`2d28319a nt!KiGeneralProtectionFault+0xfd
ffffd000`22cf2b60 fffff800`2d286432 NTFS!NtfsFindPrefix+0xea
ffffd000`22cf2c60 fffff800`2d2870c5 NTFS!NtfsFindStartingNode+0x502
ffffd000`22cf2d20 fffff800`2d285efd NTFS!NtfsCommonCreate+0x425
ffffd000`22cf2f50 fffff800`eb155047 NTFS!NtfsCommonCreateCallout+0x1d
ffffd000`22cf2f80 fffff800`eb15500d nt!KxSwitchKernelStackCallout+0x27
ffffd000`23932f30 fffff800`eb021a61 nt!KiSwitchKernelStackContinue
ffffd000`23932f50 fffff800`eb0217d6 nt!KiExpandKernelStackAndCalloutOnStackSegment+0x131
ffffd000`23932fd0 fffff800`eb02169f nt!KiExpandKernelStackAndCalloutSwitchStack+0xa6
ffffd000`23933030 fffff800`2d28a949 nt!KeExpandKernelStackAndCalloutInternal+0x2f
ffffd000`23933080 fffff800`2c9f7895 NTFS!NtfsFsdCreate+0x1d9
ffffd000`239332a0 fffff800`2ca262d7 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a5
ffffd000`23933330 fffff800`eb425d68 FLTMGR!FltpCreate+0x347
ffffd000`239333e0 00000000`00000000 nt!IopParseDevice+0x7c8

To make the file system scan part a bit more complete

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Good, keep me posted on the situation :)

Software tests aren't 100% proof, running a test doesn't rule it out 100% unfortunately.

Glad to hear your problem is solved :)