Planning

1. Right click on csgo.exe (in c:\program

files\steam\steamapps\common\Counter-Strike Global offensive), select
properties, then select Unblock
There will be this message:
"This file came from a another computer and might have been blocked to
help protect this computer." and a unblock button.
Press the unblock button, and then close the properties page. You might have
to accept a UAC dialog first.
Reopen the properties dialog and the unblock button should be gone. Now
csgo has full computer access.
2. POSSIBLE FIX !!for application blocked from accessing graphics hardware,
when i read a lot of people post about the problem on the net, they all have
one in common windows 8.1 , this has been the issue. Dont know would work
with u guys or not..But it finally solved the issue for me, i've tried everything,
resetting driver, clean unistall and install back the driver , downclock the gpu
and many other solution.. all not working, except for this one.

my solution is:
go to windows update, check for available updates. then i found update for
Microsoft .NET Framework 4.5.2. Which is before i only try reinstall the
Microsoft .NET Framework 4.5 . it seems to work well after that and i had no
more problem.
http://www.microsoft.com/en-sg/download/details.aspx?id=42642
3. i had this problem and fixed it
the only way i could fix it by downclock my graphic card
google how to downclock it
4. i downclocked "core clock" from 672 to 522
and " memory clock" from 900 to 600
my card is GetForce GT 540M
this is the setting i'm currently using and the second pic is the default setting

5. My buddy got the same problems. He resolved it by playing the Game in

window Mode and assigning dota.exe only to 2 Cores (2 physical cores, not
virtual cores like when you have a quadcore but 8 threads). Pressing the
tasgmanager and assigning while Dota loaded was sometimes impossible so
he googled a software which automatically assigns the 2 selected cores to
the dota2.exe
I will ask him later for the software but i think you will be able to google that
yourself.
6. i have been having the same problem 4 months till i came up with a fix.i just
put " -novid -nod3d9ex " this codes on my launch option.
7. https://www.youtube.com/watch?v=Jvqh2xPZbqw
8. https://www.youtube.com/watch?v=YpaVwpbFOdE
9. Matiin Anli Aliasing
10.Solutions for this issue and the "display driver/adapter has stopped working
but has recovered"
are related to differing issues for different users. Its like saying the steering
on your car doesn't work correctly, there are a bunch of different parts of the
steering that could cause it to happen.

This is that type of problem.

Some people have just had a driver issue, some change the Tdr value, some
a parameter value, some run a software in compatibility mode......In my case
it was RAM chips that tested ok, the RAM worked just fine on Windows XP all
flavors of Linux, but Windows 7 and above had this problem.
I tried different every fix you can find on the net, I also tried 3 different video
cards from 3 vendors, Nvidia and AMD ,swapped every component in my
system, MB, power supply, CPU, tested HD(fail, bad sectors) replaced, added
liquid cooling, tested ram with multiple Memtests....replaced then retired a
entire machine.
It wasnt until i was building a 4th machine for our home theater PC and i
grabbed the RAM from the retired PC to find the same issue. I replaced that
RAM(on the recommended list from MB mfg)with RAM from one of my hi end
machines that had RAM that was not recommended, but didnt have what
ever flaw that RAM had, no issues.
I have since bought new RAM for the retired PC, that isnt recommended for
the MB, (rated up to 1600, using 2400)
and now the retired PC is fine, a 1 year issue, has been working fine for 8
months since.
So with these errors you dont know what the fix is, at least they dont know
yet, but it is narrowed down to being something in Windows 7 and above, its
not your hardware.
In my case all other OS,s worked fine.

TO ANY ONE WITH THIS ERROR, or the error "display adapter/driver has stopped
working but has recovered"If you have had this problem for a while and are fed
up, I would like to test something hardware wise.
Memory is cheap. try buying some new memory, approved for your mother
board, faster than the memory you currently have though. and let us know what
happens, try for a couple weeks.
Even though you could run memtest86 and it shows your memory to be ok.
My memory tested fine also.
I rebuilt a entire system twice over with all different hardware to find it was
memory, that was approved for my motherboard, and tested fine. but had some
issue.
I have seen similar fixes on the net, so please lets give this a try.

Anyone?