"display driver stopped responding and has recovered" problem

CrossKun

Reputable
Nov 4, 2014
5
0
4,510
Hey there guys,
I've built myself a new computer a few weeks ago and I'm a bit frustrated by the "display driver stopped responding and has recovered" error Im getting each time Im playing a game that has good graphics. (e.g. Lords of the Fallen, ArcheAge)
Im getting a black screen followed by a "display driver..." message.

I've tried a couple of things so far:
- new installation of Windows 7 (which includes installing a fresh new driver)
- replaced the PSU
- replaced the Videocard (760 GTX -> 970 GTX)
- Tried the games with only one RAM stick instead of 2 (tested each)

- Set Physx in the Nv Control panel to "GPU only"
- Deinstalled everything from nvidia except the driver itself
- Went through a tutorial to enable the parked CPU cores at all time (http://www.youtube.com/watch?v=XUXrBqUuU6M)

My specs:
CPU: i7 4770 3,40 ghz
GPU: Gainward Phantom GTX 970
RAM: DDR3-1600 DIMM CL9 Dual Kit 8 GB
Board: MSI Z87-G45
PSU: 600w Corsair

I also add the Crash message from Lords of the fallen and the Crash log from Arche age here:

Problemereignisname: APPCRASH
Anwendungsname: LordsOfTheFallen.exe
Anwendungsversion: 0.0.0.0
Anwendungszeitstempel: 54525dc0
Fehlermodulname: LordsOfTheFallen.exe
Fehlermodulversion: 0.0.0.0
Fehlermodulzeitstempel: 54525dc0
Ausnahmecode: c0000005
Ausnahmeoffset: 000000000d3fae66
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 89a0
Zusatzinformation 2: 89a058713b181ca290fc7dbcc9067a3a
Zusatzinformation 3: d7a8
Zusatzinformation 4: d7a8aee6276623dd9695e20c682f3e74

Archeage.crash:
14:50:17> <CRITICAL EXCEPTION>
14:50:17> Exception Code: 0xC0000005
14:50:17> Exception Addr: 0x0023:0x68d2e9cf
14:50:17> Exception Description: EXCEPTION_ACCESS_VIOLATION
Attempt to write data to address 0x000000fc
The memory could not be "written"
14:50:17> Virtual Memory Usage: 1342Mb
14:50:17> Dumping X86 registers
14:50:17> eip=00000000, esp=00000000, ebp=00000000
14:50:17> edi=00000000, esi=00000000, eax=00000000, ebx=00000000, ecx=00000000, edx=00000000

---
is it possible that the CPU or the mainboard itself is damaged?
If any other information is needed from BIOS or dxdiag, I can provide them!
Thank you kindly for any effort and answers!
 
Solution
In that case, I'd swap the motherboard and try again.

You can test the CPU by running Prime95 for 30 minutes. Crash=probably the CPU. No crash=probably the MB.

CrossKun

Reputable
Nov 4, 2014
5
0
4,510
actually no! None of them is overclocked as far as I know. I think the RAM has even a lower frequency than normal (1333 mhz instead of 1600mhz)
8GB Corsair Vengeance LP black
DDR3-1600 DIMM CL9 Dual Kit