Far Cry 4 - Display driver stopped responding and has recovered

Get today first driver crash in Far Cry 4. Application stopped. Then i saw on events: Nvlddmkm Display driver stopped responding and has recovered. Its very random , sometimes i can play even 24 hours without driver crash and sometimes like today its crashed driver after 5 minutes of started game.
Its problem with driver or my its just my card? ( i am using stock Asus Strix 980 ). I am using the newest drivers. All other games runs without even single crash. I tested Unigine Heaven for 10 hours, without crash. I tested Metro Last Light for few hours without crash too.

Only Far Cry 4 sometimes crash after 5 minutes,but mostly often i can play 24 hours without driver crash.

Using 347.88 WHQL.


All my pc is stock, cpu is 4790k stock. GPU is on stock too.

From what i know,crashing display driver Nvlddmkm its always graphic card ( hardware ) failure? Rma graphic card?

I doubt it's a problem with the graphics card as all other games seem to be fine. Could be a driver issue, try going back a version or two and see if it helps.

TDR's are always happening because of "bad/broken" hardware.Or it can be software too?

I've previously pointed you to a great topic on how you best work out what's causing TDRs, it does, however, require that you actually get down and do the work yourself, no good for you to keep asking the yes/no question - the answer is we don't know.

On 344.75 WHQL i dont get any driver crash. Only on 347.88 WHQL i have random driver nvlddmkm crashes on Far Cry 4. Is this related to game\software or just stock OC of my card is not stable fully?
I am asking because from what i know TDR's are always happening because of "bad/broken" hardware. Or i am wrong?

You're wrong. Just use 344.75 driver.

I installed 350 HOTFIX see if it crashes.

Somebody say:"Another popular thing is when nVidia optimizes the driver, and it pushes the card even harder and reveals a card crash, then people blame the driver, when the new driver is simply revealing a problem with the card."
So i have propablly card issue when on 347.88 i have driver crashing only on Far Cry 4? Because driver pushes the card harder and is simply revealing a problem with card. It can be true?

I installed 350 HOTFIX. Far Cry 4 played 24 hours without driver crash. So on 347.88 my card is just unstable? Is this because driver 347.88 pushing my card harder and card is unstable? Or its was only driver issue?

It's the driver. Your card is fine. Feel free to RMA the card though. You'll have the same problem with the new one.

FC4 is horribly coded, you will always have problems with it, and we always have.

I installed 350.12 WHQL ( GTA V ready ) . And game is crashing video driver still.
Only on 350.05 is not crashing. I tested 24 hours Far Cry 4 on 350.05 and no single crash. TOday i installed 350.12 WHQL and after 5 mintues crash. Its something with my card if on 2 versions of drivers my card are not stable?


344.75 WHQL - no crashing
350 HOTFIX - no crashing
350.12 WHQL - crashing video driver in Far Cry 4
347.88 WHQL - crashing video driver in Far Cry 4

I would just stick with the 350 hotfix driver then if that isn't causing issues.

But i tested on all of the drivers ( 344.75 , 347.88 , 350 HOTFIX , 350.12 WHQL ) Unigine Heaven and its stable. Only Far Cry 4 is crashing on each driver versions ( 350.12 WHQL and 347.88 WHQL ). It because Far Cry 4 dont like any OC or its driver \ game problem?

I think i resolved issue. I downgraded from update 1.7 to 1.6. After that i dont see more driver crashing in Far Cry 4 using 350.12 WHQL.But i will take a look further. So how this is possible that patch was causing TDR?

Patches that fix things sometimes cause new issues to appear

Hey guys. Little update. I run memtest and shows 34 errors after 5 minutes. It can be problem then with memory with display crashing? ( TDR )? Display crashing ( TDR ) can be caused by memory then?

Also today i am buying new memory set.

What does TDR stand for?

The two that I've generally seen used are BSOD (blue screen of death) or CTD (crash to desktop)

Here is a log from memtests:

2015-04-18 16:14:35 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBF64, Expected: EFEFEFEF, Actual: EFFFEFEF
2015-04-18 16:14:36 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBF24, Expected: EFEFEFEF, Actual: EFCBEFEF
2015-04-18 16:14:37 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBC24, Expected: EFEFEFEF, Actual: EFF7EFEF
2015-04-18 16:14:39 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBB24, Expected: EFEFEFEF, Actual: EFEDEFEF
2015-04-18 16:14:40 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBAE4, Expected: EFEFEFEF, Actual: EFEBEFEF
2015-04-18 16:14:41 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DB9A4, Expected: EFEFEFEF, Actual: EFCFEFEF
2015-04-18 16:14:42 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DB464, Expected: EFEFEFEF, Actual: EFEEEFEF
2015-04-18 16:14:44 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DB424, Expected: EFEFEFEF, Actual: EFCFEFEF
2015-04-18 16:14:45 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DAFA4, Expected: EFEFEFEF, Actual: EF67EFEF
2015-04-18 16:14:46 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DAA64, Expected: EFEFEFEF, Actual: EF77EFEF
2015-04-18 16:14:47 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DAA24, Expected: EFEFEFEF, Actual: EFEDEFEF
2015-04-18 16:14:49 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA564, Expected: EFEFEFEF, Actual: EF25EFEF
2015-04-18 16:14:50 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA4E4, Expected: EFEFEFEF, Actual: EFE3EFEF
2015-04-18 16:14:51 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA0E4, Expected: EFEFEFEF, Actual: EFEBEFEF
2015-04-18 16:14:53 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA0A4, Expected: EFEFEFEF, Actual: EFE9EFEF
2015-04-18 16:14:54 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D9FE4, Expected: EFEFEFEF, Actual: EFE7EFEF
2015-04-18 16:14:55 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D9CA4, Expected: EFEFEFEF, Actual: EFE8EFEF
2015-04-18 16:14:56 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D98A4, Expected: EFEFEFEF, Actual: EFE1EFEF
2015-04-18 16:14:58 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D97E4, Expected: EFEFEFEF, Actual: EFDBEFEF
2015-04-18 16:14:59 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D9564, Expected: EFEFEFEF, Actual: EFECEFEF
2015-04-18 16:15:00 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D94E4, Expected: EFEFEFEF, Actual: EF8DEFEF
2015-04-18 16:15:01 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8F64, Expected: EFEFEFEF, Actual: EFC7EFEF
2015-04-18 16:15:03 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8F24, Expected: EFEFEFEF, Actual: EFFFEFEF
2015-04-18 16:15:04 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8EA4, Expected: EFEFEFEF, Actual: EFE7EFEF
2015-04-18 16:15:05 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8C64, Expected: EFEFEFEF, Actual: EFCFEFEF
2015-04-18 16:15:06 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8C24, Expected: EFEFEFEF, Actual: EF6DEFEF
2015-04-18 16:15:08 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8B24, Expected: EFEFEFEF, Actual: EFA7EFEF
2015-04-18 16:15:09 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8AE4, Expected: EFEFEFEF, Actual: EFEDEFEF
2015-04-18 16:15:10 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8824, Expected: EFEFEFEF, Actual: EF39EFEF
2015-04-18 16:15:12 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8764, Expected: EFEFEFEF, Actual: EFBFEFEF
2015-04-18 16:15:13 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8724, Expected: EFEFEFEF, Actual: EFCEEFEF
2015-04-18 16:15:14 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D86E4, Expected: EFEFEFEF, Actual: EFB7EFEF
2015-04-18 16:15:15 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8364, Expected: EFEFEFEF, Actual: EFE7EFEF
2015-04-18 16:15:17 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8324, Expected: EFEFEFEF, Actual: EF6EEFEF
2015-04-18 16:15:18 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8064, Expected: EFEFEFEF, Actual: EF23EFEF

TDR

TDR troubleshooting and here.

Yes it's a GPU -related issue, data is too slow to reach the GPU from the CPU, could be from a range or combination of issues: heat, overclock, throttling, bad driver, bad hardware, ...

The troubleshooting methods have been suggested to the OP, here and in other similar topics elsewhere, he continues to ask simplistic questions (driver or hardware?) without providing any real data to enable some narrowing down of potential problems/triggers.

Whoa, you have that kind of errors in Memtest?
Is the system OC'd at all? If so, put to stock and run again. If not, buy new RAM.