DPC Watchdog Violation BSOD

[danjedwards123]

In the past week or so my computer has been freezing, followed by a DPC Watchdog Violation BSOD then restarting, it seems to occur randomly. It occurs a few times a day and has only come up in the past week or so. I have just updated my SSD firmware and Graphics Card driver but it hasn't helped. I have a couple of dmp. files from the crashes but I can't upload them here, so the link to my last dump is below.

https://www.dropbox.com/s/b2lgn2rc5nu2w4t/053116-38671-01.dmp?dl=0

Thanks in advance.

 

[Regedit32]

Hi,

From the looks of it your system is hanging on the ntoskrnl.exe leading up to your DPC ERROR.

The question I have for you is whether you received this error prior to upgrading your SSD firmware. I ask as this is most likely the root of your issue.

If there was not troubles prior to upgrading the SSD firmware I'd be considering the following:

• Right-click on Start | select Device Manager
• Expand Disk drives and right-click your SSD | select Update Driver Software
  
• In window that opens select Browse my computer for driver software
• Click Let me pick from a list of device drivers from my computer
• Uncheck Show compatible hardware
  
  Select the previous driver prior to your recent upgrade and apply changes then restart computer

 

[danjedwards123]

I got the bsod then updated drivers and continued to receive them. So I'm guessing there isn't a specific cause and could be down to a number of potential causes?

 

[Regedit32]

Have you checked event viewer to see if there is more information of the error?

Right-click Start | select Event Viewer | review error messages date/time matching your BSOD error

Have you tried using a restore point to a time before the BSOD began. Perhaps something else you've installed has caused the troubles.

You could also consider a SFC /SCANNOW and/or a CHKDSK /F via an elevated command prompt.

 

[Trouble]

Something seems to be blowing up your network stack and I'm thinking that it might have something to do with
nldrv.sys 2/18/2016 NetLimiter 4 Driver LockTime Software

BugCheck 133, {0, 501, 500, 0}
*** WARNING: Unable to verify timestamp for nldrv.sys
*** ERROR: Module load completed but symbols could not be loaded for nldrv.sys
Probably caused by : NETIO.SYS ( NETIO!WfpInsertEntryLru+55 )

STACK_TEXT:
ffffd000`204d4d48 fffff802`d03e7e61 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd000`204d4d50 fffff802`d02ab037 : 00000000`00000000 00000000`00000001 fffff802`d0571e80 ffffd000`2049c180 : nt! ?? ::FNODOBFM::`string'+0xad61
ffffd000`204d4de0 fffff802`d021b9c5 : 00000000`00000000 ffffd000`2049c180 ffffd000`204cbc00 00000cb0`ac80dc04 : nt!KeClockInterruptNotify+0xa7
ffffd000`204d4f40 fffff802`d0375197 : ffffe001`766c8700 00000000`00000000 fffff586`8c048376 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffd000`204d4f70 fffff802`d03cfb8a : ffffe001`766c8600 ffffd000`204cbc00 00000000`00000000 00000000`003cb70e : nt!KiCallInterruptServiceRoutine+0x87
ffffd000`204d4fb0 fffff802`d03cffb7 : 00000001`00000000 ffffd000`204cba01 00000000`00000000 ffffd000`204cc0f0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`204cb9f0 fffff802`d02ed3c0 : ffffd000`204cbc90 fffff802`d033cd6e ffffe001`8018bd30 ffffd000`204cc0f0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd000`204cbb80 fffff802`d02ed374 : ffffe001`77597401 ffffe001`81f55040 00000da1`e473aae2 fffff800`63c78824 : nt!KxWaitForLockOwnerShip+0x30
ffffd000`204cbbb0 fffff800`63c88505 : 00000000`00000000 00000000`00000000 ffffe001`775ea1d0 ffffe001`81f55040 : nt!KeAcquireInStackQueuedSpinLock+0x44
ffffd000`204cbbe0 fffff800`63d37a8a : ffffe001`77597438 ffffd000`204cbd30 ffffe001`775973d0 00000000`00000001 : NETIO!WfpInsertEntryLru+0x55
ffffd000`204cbc30 fffff800`63d39d88 : ffffe001`80e7ed50 ffffe001`775e0002 ffffe001`775ed490 ffffe001`802f4620 : tcpip!WfpAleInsertRemoteEndpoint+0x956
ffffd000`204cbfe0 fffff800`63d387a9 : ffffe001`7a5cd220 ffffe001`775e9640 ffffe001`c8de6220 f8556a48`deeeb471 : tcpip!WfpAlepAuthorizeSend+0x1268
ffffd000`204cc410 fffff800`63d31b61 : ffffe001`7754b700 ffffd000`204ccfc8 ffffd000`204cc9c0 fffff800`6760f324 : tcpip!WfpAleAuthorizeSend+0x385
ffffd000`204cc7b0 fffff800`63d30d38 : 00000000`00000480 00000000`00000010 ffffd000`204cd010 ffffd000`204cd068 : tcpip!ProcessALEForTransportPacket+0x8c1
ffffd000`204cca90 fffff800`63d59994 : fffff800`66e3eef0 ffffe001`7a732e20 00000000`00000000 00000000`00000000 : tcpip!WfpProcessOutTransportStackIndication+0x378
ffffd000`204ccdb0 fffff800`63d57e58 : ffffe001`77e02a70 00000000`00000000 ffffe001`77e02b58 fffff800`63ecc000 : tcpip!IppInspectLocalDatagramsOut+0xf64
ffffd000`204cd0c0 fffff800`63e71ede : 00000000`00000000 ffffd000`204cd304 fffff800`63ecc000 ffffe001`80e7ed50 : tcpip!IppSendDatagramsCommon+0x408
ffffd000`204cd2c0 fffff800`63f94f30 : ffffe001`80ab6040 00001ffe`84eeaf04 fffff800`63f94e90 fffff800`63c7199b : tcpip!IppInspectInjectTlSend+0x16e
ffffd000`204cd3f0 fffff802`d029d6f5 : ffffd000`204cd5d0 ffffd000`204cd5d0 00000000`00000000 ffffe001`80bbb1e8 : fwpkclnt!FwppInjectionStackCallout+0xa0
ffffd000`204cd480 fffff800`63f96886 : ffffe001`7739f410 ffffe001`cb2cf7a0 ffffe001`773a5100 ffffe001`77399460 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd000`204cd4d0 fffff800`63f94e4e : 00000000`00000004 ffffd000`204cd610 ffffd000`204cd610 ffffe001`cb2cf7a0 : fwpkclnt!NetioExpandKernelStackAndCallout+0x52
ffffd000`204cd510 fffff800`63f96553 : ffffe001`00000000 ffffe001`80a67b90 ffffe001`77b7a998 00000000`00000687 : fwpkclnt!FwppInjectTransportSendAsync+0x552
ffffd000`204cd710 fffff800`67614439 : ffffe001`812bac18 00000000`00000000 ffffe001`812bac18 ffffd000`204cd802 : fwpkclnt!FwpsInjectTransportSendAsync0+0x63
ffffd000`204cd780 ffffe001`812bac18 : 00000000`00000000 ffffe001`812bac18 ffffd000`204cd802 ffffe001`c57b87a0 : nldrv+0x14439
ffffd000`204cd788 00000000`00000000 : ffffe001`812bac18 ffffd000`204cd802 ffffe001`c57b87a0 00000000`00000002 : 0xffffe001`812bac18

Most of the remainder of the stack
fwpkclnt, tcpip, NETIO
are native Windows drivers and while included in the stack trace are not likely to be responsible. Generally a third party driver is at fault.
I'm not familiar with Locktime Software or NetLimiter 4 Driver, but.....
IF it was me... that's where I would start.