Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Microsoft (R) Windows Debugger Version 10.0.17763.132 X86
- Copyright (c) Microsoft Corporation. All rights reserved.
- Loading Dump File [D:\Downloads\bluescreenview-x64\020719-9500-01.dmp]
- Mini Kernel Dump File: Only registers and stack trace are available
- Symbol search path is: srv*
- Executable search path is:
- Windows 10 Kernel Version 17763 MP (16 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS
- Built by: 17763.1.amd64fre.rs5_release.180914-1434
- Machine Name:
- Kernel base = 0xfffff800`51e02000 PsLoadedModuleList = 0xfffff800`5221dad0
- Debug session time: Wed Feb 6 23:59:34.342 2019 (UTC + 1:00)
- System Uptime: 0 days 2:54:12.016
- Loading Kernel Symbols
- ...............................................................
- ................................................................
- ................................................................
- ........
- Loading User Symbols
- Loading unloaded module list
- ...............
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- Use !analyze -v to get detailed debugging information.
- BugCheck 133, {1, 1e00, fffff80052344380, 0}
- *************************************************************************
- *** ***
- *** ***
- *** Either you specified an unqualified symbol, or your debugger ***
- *** doesn't have full symbol information. Unqualified symbol ***
- *** resolution is turned off by default. Please either specify a ***
- *** fully qualified symbol module!symbolname, or enable resolution ***
- *** of unqualified symbols by typing ".symopt- 100". Note that ***
- *** enabling unqualified symbol resolution with network symbol ***
- *** server shares in the symbol path may cause the debugger to ***
- *** appear to hang for long periods of time when an incorrect ***
- *** symbol name is typed or the network symbol server is down. ***
- *** ***
- *** For some commands to work properly, your symbol path ***
- *** must point to .pdb files that have full type information. ***
- *** ***
- *** Certain .pdb files (such as the public OS symbols) do not ***
- *** contain the required information. Contact the group that ***
- *** provided you with these symbols if you need this command to ***
- *** work. ***
- *** ***
- *** Type referenced: TickPeriods ***
- *** ***
- *************************************************************************
- Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+12edb5 )
- Followup: MachineOwner
- ---------
- 7: 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: 0000000000000001, The system cumulatively spent an extended period of time at
- DISPATCH_LEVEL or above. The offending component can usually be
- identified with a stack trace.
- Arg2: 0000000000001e00, The watchdog period.
- Arg3: fffff80052344380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
- additional information regarding the cumulative timeout
- Arg4: 0000000000000000
- Debugging Details:
- ------------------
- *************************************************************************
- *** ***
- *** ***
- *** Either you specified an unqualified symbol, or your debugger ***
- *** doesn't have full symbol information. Unqualified symbol ***
- *** resolution is turned off by default. Please either specify a ***
- *** fully qualified symbol module!symbolname, or enable resolution ***
- *** of unqualified symbols by typing ".symopt- 100". Note that ***
- *** enabling unqualified symbol resolution with network symbol ***
- *** server shares in the symbol path may cause the debugger to ***
- *** appear to hang for long periods of time when an incorrect ***
- *** symbol name is typed or the network symbol server is down. ***
- *** ***
- *** For some commands to work properly, your symbol path ***
- *** must point to .pdb files that have full type information. ***
- *** ***
- *** Certain .pdb files (such as the public OS symbols) do not ***
- *** contain the required information. Contact the group that ***
- *** provided you with these symbols if you need this command to ***
- *** work. ***
- *** ***
- *** Type referenced: TickPeriods ***
- *** ***
- *************************************************************************
- KEY_VALUES_STRING: 1
- STACKHASH_ANALYSIS: 1
- TIMELINE_ANALYSIS: 1
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
- DUMP_TYPE: 2
- BUGCHECK_P1: 1
- BUGCHECK_P2: 1e00
- BUGCHECK_P3: fffff80052344380
- BUGCHECK_P4: 0
- DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
- CPU_COUNT: 10
- CPU_MHZ: e10
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 9e
- CPU_STEPPING: c
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
- BUGCHECK_STR: 0x133
- PROCESS_NAME: Corsair.Service.CpuIdRemote64.exe
- CURRENT_IRQL: d
- ANALYSIS_SESSION_HOST: DESKTOP-EVLPTGD
- ANALYSIS_SESSION_TIME: 02-07-2019 02:53:21.0408
- ANALYSIS_VERSION: 10.0.17763.132 x86fre
- LAST_CONTROL_TRANSFER: from fffff800520581d5 to fffff80051fb5440
- STACK_TEXT:
- ffffc600`9e1f1ba8 fffff800`520581d5 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`52344380 : nt!KeBugCheckEx
- ffffc600`9e1f1bb0 fffff800`51f262e4 : 00002243`137778a0 00000000`00000000 00000000`000a3501 ffffc600`9e1d5180 : nt!KeAccumulateTicks+0x12edb5
- ffffc600`9e1f1c10 fffff800`52873332 : 00000000`00000000 fffff800`528d7bd8 ffffc202`9d447090 00000000`00000002 : nt!KeClockInterruptNotify+0x604
- ffffc600`9e1f1f30 fffff800`51e448b5 : 00000018`55f9eb41 ffff8008`714d4f00 ffff8008`714d4fb0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf2
- ffffc600`9e1f1f60 fffff800`51fb6e3a : ffffc202`9d447090 ffff8008`714d4f00 00000000`00000000 ffff8008`714d4f00 : nt!KiCallInterruptServiceRoutine+0xa5
- ffffc600`9e1f1fb0 fffff800`51fb7387 : 00000000`ddbeef1b ffffc202`9d447090 ffff8008`714d4f00 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
- ffffc202`9d447010 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
- THREAD_SHA1_HASH_MOD_FUNC: 5e958d63ed6cce864bfe4c595207e0e484aa7e7c
- THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 06e0b5c60ca94b3ca5424fcc0f6d146bb3b24353
- THREAD_SHA1_HASH_MOD: e2266a530ca7fbace00cfa9add8dc0ac4504d759
- FOLLOWUP_IP:
- nt!KeAccumulateTicks+12edb5
- fffff800`520581d5 cc int 3
- FAULT_INSTR_CODE: ab3944cc
- SYMBOL_STACK_INDEX: 1
- SYMBOL_NAME: nt!KeAccumulateTicks+12edb5
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: nt
- IMAGE_NAME: ntkrnlmp.exe
- DEBUG_FLR_IMAGE_TIMESTAMP: 0
- IMAGE_VERSION: 10.0.17763.292
- STACK_COMMAND: .thread ; .cxr ; kb
- BUCKET_ID_FUNC_OFFSET: 12edb5
- FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
- BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
- PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks
- TARGET_TIME: 2019-02-06T22:59:34.000Z
- OSBUILD: 17763
- OSSERVICEPACK: 292
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 272
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
- OS_LOCALE:
- USER_LCID: 0
- OSBUILD_TIMESTAMP: unknown_date
- BUILDDATESTAMP_STR: 180914-1434
- BUILDLAB_STR: rs5_release
- BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
- ANALYSIS_SESSION_ELAPSED_TIME: 1c49
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks
- FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
- Followup: MachineOwner
- ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement