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

[dandeloreon]

I was just wondering about the settings of the game a little bit, since these can lead to system issues oddly enough.

 

1) Which version of windows Is being used? ( Example is "Windows 7 Professional (64-bit edition)" )

2) Is Multi-threaded rendering enabled? ( see launcher options )

3) Is GPU accelerated launcher enabled?

4) Is the game ran in 32-bit or 64-bit mode?

[NULLNULLNIX]

Just curious, what are the specs on your rig?

 

 

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.

 

 

 

 

 

 

windows 8.1 64 bit

my specs 2 gtx770

32gb ram

amdfx8350 black edition water cooled

assrock 970 extreme 4

750 watss psu

aoc 4 k monitor

 

gpu temp never goes over 55c

Edited April 28, 2015 by plons

[CedarDpg]

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.

Keeping an eye on the GPU widget, so far, I haven't seen more than 1-1.5GB in use between both cards combined since I've been keeping an eye on it. And as far as I recall, it's after 3.5GB on each card of "fast memory", the last 500MB of memory is slower. (It's not really a manufacturing flaw, they did that on purpose.) Edited April 28, 2015 by CedarDpg

[CedarDpg]

 

windows 8.1 64 bit

my specs 2 gtx770

32gb ram

amdfx8350 black edition water cooled

assrock 970 extreme 4

750 watss psu

aoc 4 k monitor

 

gpu temp never goes over 55c

 

 

Nice!

 

I was just wondering about the settings of the game a little bit, since these can lead to system issues oddly enough.

 

1) Which version of windows Is being used? ( Example is "Windows 7 Professional (64-bit edition)" )

2) Is Multi-threaded rendering enabled? ( see launcher options )

3) Is GPU accelerated launcher enabled?

4) Is the game ran in 32-bit or 64-bit mode?

 

1) Windows 8.1 Professional, x64

2) Yes

3) Yes

4) 64

[CedarDpg]

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

 

Hi Xander,

 

Looks like underclocking didn't help. Just experienced another DPC_WATCHDOG_VIOLATION BSoD while playing Warframe.

 

Windbg

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

*                                                                             *

*                        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

 

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 fffff8014f1f0f28 to fffff8014f1d5ca0

 

STACK_TEXT:  

ffffd001`d5d38c88 fffff801`4f1f0f28 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffd001`d5d38c90 fffff801`4f0c1871 : 00000000`00000005 00000000`01f93d42 00000000`000b59ed fffff801`200d5866 : nt! ?? ::FNODOBFM::`string'+0xad68

ffffd001`d5d38d20 fffff801`4f01d7b5 : ffffe000`00400a02 fffff801`4f12adc4 fffff801`1d0b7b68 00000000`00006001 : nt!KeClockInterruptNotify+0x91

ffffd001`d5d38f40 fffff801`4f15c143 : ffffe54c`9c5579d1 00000000`00000008 00000000`00000000 ffffe000`9d33d401 : hal!HalpTimerClockIpiRoutine+0x15

ffffd001`d5d38f70 fffff801`4f1d712a : ffffe000`97801200 00000000`00418d1c ffffe000`9c9c4000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3

ffffd001`d5d38fb0 fffff801`4f1d750f : 00000000`00000010 fffff801`2006e22a 00000000`00000008 00000000`00000801 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffd001`d5d29410 fffff801`200585d5 : fffff801`200d7f6c ffffe000`9c9c1000 ffffe000`9c9c1000 ffffe000`9d5fc9f0 : nt!KiInterruptDispatchLBControl+0x11f

ffffd001`d5d295a8 fffff801`200d7f6c : ffffe000`9c9c1000 ffffe000`9c9c1000 ffffe000`9d5fc9f0 fffff801`20071bc9 : nvlddmkm+0x1885d5

ffffd001`d5d295b0 fffff801`200d7e4d : 00000000`00000000 00000000`00418d1c 00000000`00000000 ffff690b`d68b7b18 : nvlddmkm+0x207f6c

ffffd001`d5d29620 fffff801`200d8098 : ffffe000`9c9df4d0 00000000`00000000 ffffe000`9c9c1000 ffffe000`9c9df4d0 : nvlddmkm+0x207e4d

