Display driver AMD has stopped responding and has recovered

[Dragsooth]

Okay, I've tried everything to fix this issue. I can replicate the issue by opening a store page for a game on Steam. It will freeze up when trying to load the store video and then blackscreen for a second and give that error. I've reinstalled steam and it still happens. It just started recently after messing around with my overclock. I've deactivated my OC but I can still replicate the issue. Nothing I do seems to fix it.

I also recently enabled AMD Turbo Core Technology in my BIOS, could that be the cause?

Here's the Event Log data:

Log Name: System
Source: Display
Date: 3/4/2014 2:24:36 PM
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Dragsooth-PC
Description:
Display driver amdkmdap stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-03-04T19:24:36.000000000Z" />
<EventRecordID>134933</EventRecordID>
<Channel>System</Channel>
<Computer>Dragsooth-PC</Computer>
<Security />
</System>
<EventData>
<Data>amdkmdap</Data>
<Data>
</Data>
</EventData>
</Event>

 

[carwiz]

If your display drivers are up to date, this could be caused by over heating, AV software or other errant drivers. How old is the PC and when was the last time it was cleaned (dusted)?

 

[Dragsooth]

The highest my temps have gone up is 35c. PC is almost 2 years old, I've cleaned the filters a bit, but not inside yet. It isn't that dusty, I've opened it up when checking for extra cords. I also use Microsoft Essentials and I've had it way before this started to happen. Could I somehow damaged a thread on my GPU?

 

[smarteyeball]

Highly unlikely your GPU is damaged. And AMD Turbo Core Technology shouldn't affect your GPU. However have you since disabled this as well for elimination purposes?

It's not a temp issue either.

You mentioned it happened after overclocking, but you've since gone back to defaults.

A CPU overclock wouldn'y cause this error, but a GPU overclock would.

How did you overclock? BIOS, app etc? Did you double check that the GPU is back to stock settings?

 

[Dragsooth]

Highly unlikely your GPU is damaged. And AMD Turbo Core Technology shouldn't affect your GPU. However have you since disabled this as well for elimination purposes?

It's not a temp issue either.

You mentioned it happened after overclocking, but you've since gone back to defaults.

A CPU overclock wouldn'y cause this error, but a GPU overclock would.

How did you overclock? BIOS, app etc? Did you double check that the GPU is back to stock settings?

Okay, so after I disabled Turbo Core Technology, I can no longer reproduce this problem as before. Everything online I've read about TCT, says that it's best used if what you do doesn't require all of your cores, like if you have 6 cores and if you leave it idle alot... so I guess it disabled my cores and Win7 didn't give it enough to to reactivate it and that somehow affected my display...?

*UPDATE/EDIT* I received the error again after trying to watch a .wmv. Loaded a video in Windows Media Player and it froze then gave the error.

 

[smarteyeball]

As you discovered it doesn't have an impact. I didn't think it would, but it was worth a check.

Did you update your drivers at the same time too? if so, roll back to previous version.

If not - did you double check that the GPU is running at stock speeds again?

 

[Dragsooth]

As you discovered it doesn't have an impact. I didn't think it would, but it was worth a check.

Did you update your drivers at the same time too? if so, roll back to previous version.

If not - did you double check that the GPU is running at stock speeds again?

So I got a blue screen and I'm pretty sure they're related, I'll give a link to the thread. I am sure that my OC is disabled. http://www.sevenforums.com/bsod-help-support/323409-bsod-while-idle.html#post2711447