Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
- Copyright (c) Microsoft Corporation. All rights reserved.
- Loading Dump File [C:\Windows\MEMORY.DMP]
- Kernel Bitmap Dump File: Only kernel address space is available
- ************* Symbol Path validation summary **************
- Response Time (ms) Location
- OK c:\symbols\private
- Deferred srv*c:\symbols\web*http://msdl.microsoft.com/download/symbols
- ************* Symbol Path validation summary **************
- Response Time (ms) Location
- OK c:\symbols\private
- Deferred srv*c:\symbols\web*http://msdl.microsoft.com/download/symbols
- Symbol search path is: c:\symbols\private;srv*c:\symbols\web*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 Personal
- Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
- Machine Name:
- Kernel base = 0xfffff802`dc676000 PsLoadedModuleList = 0xfffff802`dc94f850
- Debug session time: Wed May 27 09:17:12.780 2015 (UTC + 8:00)
- System Uptime: 0 days 0:40:20.489
- Loading Kernel Symbols
- ...............................................................
- ................................................................
- .................................
- Loading User Symbols
- Loading unloaded module list
- ........
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- Use !analyze -v to get detailed debugging information.
- BugCheck 133, {0, 501, 500, 0}
- *** ERROR: Module load completed but symbols could not be loaded for HpCISSs3.sys
- Probably caused by : HpCISSs3.sys ( HpCISSs3+cebb )
- Followup: MachineOwner
- ---------
- 5: kd> !analyze -v
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- 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
- DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
- BUGCHECK_STR: 0x133
- PROCESS_NAME: System
- CURRENT_IRQL: d
- ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
- LAST_CONTROL_TRANSFER: from fffff802dc7e1f28 to fffff802dc7c6ca0
- STACK_TEXT:
- ffffd000`206f1c88 fffff802`dc7e1f28 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
- ffffd000`206f1c90 fffff802`dc6b2f67 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xad68
- ffffd000`206f1d20 fffff802`dc60e67f : fffff802`dc62214c fffff802`dc74d12e ffffe000`962012b0 00000000`00000001 : nt!KeClockInterruptNotify+0x787
- ffffd000`206f1f40 fffff802`dc74d143 : ffffe000`96201200 00000000`00000000 ffffd000`206c6340 fffff802`dc676000 : hal!HalpTimerClockInterrupt+0x4f
- ffffd000`206f1f70 fffff802`dc7c812a : ffffe000`96201200 00000696`1badc61b 00000000`00000001 fffff969`e454898d : nt!KiCallInterruptServiceRoutine+0xa3
- ffffd000`206f1fb0 fffff802`dc7c850f : 00000000`00000000 00000000`00000000 00000028`00000000 00001fa0`007c061c : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
- ffffd000`206bf290 fffff802`dc60b6b1 : 00000000`00000010 00000000`00000282 ffffd000`206bf440 00000000`00000018 : nt!KiInterruptDispatchLBControl+0x11f
- ffffd000`206bf420 fffff800`e5da1ebb : ffffe000`99dae010 ffffe000`99dae010 00000000`00000000 00000000`00000000 : hal!KeStallExecutionProcessor+0x123
- ffffd000`206bf4b0 fffff800`e5da0cb9 : ffffe000`99dae010 ffffe000`99dae010 00000000`00000005 ffffffff`ffffffff : HpCISSs3+0xcebb
- ffffd000`206bf510 fffff800`e5d9e468 : ffffe000`000b1000 00000000`00000000 00000000`00000000 ffffe000`9a566010 : HpCISSs3+0xbcb9
- ffffd000`206bf6a0 fffff800`e49221e2 : ffffe000`99da91a0 ffffe000`9a566010 ffffe000`9c745002 00000000`00000004 : HpCISSs3+0x9468
- ffffd000`206bf6f0 fffff800`e4923d34 : ffffe000`99da91a0 ffffe000`9c745010 ffffe000`99e63050 ffffe000`9bfe5128 : storport!RaCallMiniportAdapterControl+0x22
- ffffd000`206bf720 fffff800`e4923bc2 : ffffe000`99da91a0 ffffe000`9c745010 ffffe000`9bfe5010 ffffd000`206bf780 : storport!RaidAdapterRestartAdapter+0x44
- ffffd000`206bf750 fffff800`e491c9d3 : ffffe000`99da91a0 00000000`00000000 fffff802`dc7af1fc fffff802`dc71d662 : storport!RaidAdapterPowerUpDeviceCompletionLastStep+0x32
- ffffd000`206bf7b0 fffff802`dc71cc00 : ffffd000`206bf990 fffff802`dc966940 ffffd000`206bfba0 ffffe000`99da9118 : storport!RaidpAdapterDpcRoutine+0xf3
- ffffd000`206bf890 fffff802`dc71beb7 : 00000000`00000000 00000000`00000000 ffffd000`206c0180 00000000`00000000 : nt!KiExecuteAllDpcs+0x1b0
- ffffd000`206bf9e0 fffff802`dc7ca7ea : ffffd000`206c0180 ffffd000`206c0180 ffffd000`206cc3c0 ffffe000`9b65e080 : nt!KiRetireDpcList+0xd7
- ffffd000`206bfc60 00000000`00000000 : ffffd000`206c0000 ffffd000`206ba000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
- STACK_COMMAND: kb
- FOLLOWUP_IP:
- HpCISSs3+cebb
- fffff800`e5da1ebb ffc7 inc edi
- SYMBOL_STACK_INDEX: 8
- SYMBOL_NAME: HpCISSs3+cebb
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: HpCISSs3
- IMAGE_NAME: HpCISSs3.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 546f6971
- FAILURE_BUCKET_ID: 0x133_DPC_HpCISSs3+cebb
- BUCKET_ID: 0x133_DPC_HpCISSs3+cebb
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:0x133_dpc_hpcisss3+cebb
- FAILURE_ID_HASH: {ce030135-c8cb-8d6f-1b50-3c5c1e821bd4}
- Followup: MachineOwner
- ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement