[Random/Frequent BSODs] DPC_WATCHDOG_VIOLATION

A

Ainstra

New Member
Messages
6
I am at a standstill ever since I recieved this BSOD. At first I thought it was just a random crash and that I would've resolved it later, however it became frequent in just a matter of minutes. Playing a game, browsing the internet, listening to music, anything I do will result in another BSOD only just minutes later. It's completely random too.

This has happened a total of 6 times now and it started happening only just an hour ago. Sometime after the 4th BSOD, I tried getting my crash dump files before it happened, again. Right after the 5th BSOD I managed to obtain and zip my crash files but I couldn't even type in anything on the forum post before it happened yet again. If I leave my laptop idle or use applications that take a minimal amount of CPU/memory usage, everything remains normal. By minimal, I mean something like Notepad or Hamachi (I'm writing this on Notepad, before I copied it into the forum post).


Assuming it had something to do with the power options and Windows 8 Low Power Management system, I turned off the "Turn on quick startup" option hoping it would fix the issue. Unfortunately, it didn't. Now I'm just assuming it's either an application I installed; considering I didn't install anything onto my computer recently and the last time I installed an application was about a month ago, or it had something to do with the drivers.


I'd like do something about this as well to try and pinpoint the exact problem but I don't want to make any moves yet. I've attached my crash dump files with this post, along with everything else system related.


Appreciate what anyone can do to resolve this issue, because it's getting really frustrating to just try and do something without having another crash happen.
 

My Computer

System One

  • OS
    Windows 8 64-bit
Hi ainstra & Welcome to the forums ^_^,

I am extremely sorry for the late response. There are not enough analysts. Do you still need help with your problem? If you still need help with this, kindly reply back to this topic and I would reply within 48 hours and will be notified by email.


-Pranav
 

My Computer

System One

  • OS
    Windows 8.1 Industry Pro B-)
    Computer type
    Laptop
    System Manufacturer/Model
    Toshiba
    CPU
    Core I5 2430M @ 2.4GHz
    Memory
    8 GB DDR3 @ 1600MHz Dual Channel ^_^
    Graphics Card(s)
    Intel HD 3000 B-)
    Screen Resolution
    1366x768
    Hard Drives
    Toshiba 500 GB
    Browser
    Google Chrome
    Antivirus
    Windows Defender & Common Sense!
Well, it's alright. I already know there aren't a lot of people who monitor the BSOD section, and the issue itself had seemed to go away the next day.

I'd still like to know the problem that caused the crash in order to fix it should it arise again.
 

My Computer

System One

  • OS
    Windows 8 64-bit
Hi Ainstra ^_^,

Thank you for understanding the situation :)
I have analysed the dump files and below has been provided an analysis of the same for informative purposes :-
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
Code: 
2: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`016943c8 fffff800`6ebf2fbb nt!KeBugCheckEx
01 fffff880`016943d0 fffff800`6eab77d4 nt! ?? ::FNODOBFM::`string'+0x145a4
02 fffff880`01694450 fffff800`6f187eba nt!KeUpdateTime+0x2ec
03 fffff880`01694630 fffff800`6ea6bfce hal!HalpTimerClockInterrupt+0x86
04 fffff880`01694660 fffff800`6ea542e3 nt!KiInterruptDispatchLBControl+0x1ce
05 fffff880`016947f0 fffff800`6eac5565 nt!KxWaitForSpinLockAndAcquire+0x23
06 fffff880`01694820 fffff880`03e03608 nt!KeAcquireSpinLockRaiseToDpc+0x35
07 fffff880`01694850 fffffa80`0ada4980 [U][B][COLOR=#FF0000]Hamdrv[/COLOR][/B][/U]+0x3608
08 fffff880`01694858 fffff880`01694950 0xfffffa80`0ada4980
09 fffff880`01694860 fffffa80`0ada4980 0xfffff880`01694950
0a fffff880`01694868 fffffa80`0e173d30 0xfffffa80`0ada4980
0b fffff880`01694870 fffffa80`0e173d30 0xfffffa80`0e173d30
0c fffff880`01694878 00000000`00000001 0xfffffa80`0e173d30
0d fffff880`01694880 fffffa80`00000056 0x1
0e fffff880`01694888 fffff880`01694910 0xfffffa80`00000056
0f fffff880`01694890 fffff880`01694966 0xfffff880`01694910
10 fffff880`01694898 00000000`00000000 0xfffff880`01694966
So, the system crashed because Windows detected that Hamdrv.sys (LogMeIn Hamachi) raised the IRQL (Interrupt ReQuest Level) for a longer time than the time it was allotted and hence the system crashed.

The problem was probably caused by LogMein Hamachi. The problem could have cropped up because you are using multiple VPNs as well.

In case of any further problems, please do not hesitate to post back ^_^

-Pranav
 

My Computer

System One

  • OS
    Windows 8.1 Industry Pro B-)
    Computer type
    Laptop
    System Manufacturer/Model
    Toshiba
    CPU
    Core I5 2430M @ 2.4GHz
    Memory
    8 GB DDR3 @ 1600MHz Dual Channel ^_^
    Graphics Card(s)
    Intel HD 3000 B-)
    Screen Resolution
    1366x768
    Hard Drives
    Toshiba 500 GB
    Browser
    Google Chrome
    Antivirus
    Windows Defender & Common Sense!
Hi again,

The issue has returned but the problem doesn't seem to be Hamachi now. With this post, I've attached my new crash dump files. SF Diagnostic Tool failed to gather information because of an unhandled exception error, so instead I've used DM Log Collector.
 

My Computer

System One

  • OS
    Windows 8 64-bit
Code: 
0: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000000 00000000`00000501 00000000`00000500 00000000`00000000

0: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff801`fff67bb8 fffff802`0025cd9b nt!KeBugCheckEx
01 fffff801`fff67bc0 fffff802`00121921 nt! ?? ::FNODOBFM::`string'+0x142f2
02 fffff801`fff67c40 fffff802`00039e94 nt!KeUpdateRunTime+0x51
03 fffff801`fff67c70 fffff802`000d5fde hal!HalpTimerClockInterrupt+0x50
04 fffff801`fff67ca0 fffff802`000be2b3 nt!KiInterruptDispatchLBControl+0x1ce
05 fffff801`fff67e30 fffff802`0012f5e5 nt!KxWaitForSpinLockAndAcquire+0x23
06 fffff801`fff67e60 fffff880`01a32608 nt!KeAcquireSpinLockRaiseToDpc+0x35
07 fffff801`fff67e90 fffffa80`0af17040 Hamdrv+0x3608
08 fffff801`fff67e98 fffff801`fff67f90 0xfffffa80`0af17040
09 fffff801`fff67ea0 fffffa80`0af17040 0xfffff801`fff67f90
0a fffff801`fff67ea8 fffffa80`0e455190 0xfffffa80`0af17040
0b fffff801`fff67eb0 fffffa80`0e455190 0xfffffa80`0e455190
0c fffff801`fff67eb8 00000000`00000001 0xfffffa80`0e455190
0d fffff801`fff67ec0 fffffa80`00000042 0x1
0e fffff801`fff67ec8 fffff801`fff67f50 0xfffffa80`00000042
0f fffff801`fff67ed0 fffff801`fff67f92 0xfffff801`fff67f50
10 fffff801`fff67ed8 00000000`00000000 0xfffff801`fff67f92


Code: 
0: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00001e00 00000000`00000000 00000000`00000000
0: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff880`1baf94d8 fffff803`345f6df3 nt!KeBugCheckEx [COLOR=#800080]//BSOD[/COLOR]
01 fffff880`1baf94e0 fffff803`344baeb4 nt!KeAccumulateTicks+0x1434e [COLOR=#800080]//Count ticks[/COLOR]
02 fffff880`1baf9560 fffff803`34b88eca nt!KeUpdateTime+0x2ec [COLOR=#800080]//Update the system time[/COLOR]
03 fffff880`1baf9740 fffff803`3446ffde hal!HalpTimerClockInterrupt+0x86[COLOR=#800080] //Clock interrupt[/COLOR]
04 fffff880`1baf9770 fffff803`344582b0 nt!KiInterruptDispatchLBControl+0x1ce [COLOR=#800080]//Interrupt routine[/COLOR]
05 fffff880`1baf9900 fffff803`344c95e5 nt!KxWaitForSpinLockAndAcquire+0x20 [COLOR=#800080]//Spin on the lock and acquire when available[/COLOR]
06 fffff880`1baf9930 fffff880`1bc11608 nt!KeAcquireSpinLockRaiseToDpc+0x35 [COLOR=#800080]//Acquire spinlock and raise the IRQL to dispatch/DPC level[/COLOR]
07 fffff880`1baf9960 fffffa80`0ad3b900 Hamdrv+0x3608 [COLOR=#800080]//LogMeIn Hamachi[/COLOR]
08 fffff880`1baf9968 fffff880`1baf9a60 0xfffffa80`0ad3b900
09 fffff880`1baf9970 fffffa80`0ad3b900 0xfffff880`1baf9a60
0a fffff880`1baf9978 fffffa80`08584aa0 0xfffffa80`0ad3b900
0b fffff880`1baf9980 fffffa80`08584aa0 0xfffffa80`08584aa0
0c fffff880`1baf9988 fffffa80`085707b4 0xfffffa80`08584aa0
0d fffff880`1baf9990 fffffa80`00000036 0xfffffa80`085707b4
0e fffff880`1baf9998 fffff880`1baf9a20 0xfffffa80`00000036
0f fffff880`1baf99a0 fffff880`1baf9a56 0xfffff880`1baf9a20
10 fffff880`1baf99a8 fffffa80`0b0ccd01 0xfffff880`1baf9a56
11 fffff880`1baf99b0 fffff880`1baf9998 0xfffffa80`0b0ccd01
12 fffff880`1baf99b8 00000000`00000421 0xfffff880`1baf9998
13 fffff880`1baf99c0 fffff880`1baf9a20 0x421
14 fffff880`1baf99c8 fffff880`1baf9a2e 0xfffff880`1baf9a20
15 fffff880`1baf99d0 fffff880`1baf9a2e 0xfffff880`1baf9a2e
16 fffff880`1baf99d8 fffff880`1baf9a42 0xfffff880`1baf9a2e
17 fffff880`1baf99e0 fffff880`1baf9a42 0xfffff880`1baf9a42
18 fffff880`1baf99e8 fffff880`1baf9a56 0xfffff880`1baf9a42
19 fffff880`1baf99f0 fffff880`1baf9a56 0xfffff880`1baf9a56
1a fffff880`1baf99f8 fffff880`1baf9a56 0xfffff880`1baf9a56
1b fffff880`1baf9a00 fffff880`1baf9a56 0xfffff880`1baf9a56
1c fffff880`1baf9a08 fffff880`1baf9a56 0xfffff880`1baf9a56
1d fffff880`1baf9a10 ffff5927`3719797a 0xfffff880`1baf9a56
1e fffff880`1baf9a18 fffff803`34b6efdb 0xffff5927`3719797a [COLOR=#800080]//Context not saved[/COLOR]
1f fffff880`1baf9a20 fffff803`34b6dcd5 hal!HalpMapTransferV2+0x7f [COLOR=#800080]//Map the transfer[/COLOR]
20 fffff880`1baf9ab0 fffff803`34b72534 hal!IoMapTransferInternal+0x10d [COLOR=#800080]//IO map data transfer[/COLOR]
21 fffff880`1baf9af0 fffff880`01eecbcb hal!HalpAllocateAdapterCallbackV2+0x14c [COLOR=#800080]//Allocate a callback routine[/COLOR]
22 fffff880`1baf9b80 fffff880`01eec8b5 wfplwfs!L2pNativeLayerDirectClassify+0x2eb [COLOR=#800080]//Direct access[/COLOR]
23 fffff880`1baf9e90 fffff880`01eecca5 wfplwfs!L2NativeIsNetBufferListPermitted+0x235 [COLOR=#800080]//Check the autentication for this net buffer[/COLOR]
24 fffff880`1baf9fa0 00000000`00000000 wfplwfs!L2InspectNetBufferLists+0xb5[COLOR=#800080] //Inspect the net buffer lists
[/COLOR]
0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 13

We can see in both bugchecks, the hamachi driver failed to complete its work in time, thus crashing the system.
It most likely failed to expire its timers on the current hand. What is usually meant to happen is the driver should set the task in a DPC object to stop the system being at DIRQL for too long.

Code: 
0: kd> lmvm hamdrv
start             end                 module name
fffff880`1bc0e000 fffff880`1bc1c000   Hamdrv   T (no symbols)           
    Loaded symbol image file: Hamdrv.sys
    Image path: \SystemRoot\system32\DRIVERS\Hamdrv.sys
    Image name: Hamdrv.sys
    Timestamp:        Sat Dec 13 16:01:02 2014 (548C62BE)
    CheckSum:         00018090
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If there's an update I reccomend you to install it, if not then I would consider finding some different software to use.
 

My Computer

System One

  • OS
    Windows 7
You must log in or register to reply here.
Back
Top