Hello,
I just found your forum and couldn't create the health report and run the system file collection app since I'm at work right now.
Anyway, I hope you can help me with the following information:
All drivers and firmwares are up to date.
I get a BSOD since 3 days if I'm playing games. The first one appears after ~20-30 minutes and the next one in under 20 minutes. After 3 BSOD I get it almost instantly, mostly in under 1-2 minutes.
The dump file says that it's probably caused by nvlddmkm.sys and ntoskrnl.exe.
Here is a quote of another dump file.
That's what I've already tested:
Someone reminded me today, that the problem appeared after I've installed Far Cry Primal.
Maybe it's caused by the DirectX version or something which comes with Primal?!
I don't know what else could be the problem. I spent the last few days with testing and configuration but the problem still occurs.
I hope you guys can help me with some information from the dump files.
Kind regards
Julien
I just found your forum and couldn't create the health report and run the system file collection app since I'm at work right now.
Anyway, I hope you can help me with the following information:
- OS: Windows 10 Pro x64
- CPU: Core i7 4790k
- Motherboard: AsRock Fatal1ty Z87 professional
- RAM: 16GB DDR3 1600
- GPU: GTX 980 SLI, EVGA SC ACX2.0
- PSU: Corsair HX850
- OS SSD: Samsung 840 - 250GB
- Old OS SSD: Samsung 830 - 120GB
All drivers and firmwares are up to date.
I get a BSOD since 3 days if I'm playing games. The first one appears after ~20-30 minutes and the next one in under 20 minutes. After 3 BSOD I get it almost instantly, mostly in under 1-2 minutes.
The dump file says that it's probably caused by nvlddmkm.sys and ntoskrnl.exe.
Here is a quote of another dump file.
Code:
VIDEO_ENGINE_TIMEOUT_DETECTED (141)One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe00023beb010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8007cb77d80, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 000000000000071c, Optional internal context dependent data.
That's what I've already tested:
- Hardware check (memtest, chkdsk, testing the RAM manually, testing the GPUs manually, etc,...)
- Tried different versions of chipset drivers and GPU drivers
- Reinstalled windows on another SSD
- Cleanboot and disconnect all other SATA devices
- BIOS reset
- Set TDR timeout and delay to 60
- other small changes
Someone reminded me today, that the problem appeared after I've installed Far Cry Primal.
Maybe it's caused by the DirectX version or something which comes with Primal?!
I don't know what else could be the problem. I spent the last few days with testing and configuration but the problem still occurs.
I hope you guys can help me with some information from the dump files.
Kind regards
Julien