Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\111217-15693-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols\*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600 Machine Name: Kernel base = 0xfffff800`0e808000 PsLoadedModuleList = 0xfffff800`0ea4a750 Debug session time: Sun Nov 12 00:09:20.410 2017 (UTC + 1:00) System Uptime: 0 days 0:31:01.253 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039d89c08b4e8, b3b7465eee8690aa, fffff88001893000, 1} Probably caused by : ndis.sys ( ndis!__PchSym_+f0 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d89c08b4e8, Reserved Arg2: b3b7465eee8690aa, Reserved Arg3: fffff88001893000, Failure type dependent information Arg4: 0000000000000001, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000e878e00 SYMBOL_ON_RAW_STACK: 1 STACK_ADDR_RAW_STACK_SYMBOL: fffff880033bd4c0 STACK_COMMAND: dds FFFFF880033BD4C0-0x20 ; kb STACK_TEXT: fffff880`033bd4a0 00000109 fffff880`033bd4a4 00000000 fffff880`033bd4a8 9c08b4e8 fffff880`033bd4ac a3a039d8 fffff880`033bd4b0 ee8690aa fffff880`033bd4b4 b3b7465e fffff880`033bd4b8 01893000 fffff880`033bd4bc fffff880 fffff880`033bd4c0 00000001 fffff880`033bd4c4 00000000 fffff880`033bd4c8 00000000 fffff880`033bd4cc 00000000 fffff880`033bd4d0 00000000 fffff880`033bd4d4 00000000 fffff880`033bd4d8 00000000 fffff880`033bd4dc 00000000 fffff880`033bd4e0 00000000 fffff880`033bd4e4 00000000 fffff880`033bd4e8 00000000 fffff880`033bd4ec 00000000 fffff880`033bd4f0 00000000 fffff880`033bd4f4 00000000 fffff880`033bd4f8 00000000 fffff880`033bd4fc 00000000 fffff880`033bd500 00000000 fffff880`033bd504 00000000 fffff880`033bd508 00000000 fffff880`033bd50c 00000000 fffff880`033bd510 00000000 fffff880`033bd514 00000000 fffff880`033bd518 00000000 fffff880`033bd51c 00000000 FOLLOWUP_IP: ndis!__PchSym_+f0 fffff880`01893000 0010 add byte ptr [rax],dl SYMBOL_NAME: ndis!__PchSym_+f0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndis IMAGE_NAME: ndis.sys DEBUG_FLR_IMAGE_TIMESTAMP: 561c7ad7 FAILURE_BUCKET_ID: X64_0x109_VRF_ndis!__PchSym_+f0 BUCKET_ID: X64_0x109_VRF_ndis!__PchSym_+f0 Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d89c08b4e8, Reserved Arg2: b3b7465eee8690aa, Reserved Arg3: fffff88001893000, Failure type dependent information Arg4: 0000000000000001, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000e878e00 SYMBOL_ON_RAW_STACK: 1 STACK_ADDR_RAW_STACK_SYMBOL: fffff880033bd4c0 STACK_COMMAND: dds FFFFF880033BD4C0-0x20 ; kb STACK_TEXT: fffff880`033bd4a0 00000109 fffff880`033bd4a4 00000000 fffff880`033bd4a8 9c08b4e8 fffff880`033bd4ac a3a039d8 fffff880`033bd4b0 ee8690aa fffff880`033bd4b4 b3b7465e fffff880`033bd4b8 01893000 fffff880`033bd4bc fffff880 fffff880`033bd4c0 00000001 fffff880`033bd4c4 00000000 fffff880`033bd4c8 00000000 fffff880`033bd4cc 00000000 fffff880`033bd4d0 00000000 fffff880`033bd4d4 00000000 fffff880`033bd4d8 00000000 fffff880`033bd4dc 00000000 fffff880`033bd4e0 00000000 fffff880`033bd4e4 00000000 fffff880`033bd4e8 00000000 fffff880`033bd4ec 00000000 fffff880`033bd4f0 00000000 fffff880`033bd4f4 00000000 fffff880`033bd4f8 00000000 fffff880`033bd4fc 00000000 fffff880`033bd500 00000000 fffff880`033bd504 00000000 fffff880`033bd508 00000000 fffff880`033bd50c 00000000 fffff880`033bd510 00000000 fffff880`033bd514 00000000 fffff880`033bd518 00000000 fffff880`033bd51c 00000000 FOLLOWUP_IP: ndis!__PchSym_+f0 fffff880`01893000 0010 add byte ptr [rax],dl SYMBOL_NAME: ndis!__PchSym_+f0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndis IMAGE_NAME: ndis.sys DEBUG_FLR_IMAGE_TIMESTAMP: 561c7ad7 FAILURE_BUCKET_ID: X64_0x109_VRF_ndis!__PchSym_+f0 BUCKET_ID: X64_0x109_VRF_ndis!__PchSym_+f0 Followup: MachineOwner ---------