I have ran memtest86 twice, Windows Memory Diagnostic and Intel Extreme Tuning Utility tests once with no faults or errors found.

All commands in Command Prompt were ran using Admin Privileges.

Hardware: http://pastebin.com/Kr09ZMVQ


I have been using Windows 10 Pro. 64-bit (upgraded from Windows 7 Pro. 64-bit) for the past month and I have had endless amounts of blue screens. After investigating, I have narrowed the issue to the boot SSD, but I haven't been able to actually fix it.

I downloaded the associated software for my SSD, Samsung Magician, which allowed to enable something called "Over Provisioning," which delayed the blue screens for about six or seven hours.

It also comes with a S.M.A.R.T. analyzing tool, the results of which can be seen here: Imgur, as you can see, it's all good.

Except every, single, time I run sfc /scannow, it always tells me that I have corrupt files and was unable to fix them.

In the image, it tells me that it gave me a log showing me all the files it couldn't fix, which you can see a partial of here, and a full one here. A quick glance shows that there's a lot of wrongful and double ownership errors.

I tried another solution, which was running Dism /Online /Cleanup-Image /RestoreHealth, but that only gave me this: Error: 1726 \ The remote procedure call failed, and this log. Apparently people have been solving this problem by closing whatever application('s) is running "dxgi.dll" and figuring that out by running Process Explorer, and it tells me that one of programs running "dxgi.dll" is Windows File Explorer.

Update: Closing every application running "dxgi.dll" and rerunning the Dism string above didn't solve anything, it result with the same 1726 error.

Someone please help me, I've had these incredibly arcane problems annoy the bejesus out of me for quite some time, and I have no idea where to go from here :/


  • After looking at some of your dump files, I saw the 3b blue screen was semi common. I had a problem with that a while ago. Memtest86 only once showed one error. I then ran Memtest several times again and nothing happened. I reseated the RAM and it stopped the BSOD. It was weird because the RAM was installed for several months before it started to happen. As far as the SSD, have you used something like CrystalDiskInfo to check the health of the disk? It could be possible that it has gone bad. Let us know what CrystalDisk says. – DrZoo Aug 20 '15 at 4:32
  • I thought of another thing. If you let the computer idle, will it BSOD too, or does it only do this when you are doing something? – DrZoo Aug 20 '15 at 4:36
  • @DrZoo Thank you for the reponse! I tried reseating the RAM awhile to the alternate channel, but the computer would go through many restarts and would usually stop at CPU initialization before restarting again (motherboard has a mini-basic LED display). I will run CrystalDiskInfo and return the results. – IfOnlyIHadAGoodUsername Aug 20 '15 at 4:37
  • @DrZoo It's pretty rare for it to BSOD when idle, most times it happens is at startup consecutively about 2-3 times before remaining stable for awhile. Sometimes when I exit an application, it BSODs, and others are during gameplay. – IfOnlyIHadAGoodUsername Aug 20 '15 at 4:39
  • This may be a long shot, but it could be a faulty PSU that is causing some of this. If it's not producing enough power for some reason it could very likely be a culprit of your troubles. After all, you do have a lengthy dump collection. – DrZoo Aug 20 '15 at 4:41

I just had almost an identical problem on my samsung 840 pro 512gb ssd. What I did to fix it was did a fresh install of windows 10. But even after that I were still getting random bluescreens multiple times daily and it is extremely FRUSTRATING!!! So in a last ditch effort I OVERCLOCKED my cpu and I havent had a hiccup since. I didnt mess with any voltages or anything (yet) all i did was increase the multiplier and am sitting at a stable 4.3ghz and the OS is more responsive as well. It has been 4 days and I havent had a single bluescreen or hiccup.

  • i also want to add that the bluescreens i were getting were because of random dll's. sfc /scannow always returned fine. But if you have upgraded to windows 10, you can now reinstall fresh from scratch. – james28909 Aug 29 '15 at 16:54

i think i solved the situation guys. first disable superfetch and prefetch. also disable indexing . u can search online on how to do that.

what happens is the there is memory bug somehow and the prefetch and superfetch is eating ram and cpu cycles more and more until it overflows giving you the blue screen of death... if you have ssd you dont need indexing prefetch and superfetch .

  • 2
    I promise you there isn't a memory leak superfetch and prefetch.... – Ramhound Apr 22 '16 at 23:19
  • @Ramhound I actually finally figured out the problem. So I pulled out both my RAM sticks and found that the contacts on one of them was covered in some black soot-thing? Whatever it was, it damaged the contacts, so I got new sticks of RAM and it works fine now. The RAM contacts in the motherboard may require cleaning later, but alright for now. I still don't understand how Memtest86 didn't pickup on that though. Also thanks you guys for still trying to fix this. – IfOnlyIHadAGoodUsername Apr 24 '16 at 3:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.