Several different BSOD errors

essenbe said:

Just so you understand, we can't find anything causing your problems. It is looking more and more like a hardware problem, and could very well be the graphics card. It could be the graphics card could be bad, The motherboard PCIe slots could be not working right, or it could be the PSU is not big enough. The best testing scenario would be a similar power consuming card to test, just so we could determine if it is the card or motherboard. If that doesn't work, try a lower power draw card. If you could arrange it, the best test would be if one of your friends would swap cards with you. Test your card in his computer and his card in your computer. I think you can see the logic there. We are just trying to find the root cause.

Fair enough, I understand this has been a large process of elimination test. I'm going to just bring it into a computer repair shop; my friends either don't have a spare card or are unwilling to let me use their main card for the swap.

Thank you, essenbe and Arc for your help. I will post the solution/problem for others once they've figured it out.

essenbe said:

Can you borrow a spare card? I hate for you to spend money for something we could rule in or out fairly easily. If you decide to take it to a computer Shop, I hope you will let us know the results.

As I said no one will let me borrow their card, so I'm kinda stuck with going to a shop. I will post here to let you know.

Wow, so they ran diagnostics on it and said that it was fine. They also realized my CPU fan was not set properly, so they cleaned it and re-added thermal paste, and set the CPU fan properly. For some reason it's even worse now. I am attaching the dump files just from this past 40 minutes. Overwatch now won't even play, it freezes before I can do anything, and now I'm getting 2 errors, VIDEO_TDR_FAILURE, and THREAD_STUCK_IN_DEVICE_DRIVER.

essenbe said:

Did you run memtest86+ again? Also, make sure your system is configured to create small memory dumps. This will show you how.

So I took it back to the repair guy, and after doing more testing, he said that the graphics card was overheating, and it was not able to rest properly because the heat sink on the MOBO blocks it from "clicking" into place. I'm going to get it refunded/replaced by XFX under warranty.

However, I still got some weird BSODs tonight, sans graphics card. The errors without graphics card are from June 2 2016. What could possibly still be causing these BSODs?

essenbe said:

Please upload the BSOD Posting instructions BSOD - Posting Instructions - Windows 10 Forums. Upload them here. This will tell you how Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.

I will take a look at the files. if you are still having BSODs after removing a supposed faulty graphics card, I would be suspect of what the computer shop told you. If you have removed the problem, you shouldn't still be having the same issues. That is only logic. Also, didn't we monitor the Graphics card temps before? Plus, another card will still have the same space issues, if that was in fact a problem.

The temps were around 79° in the store, granted the case was open and the store was extremely cool. When I ran it at my place, the card was at 83° after a minute, and were continuing to increase. I stopped it before damaging the card...didn't want it to get to 90 or higher. I think there is some validity to it running hot in my small case.

I did see him trying to put in the card, and it does not "click" like the test card he used, so it doesn't fit due to the heat sink so close by. It seems like most of the pins are in, but it can't lock so that may cause concern.


The BSODs from May 31 and June 1 are from the repair guy with the gfx card in. "pci.sys", "memory_corruption" "dxgkrnl.sys" for another,. The June 1 at 21:00 is me, and it says "memory_corruption". It was a PAGE_FAULT_IN_NON PAGED AREA BSOD
The two June 2 BSODS are memory_corruption and "dxgmms2.sys" which I think is DirectX, PAGE FAULT IN NONPAGED AREA and SPECIAL POOL MEMORY CORRUPTION (while running driver verifier). I know the repair guy used a Nvidia 610 so maybe there are still drivers from the card on the computer??

It's weird, my RAM has passed the memtest about 3 times now but I keep getting the error. Could RAM be faulty but still pass that test? Can a SDD, CPU or MOBO cause a memory_corruption error? I'm really at a loss here.

essenbe said:

Grenburrito, I am beginning to be at a loss as well. The answer to could any of those things cause it is yes, they all could. I am going to ask you to do a couple of things. We may have done them before, but lets try again.
Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

If that works, could you get your computer guy to loan you some known good working ram and replace the ram you have installed with what he gives you. Hopefully, that may answer the question about ram. You could even run with just 1 stick just for a test.

Ran sfc, had no integrity violations.

I have tested my RAM sticks and lo and behold, one is defective. I have had my graphics shipped to California for a warranty repair/replacement... here's to hoping that it was defective too and they replace it with a 8gb RX 480