ffffd001`d5d29660 fffff801`201b95a0 : ffffe000`9c9df4d0 ffffe000`04551000 00000000`00000000 ffffd001`d5d29620 : nvlddmkm+0x208098

ffffd001`d5d296a0 fffff801`20112a85 : ffffd001`d5d29800 fffff801`2035f600 00000000`00000000 00000000`00000000 : nvlddmkm+0x2e95a0

ffffd001`d5d29740 fffff801`2037ba14 : ffffe000`a7494170 ffffd001`d5d29880 ffffe000`9c9eeab0 ffffe000`9c9c1000 : nvlddmkm+0x242a85

ffffd001`d5d29780 fffff801`2037984e : ffffe000`9e48b000 ffffe000`9c9eeab0 ffffe000`9c9eeab0 00000000`00000000 : nvlddmkm+0x4aba14

ffffd001`d5d299d0 fffff801`201e6969 : 00000000`efeff6ff ffffe000`124f0000 00000000`02000000 00000000`00000020 : nvlddmkm+0x4a984e

ffffd001`d5d29ae0 fffff801`201ea1fe : 00000000`00000003 00000000`00000001 ffffe000`997f46f8 ffffe000`9e488540 : nvlddmkm+0x316969

ffffd001`d5d29b80 fffff801`20719e24 : ffffe000`00000001 00000000`00000000 ffffe000`9e48b000 ffffe000`9c9eeab0 : nvlddmkm+0x31a1fe

ffffd001`d5d29c20 fffff801`201e611e : 00000000`00000000 00000000`00000000 00000000`20000000 ffffe000`9c9c1000 : nvlddmkm+0x849e24

ffffd001`d5d29c80 fffff801`201e6a49 : 00000000`60000000 ffffe000`9c9eeab0 0001d68a`6df9bd28 00000000`60000000 : nvlddmkm+0x31611e

ffffd001`d5d29d10 fffff801`200ba2de : ffffe000`9c9c1000 00000000`00000000 00000000`00000001 ffffe000`9e47d000 : nvlddmkm+0x316a49

ffffd001`d5d29d70 fffff801`200ba8e1 : ffffe000`9c9c1000 00000000`00000000 ffffe000`9e47d000 ffffe000`9c9c4000 : nvlddmkm+0x1ea2de

ffffd001`d5d29da0 fffff801`202c7e36 : ffffe000`9c9c1000 00000000`00000000 ffffe000`9c9c1000 ffffe000`9c9c1000 : nvlddmkm+0x1ea8e1

ffffd001`d5d29e60 fffff801`201e8939 : ffffe000`9c9c1000 ffffd001`d5d29f38 ffffe000`9c9c4000 00000000`00000000 : nvlddmkm+0x3f7e36

ffffd001`d5d29e90 fffff801`201e06aa : ffffe000`9c9c1000 ffffd001`d5d29f01 ffffe000`997f46f8 ffffe000`9e4e5010 : nvlddmkm+0x318939

ffffd001`d5d29ec0 fffff801`201df80e : 00000000`0000003d 00000000`00000000 ffffd001`d5d29f50 ffffe000`9c9c1000 : nvlddmkm+0x3106aa

ffffd001`d5d29f00 fffff801`201e6b88 : ffffe000`a5e646f0 ffffe000`9c9c1000 ffffe000`a15e83a0 00000000`00000001 : nvlddmkm+0x30f80e

ffffd001`d5d29f90 fffff801`201fd705 : ffffd001`00000000 ffffe000`9ead0220 ffffe000`a15e83a0 fffff801`00000001 : nvlddmkm+0x316b88

ffffd001`d5d2a000 fffff801`201e3d6f : ffffe000`997f46f8 ffffe000`9c9c1000 ffffe000`a15e83a0 00000000`00000015 : nvlddmkm+0x32d705

ffffd001`d5d2a060 fffff801`201e4c1e : ffffe000`9e4e5010 00000000`00000000 ffffd001`00000001 ffffd001`d5d2a160 : nvlddmkm+0x313d6f

ffffd001`d5d2a0e0 fffff801`2037a587 : 00000000`00000001 00000000`00000001 00000000`00000000 ffffe000`9c9c1000 : nvlddmkm+0x314c1e

ffffd001`d5d2a1a0 fffff801`2037914d : ffffd001`d5d2a300 ffffd001`d5d2a260 ffffe000`9c9eeab0 ffffe000`00000001 : nvlddmkm+0x4aa587

ffffd001`d5d2a200 fffff801`203799c6 : ffffe000`00010001 00000000`00000000 00000000`00000000 ffffd001`00000000 : nvlddmkm+0x4a914d

ffffd001`d5d2a2a0 fffff801`201e6969 : 00000000`efeff6ff ffffe000`124f0000 00000000`02000000 00000000`00000020 : nvlddmkm+0x4a99c6

ffffd001`d5d2a3b0 fffff801`201ea1fe : 00000000`00000003 00000000`00000001 ffffe000`997f46f8 ffffe000`9e488540 : nvlddmkm+0x316969

ffffd001`d5d2a450 fffff801`20719e24 : ffffe000`00000001 00000000`00000000 ffffe000`9e48b000 ffffe000`9c9eeab0 : nvlddmkm+0x31a1fe

ffffd001`d5d2a4f0 fffff801`201e611e : 00000000`00000000 00000000`00000000 00000000`20000000 ffffe000`9c9c1000 : nvlddmkm+0x849e24

ffffd001`d5d2a550 fffff801`201e6a49 : 00000000`60000000 ffffe000`9c9eeab0 0001d68a`4410e720 00000000`60000000 : nvlddmkm+0x31611e

ffffd001`d5d2a5e0 fffff801`200ba2de : ffffe000`9c9c1000 00000000`00000007 00000000`00000001 ffffe000`bd4b63c0 : nvlddmkm+0x316a49

ffffd001`d5d2a640 fffff801`200b9e6e : ffffe000`9c9c1000 00000000`00000007 ffffe000`9c9c4000 ffffe000`a11ffb60 : nvlddmkm+0x1ea2de

ffffd001`d5d2a670 fffff801`200ba069 : ffffe000`a774fe20 00000000`00000080 ffffe000`9c9c1000 ffffe000`00000017 : nvlddmkm+0x1e9e6e

ffffd001`d5d2a6d0 fffff801`200bab04 : 00000000`00000000 ffffd001`d5d2a829 ffffe000`9c9c4000 ffffe000`9c9c1000 : nvlddmkm+0x1ea069

ffffd001`d5d2a710 fffff801`2030fcaa : ffffe000`9c9c1000 ffffd001`d5d2a829 ffffe000`9c9c4000 00000000`00000200 : nvlddmkm+0x1eab04

ffffd001`d5d2a750 fffff801`20058908 : ffffe000`9c9c1000 ffffd001`d5d2a829 00000000`00000000 fffff801`4f13ac2a : nvlddmkm+0x43fcaa

ffffd001`d5d2a780 fffff801`4f12bc00 : ffffd001`d5d02f00 fffff801`4f085000 ffffd001`d5d2ab30 ffffe000`9c620f44 : nvlddmkm+0x188908

ffffd001`d5d2a890 fffff801`4f12aeb7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x1b0

ffffd001`d5d2a9e0 fffff801`4f1d97ea : ffffd001`d5d00180 ffffd001`d5d00180 ffffd001`d5d0c4c0 ffffe000`a84ee880 : nt!KiRetireDpcList+0xd7

ffffd001`d5d2ac60 00000000`00000000 : ffffd001`d5d2b000 ffffd001`d5d25000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP: 

nvlddmkm+1885d5

