none
What else does "netsh int ip reset" do? RRS feed

  • Question

  • According to this article when you run the "netsh int ip reset" command, all it does is to reset the content of two registry keys:

    SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ SYSTEM\CurrentControlSet\Services\DHCP\Parameters\ but on my test system it appears to do more.

    On a Windows Server 2012 R2 x64 machine, after my application does something wrong,

    if I try to set up a static IP to a network interface I get instant BSOD.

    To fix the issue I have to run "netsh int ip reset" and then I can set a static IP.
    Now, I'm trying to figure it out how does "netsh int ip reset" fix the problem.

    I know is not the content of those 2 registry keys because I did the following
    on my virtual machine:

    1. Make a VM backup when the system is troubled.
    2. Launch the VM and run the "netsh int ip reset" command
    3. Export the two registry keys
    4. Roll back to the backup made before the "netsh int ip reset" command
    5. Import the saved registries keys
    6. Set up a static IP on an network interface, but I still get a BSOD

    When my application tries to configure a network interface with an IP address that was already used by another network interface in the past, first it has to remove that IP configuration for the non-present device and then it can use that IP.

    To do that I search in every registry in SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces and see if any of the interfaces did use the IP addres I want to use by comparing the value in "IPAddress" property with the one I want to use.
     If I find a match, I first check if that interface is live, and if it's not, I delete the value in "IPAddress" property and set property "EnableDHCP" to 1, then I use that IP on my interface.
    This is what my application did wrong. When this interface comes back live again, it will get an IP configuration through DHCP, but it will BSOD if you try to set a static IP on it.
    The correct way to do it is to set "IPAddress" property to "0.0.0.0" and "EnableDHCP" to 1. If you leave "IPAddress" empty and set "EnableDHCP" to 1, something goes wrong in TCPIP configuration, that "netsh int ip reset" will fix .. but what exactly it fixes, I have no idea. All I know it's that it's not in the two registries keys that the KB article mentions.

    So what else does "netsh int ip reset" do, except resetting the content of those two registries, that fixes the problem on my test system?








    • Edited by Chris.DB Wednesday, December 11, 2013 3:58 PM
    Wednesday, December 11, 2013 3:08 PM

Answers

  • Hi,

    The analysis result is :

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000000000a8, memory referenced
    Arg2: 0000000000000006, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000298636f, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b090e8
    GetUlongFromAddress: unable to read from fffff80002b09198
     00000000000000a8 Nonpaged pool
    
    CURRENT_IRQL:  6
    
    FAULTING_IP: 
    nt!PsChargeProcessCpuCycles+10f
    fffff800`0298636f 4c296628        sub     qword ptr [rsi+28h],r12
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  fffff8800584b190 -- (.trap 0xfffff8800584b190)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000006
    rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000298636f rsp=fffff8800584b320 rbp=fffff80002a4ae80
     r8=0000000000000029  r9=0000000000000000 r10=0000000000000000
    r11=fffffa800f13518c r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na pe nc
    nt!PsChargeProcessCpuCycles+0x10f:
    fffff800`0298636f 4c296628        sub     qword ptr [rsi+28h],r12 ds:00000000`00000028=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800028d7be9 to fffff800028d8640
    
    STACK_TEXT:  
    fffff880`0584b048 fffff800`028d7be9 : 00000000`0000000a 00000000`000000a8 00000000`00000006 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0584b050 fffff800`028d6860 : fffff8a0`0391c0ac 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69
    fffff880`0584b190 fffff800`0298636f : fffff8a0`02007f20 00000000`00000000 00000000`00000000 fffff800`00000000 : nt!KiPageFault+0x260
    fffff880`0584b320 fffff800`028d403a : 00000000`00000000 fffff880`0584b3e0 fffffa80`0dd1ff00 fffff800`02a031de : nt!PsChargeProcessCpuCycles+0x10f
    fffff880`0584b360 fffff880`04b7a02e : fffff880`04b792fc 00000000`00000000 00000000`00000022 fffffa80`0e355e50 : nt!KiChainedDispatch+0x10a
    fffff880`0584b4f8 fffff880`04b792fc : 00000000`00000000 00000000`00000022 fffffa80`0e355e50 fffffa80`0f066840 : 0xfffff880`04b7a02e
    fffff880`0584b500 00000000`00000000 : 00000000`00000022 fffffa80`0e355e50 fffffa80`0f066840 fffff880`0584b540 : 0xfffff880`04b792fc
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!PsChargeProcessCpuCycles+10f
    fffff800`0298636f 4c296628        sub     qword ptr [rsi+28h],r12
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!PsChargeProcessCpuCycles+10f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    IMAGE_VERSION:  6.1.7601.17514
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!PsChargeProcessCpuCycles+10f
    
    BUCKET_ID:  X64_0xA_nt!PsChargeProcessCpuCycles+10f
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!pschargeprocesscpucycles+10f
    
    FAILURE_ID_HASH:  {8eeeeb21-a639-8c21-c8a3-9a37cf39b50b}
    
    Followup: MachineOwner
    ---------
    
    

    For the bugcheck, please refer to the article to troublshoot the issue.

    Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560129%28v=vs.85%29.aspx

    Hope this helps,


    Ada Liu
    TechNet Community Support

    Thursday, December 19, 2013 1:55 AM

All replies

  • Hi,

    It’s hard for as to analyze what cause the result you encountered.

    Please follow the steps to provide us with BSOD file for further analysis.

    Help solve Blue Screen of Death (BSOD)

    http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d

    Regards,


    Ada Liu
    TechNet Community Support

    Friday, December 13, 2013 8:03 AM
  • Hi,

    These are 3 DMP files generated after setting up an static IP address for the troubled network interface through the TCP/IPv4 user interface.

    https://skydrive.live.com/redir?resid=2CF05A900F9844D3%214794

    Thanks


    • Edited by Chris.DB Friday, December 13, 2013 11:45 AM
    Friday, December 13, 2013 11:44 AM
  • Hi,

    The analysis result is :

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000000000a8, memory referenced
    Arg2: 0000000000000006, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000298636f, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b090e8
    GetUlongFromAddress: unable to read from fffff80002b09198
     00000000000000a8 Nonpaged pool
    
    CURRENT_IRQL:  6
    
    FAULTING_IP: 
    nt!PsChargeProcessCpuCycles+10f
    fffff800`0298636f 4c296628        sub     qword ptr [rsi+28h],r12
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  fffff8800584b190 -- (.trap 0xfffff8800584b190)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000006
    rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000298636f rsp=fffff8800584b320 rbp=fffff80002a4ae80
     r8=0000000000000029  r9=0000000000000000 r10=0000000000000000
    r11=fffffa800f13518c r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na pe nc
    nt!PsChargeProcessCpuCycles+0x10f:
    fffff800`0298636f 4c296628        sub     qword ptr [rsi+28h],r12 ds:00000000`00000028=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800028d7be9 to fffff800028d8640
    
    STACK_TEXT:  
    fffff880`0584b048 fffff800`028d7be9 : 00000000`0000000a 00000000`000000a8 00000000`00000006 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0584b050 fffff800`028d6860 : fffff8a0`0391c0ac 00000000`00000000 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69
    fffff880`0584b190 fffff800`0298636f : fffff8a0`02007f20 00000000`00000000 00000000`00000000 fffff800`00000000 : nt!KiPageFault+0x260
    fffff880`0584b320 fffff800`028d403a : 00000000`00000000 fffff880`0584b3e0 fffffa80`0dd1ff00 fffff800`02a031de : nt!PsChargeProcessCpuCycles+0x10f
    fffff880`0584b360 fffff880`04b7a02e : fffff880`04b792fc 00000000`00000000 00000000`00000022 fffffa80`0e355e50 : nt!KiChainedDispatch+0x10a
    fffff880`0584b4f8 fffff880`04b792fc : 00000000`00000000 00000000`00000022 fffffa80`0e355e50 fffffa80`0f066840 : 0xfffff880`04b7a02e
    fffff880`0584b500 00000000`00000000 : 00000000`00000022 fffffa80`0e355e50 fffffa80`0f066840 fffff880`0584b540 : 0xfffff880`04b792fc
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!PsChargeProcessCpuCycles+10f
    fffff800`0298636f 4c296628        sub     qword ptr [rsi+28h],r12
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!PsChargeProcessCpuCycles+10f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    IMAGE_VERSION:  6.1.7601.17514
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!PsChargeProcessCpuCycles+10f
    
    BUCKET_ID:  X64_0xA_nt!PsChargeProcessCpuCycles+10f
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!pschargeprocesscpucycles+10f
    
    FAILURE_ID_HASH:  {8eeeeb21-a639-8c21-c8a3-9a37cf39b50b}
    
    Followup: MachineOwner
    ---------
    
    

    For the bugcheck, please refer to the article to troublshoot the issue.

    Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560129%28v=vs.85%29.aspx

    Hope this helps,


    Ada Liu
    TechNet Community Support

    Thursday, December 19, 2013 1:55 AM