"application has been blocked from accessing graphics hardware"

Just put in upgraded ram, 2x 8 gb from same batch so i can put them in dual mode. but that doesnt seem to work either. I think my motherboard is kinda fried :S

I threw $$ at my problem, I tried every known software fix, then started to replace hardware. last piece of hardware I replaced was memory, because memtest, tested ok.  It did in fact end up being something with the memory.

What was strange was i used a module that was not recommended for my motherboard, motherboard was rated to DDR3 1600, I used DDR3 2400, no more issues.

I had given up on that rig and put it in the closet, I figured i would try one last thing, i put in a module from my new rig, and all was good.

Something else you can try that is interesting, make a bootable USB Linux,

http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows

boot from the USB and try Linux for a few days, Im sure you will notice no problems as I did.

Only help I can be is that I swapped out memory and it was fine, try it , memory is cheap, and you might keep your hair.

@ Justinreeves16,

i've been having several errors, ever since i have my new AMD r9 390

thing's i've already tried (without resolve)

-clean install latest gpu drivers (several times)

-turned off onboard gpu (in bios) (intel graphics hd on gigabyte sniper g1 b5)

-memtest (came out clean)

-reinstalled windows 

-installed windows on new harddrive

-upgraded power supply to 750w Gold

-Bios update

-in registry perform TdrDelay (set to 8)

-installed extra fan for cooling 

-tried with older videocard (geforce gtx 285, no issues what so ever)

even gotten a new GPU from manufacturer, did not resolve issue at all! (its not getting hotter then 70-75°C)

Could be 2 things now, either my motherboard is fried, especially the PCI slots, or my memory is just fcked up. 

I absolutely have no clue what causes this issue and im really close to pulling out my hair because i have been having this issue for almost 6 months now.

Does anybody else have an idea what could be the root cause of this issue?

added my dxdiag file

People, read the older posts, this problem has been happening since windows 7, Its not a "well since Windows 10"issue.

          I had this issue back in 2010 with release of Windows 7, had it in Windows 8, 8.1, and 10. issue on my machine was memory, it tested FINE but once replaced problem gone,

      I could put it back and recreate the problem instantly.

There are different reasons for this problem but don't get stuck on the "Its a Windows 10 issue, they will fix it soon" Not TRUE!

     This is a old (2009)problem that hasn't been fixed. And no one knows what it exactly is caused by or the multiple things that may causes it.

Try a more thoughtful suggestion - this is about as close to "reboot your machine and try again".  Every possible problem could be responded to with "update your drivers".