Yo guys, before driving nuts i thought i might aswell share my story of me vs.. something in my PC.

the following, after a certain amount of time (especially fast while playing games) the display turns black for 2 secs, comes back and say's "AMD Driver didnt respond and was successfully restored."

what it effectively does: stops games for 2-3 seconds. HOWEVER, certain games seem to be killed by that. especially Civ 5, which doesnt respond anymore afterwards. 

what i did thus far; 

- tried every driver i could try. (properly deinstalling old ones.)

- changed the time the GPU has to respond. 

- cleared the system of EVERY driver, cleared CMOS and started all over.

- reinstalled Windows. (in both legacy and UEFI style, with diferent partition layouts.)

- checked voltages. (it seems that my Power supply is steadily holding up that 12V line judging from the BIOS)

- updated the BIOS. (with live update from MSI though.)

- tried to down/up windows updates.

- checked the RAM with some stressing program.

- checked temperatures. (My GPU runs at 59 degrees Celsius under full load, i tried running the fan at 100%, resulting in even lower temps)

-Hardcore Check for any kind of Malware with norton, kaspersky, avira. (of course not all at one.)

what i am doing right now; Overclocked the GPU running Unigine Heaven.

( i thought it was the newly added R9 270, HOWEVER when i put it back in the box for RMA the error started occuring with the INTEL HD Driver aswell, which didnt happen before. so iput the fucking card back in and declared war! )

i dont expect any help (i tested pretty much every thing i found on mister goggle, however ANY idea how to fix this is of course more than appreciated!) ut i just wanna share this disaster with someone. gotta keep yer updated. (:

edit: my system: Intel  Core i3-4130/4GB 1600 RAM/ 500W be quiet PURE POWER/MSI b85m-e33/HIS r9 270 Ice Q turbo x2 /WD BLUE 1TB

update 1: Unigine Heaven benchmarked all the way through without problems at around 40FPS with everything up to max at 1920x1080 (and YT video running in the back). funny: the GPU seems to be cooler when overlocked. dafuq. (56 degrees @1050/1500. was 59 with 975/1400)

*random thought: wanted to blame steam, however the error also occured with SWToR*

edit: i think i'll try the GPU in my bro's PC tomorrow, even though i am scared of ruining his rig aswell. :p (and he has only a 420 PSU. its a quality one, but still..)

edit 2: okay error also occured with Unigine now after roughly 10-15 minutes.

would be happy if they dropped their opinion in here then, i really dont want to bug you peeps though. its just that days worth of troubleshooting leaves a mark on mah bwainz. :) so i just really wanted to tell someone about this stuff. preferably people who actually own a PC.

but this shit is the reason i sticked to consoles so long. :DD ..(i remember now, hurrdurr. )

You will have to wait for amd's driver release. New video cards always have crummy drivers. Happens to nvidia to.Had that happen to me.

Did you OC your GPU ? What are the factory clocks ?

i did just now. (yeah.. i know..) however the error did occur on factory clocks. (975gpu/1400mem) as far as i know the card is factory OC'ed, the R9 270 is supposed to sit on a gpu clock of 950 or something

@bucky:

that sounds reasonable, what might be interesting though is that there are a lot of actually happy owners of a R9 270. (which is basically an old 7870)., and the beta drivers from AMD neither improved nor worsened anything.

A regular R9 270 is supposed to sit at 900 mhz core and 1400 mhz mem. Why don't you try these clocks. 

oh. ohohohoh. 900? gotta try that. :3 guess i oc'ed it quite a lot by putting it up to 1050 then. haha. thanks pal.

(i'll do so after updating my MB chipsetdrivers. doin' that rite now.)

Once your done come back and give me an update. 

Had this issue a while back. I updated my drivers and reinstalled DX and it stopped.