Windows 10: Debug: Symbol for Kernel 10586.162.amd64fre.th2_release_sec.160223-172

Discus and support Debug: Symbol for Kernel 10586.162.amd64fre.th2_release_sec.160223-172 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi Im doing debugging with Windbg and urgently need the correct symbol for kernel version 10586.162.amd64fre.th2_release_sec.160223-1728? Thx for... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by sroghen, Nov 11, 2016.

  1. sroghen Win User

    Debug: Symbol for Kernel 10586.162.amd64fre.th2_release_sec.160223-172


    Hi
    Im doing debugging with Windbg and urgently need the correct symbol for kernel version 10586.162.amd64fre.th2_release_sec.160223-1728?

    Thx for your help

    :)
     
    sroghen, Nov 11, 2016
    #1

  2. BugCheck 109, {a3a01f58d87bf826, b3b72bdf2afcc883, 1a0, 7} Windows 10 Build 10586.162

    I have this problem on and off for 3 months and I normally blue screen within 90 minutes after a cold boot. It sometimes happens when I'm watching videos on youtube, or like this morning, 60 minutes after just booting up with no interaction from me.

    There was a period of about 6 weeks, where everything was fine, and then yesterday it started again.

    My solution/stab in the dark, back 6 weeks ago was to switch out the power supply. This was after testing and replacing memory (no issues with memtest86 and Microsoft's memory tester.) I also completed dozens of fresh installs of Windows 10 to try and
    figure out if it was some errant software. I ran the Application Verifier only to complain about my anti virus (KTS). Needless to say I, also blue screened with no trace of it or any other av/malware detectors I run. I also switched out my HD and the cables
    to go with it.

    Enough of my rant, here is an edited for space, Bugcheck Analysis. I have a specs (via msinfo32), minidump ,compressed 4gb dump available as well. If you are interested, email me at dxh800 (a) gmail.com and I'll send you the links.

    Thank you for your time.

    Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Kernel Bitmap Dump File: Full address space is available

    ************* Symbol Path validation summary **************

    Response Time (ms) Location

    Deferred SRV*c:\Symbols*Symbol information

    Symbol search path is: SRV*c:\Symbols*Symbol information

    Executable search path is:

    Windows 10 Kernel Version 10586 MP (4 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 10586.162.amd64fre.th2_release_sec.160223-1728

    Machine Name:

    Kernel base = 0xfffff801`d3680000 PsLoadedModuleList = 0xfffff801`d395ecd0

    Debug session time: Mon Apr 4 17:59:24.205 2016 (UTC - 5:00)

    System Uptime: 0 days 6:57:54.923

    Loading Kernel Symbols

    ...............................................................

    .

    Loading User Symbols

    Loading unloaded module list

    .........

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 109, {a3a01f58d87bf826, b3b72bdf2afcc883, 1a0, 7}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner

    ---------

    0: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    CRITICAL_STRUCTURE_CORRUPTION (109)

    Arguments:

    Arg1: a3a01f58d87bf826, Reserved

    Arg2: b3b72bdf2afcc883, Reserved

    Arg3: 00000000000001a0, Failure type dependent information

    Arg4: 0000000000000007, Type of corrupted region, can be



    Debugging Details:

    ------------------

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 402

    BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

    SYSTEM_MANUFACTURER: PERFORMANCE DESIGN

    SYSTEM_PRODUCT_NAME: BLKDQ57TM

    SYSTEM_VERSION: E70931-401

    BIOS_VENDOR: Intel Corp.

    BIOS_VERSION: TMIBX10H.86A.0050.2011.1207.1134

    BIOS_DATE: 12/07/2011

    BASEBOARD_MANUFACTURER: Intel Corporation

    BASEBOARD_PRODUCT: DQ57TM

    BASEBOARD_VERSION: AAE70931-401

    DUMP_TYPE: 0

    BUGCHECK_P1: a3a01f58d87bf826

    BUGCHECK_P2: b3b72bdf2afcc883

    BUGCHECK_P3: 1a0

    BUGCHECK_P4: 7

    PG_MISMATCH: 40000

    CPU_COUNT: 4

    CPU_MHZ: c78

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 25

    CPU_STEPPING: 2

    CPU_MICROCODE: 6,25,2,0 (F,M,S,R) SIG: E'00000000 (cache) E'00000000 (init)

    DEFAULT_BUCKET_ID: BAD_STACK_0x109

    BUGCHECK_STR: 0x109

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: HQ

    ANALYSIS_SESSION_TIME: 04-04-2016 20:41:53.0746

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre

    STACK_TEXT:

    fffff801`d5ad7368 00000000`00000000 : 00000000`00000109 a3a01f58`d87bf826 b3b72bdf`2afcc883 00000000`000001a0 : nt!KeBugCheckEx

    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

    THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION:

    BUCKET_ID: BAD_STACK_0x109

    PRIMARY_PROBLEM_CLASS: BAD_STACK

    FAILURE_BUCKET_ID: BAD_STACK_0x109

    TARGET_TIME: 2016-04-04T22:59:24.000Z

    OSBUILD: 10586

    OSSERVICEPACK: 0

    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: 2016-02-23 23:48:00

    BUILDDATESTAMP_STR: 160223-1728

    BUILDLAB_STR: th2_release_sec

    BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

    ANALYSIS_SESSION_ELAPSED_TIME: 9fe

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:bad_stack_0x109

    FAILURE_ID_HASH: {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

    Followup: MachineOwner

    ---------
     
    Annoyed Win user, Nov 11, 2016
    #2
  3. DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD [Dump file attached] on Windows 10.

    Original Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD [Dump file attached]

    Microsoft (R) Windows Debugger Version 10.0.10586.567 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\032016-4281-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 10586 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 10586.162.amd64fre.th2_release_sec.160223-1728

    Machine Name:

    Kernel base = 0xfffff803`09089000 PsLoadedModuleList = 0xfffff803`09367cd0

    Debug session time: Sun Mar 20 18:38:44.648 2016 (UTC - 7:00)

    System Uptime: 0 days 4:56:04.276

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .........................................

    Loading User Symbols

    Loading unloaded module list

    ...............................................

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {0, d, 8, 0}

    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247 )

    Followup: MachineOwner

    ---------

    4: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high. This is usually

    caused by drivers using improper addresses.

    If kernel debugger is available get stack backtrace.

    Arguments:

    Arg1: 0000000000000000, memory referenced

    Arg2: 000000000000000d, IRQL

    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation

    Arg4: 0000000000000000, address which referenced memory

    Debugging Details:

    ------------------

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

    SYSTEM_MANUFACTURER: System manufacturer

    SYSTEM_PRODUCT_NAME: System Product Name

    SYSTEM_SKU: SKU

    SYSTEM_VERSION: System Version

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 1101

    BIOS_DATE: 10/01/2015

    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT: Z170-A

    BASEBOARD_VERSION: Rev 1.xx

    DUMP_TYPE: 2

    BUGCHECK_P1: 0

    BUGCHECK_P2: d

    BUGCHECK_P3: 8

    BUGCHECK_P4: 0

    READ_ADDRESS: fffff80309407520: Unable to get MiVisibleState

    0000000000000000

    CURRENT_IRQL: d

    FAULTING_IP:

    +0

    00000000`00000000 ?? ???

    PROCESS_NAME: System

    CPU_COUNT: 8

    CPU_MHZ: fa8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 39'00000000 (cache) 39'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    ANALYSIS_SESSION_HOST: JOHN-PC

    ANALYSIS_SESSION_TIME: 03-20-2016 18:42:01.0229

    ANALYSIS_VERSION: 10.0.10586.567 x86fre

    TRAP_FRAME: ffffd000e63a3da0 -- (.trap 0xffffd000e63a3da0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=000040d3a7274993 rbx=0000000000000000 rcx=ffffd000e633f5e0

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=0000000000000000 rsp=ffffd000e63a3f38 rbp=0000000000000000

    r8=0000000000000000 r9=0000000000000000 r10=ffffd000e632f444

    r11=000000000000011b r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei ng nz na pe nc

    00000000`00000000 ?? ???

    Resetting default scope

    IP_IN_FREE_BLOCK: 0

    LAST_CONTROL_TRANSFER: from fffff803091d62e9 to fffff803091cb760

    FAILED_INSTRUCTION_ADDRESS:

    +0

    00000000`00000000 ?? ???

    STACK_TEXT:

    ffffd000`e63a3c58 fffff803`091d62e9 : 00000000`0000000a 00000000`00000000 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx

    ffffd000`e63a3c60 fffff803`091d4ac7 : 00000000`00000000 ffff9543`dcb8db1f 00000000`00000000 000040d3`a708a15e : nt!KiBugCheckDispatch+0x69

    ffffd000`e63a3da0 00000000`00000000 : fffff803`090189c5 00000000`00000000 ffffd000`e6329180 00000000`0580e760 : nt!KiPageFault+0x247

    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: bf99962f16aee8a6a536cfcc5454c0cd4db15ac9

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3fc3928ee7b2857c7b0acb22199e00ab7dceb90c

    THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:

    nt!KiPageFault+247

    fffff803`091d4ac7 33c0 xor eax,eax

    FAULT_INSTR_CODE: ffb0c033

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiPageFault+247

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 56cd4410

    IMAGE_VERSION: 10.0.10586.162

    BUCKET_ID_FUNC_OFFSET: 247

    FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault

    BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault

    PRIMARY_PROBLEM_CLASS: AV_CODE_AV_NULL_IP_nt!KiPageFault

    TARGET_TIME: 2016-03-21T01:38:44.000Z

    OSBUILD: 10586

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 784

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-02-23 21:48:00

    BUILDDATESTAMP_STR: 160223-1728

    BUILDLAB_STR: th2_release_sec

    BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

    ANALYSIS_SESSION_ELAPSED_TIME: 1359

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_code_av_null_ip_nt!kipagefault

    FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

    Followup: MachineOwner

    ---------
     
    Starshield, Nov 11, 2016
    #3
  4. Ztruker Win User

    Debug: Symbol for Kernel 10586.162.amd64fre.th2_release_sec.160223-172

    Ztruker, Nov 11, 2016
    #4
  5. sroghen Win User
    10586.162.amd64fre.th2_release_sec.160223-1728 are NOT on Microsoft public symbol server. So WinDbg cannot downlowd the symbol for this OS version automatically.
     
    sroghen, Nov 11, 2016
    #5
  6. Ztruker Win User
    Sorry, if they are not there then they are not available publicly anywhere that I know of.
     
    Ztruker, Apr 5, 2018
    #6
Thema:

Debug: Symbol for Kernel 10586.162.amd64fre.th2_release_sec.160223-172

Loading...
  1. Debug: Symbol for Kernel 10586.162.amd64fre.th2_release_sec.160223-172 - Similar Threads - Debug Symbol Kernel

  2. Critical Error: Kernel-Power ID:41 Information: Kernel-Power ID:172

    in Windows 10 Gaming
    Critical Error: Kernel-Power ID:41 Information: Kernel-Power ID:172: So my pc has been randomly shutting off whenever I play games, and I mean *any* games. I checked my temps and they're fine. I checked my power draw and it was fine. I then checked event viewer log files here:...
  3. Critical Error: Kernel-Power ID:41 Information: Kernel-Power ID:172

    in Windows 10 Software and Apps
    Critical Error: Kernel-Power ID:41 Information: Kernel-Power ID:172: So my pc has been randomly shutting off whenever I play games, and I mean *any* games. I checked my temps and they're fine. I checked my power draw and it was fine. I then checked event viewer log files here:...
  4. Microsoft Kernel Debug Network Adapter

    in Windows 10 Gaming
    Microsoft Kernel Debug Network Adapter: I noticed an adapter called Microsoft Kernel Debig Network Adapter show up on my computer so I looked it up and read a post saying to use cmd as elevated user and enter the command "bcdedit/debug off" to make sure it was off and when I did this an error message said "The...
  5. Microsoft Kernel Debug Network Adapter

    in Windows 10 Software and Apps
    Microsoft Kernel Debug Network Adapter: I noticed an adapter called Microsoft Kernel Debig Network Adapter show up on my computer so I looked it up and read a post saying to use cmd as elevated user and enter the command "bcdedit/debug off" to make sure it was off and when I did this an error message said "The...
  6. Critical: Kernel-Power; Event 41/Event 172

    in Windows 10 BSOD Crashes and Debugging
    Critical: Kernel-Power; Event 41/Event 172: This has become a problem. My computer crashes and does a restart with these errors. Event 41 - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectantly. Event 172 -...
  7. Kernel Power 41 with NIC compliance 172

    in Windows 10 BSOD Crashes and Debugging
    Kernel Power 41 with NIC compliance 172: So I was having this issue start up in the beginning of December, whenever I started playing a newer game like Call of Duty or Escape From Tarkov, my PC would appear to shut down but would not let me turn it on or off until I flipped the switch on the PSU. Tried everything...
  8. 172 CESSNA

    in Windows 10 BSOD Crashes and Debugging
    172 CESSNA: I PURCHASED THE FLT SIM 2020 MAINLY BECAUSE IT HAD THE STANDARD 172 SKYHAWK. AFTER I RECIEVED THE DOWN LOAD IT WAS THERE. THEN THEY TOOK IT AWAY. CAN'T CONTACT THEM, NOTHING LIKE FRAUD! WHAT THEY DID IS ILLEGAL. CANT GET BACK WHAT I PURCHASED OR A REFUND....
  9. Microsoft Kernel Debug Network Adapter

    in Windows 10 Installation and Upgrade
    Microsoft Kernel Debug Network Adapter: Hey, so recently deleted : Microsoft Kernel Debug Network Adapter, by accident. Only now it wont let me play online anymore on xbox. So is there any solution in how to get back the network adapter?...
  10. Do we have debug symbols yet?

    in Windows 10 BSOD Crashes and Debugging
    Do we have debug symbols yet?: As stated clearly in the title, I wanna know when we are gonna get our debug symbols? Would have been nice to have my bsods debugged BEFORE RTM, but since that is tomorrow that obviously isn't going to happen. Does anyone know when the symbols will be available? Will they be...