AMD Radeon R7770 TDR BSOD problem, please help

AValladares

Honorable
Feb 3, 2014
5
0
10,510
You guys have probably gotten this a lot in the past (having google searched and reaching this site many times) but I recently got an R7770 to replace my old GT440 and I just can't seem to get rid of this problem with the display driver stopping and restarting (atikmdag.sys) but still giving me a BSOD. It seems to be on a case by case basis, to list off a few games I play and specify if I get a BSOD during gameplay:

1) Phantasy Star Online 2 (only ever got it once and it stopped when I set CCC to force V-Sync systemwide)
2) TERA (as of this topic, this has only happened twice, barring the game's poor optimization for anything not in Korea's hardware range)
3) The Elder Scrolls V: Skyrim (Just about every session after some time)
4) F.E.A.R (ditto)
5) Dead Space 1 (BSOD on startup but even though CCC has V-Sync forced on my 60Hz monitor, Bandicam's FPS counter reads Dead Space going up as high as 900+ FPS before the whole thing implodes, this in particular concerns me) Dead Space 2 (nothing, perfect), Dead Space 3 (same, perfect)
6) Darksiders II (a BSOD occurred frequently at one particular location that CCC's V-Sync rectified, so this as far as I know, runs perfectly as of this writing)
7) Metal Gear Rising: Revengeance (perfectly fine)
8) Injustice: Gods Among Us and Mortal Kombat Komplete Edition (both run perfect, with SweetFX enabled for both)

When idle, the computer is just fine, it boots up fine, I can watch videos just fine, I can emulate as good as the emulator can get (PCSX2 in particular runs perfectly fine). Running MSi Kombustor shows the card at 40 C at rest and ~60 C when at 99% load for the past 30 minutes (somewhat steady 60fps, Direct3D 9 mode, Horus). I didn't OC anything at all from general paranoia. At most I use 4x MSAA on TERA with maybe 8x or 16x AF on the games that didn't trigger this BSOD. My system specs are:

AMD Radeon R7770 (MSi 1GB GDDR5 128-bit)
AMD FX 4100 Quad Core 3.6GHz
MSi 970A-G46
8GB RAM
Windows 7 Ultimate x64
Rosewill RG630-S12 630W PSU, 50A on the 12V rail (the R7770 says it needs 450W minimum, I went ahead and got it some extra juice from a brand I like)

I've updated my R7770's drivers several times, cleaning it completely via Safe Mode + Driver Sweeper, I updated my motherboard's BIOS yesterday, which aside from making the PC boot incredibly fast, didn't stop the BSODs. If anyone who can read through dumps wants, I have a dump file on hand and if you tell me which upload site this forum prefers, I'll upload it there and post. One thing peculiar about this is the first BSOD (PSO2) and various other ones concerning this driver happened around areas of the game with a lot of water. I'm not sure if that's relevant at all but whatever. I hope to get a response and hopefully some good news.

Thank you.
 
you can post the memory dumps on any cloud server with public access. (skydrive works)
you can also use automated tools like whocrashed.exe to sometimes get a idea of the crashing device driver.




 
basically windows directx sent a request to the graphics card, the graphics card driver never responded and directx determined that the graphics driver was hung and called a bugcheck.
- make sure you have all the current windows updates

- bug in the graphics driver. You have the current release version but they just put up a beta version on their website
I would give that a try. if it fails all you can really do is attempt to change the timing in your graphics card to the standard for that card (no overclock) and wait for a driver update from AMD.

debug info
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.22436.amd64fre.win7sp1_ldr.130828-1532



BugCheck 116, {fffffa8006c3a010, fffff880068d4d88, 0, d}
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006c3a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880068d4d88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.


3: kd> kc
Call Site
nt!KeBugCheckEx
dxgkrnl!TdrBugcheckOnTimeout
dxgkrnl!TdrIsRecoveryRequired
dxgmms1!VidSchiReportHwHang
dxgmms1!VidSchWaitForCompletionEvent
dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines
dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer
dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal
dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment
dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange
dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource
dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource
dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations
dxgmms1!VIDMM_GLOBAL::prepareDmaBuffer
dxgmms1!VidSchiSubmitRenderCommand
dxgmms1!VidSchiSubmitQueueCommand
dxgmms1!VidSchiWorkerThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread


Image name: dxgmms1.sys Timestamp: Tue Apr 09 20:27:15 2013
Image name: atikmpag.sys Timestamp: Fri Dec 06 12:21:45 2013
 

AValladares

Honorable
Feb 3, 2014
5
0
10,510
Tried the beta earlier, didn't last a second in 3dmark, it didn't even give a BSOD, it just made the computer hang completely. As I said in my first post, I didn't overclock a thing due to my own paranoia about this stuff lol. Would rolling back a driver or two help (or searching for a downloadable copy of the driver that came with the graphics card)? I find it peculiar how it can act so strangely game-by-game when something like Tera, which renders an entire world and other players, can run without a hitch yet F.E.A.R, an fps made in 2005 triggers this thing.
 
they are using the same driver on many cards, when they introduce a faster card a bunch of timing issues start popping up in the driver. You may find that going to control panel and disable your amd hd audio devices might help. I would check your card to see if it comes already at a overclocked speed by default. I would try to set my card as close to the reference cards settings as I could get until they get the drivers fixed.



 

AValladares

Honorable
Feb 3, 2014
5
0
10,510
Let's see, I'm guessing from this http://us.msi.com/product/vga/R7770-PMD1GD5.html#/?div=Specification
The card didn't come OC'd, GPU-Z agrees that it's at 1000MHz. I have disabled the AMD HD Audio Devices... which it installed like 6 of them... I'll see if that helps any after MalwareBytes finishes scanning, figured it couldn't hurt if maybe something infected my computer. Afterwards I'll try and see if maybe rolling back to the drivers the card came with may help, and work my way up.

Update: So after cleaning up the updated driver and installing the one that came with the R7770, it no longer BSODs, but I still can't get the card to finish a 3dmark test, but it can still do a Kombustor stress test (as well as Unigine Valley benchmark). I'll see how it works with an actual game.
 

AValladares

Honorable
Feb 3, 2014
5
0
10,510
Browsing around all night last night I came across someone with my card and solved their issue by turning down their core and memory clocks by 25 each. I tried it and sure enough it worked but I wanted to see if maybe I could make the errors go away and keep the stock speeds and one of these two things did the trick:

1) I went against my norm and installed the 13.12 drivers on top of the 9.12 drivers (driver that came with the card, no driver sweeping)

2) I used Sapphire Trixxx to raise the fan speed to a constant 70% (normally 30%) and raised the voltage from 1200 to 1250.

Played around in F.E.A.R for about an hour and no more TDR bugcheck. Anyone have an idea why either, or both, those actions may have alleviated the problem?