locked
Windows 8.1 x64 - BSOD - ntkrnlmp.exe crash RRS feed

  • Question

  • Hello guys,

    I need some help regarding a BSOD.

    Before BSOD I created the second logical network on lan adapter for an VLAN connection. First logical connection works but when configuring the second one, windows get BSOD. 

    After analysis with Debug Diagnostic Tool I get the following result:

    Type of Analysis Performed   Hang Analysis
    Machine Name   
    Operating System   Unexpected
    Number Of Processors   
    Process ID   7858576
    Process Image   ntkrnlmp.exe
    System Up-Time   00:09:20
    Process Up-Time   

    00:00:00

    Top 5 Threads by CPU time

    Note - Times include both user mode and kernel mode for each thread

    Extended thread information (including thread CPU times) is unavailable in this dump 

     Script Summary 

     ScripT Name                Status Error Code Error              Source Line

    CrashHangAnalysis.asp  Failed           0x80010105          Line 10638, Column 3

    Hardware: Fujitsu Esprimo E920 85+

    Please help. Thank you


    • Edited by Adrix8657 Wednesday, April 6, 2016 2:01 PM
    Wednesday, April 6, 2016 1:54 PM

Answers

  • Clean install may be the fastest way to resolve this if it is not hardware related and if you do not install the same software that may have caused this in the  first place.

    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Monday, April 18, 2016 11:09 AM

All replies

  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask

    • Edited by ZigZag3143x Wednesday, April 6, 2016 2:18 PM
    Wednesday, April 6, 2016 2:17 PM
  • Hi Adrix8657,

    .

    Would you mind to tell us how did you configure multiple logical networks on one same lan adapter?

    Based on your description, this issue seems occurs after you changed the networks setting,

    Maybe we could try to change it back to have a test.

    .

    Best regards.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, April 7, 2016 12:03 PM
  • Hello, below you can find the dump files. Please complete with "www"

    wetransfer.com/downloads/2086fa1d107b8a769f839553697988ee20160408112141/b4b49a228c2504ac247e2fd356358cab20160408112141/bc9d19

    Thank you.

    Friday, April 8, 2016 11:33 AM
  • These were related to iansw60e.sys (Intel Ethernet Controller I350 driver)

    Completely remove the current driver and install a fresh copy of the most recent driver

    Microsoft (R) Windows Debugger Version 10.0.14281.933 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\ZigZag3143\Desktop\040616-26015-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.18202.amd64fre.winblue_ltsb.160119-0600
    Machine Name:
    Kernel base = 0xfffff801`fe08d000 PsLoadedModuleList = 0xfffff801`fe360630
    Debug session time: Wed Apr  6 09:01:03.904 2016 (UTC - 4:00)
    System Uptime: 0 days 1:38:08.577
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C2, {7, 1200, 0, ffffe000f35f5cec}
    
    *** WARNING: Unable to verify timestamp for iansw60e.sys
    *** ERROR: Module load completed but symbols could not be loaded for iansw60e.sys
    Probably caused by : iansw60e.sys ( iansw60e+8162 )
    
    Followup:     MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, Attempt to free pool which was already freed
    Arg2: 0000000000001200, Pool tag value from the pool header
    Arg3: 0000000000000000, Contents of the first 4 bytes of the pool header
    Arg4: ffffe000f35f5cec, Address of the block of pool being deallocated
    
    Debugging Details:
    ------------------
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  9600.18202.amd64fre.winblue_ltsb.160119-0600
    
    SYSTEM_MANUFACTURER:  FUJITSU
    
    SYSTEM_PRODUCT_NAME:  ESPRIMO E920
    
    SYSTEM_SKU:  S26361-Kxxx-Vyyy
    
    SYSTEM_VERSION:                        
    
    BIOS_VENDOR:  FUJITSU // American Megatrends Inc.
    
    BIOS_VERSION:  V4.6.5.4 R1.25.0 for D3222-A1x
    
    BIOS_DATE:  06/24/2014
    
    BASEBOARD_MANUFACTURER:  FUJITSU
    
    BASEBOARD_PRODUCT:  D3222-A1
    
    BASEBOARD_VERSION:  S26361-D3222-A1            
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 7
    
    BUGCHECK_P2: 1200
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: ffffe000f35f5cec
    
    BUGCHECK_STR:  0xc2_7
    
    CPU_COUNT: 4
    
    CPU_MHZ: d40
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3c
    
    CPU_STEPPING: 3
    
    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1A'00000000 (cache) 1A'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_SESSION_HOST:  DESKTOP-T34NCI2
    
    ANALYSIS_SESSION_TIME:  04-08-2016 05:58:18.0761
    
    ANALYSIS_VERSION: 10.0.14281.933 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff801fe32bf5c to fffff801fe1db3a0
    
    STACK_TEXT:  
    ffffd000`241dee48 fffff801`fe32bf5c : 00000000`000000c2 00000000`00000007 00000000`00001200 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`241dee50 fffff800`c048fb91 : ffffe000`f536acf8 ffffe000`f536acf8 00000000`00000001 ffffd000`00000000 : nt!ExDeferredFreePool+0x6ec
    ffffd000`241def40 fffff800`c4807162 : ffffd000`241df2c0 ffffd000`241deff9 ffffe000`f57ff010 ffffe000`f3777160 : ndis!NdisFreeMemory+0x15
    ffffd000`241def70 ffffd000`241df2c0 : ffffd000`241deff9 ffffe000`f57ff010 ffffe000`f3777160 00000002`00280180 : iansw60e+0x8162
    ffffd000`241def78 ffffd000`241deff9 : ffffe000`f57ff010 ffffe000`f3777160 00000002`00280180 fffff800`00000001 : 0xffffd000`241df2c0
    ffffd000`241def80 ffffe000`f57ff010 : ffffe000`f3777160 00000002`00280180 fffff800`00000001 ffffffff`ffffffff : 0xffffd000`241deff9
    ffffd000`241def88 ffffe000`f3777160 : 00000002`00280180 fffff800`00000001 ffffffff`ffffffff ffffffff`ffffffff : 0xffffe000`f57ff010
    ffffd000`241def90 00000002`00280180 : fffff800`00000001 ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 : 0xffffe000`f3777160
    ffffd000`241def98 fffff800`00000001 : ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 fffff801`fe02369a : 0x00000002`00280180
    ffffd000`241defa0 ffffffff`ffffffff : ffffffff`ffffffff 00000000`00000000 fffff801`fe02369a 00000000`00700198 : 0xfffff800`00000001
    ffffd000`241defa8 ffffffff`ffffffff : 00000000`00000000 fffff801`fe02369a 00000000`00700198 ffffe000`f0ade1a0 : 0xffffffff`ffffffff
    ffffd000`241defb0 00000000`00000000 : fffff801`fe02369a 00000000`00700198 ffffe000`f0ade1a0 40020006`00000000 : 0xffffffff`ffffffff
    
    
    STACK_COMMAND:  kb
    
    THREAD_SHA1_HASH_MOD_FUNC:  5cc7a456fa28b3be73618ac511b70c0c5edba481
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ea5499070cf733705bbeaa5d6244be5f729f96a3
    
    THREAD_SHA1_HASH_MOD:  15d303175a5b218bb9a79cc646b4be27c89d537c
    
    FOLLOWUP_IP: 
    iansw60e+8162
    fffff800`c4807162 ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  iansw60e+8162
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: iansw60e
    
    IMAGE_NAME:  iansw60e.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  558a979d
    
    BUCKET_ID_FUNC_OFFSET:  8162
    
    FAILURE_BUCKET_ID:  0xc2_7_iansw60e!Unknown_Function
    
    BUCKET_ID:  0xc2_7_iansw60e!Unknown_Function
    
    PRIMARY_PROBLEM_CLASS:  0xc2_7_iansw60e!Unknown_Function
    
    TARGET_TIME:  2016-04-06T13:01:03.000Z
    
    OSBUILD:  9600
    
    OSSERVICEPACK:  0
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 8.1
    
    OSEDITION:  Windows 8.1 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2016-01-19 11:19:09
    
    BUILDDATESTAMP_STR:  160119-0600
    
    BUILDLAB_STR:  winblue_ltsb
    
    BUILDOSVER_STR:  6.3.9600.18202.amd64fre.winblue_ltsb.160119-0600
    
    ANALYSIS_SESSION_ELAPSED_TIME: 173d
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc2_7_iansw60e!unknown_function
    
    FAILURE_ID_HASH:  {bb877e63-4fcd-f060-07f3-7aa78c9388b7}
    
    Followup:     MachineOwner
    ---------
    
    3: kd> lmvm iansw60e
    Browse full module list
    start             end                 module name
    fffff800`c47ff000 fffff800`c482a000   iansw60e T (no symbols)           
        Loaded symbol image file: iansw60e.sys
        Image path: \SystemRoot\system32\DRIVERS\iansw60e.sys
        Image name: iansw60e.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Jun 24 07:42:21 2015 (558A979D)
        CheckSum:         0002B618
        ImageSize:        0002B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    




    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    • Proposed as answer by S.SenguptaMVP Saturday, April 9, 2016 12:38 AM
    Friday, April 8, 2016 12:36 PM
  • Thanks for advice. I tried before the all versions, from 18.4 to 20.2 available on intel site.

    With the driver that you suggest there are no changes, the same bluescreen appear when you create new vlan connection.

    Any suggestion?

    Wednesday, April 13, 2016 12:58 PM
  • Either dont do what you are doing, use different lan adapter, or as a last step do a clean install.  I would run a system file check to find the state of the OS

    Please run a system file check (SFC) & DISM  if you are on win 8 or higher

    All instructions are in our Wiki article below...Should you have any questions please ask us.



    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Wednesday, April 13, 2016 1:10 PM
  • I don't have a different adapter.

    SFC and DISM completed successfully.

    Need to reinstall the OS?

    Monday, April 18, 2016 10:43 AM
  • Clean install may be the fastest way to resolve this if it is not hardware related and if you do not install the same software that may have caused this in the  first place.

    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Monday, April 18, 2016 11:09 AM