Ok, Had Yet Another Bsod-Dpc_Watchdog_Violation While Running Wf.

[CedarDpg]

Running WF as per normal...game froze, then everything froze...then BSoD. So far, the only times my machine blue screens is when WF is running, so it's somewhat suspect.

 

Ran WhoCrashed, as per a request from someone on another thread, so here's that one.

System Information (local)

computer name: N
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: MS-7885, MSI, X99S GAMING 7 (MS-7885)
CPU: GenuineIntel Intel® Core i7-5930K CPU @ 3.50GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17070211072 total


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 4/26/2015 7:14:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042615-41609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sun 4/26/2015 7:14:12 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x199A77) 
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12 
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation). 
Google query: NVIDIA Corporation DPC_WATCHDOG_VIOLATION



On Fri 4/17/2015 3:45:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041615-153593-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF801B7502FA0) 
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF801B7502FA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



 

Conclusion

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 

 

And the normal WinDbg(X64).

 

5: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

component can usually be identified with a stack trace.

Arg2: 0000000000000501, The DPC time count (in ticks).

Arg3: 0000000000000500, The DPC time allotment (in ticks).

Arg4: 0000000000000000

 

Debugging Details:

------------------

 

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

 

OVERLAPPED_MODULE: Address regions for 'ENG64' and 'ENG64.SYS' overlap

 

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

BUGCHECK_STR:  0x133

 

PROCESS_NAME:  System

 

CURRENT_IRQL:  d

 

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

 

LAST_CONTROL_TRANSFER:  from fffff80346778f28 to fffff8034675dca0

 

STACK_TEXT:  

ffffd001`cb738c88 fffff803`46778f28 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffd001`cb738c90 fffff803`46649871 : 00000000`00000000 00000000`01c88d1b 00000000`00033ce9 fffff801`534fb866 : nt! ?? ::FNODOBFM::`string'+0xad68

ffffd001`cb738d20 fffff803`46da97b5 : ffffe000`00400a02 fffff803`00000000 fffff801`52e53164 00000000`00007001 : nt!KeClockInterruptNotify+0x91

ffffd001`cb738f40 fffff803`466e4143 : ffff639f`8281ce7b 00000000`00000008 ffffe000`d790c0b8 ffffe000`d7302000 : hal!HalpTimerClockIpiRoutine+0x15

ffffd001`cb738f70 fffff803`4675f12a : ffffe000`cb001200 ffffd001`cb730980 00000000`c1d06611 00000000`00000002 : nt!KiCallInterruptServiceRoutine+0xa3

ffffd001`cb738fb0 fffff803`4675f50f : ffffd001`cb7016c0 fffff803`468b11a6 ffffd001`cb701840 fffff803`468b11a6 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffd001`cb730730 fffff801`5348fa77 : fffff801`534d4052 00000000`00000000 fffff801`53489df8 ffffd001`cb730a08 : nt!KiInterruptDispatchLBControl+0x11f

ffffd001`cb7308c8 fffff801`534d4052 : 00000000`00000000 fffff801`53489df8 ffffd001`cb730a08 fffff801`53489df8 : nvlddmkm+0x199a77

ffffd001`cb7308d0 fffff801`534d4482 : 00000000`00000000 00000000`00000000 ffffe000`d15ab000 00000000`00000000 : nvlddmkm+0x1de052

ffffd001`cb730910 fffff801`5349879e : 00000000`00000001 ffffe000`d15ab000 ffffe000`e26f6880 00000000`00000000 : nvlddmkm+0x1de482

ffffd001`cb730940 fffff801`534a2dce : 00000000`00000000 ffffe000`d15ab000 00000000`00000000 ffffe000`dfaac0b8 : nvlddmkm+0x1a279e

ffffd001`cb730980 fffff801`534ae78a : 00000000`00000057 ffffd001`cb730a68 00000000`00000000 ffffd001`cb730a68 : nvlddmkm+0x1acdce

ffffd001`cb7309b0 fffff801`534adb0b : 00000000`00000000 00000000`00000000 ffffe000`d0413f80 00000000`00000000 : nvlddmkm+0x1b878a

ffffd001`cb7309f0 fffff801`534adf7a : ffffe000`d1f210f0 ffffe000`cff9f000 ffffe000`ff020001 00000000`00000000 : nvlddmkm+0x1b7b0b

ffffd001`cb730a50 fffff801`537a1d24 : ffffd001`cb730bd0 ffffe000`cffcdab0 00000000`00000000 ffffe000`d6daeae0 : nvlddmkm+0x1b7f7a

ffffd001`cb730ad0 fffff801`5379f84e : ffffe000`d1581000 ffffe000`cffcdab0 ffffe000`cffcdab0 00000000`00000000 : nvlddmkm+0x4abd24

ffffd001`cb730d20 fffff801`5360c969 : 00000000`efeff6ff ffffe000`124f0000 00000000`02000000 00000000`00000020 : nvlddmkm+0x4a984e

ffffd001`cb730e30 fffff801`536101fe : 00000000`00000003 00000000`00000001 ffffe000`e28726e8 ffffe000`d158a420 : nvlddmkm+0x316969

ffffd001`cb730ed0 fffff801`53b3fe24 : ffffe000`00000001 00000000`00000000 ffffe000`d1581000 ffffe000`cffcdab0 : nvlddmkm+0x31a1fe

ffffd001`cb730f70 fffff801`5360c11e : 00000000`00000000 00000000`00000000 00000000`20000000 ffffe000`cff9f000 : nvlddmkm+0x849e24

ffffd001`cb730fd0 fffff801`5360ca49 : 00000000`60000000 ffffe000`cffcdab0 0001a932`487bea10 00000000`60000000 : nvlddmkm+0x31611e

ffffd001`cb731060 fffff801`534e02de : ffffe000`cff9f000 00000000`00000000 00000000`00000001 ffffe000`d116c000 : nvlddmkm+0x316a49

ffffd001`cb7310c0 fffff801`534e08e1 : ffffe000`cff9f000 00000000`00000000 ffffe000`d116c000 ffffe000`cffa3000 : nvlddmkm+0x1ea2de

ffffd001`cb7310f0 fffff801`536ede36 : ffffe000`cff9f000 00000000`00000000 ffffe000`cff9f000 ffffe000`cff9f000 : nvlddmkm+0x1ea8e1

ffffd001`cb7311b0 fffff801`5360e939 : ffffe000`cff9f000 ffffd001`cb731288 ffffe000`cffa3000 00000000`00000000 : nvlddmkm+0x3f7e36

ffffd001`cb7311e0 fffff801`536066aa : ffffe000`cff9f000 ffffd001`cb731201 ffffe000`e28726e8 ffffe000`d15ae010 : nvlddmkm+0x318939

ffffd001`cb731210 fffff801`5360580e : 00000000`0000000a 00000000`00000000 ffffd001`cb7312a0 ffffe000`cff9f000 : nvlddmkm+0x3106aa

ffffd001`cb731250 fffff801`5360cb88 : ffffe000`d2528110 ffffe000`cff9f000 ffffe000`d0563580 00000000`00000001 : nvlddmkm+0x30f80e

ffffd001`cb7312e0 fffff801`53623705 : ffffd001`00000000 ffffe000`d92b5120 ffffe000`d0563580 fffff801`00000001 : nvlddmkm+0x316b88

ffffd001`cb731350 fffff801`53609d6f : ffffe000`e28726e8 ffffe000`cff9f000 ffffe000`d0563580 00000000`00000029 : nvlddmkm+0x32d705

ffffd001`cb7313b0 fffff801`5360ac1e : ffffe000`d15ae010 00000000`00000000 ffffd001`00000001 ffffd001`cb7314b0 : nvlddmkm+0x313d6f

ffffd001`cb731430 fffff801`537a0587 : 00000000`00000001 00000000`00000001 00000000`00000000 ffffe000`cff9f000 : nvlddmkm+0x314c1e

ffffd001`cb7314f0 fffff801`5379f14d : ffffd001`cb731650 ffffd001`cb7315b0 ffffe000`cffcdab0 ffffe000`00000001 : nvlddmkm+0x4aa587

ffffd001`cb731550 fffff801`5379f9c6 : ffffe000`00010001 00000000`00000000 00000000`00000000 ffffd001`00000000 : nvlddmkm+0x4a914d

ffffd001`cb7315f0 fffff801`5360c969 : 00000000`efeff6ff ffffe000`124f0000 00000000`02000000 00000000`00000020 : nvlddmkm+0x4a99c6

ffffd001`cb731700 fffff801`536101fe : 00000000`00000003 00000000`00000001 ffffe000`e28726e8 ffffe000`d158a420 : nvlddmkm+0x316969

ffffd001`cb7317a0 fffff801`53b3fe24 : ffffe000`00000001 00000000`00000000 ffffe000`d1581000 ffffe000`cffcdab0 : nvlddmkm+0x31a1fe

ffffd001`cb731840 fffff801`5360c11e : 00000000`00000000 00000000`00000000 00000000`20000000 ffffe000`cff9f000 : nvlddmkm+0x849e24

ffffd001`cb7318a0 fffff801`5360ca49 : 00000000`60000000 ffffe000`cffcdab0 0001a932`14547950 00000000`60000000 : nvlddmkm+0x31611e

ffffd001`cb731930 fffff801`534e02de : ffffe000`cff9f000 00000000`00000007 00000000`00000001 ffffd001`caf3b470 : nvlddmkm+0x316a49

ffffd001`cb731990 fffff801`534dfe6e : ffffe000`cff9f000 00000000`00000007 ffffe000`cffa3000 ffffe000`d247b810 : nvlddmkm+0x1ea2de

ffffd001`cb7319c0 fffff801`534e0069 : ffffe000`db2d4170 00000000`00000080 ffffe000`cff9f000 ffffe000`00000017 : nvlddmkm+0x1e9e6e

ffffd001`cb731a20 fffff801`534e0b04 : 00000000`00000000 00000000`00000080 ffffe000`cffa3000 ffffe000`cff9f000 : nvlddmkm+0x1ea069

ffffd001`cb731a60 fffff801`53735caa : ffffe000`cff9f000 ffffd001`cb731b79 ffffe000`cffa3000 00000000`00000200 : nvlddmkm+0x1eab04

ffffd001`cb731aa0 fffff801`5347e908 : ffffe000`cff9f000 ffffd001`cb731b79 00000000`00000000 fffff803`466b07f9 : nvlddmkm+0x43fcaa

ffffd001`cb731ad0 fffff803`466b3c00 : ffffd001`cb702f00 fffff803`4660d000 ffffd001`cb731e70 ffffe000`cd7e0f44 : nvlddmkm+0x188908

ffffd001`cb731be0 fffff803`466b2eb7 : 0064002e`00720065 01ce9f3c`00000000 00010000`00114840 00000000`00600070 : nt!KiExecuteAllDpcs+0x1b0

ffffd001`cb731d30 fffff803`46760dd5 : 00000000`00000000 ffffd001`cb700180 00000000`00000000 ffffe000`e2002900 : nt!KiRetireDpcList+0xd7

ffffd001`cb731fb0 fffff803`46760bd9 : 000000ff`fff820b8 fffff801`533e0ca6 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5

ffffd001`d89b97c0 fffff803`46762cfa : 000000ff`fff82000 00000000`00000001 ffffd001`d89b9960 fffff801`533e1531 : nt!KiDispatchInterruptContinue

ffffd001`d89b97f0 fffff803`466e5082 : ffffe000`d127e000 ffffe000`e2002ea0 ffffe000`e20029d0 00000000`00000000 : nt!KiDpcInterrupt+0xca

ffffd001`d89b9980 fffff801`533e2daf : ffffe000`d127c000 00000000`00000000 ffffe000`d127c000 ffffe000`e20029d0 : nt!KeReleaseSpinLock+0x22

ffffd001`d89b99b0 fffff801`533e2e35 : ffffd001`cba80100 ffffe000`e26f6900 ffffe000`00000063 fffff801`533e2af6 : nvlddmkm+0xecdaf

ffffd001`d89b9ab0 fffff803`466ba427 : 00000000`00000000 ffff0432`5b0ebf1d 00000000`00000001 fffff803`00000000 : nvlddmkm+0xece35

ffffd001`d89b9ae0 fffff803`466ba6bc : fffff803`46a50304 fffff803`466ba32c ffffe000`d03f9d30 fffff803`468bf340 : nt!IopProcessWorkItem+0xfb

ffffd001`d89b9b50 fffff803`4670d36c : 78ff85db`33535e7e ffffe000`e26f6880 00000000`00000080 ffffe000`e26f6880 : nt!ExpWorkerThread+0x28c

ffffd001`d89b9c00 fffff803`467642c6 : fffff803`46910180 ffffe000`e26f6880 fffff803`46969a00 687e3b47`08558b13 : nt!PspSystemThreadStartup+0x58

ffffd001`d89b9c60 00000000`00000000 : ffffd001`d89ba000 ffffd001`d89b4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP: 

nvlddmkm+199a77

fffff801`5348fa77 c3              ret

 

