hi,
after i update to 8.1 im keep getting dpc watchdog violation
heres my minidump https://skydrive.live.com/?lc=1086&mkt=ms-MY#cid=A14A4FE13CFBC2E0&qt=sharedby
thank you in advanced.
liran
Technology Tips and News
hi,
after i update to 8.1 im keep getting dpc watchdog violation
heres my minidump https://skydrive.live.com/?lc=1086&mkt=ms-MY#cid=A14A4FE13CFBC2E0&qt=sharedby
thank you in advanced.
liran
LIranoz
This was Related to
SAlpham64.sys HID Driver from SteelSeries Corporation I would install the newest driver available.
Windows 8 Kernel Version 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505 Machine Name: Kernel base = 0xfffff803`3aa11000 PsLoadedModuleList = 0xfffff803`3acd5990 Debug session time: Sun Jan 19 12:23:44.116 2014 (UTC - 5:00) System Uptime: 0 days 0:01:13.784 BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for SAlpham64.sys *** ERROR: Module load completed but symbols could not be loaded for SAlpham64.sys Probably caused by : SAlpham64.sys ( SAlpham64+32c0 ) 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: ------------------ DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x133 PROCESS_NAME: System CURRENT_IRQL: d ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from fffff8033ab82f7c to fffff8033ab5eca0 STACK_TEXT: fffff803`3c432e38 fffff803`3ab82f7c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx fffff803`3c432e40 fffff803`3aa6581b : ffffd000`20d0a6f0 fffff803`3acff180 ffffd000`00000000 00000000`0000000a : nt! ?? ::FNODOBFM::`string'+0x13ddc fffff803`3c432ed0 fffff803`3abe43a3 : fffff803`3b1e5800 fffff803`3acff180 00000000`00000001 ffffe000`0214aae8 : nt!KiUpdateRunTime+0x57 fffff803`3c432f10 fffff803`3b198f85 : ffffe000`021461a0 fffff803`00000000 ffffd000`20d0a780 ffffd000`20d0a500 : nt!KeClockInterruptNotify+0xe3 fffff803`3c432f40 fffff803`3aaa7343 : ffffd000`20d0a3c0 fffff803`3c424150 ffffd000`20d0aa08 fffff803`3ab5fd4a : hal!HalpTimerClockIpiRoutine+0x15 fffff803`3c432f70 fffff803`3ab6012a : fffff803`3b1e5800 ffffe000`0214aae8 ffffffff`c0000120 ffffe000`0214a730 : nt!KiCallInterruptServiceRoutine+0xa3 fffff803`3c432fb0 fffff803`3ab6050f : 00000000`00000001 fffff800`0165d961 ffffe000`05333198 fffff803`3c424220 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea fffff803`3c4240d0 fffff803`3aaa5df8 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff803`3acb0100 : nt!KiInterruptDispatchLBControl+0x11f fffff803`3c424260 fffff803`3aaa5dc2 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x18 fffff803`3c424290 fffff800`028ef2c0 : 00000000`00000002 00000000`00000000 00000000`0d0d0d0d 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x32 fffff803`3c4242c0 00000000`00000002 : 00000000`00000000 00000000`0d0d0d0d 00000000`00000000 00000000`00000000 : SAlpham64+0x32c0 fffff803`3c4242c8 00000000`00000000 : 00000000`0d0d0d0d 00000000`00000000 00000000`00000000 fffff803`3aac209f : 0x2 STACK_COMMAND: kb FOLLOWUP_IP: SAlpham64+32c0 fffff800`028ef2c0 ?? ??? SYMBOL_STACK_INDEX: a SYMBOL_NAME: SAlpham64+32c0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: SAlpham64 IMAGE_NAME: SAlpham64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e739ccd FAILURE_BUCKET_ID: 0x133_DPC_SAlpham64+32c0 BUCKET_ID: 0x133_DPC_SAlpham64+32c0 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x133_dpc_salpham64+32c0 FAILURE_ID_HASH: {d7ac8d78-d9d8-aca5-9ad9-122f8f02cd16} Followup: MachineOwner ---------