Windows 8.1 Pro DPC_WATCHDOG_VIOLATION BSOD

Question

I built a PC a few months ago, and recently decided to move to Windows 8. I had a Windows 8 upgrade key, so I had to go through Windows 8 before I could move to 8.1. Before I could upgrade to 8.1, I needed my Ethernet driver updated, because W8 does not
have the proper Intel I217-V driver. I downloaded the latest driver off of the internet, and when I went to install it, every time just before the installation finished, I got a BSOD (DPC_WATCHDOG_VIOLATION). I had to install the drivers off the CD. I upgraded
to Windows 8.1, and updated the drivers without a problem. But now, every once in a while, I get the same BSOD in the Windows 8.1 login screen. I have uploaded the dump file to SkyDrive.
http://sdrv.ms/Ml26aW

Answer 1

D4
This one was related to a known problem with LogMeIn Hamachi Virtual Miniport Driver. Driver Update Site: https://secure.logmein.com/products/ios/
Their 1/23/2014 driver (which is your date) is buggy.  I suggest you contact them for a patch, beta, or work around or wailing that revert to an older driver until they figure it out
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\013014-6031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff802`a1674000 PsLoadedModuleList = 0xfffff802`a1938990
Debug session time: Thu Jan 30 09:32:29.245 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:21.933
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 44, {ffffe00003338db0, f8a, 0, 0}
*** WARNING: Unable to verify timestamp for Hamdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for Hamdrv.sys
Probably caused by : Hamdrv.sys ( Hamdrv+1f0a )
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffe00003338db0, Address of the IRP
Arg2: 0000000000000f8a
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
IRP_ADDRESS: ffffe00003338db0
FOLLOWUP_IP:
Hamdrv+1f0a
fffff800`01985f0a ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
DEVICE_OBJECT: ffffe00001fcb9e0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff802a17fcb4b to fffff802a17c1ca0
STACK_TEXT:
ffffd000`22bc9818 fffff802`a17fcb4b : 00000000`00000044 ffffe000`03338db0 00000000`00000f8a 00000000`00000000 : nt!KeBugCheckEx
ffffd000`22bc9820 fffff800`01985f0a : 00000000`00000000 ffffd000`2256bb00 ffffe000`01f6db80 ffffe000`01f6db80 : nt! ?? ::FNODOBFM::`string'+0x2a9ab
ffffd000`22bc9930 00000000`00000000 : ffffd000`2256bb00 ffffe000`01f6db80 ffffe000`01f6db80 ffffd000`00000020 : Hamdrv+0x1f0a
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Hamdrv+1f0a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Hamdrv
IMAGE_NAME: Hamdrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52e10c23
FAILURE_BUCKET_ID: 0x44_Hamdrv+1f0a
BUCKET_ID: 0x44_Hamdrv+1f0a
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x44_hamdrv+1f0a
FAILURE_ID_HASH: {af270f7d-2329-db64-39cf-85dffdd63412}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag