Error on new Graphic card (R7-240)

[human1969]

Hello,

I install my new Gigabyte R7-240 vga card and i am getting the below error intermittently.
"Display Driver Stopped Responding and Has Recovered Error".

I have already tried several driver version, but did not resolve the above error.
Understand from googling this error occurs when Timeout Detection and Recovery (TDR) feature detects that the graphics card (GPU) does not respond within a period of time

One observation,
The card GPU/Mem Clock read back is at 300/300MHz, even when i am playing multiple 720p video on my vlc player. (according to both GPU-Z & CCC)
Only certain task like running Win Experience Index or FurMark than the GPU/Mem max out 760/760MHz (my CCC setting).
Is this normal ?

I am thinking to update the VGA card bios first,
Anyone used the Gigabyte Vga Utility successfully before ?
The only time i use such utility (other than dos-based), the utility brick my card.

If not safe, than i will try increase the tdr timing in RegEdit.


Thanks

 

[wwenze]

Exchange with the shop

 

[ZrE0_Cha0s]

base on your issues, most probably the gpu is faulty. or worse is the mobo

 

[human1969]

Bought from amazon, lazy to RMA.
Other than this error, so far so good.

Was using a previous card (HD6450) and iGPU (i7-6770) without any problem, dont think its the MB.

 

[Encrypted11]

Hello,

I install my new Gigabyte R7-240 vga card and i am getting the below error intermittently.
"Display Driver Stopped Responding and Has Recovered Error".

I have already tried several driver version, but did not resolve the above error.
Under from googling this error occurs when Timeout Detection and Recovery (TDR) feature detects that the graphics card (GPU) does not respond within a period of time

One observation,
The card GPU/Mem Clock read back is at 300/300MHz, even when i am playing multiple 720p video on my vlc player. (according to both GPU-Z & CCC)
Only certain task like running Win Experience Index or FurMark than the GPU/Mem max out 760/760MHz (my CCC setting).
Is this normal ?

I am thinking to update the VGA card bios first,
Anyone used the Gigabyte Vga Utility successfully before ?
The only time i use such utility (other than dos-based), the utility brick my card.

If not safe, than i will try increase the tdr timing in RegEdit.


Thanks

That's not faulty GPU. It's the VCE-UVD bug ever since AMD redone Media Foundation Transcoder as Advanced Media Framework Runtime as part of the GPU Open initiative.
On MFT, you get up to C State 5/7 (at least on polaris, other VCE 2-3 GPUs should have a similar behaviour) with hardware accelerated decode/encode.
On AMF, it will lock GPU clocks to 2d clocks and cause stability issues running H.264 content especially.
The 2d clock priority takes precedence over anything else even if you run a 3d game.

You need to run 16.7.2 WHQL or earlier drivers to avoid the current AMF runtime bugs.
Driver archive
http://support.amd.com/en-us/download/desktop/previous?os=Windows 10 - 64

 

[Encrypted11]

16.7.2 and earlier = MFT
16.7.3 and later = AMF

 

[human1969]

Thanks,

I only use Crimson v16.9.2 briefly,
somehow my PwrDvd8 always crash when opening BD movie on that driver.
Also note with PwrDvd8 running, the clk will lock at 842/800 regardless of OverDrive settings.

Most of my driver testing is btw v13.12 to v15.12.
Currently trying out v15-12, looks more normal/responsive.
You can see the GPU/Mem Clk moving btw 300/300 & 760/760.
With v13.12, its mostly struck at 300/300 except when i open OverDrive.

Anyway, if the Driver Crash error still appear,
i will try to increase the TdrDelay to 8s (ms website recommendation).

Still cannot, then try to update the vga bios.


Thanks

 

[Encrypted11]

Thanks,

I only use Crimson v16.9.2 briefly,
somehow my PwrDvd8 always crash when opening BD movie on that driver.
Also note with PwrDvd8 running, the clk will lock at 842/800 regardless of OverDrive settings.

Most of my driver testing is btw v13.12 to v15.12.
Currently trying out v15-12, looks more normal/responsive.
You can see the GPU/Mem Clk moving btw 300/300 & 760/760.
With v13.12, its mostly struck at 300/300 except when i open OverDrive.

Anyway, if the Driver Crash error still appear,
i will try to increase the TdrDelay to 8s (ms website recommendation).

Still cannot, then try to update the vga bios.


Thanks

Might wanna try 16.7.2. It's on the final MFT version before AMD flipped to AMF (includes 16.9.2)

 

[Entry Level PC]

maybe card spoil liao due to incompatible latest drivers?

 

[human1969]

Thanks,

Yah, will download few more version btw v15.12 to v16.7.2.
In case they cant by easily found later.

Btw,
Is it possible to use the MFT from older version,
and pair it with the newer version of Display driver.

(Install older version, then do a manual upgrade of the display driver only)

 

[Encrypted11]

Thanks,

Yah, will download few more version btw v15.12 to v16.7.2.
In case they cant by easily found later.

Btw,
Is it possible to use the MFT from older version,
and pair it with the newer version of Display driver.

(Install older version, then do a manual upgrade of the display driver only)

MFT is part of the display driver.
On implanting MFT, there are some workarounds like copying older hardware acceleration related .dlls of "working drivers" to implant on newer drivers (not familiar with this). Mileage will vary though. Some people (esp on guru3d forums) have been doing these workarounds for very long already.

I'm not into driver modding (implanting different ccc/crimson is the max I'd go). That's not expected behaviour imo. Just go for a fully working package than hacking a latest broken release to work.

Btw, AMD only really fully acknowledged the new AMF runtime's key stability issues this month on the october driver release notes. This will probably take awhile to fix, although the original intent was fixing AMF bugs and adding new RX 400 decode/encode features by december. I don't think they'll meet the eta.

 

[human1969]

MFT is part of the display driver.
On implanting MFT, there are some workarounds like copying older hardware acceleration related .dlls of "working drivers" to implant on newer drivers (not familiar with this). Mileage will vary though. Some people (esp on guru3d forums) have been doing these workarounds for very long already.

I'm not into driver modding (implanting different ccc/crimson is the max I'd go). That's not expected behaviour imo. Just go for a fully working package than hacking a latest broken release to work.

Noted...appreciate