fffff801`200585d5 c3              ret

 

SYMBOL_STACK_INDEX:  7

 

SYMBOL_NAME:  nvlddmkm+1885d5

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: nvlddmkm

 

IMAGE_NAME:  nvlddmkm.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  55259065

 

FAILURE_BUCKET_ID:  0x133_DPC_nvlddmkm+1885d5

 

BUCKET_ID:  0x133_DPC_nvlddmkm+1885d5

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:0x133_dpc_nvlddmkm+1885d5

 

FAILURE_ID_HASH:  {c9e24edd-7a2f-1405-7f59-9be3f6f4b74b}

 

Followup: MachineOwner

 

WhoCrashedMe

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 5/2/2015 7:00:38 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\050215-51875-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 Sat 5/2/2015 7:00:38 AM GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1885D5)

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 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 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

4 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.

 

[CedarDpg]

Oh, also, ran memory tests on both GTX970s and both passed without errors.

[Urlan]

The one error suggests there is miscommunition between the processor's kernal and the video driver's texture handling. Something might not be getting sent though properly. Maybe there is a local setting blocking the memory reading, or resource being called is not able be read from both references. Other situations with a similar error log have been blamed on antivirus software making drivers time out on newer systems. Are you using Kaspersky? That antivirus was pegged as a possible culprit in one of Microsoft technet's similar user issues.

[Shi-Susanoo]

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 ?

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 ?

usually when a pc or laptop, usually laptops, overheat is because its not elevated or is running to a point where your system cant handle the game. Elevating your pc allows air to flow so it can breath and run smoother, depending on what your using of course. If u have a laptop try placing something under it so air can flow. If u were to keep using it on a flat surface it would kill your battery and all computer systems would be affected. If it still tends to overheat. It may be the game, so it would be good to run over all the settings and see what process could be causing it. Or your internet might be slow and your computer is having a really hard time trying to run wth it.

[[DE]Xander]

That antivirus was pegged as a possible culprit in one of Microsoft technet's similar user issues.

 

That's where things can get tricky, as the antivirus software's job is to hang out in the OS and watch all the files coming and going; it commonly gets accused for basically being in the wrong place at the wrong time. Sometimes it can be the cause though.

 

 

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)

 

Most of the memory dumps are complaining about your nvidia driver, which appears to be up to date (to be positive, you could attempt a clean uninstall/reinstall). This dump is interesting though, because it's complaining about your network driver. You should make sure your network driver is up to date, and as a previous user suggested, try disabling your antivirus temporarily to see if it's interfering.

[weezedog]

I have a GTX 970 and I have some driver crashes as well. I've posted the event logs in the Persistent Stuttering thread. Luckily mine has not been BSoDing, the driver has been able to recover to the desktop. I recently revalidated the local game cache through steam and redownloaded all the updates to make sure I didn't have any corrupted files. Now just waiting to see if the driver still crashes.

Part of me suspects an NVIDIA driver issue.

Edited May 4, 2015 by weezedog

[CedarDpg]

The one error suggests there is miscommunition between the processor's kernal and the video driver's texture handling. Something might not be getting sent though properly. Maybe there is a local setting blocking the memory reading, or resource being called is not able be read from both references. Other situations with a similar error log have been blamed on antivirus software making drivers time out on newer systems. Are you using Kaspersky? That antivirus was pegged as a possible culprit in one of Microsoft technet's similar user issues.

 

Yo. I'm using Norton.

 

That's where things can get tricky, as the antivirus software's job is to hang out in the OS and watch all the files coming and going; it commonly gets accused for basically being in the wrong place at the wrong time. Sometimes it can be the cause though.

 

 

 

Most of the memory dumps are complaining about your nvidia driver, which appears to be up to date (to be positive, you could attempt a clean uninstall/reinstall). This dump is interesting though, because it's complaining about your network driver. You should make sure your network driver is up to date, and as a previous user suggested, try disabling your antivirus temporarily to see if it's interfering.

 

Yeah, almost all of the past crash dump analyses involve the nVidia drivers. The ndis.sys thing appears to be relatively new. Dunno what's up with that. Network driver is up-to-date. The mobo is an MSI X99S Gaming 7 board...network driver is for "Killer Network" v 1.1.50.1073. I can try another clean reinstall with the nVidia drivers. It was actually one of the things I attempted in the past because of a different problem I had. (I'd get a random split second glitch in which all the screens would show some random lines of color up near the top of a black screen then return to normal. nVidia and other sites suggested that Microsoft Update messes some stuff up and installs its own version of the display driver alongside the nVidia one, so I did an uninstall and clean reinstall as per the website's suggestions, which got rid of the glitch.) I can try the reinstall process again if you think second time would be the charm. And I can try disabling the antivirus when I play.

[[DE]Xander]

 I can try the reinstall process again if you think second time would be the charm. And I can try disabling the antivirus when I play.

At this point I want to say there's a driver in there somewhere that's not playing nice. You could try to reinstall the nvidia drivers, but I don't have much hope for that will work if you've done it recently.

 

A much more complicated investigation would be to run Driver Verifier (verifier.exe) and allow it to crash your computer multiple times; those minidumps will hopefully reveal the bogus driver behind this all.

[Djangofett]

At this point I want to say there's a driver in there somewhere that's not playing nice. You could try to reinstall the nvidia drivers, but I don't have much hope for that will work if you've done it recently.

 

A much more complicated investigation would be to run Driver Verifier (verifier.exe) and allow it to crash your computer multiple times; those minidumps will hopefully reveal the bogus driver behind this all.

If for example it is a problem with the Nvidia Drivers, then why does Warframe has the same problem on an AMD gpu as well. Also these issues do not occur at all when playing any other game. I use a Radeon R9 290X and I run warframe on max settings on constant 60fps. But after the changes. I feel like I'm playing on integrated graphics.

[[DE]Xander]

If for example it is a problem with the Nvidia Drivers, then why does Warframe has the same problem on an AMD gpu as well. Also these issues do not occur at all when playing any other game. I use a Radeon R9 290X and I run warframe on max settings on constant 60fps. But after the changes. I feel like I'm playing on integrated graphics.

 

OP is experiencing display driver crashes, which can be caused by a variety of things, and aren't exclusive to Nvidia; this thread is specifically trying to deal with his particular crash.

 

As for your 290x, that's beyond the scope of this thread, so please make a new one; I'm curious if you're referring to a recent Warframe update that started your issues, or if you mean you switched to the beta catalyst drivers.

[Djangofett]

OP is experiencing display driver crashes, which can be caused by a variety of things, and aren't exclusive to Nvidia; this thread is specifically trying to deal with his particular crash.

 

As for your 290x, that's beyond the scope of this thread, so please make a new one; I'm curious if you're referring to a recent Warframe update that started your issues, or if you mean you switched to the beta catalyst drivers.

Recent Warframe Update as in U16 yes. Also I have reported this in Glen's AMD thread.

[dandeloreon]

I did have some crashing in my system too, and it's not resolved yet... To be exact, I am Geforce 347.88 ( previously) and 350.12 (current, after "Clean Install" ).

[CedarDpg]

At this point I want to say there's a driver in there somewhere that's not playing nice. You could try to reinstall the nvidia drivers, but I don't have much hope for that will work if you've done it recently.

 

A much more complicated investigation would be to run Driver Verifier (verifier.exe) and allow it to crash your computer multiple times; those minidumps will hopefully reveal the bogus driver behind this all.

 

Alrighty, I'll give verifier.exe a go as soon as I have a little bit of time to allow it to crash my computer.

[MillbrookWest]

What are the widgets you reference? Generally to collect data a program intercepts calls being sent through the system; MSI Afterburner can crash and cause issues with drivers (though it seldom does because the program has good support).

 

If the widget exists on your Keyboard, i'd imagine it was one of the first things you plugged in when you got the system, its driver/firmware may be outdated and it could cause issues intercepting Windows 8 system calls. 

 

Just my 2c on the fact it could literally be the tiniest of things causing that issue O_O

[CedarDpg]

Hmmm, so I started running verifier since I had a time where I could allow my computer to crash itself a bunch, and left the settings stock, which means it includes all of the Microsoft Windows drivers... I mean, what harm could there be from stressing out the drivers from Microsoft itself, right? They obviously do testing on their own drivers, right? Haha, wishful thinking. All of the crashes from that test run were from drivers written by Microsoft belonging to the operating system itself. And the crashes were practically immediate. So I eventually had to boot into safe mode to disable verifier, since the OS would crash too fast if I booted into normal mode.

 

I'll have to find another time to run verifier again, this time with only the non-Microsoft drivers selected in the driver stress test.

[TheFizio]

I have the same problem aswell... Since 16.4.5, warframe makes my PC end up in BSODs every time i play for more than 15 mins... and it used to run it smooth as hell before that update...

Edited May 15, 2015 by fizio900