Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Server 2012 R2 WatchDog Violation

  • Please log in to reply
1 reply to this topic

#1 Bookerf


  • Members
  • 1 posts
  • Local time:08:42 PM

Posted 24 May 2015 - 02:43 PM

Hey guys I need help with this one, I'll attach the dmp file. Any ideas or tips would be great. Thanks!


*Update I'm now also receiving the following error message upon start up. Not sure if there related but just in case here it is.


   TAPIBrowser MFC Application has stopped working:


   Problem Event Name: BEX

   Application Name: mszdf.exe



The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
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:
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff8003dbecf28 to fffff8003dbd1ca0
ffffd001`55fc6c88 fffff800`3dbecf28 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd001`55fc6c90 fffff800`3dabd871 : 00000000`00000000 00000000`000ef645 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xad68
ffffd001`55fc6d20 fffff800`3da197b5 : ffffe000`c3325040 ffffe000`c4ea5880 ffffd001`55f51d40 fffff800`3da81000 : nt!KeClockInterruptNotify+0x91
ffffd001`55fc6f40 fffff800`3db58143 : ffffd001`55f75b50 fffff800`3db80057 ffffd001`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`55fc6f70 fffff800`3dbd312a : ffffe000`c3401b00 ffffe000`c3e909b0 ffffe000`c3e8c778 ffffe000`c3e8c730 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`55fc6fb0 fffff800`3dbd350f : 00000000`00000000 fffff800`a3ac5238 ffff252b`62d21b00 00000000`00000f3f : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`55f75720 fffff800`3db5911b : 0000004c`82a33f4a fffff800`a3a835b3 00000000`00000031 00000000`0002fc18 : nt!KiInterruptDispatchLBControl+0x11f
ffffd001`55f758b0 fffff800`3db763f1 : 00000000`00000002 ffffa476`60c02b77 00000000`00000000 ffffe000`c442a510 : nt!KxWaitForSpinLockAndAcquire+0x1f
ffffd001`55f758e0 fffff800`a4a2d248 : ffffd001`55f4b180 ffffd001`55f4b180 ffffd001`55f75a20 00000008`598e7c8a : nt!KeAcquireInterruptSpinLock+0x45
ffffd001`55f75920 fffff800`a4a12470 : ffffd001`55f759b0 00000000`00000000 ffffffff`a3000100 00000000`00000001 : storport!RaidAdapterAcquireInterruptLock+0x18258
ffffd001`55f75950 fffff800`a4a17fe1 : ffffa476`ffffffff 00000008`598f8ac3 ffffe000`c37e1480 00000000`00000001 : storport!RaidAdapterAcquireStartIoLock+0x2a
ffffd001`55f75980 fffff800`3db272d8 : ffffd001`55f75b20 00000000`0023c34a ffffffff`b8797400 ffffd001`00000000 : storport!RaidpAdapterTimerDpcRoutine+0x49
ffffd001`55f759e0 fffff800`3dbd57ea : ffffd001`55f4b180 ffffd001`55f4b180 ffffd001`55f57dc0 ffffe000`c4ea5880 : nt!KiRetireDpcList+0x4f8
ffffd001`55f75c60 00000000`00000000 : ffffd001`55f76000 ffffd001`55f70000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
fffff800`a4a2d248 8ad8            mov     bl,al
SYMBOL_NAME:  storport!RaidAdapterAcquireInterruptLock+18258
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: storport
IMAGE_NAME:  storport.sys
IMAGE_VERSION:  6.3.9600.17383
FAILURE_BUCKET_ID:  0x133_DPC_storport!RaidAdapterAcquireInterruptLock
BUCKET_ID:  0x133_DPC_storport!RaidAdapterAcquireInterruptLock
FAILURE_ID_HASH_STRING:  km:0x133_dpc_storport!raidadapteracquireinterruptlock
FAILURE_ID_HASH:  {68c01c36-9815-9d5d-7186-f981078389f4}
Followup: MachineOwner

Edited by Bookerf, 24 May 2015 - 03:02 PM.

BC AdBot (Login to Remove)


#2 Wand3r3r


  • Members
  • 2,027 posts
  • Local time:05:42 PM

Posted 26 May 2015 - 11:46 AM

Appears to me that you are having a issue with a raid controller driver or the driver is having a issue with the hardware.  See if you can find a updated driver for your raid controller would be my suggestion.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users