"Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\030519-8218-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol Path validation summary * Response Time (ms) Location Deferred SRV
C:\SymCacheSymbol information Symbol search path is: SRV
C:\SymCacheSymbol information Executable search path is: Windows 8 Kernel Version 17763 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 17763.1.amd64fre.rs5_release.180914-1434 Machine Name: Kernel base = 0xfffff804
57a9a000 PsLoadedModuleList = 0xfffff80457eb5ad0 Debug session time: Tue Mar 5 21:23:30.760 2019 (UTC + 1:00) System Uptime: 0 days 1:03:38.579 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................................... Loading User Symbols Loading unloaded module list ...................
* * * Bugcheck Analysis * * * Use !analyze -v to get detailed debugging information. BugCheck 133, {1, 1e00, fffff80457fdc380, 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 * WARNING: Unable to verify timestamp for win32k.sys ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 0: 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: fffff80457fdc380 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 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x133 PROCESS_NAME: System CURRENT_IRQL: d ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff80457cf01d5 to fffff80457c4d440 STACK_TEXT: fffff804
5aff9ba8 fffff80457cf01d5 : 00000000
00000133 0000000000000001 00000000
00001e00 fffff80457fdc380 : nt!KeBugCheckEx fffff804
5aff9bb0 fffff80457bbe2e4 : 000006ec
87553208 0000000000000000 00000000
0003baa5 fffff80455a3d180 : nt!KeAccumulateTicks+0x12edb5 fffff804
5aff9c10 fffff80457a03332 : 00000000
00000000 fffff80457a67bf0 ffffa784
f1d12560 0000000000000002 : nt!KeClockInterruptNotify+0x604 fffff804
5aff9f30 fffff80457adc8b5 : 00000008
e423fe6a fffff80457a6a7e0 fffff804
57a6a890 0000000000000000 : hal!HalpTimerClockInterrupt+0xf2 fffff804
5aff9f60 fffff80457c4ee3a : ffffa784
f1d12560 fffff80457a6a7e0 ffffc104
74edf010 fffff80457a6a7e0 : nt!KiCallInterruptServiceRoutine+0xa5 fffff804
5aff9fb0 fffff80457c4f387 : 00000000
b9798ca0 ffffa784f1d12560 fffff804
57a6a7e0 8b4cd28b4c0449b7 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffa784
f1d124e0 0000000000000000 : 00000000
00000000 0000000000000000 00000000
00000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff80457b1d256-fffff80457b1d257 2 bytes - nt!MiTradeActivePage+52 [ 80 fa:00 ac ] 2 errors : !nt (fffff80457b1d256-fffff80457b1d257) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: LARGE FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE BUCKET_ID: MEMORY_CORRUPTION_LARGE ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:memory_corruption_large FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c} Followup: memory_corruption --------- 0: kd> !wmitrace.strdump ----- ETW minidump data unavailable----- (WmiTracing)StrDump Generic"