SYMBOL_STACK_INDEX:  7

 

SYMBOL_NAME:  nvlddmkm+199a77

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: nvlddmkm

 

IMAGE_NAME:  nvlddmkm.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  55259065

 

FAILURE_BUCKET_ID:  0x133_DPC_nvlddmkm+199a77

 

BUCKET_ID:  0x133_DPC_nvlddmkm+199a77

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:0x133_dpc_nvlddmkm+199a77

 

FAILURE_ID_HASH:  {2f60e565-04f6-4ddf-cb37-958bc0397dca}

 

Followup: MachineOwner

---------

 

 

Can post dxdiag if needed. But the system has two nVidia GTX970s connected with an SLI bridge.

Edited April 26, 2015 by CedarDpg

[Circle_of_Psi]

Wat iz this?

 

 

Also, watchdog, sounds like your being hacked

[CedarDpg]

Wat iz this?

 

 

Also, watchdog, sounds like your being hacked

It's basically an analysis of my crash dump logs from my last blue screen. Mostly of interest to the devs more than any particular player.

 

Watchdog just refers to a watchdog timer which basically keeps tabs on hardware to make sure it's responding in a timely and normal fashion. DPC just stands for deferred procedure call. Nothing to do with being hacked as far as I know.

Edited April 26, 2015 by CedarDpg

[Urlan]

The DPC_Watchdog_Violation is just the core process the Windows 8 uses for validation of errors and driver/hardware conflicts. If the watchdog related errors are showing its time to closely examine your software installations and driver configs. Such errors can signify bad configurations, badly done DRM like Targes or that hardware is going out in a gradual or partial fashion.

 

According to your logs, I would suggest that your graphics card or drivers are having and issue somewhere. Might be worth looking at the last video driver you installed and seeing if other users are having similar issues with your hardware setup. Check to see if you have a good older system restore point or backup to restore back to as well. Save that though for when you are reasonably sure that it is the driver itself. Try to do as few or small changes as you can when testing as possible so that you can narrow down your suspects. It also must be considered that it is a flaw inherent in the video to cpu communication as well but it would be best to focus on drivers and installed software interactions first if it hadn't happened before.

[CedarDpg]

This has been an issue ever since I got the machine. This has been an ongoing thing through a number of nVidia driver versions. The behavior only occurs when Warframe is running. I can run any other number of software in conjunction with each other...including other GPU/CPU intensive games and there's never been a problem until Warframe is started.

 

Also, I doubt it's hardware going out, though I guess it's possible. But the hardware is relatively new. Less than a half year old.

Edited April 26, 2015 by CedarDpg

[Urlan]

I hope its not hardware going out but it is a possibility when those error messages start showing.up. That said, if it is only happening on Warframe, check your graphic settings in game. The graphic settings for the game maybe trying to run features they don't really have. Copy your graphic settings down and try to lower the game's settings as low as you can and try to play Warframe to get the same crash. If you can't get the crash, start turning settings back up, one by one until you do get the crash.

[NULLNULLNIX]

same trouble here

.......

[[DE]Xander]

That violation is commonly caused by overclocking, or bad memory. Alternatively, there could be a driver issue.

[CedarDpg]

That violation is commonly caused by overclocking, or bad memory. Alternatively, there could be a driver issue.

Nothing in my machine is overclocked. And already ran a test on the memory (at least using the Windows Memory Diagnostic tool) using the extended test settings. (No errors found.) Is there some other memory test I should run? I'm sure it's probably some driver issue... And it's probably nVidia's drivers, I'll bet. However, this has been an issue since the machine was first commissioned in late December of 2014 and whatever current nVidia driver version that was available at that time. Current nVidia driver version installed is: 350.12...

Edited April 27, 2015 by CedarDpg

[NULLNULLNIX]

same here nothing is overclocked ..... 

[[DE]Xander]

If you're familiar with using MSI Afterburner or similar software, I'm curious what sort of temperatures you're seeing prior to the BSOD.

[Garuger]

If you're familiar with using MSI Afterburner or similar software, I'm curious what sort of temperatures you're seeing prior to the BSOD.

For me Warframe is one of the worst games that my gpu handles in matter of heat . Normal games runs around ~60~70 but with warframe it overpasses 80+ celcius . Any help with that ?

[3thereal]

FYI if their video card has a bad RAM chip, they could not be overheating but just have a bad card. Also Windows Memory Diagnotic Tool won't catch bad Video card RAM, as it's meant to test the RAM on your MB (for the processor).

[[DE]Xander]

FYI if their video card has a bad RAM chip, they could not be overheating but just have a bad card. Also Windows Memory Diagnotic Tool won't catch bad Video card RAM, as it's meant to test the RAM on your MB (for the processor).

This is true, but I'd assume other games would've revealed a faulty card by now, and not just Warframe. Luckily OP is running SLi, so it's as easy as trying each one solo to see if the card is at fault, unless they were unfortunate to have 2 dud 970s.

[CedarDpg]

If you're familiar with using MSI Afterburner or similar software, I'm curious what sort of temperatures you're seeing prior to the BSOD.

 

Hi, yeah...I'm familiar with it, and actually I have widgets that display current GPU and CPU Temps, Drive/Network/CPU Activity. The crashes come at random times. Sometimes one of the cards is running hot ~80C if I'm really taxing the GPUs, though i don't think it is causal since I've had crashes occur at 50-60C. I suppose I could change the fan speeds manually to keep the GPUs at a lower temp...but that's what the manufacturer has set for its max target temp point. (The program lets it get to 80C, but not above...and the GPU hasn't gone above 80C as far as I've ever seen.)

 

FYI if their video card has a bad RAM chip, they could not be overheating but just have a bad card. Also Windows Memory Diagnotic Tool won't catch bad Video card RAM, as it's meant to test the RAM on your MB (for the processor).

 

This is definitely true. I'll run a memtest on the video cards, if this CUDA GPU memtest thing on Sourceforge works...or perhaps I can find a better program with more searching.

 

This is true, but I'd assume other games would've revealed a faulty card by now, and not just Warframe. Luckily OP is running SLi, so it's as easy as trying each one solo to see if the card is at fault, unless they were unfortunate to have 2 dud 970s.

 

Yeah, I could decouple the cards and test, but I've played many games on the cards without incident. Here are some of the games played on this machine without BSoD: Far Cry 3/4, Borderlands 2/TPS, Crysis 3, Witcher 1/2, Evolve, Metro 2033/Last Light, Portal 1/2, Natural Selection 2, Left 4 Dead 1/2, TESV: Skyrim, Dragon Age Origins/Inquisition, Dishonored, Dead Space 1/2/3, Mass Effect 1/2/3, Diablo 3, Minecraft (seems more CPU intensive)...

Edited April 27, 2015 by CedarDpg

[[DE]Xander]

Yeah, I could decouple the cards and test, but I've played many games on the cards without incident. Here are some of the games played on this machine without BSoD: Far Cry 3/4, Borderlands 2/TPS, Crysis 3, Witcher 1/2, Evolve, Metro 2033/Last Light, Portal 1/2, Natural Selection 2, Left 4 Dead 1/2, TESV: Skyrim, Dragon Age Origins/Inquisition, Dishonored, Dead Space 1/2/3, Mass Effect 1/2/3...

 

Based on that list, I'm hesitant to accuse your card being at fault, but it's still not impossible something while you're playing Warframe is pushing the card over the edge.

 

You might get results though from downclocking; we had another player who stopped crashing when they noticed their stock clock was a little high.

[CedarDpg]

Based on that list, I'm hesitant to accuse your card being at fault, but it's still not impossible something while you're playing Warframe is pushing the card over the edge.

 

You might get results though from downclocking; we had another player who stopped crashing when they noticed their stock clock was a little high.

Any particular settings you recommend? Here's a copy of what GPU-Z says about the card (both are identical):

 

Edited April 27, 2015 by CedarDpg

[[DE]Xander]

Try bumping down to 1000mhz and let me know if you're still getting the BSOD.

[CedarDpg]

Try bumping down to 1000mhz and let me know if you're still getting the BSOD.

I assume just adjust the core clock? Should I touch memory clock speeds?

[[DE]Xander]

Sorry, bring your core to 1000mhz, and the memory to 1600mhz

[CedarDpg]

Sorry, bring your core to 1000mhz, and the memory to 1600mhz

Ok, I'll play with these settings. Unknown how long an ETA to crash is, since it happens seemingly at random even during normal operations. But if I BS again, I'll update this immediately. Also, I am installing Cygwin (instead of installing a standalone linux distro) to run this CUDA GPU memtest thing...if the program can be successfully installed and run, I will post the results.

 

Also, thanks for your help. :)

Edited April 27, 2015 by CedarDpg

[CedarDpg]

same here nothing is overclocked ..... 

 

Just curious, what are the specs on your rig?

 

For me Warframe is one of the worst games that my gpu handles in matter of heat . Normal games runs around ~60~70 but with warframe it overpasses 80+ celcius . Any help with that ?

 

What I've done in the past is use either Zotac's Firestorm (because my nVidia cards are of Zotac make), or MSI Afterburner and I've made a custom fan graph/settings... I made it so that at 80C the fans run at 100% and adjusted the curve somewhat to make the fans run at a higher speed than normal when temps get above 60C. It has kept my cards cool. (Recently made some changes to some software and the thing went back to automatic control, which is why my main GPU ran at 80C max.) Since Xander has me playing around with underclocking, I took the time to reinstate my custom fan settings, so my card shouldn't get too much over 60C even under load.

[Xaiux]

I've had this error as well. I have an Nvidia GT 750M, i7-4700MQ. Warframe is the only game that does this for me, as well. I haven't touched the clocks, due to it being a laptop, but I have used afterburner just to look at temps while playing. Warframe is brutal for temps for me. My previous laptop actually started to overheat while playing (97C on a 660M), and I had to get a new one. I don't think that I've gone above 70C with my current laptop.

[Djangofett]

Thank god I'm not the only one, I been getting the exact same issues recently, game freezing, comp freezing and BSoD. I'm also pretty sure my hardware's are in perfect condition.

[Urlan]

I couldn't say for the other graphics cards, but the 970 GTX does have a manufacturing flaw with its RAM. When the RAM's use climbs above 3GB, the card will start winding down its clock speeds for its memory bus to a slower tier. The last 1G is not actually at the same speed as the first 3GB. That could cause some slowdown type effects in games that use large textures as the card would basically be acting like a lower grade card at that point while already trying to do the work of a 970 GTX. MIght not be related to your issue but it is something to keep in mind.