none
Windows Server 2012 BSOD caused by vmswitch.sys

    일반 토론

  • Hello guys,

    Situation is the following. I have 2 Windows Server 2012 with Hyper-V installed. We have approximately 10 VMs on each server and these VMs are replicating in both directions.

    We had 2 NICs in teaming (switch independent) connected to 1 switch. Interfaces are in access mode.

    On Friday evening we added another switch, where we connected the other 2 NICs of each server, so we decrease the load from the 1st switch. We added these NICs to the team. The switches are connected by trunk port.

    Today (Monday) at around 11am (maybe higher network load), both servers got BSOD with 3 minutes difference. One at 11:02, the other at 11:05.

    On both servers the cause is listed as vmswitch.sys. I did not find any info on this happening in Google. Here is the output from WinDBG:

    Server1

    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\pavel.dokov\Desktop\темп\MEMORY92.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available

    Symbol search path is: SRV*C:\TEMP*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: Server, suite: TerminalServer DataCenter SingleUserTS
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    Machine Name:
    Kernel base = 0xfffff802`96a08000 PsLoadedModuleList = 0xfffff802`96cd4a20
    Debug session time: Mon Jul 22 11:05:42.903 2013 (UTC + 3:00)
    System Uptime: 5 days 2:15:02.785
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........
    Loading User Symbols

    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 133, {1, 1e0d, 0, 0}

    *** ERROR: Module load completed but symbols could not be loaded for bxnd60a.sys
    *** ERROR: Module load completed but symbols could not be loaded for bxvbda.sys
    Probably caused by : vmswitch.sys ( vmswitch!VmsPtNicPvtPacketRouted+ae )

    Followup: MachineOwner
    ---------

    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: 0000000000001e0d, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:
    ------------------


    DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x133

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    TAG_NOT_DEFINED_c000000f:  FFFFF8029720DFB0

    LAST_CONTROL_TRANSFER:  from fffff80296be1fa3 to fffff80296a62440

    STACK_TEXT:  
    fffff802`9720cb48 fffff802`96be1fa3 : 00000000`00000133 00000000`00000001 00000000`00001e0d 00000000`00000000 : nt!KeBugCheckEx
    fffff802`9720cb50 fffff802`96aa6774 : fffffa80`15bee070 00000000`01ae7950 fffff802`9720ccd0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x14600
    fffff802`9720cbd0 fffff802`97176eca : fffffa80`16f35d20 fffffa80`1812d000 00000008`00000001 00000000`00000197 : nt!KeUpdateTime+0x2ec
    fffff802`9720cdb0 fffff802`96a5b01e : 00000400`b1b3ba59 fffffa80`18e38a88 fffff802`971a0580 fffffa80`177c0950 : hal!HalpTimerClockInterrupt+0x86
    fffff802`9720cde0 fffff880`0501694e : fffffa80`21773c58 fffffa80`16c96280 fffff802`ffffffff 00000000`624e7356 : nt!KiInterruptDispatchLBControl+0x1ce
    fffff802`9720cf70 fffff880`05016487 : fffffa80`169edd20 fffff802`97200001 fffffa80`169edd20 fffffa80`181ff740 : vmswitch!VmsPtNicPvtPacketRouted+0xae
    fffff802`9720cfe0 fffff880`050153e7 : ffffffff`00000000 00000000`00000000 fffffa80`16d083f0 fffff802`9720d020 : vmswitch!VmsExtIoPacketRouted+0x197
    fffff802`9720d070 fffff880`050190f4 : fffffa80`1812d000 00000000`00000000 fffffa80`13103001 fffffa80`16bfe8a0 : vmswitch!VmsRouterDeliverNetBufferLists+0x2b7
    fffff802`9720d160 fffff880`05013a69 : fffffa80`00000000 fffffa80`13103000 00000000`00000000 0000ffff`ffffffff : vmswitch!VmsExtMppIndicatePackets+0x34
    fffff802`9720d1a0 fffff880`05013652 : fffffa80`13103000 fffffa80`13103000 00000000`00000001 a8c06200`00000001 : vmswitch!VmsExtMpRoutePackets+0x339
    fffff802`9720d300 fffff880`05012fef : fffff802`9720d340 fffffa80`16d00001 00000000`00000000 00000000`00000000 : vmswitch!VmsExtPtRouteNetBufferLists+0x272
    fffff802`9720d3d0 fffff880`014dcb06 : 0001ff00`00000000 00000000`00000000 00000000`00000001 00000000`000001ff : vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
    fffff802`9720d490 fffff880`014dc605 : fffffa80`181fd002 fffffa80`169edd20 fffffa80`130972c0 00000000`000001ff : NDIS!ndisMIndicateNetBufferListsToOpen+0x126
    fffff802`9720d540 fffff880`014dc843 : 00000000`00000000 00000000`00000001 00000000`000001ff 00000000`00000000 : NDIS!ndisInvokeNextReceiveHandler+0x6f5
    fffff802`9720d610 fffff880`05366695 : 00000000`00000000 00000000`00000000 fffffa80`177e9000 fffffa80`169edd20 : NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
    fffff802`9720d6c0 fffff880`05366161 : fffffa80`1786e880 fffffa80`177e9000 00000000`00000001 fffff802`000001ff : NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
    fffff802`9720d730 fffff880`014dcb06 : 00000001`ff01ffff 00000000`00000000 fffffa80`169edd20 ffff3e07`000001ff : NdisImPlatform!implatReceiveNetBufferLists+0x1a9
    fffff802`9720d7b0 fffff880`014dc5c9 : fffffa80`12a9d002 fffff880`00000000 fffffa80`13097008 fffff880`000001ff : NDIS!ndisMIndicateNetBufferListsToOpen+0x126
    fffff802`9720d860 fffff880`014dc843 : fffffa80`16d083f0 00000000`00001001 00000000`000001ff 00000000`00000008 : NDIS!ndisInvokeNextReceiveHandler+0x6b9
    fffff802`9720d930 fffff880`051974c3 : 00000000`00000030 fffffa80`16d083f0 00000000`000001ff fffffa80`16d08550 : NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
    fffff802`9720d9e0 fffff880`05197a3b : fffff802`9720db30 fffffa80`15bf4070 00000003`00001001 fffffa80`127d3160 : bxnd60a+0x154c3
    fffff802`9720da60 fffff880`00a9319a : fffffa80`12a9d010 00000000`00000000 00000000`00000000 00000000`000001ff : bxnd60a+0x15a3b
    fffff802`9720db00 fffff880`00a9573c : fffff802`9720dc58 00000000`00000000 fffffa80`12a9d010 00000000`00000001 : bxvbda+0xb19a
    fffff802`9720db90 fffff880`00a9829e : fffffa80`12a9d010 fffff802`9720dc70 fffffa80`12a9d680 fffff880`010cfbf1 : bxvbda+0xd73c
    fffff802`9720dc10 fffff880`00a9974f : fffffa80`12a9d010 00000000`00000000 00000000`00010000 00000000`00000000 : bxvbda+0x1029e
    fffff802`9720dca0 fffff880`00a98a79 : fffffa80`12a9d010 00000400`b1b158fa 00000000`00000000 00000000`00000000 : bxvbda+0x1174f
    fffff802`9720dcd0 fffff802`96a8aca1 : fffff802`96d02f00 fffff802`9720de00 fffffa80`12ab6d90 fffff880`01e12da8 : bxvbda+0x10a79
    fffff802`9720dd00 fffff802`96a8a8e0 : fffff802`96d00180 00000400`20fd9641 fffffa80`185e1080 00000000`00000025 : nt!KiExecuteAllDpcs+0x191
    fffff802`9720de40 fffff802`96a5c3a5 : 00000000`00000000 fffff802`96d00180 fffff880`016bfb00 fffff880`035abb40 : nt!KiRetireDpcList+0xd0
    fffff802`9720dfb0 fffff802`96a5c1a9 : 0000057f`ed2551c8 fffff802`96b4bf81 00000000`00000010 00000000`00000282 : nt!KxRetireDpcList+0x5
    fffff880`016bfa40 fffff802`96b4bf95 : fffff802`971926a0 fffff802`96a5ad13 fffffa80`1c6be8c0 fffffa80`1d749c01 : nt!KiDispatchInterruptContinue
    fffff880`016bfa70 fffff802`96a5ad13 : fffffa80`1c6be8c0 fffffa80`1d749c01 00000000`00000000 00001f80`00400010 : nt!KiDpcInterruptBypass+0x25
    fffff880`016bfa80 fffff880`0501005d : 00000000`00000001 fffffa80`1aa70690 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x273
    fffff880`016bfc10 fffff880`00bdc916 : fffffa80`19f1a9c0 00000000`00000001 fffffa80`1c6be910 fffffa80`19f1a600 : vmswitch!VmsVmNicPvtKmclPacketSent+0x4d
    fffff880`016bfc40 fffff880`00bdb873 : fffffa80`1aa5c0d0 fffff802`96a37b00 fffffa80`19f1a601 fffff880`016bfd20 : vmbkmcl!InpProcessQueue+0x236
    fffff880`016bfcd0 fffff880`0107807f : fffffa80`19f1a600 fffffa80`1342d800 fffffa80`1cf8ca10 fffffa80`1cf8ca10 : vmbkmcl!InpProcessingWorkerRoutine+0x1b3
    fffff880`016bfd20 fffff802`96a34fd9 : fffffa80`133d2780 00000000`00000080 fffff880`01084110 fffff802`96d5a880 : vmbusr!WPP_SF_+0xffffffff`ffffffef
    fffff880`016bfd50 fffff802`96ae97e6 : fffff802`96d00180 fffffa80`133d2780 fffff802`96d5a880 fffffa80`12833980 : nt!PspSystemThreadStartup+0x59
    fffff880`016bfda0 00000000`00000000 : fffff880`016c0000 fffff880`016ba000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    vmswitch!VmsPtNicPvtPacketRouted+ae
    fffff880`0501694e 49897108        mov     qword ptr [r9+8],rsi

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  vmswitch!VmsPtNicPvtPacketRouted+ae

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: vmswitch

    IMAGE_NAME:  vmswitch.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  510cbec2

    BUCKET_ID_FUNC_OFFSET:  ae

    FAILURE_BUCKET_ID:  0x133_ISR_vmswitch!VmsPtNicPvtPacketRouted

    BUCKET_ID:  0x133_ISR_vmswitch!VmsPtNicPvtPacketRouted

    Followup: MachineOwner
    ---------

    0: kd> lmvm vmswitch
    start             end                 module name
    fffff880`0500f000 fffff880`050a0000   vmswitch   (private pdb symbols)  c:\temp\vmswitch.pdb\C3BB001449F5486880C49B8C87592D831\vmswitch.pdb
        Loaded symbol image file: vmswitch.sys
        Image path: \SystemRoot\system32\DRIVERS\vmswitch.sys
        Image name: vmswitch.sys
        Timestamp:        Sat Feb 02 09:22:42 2013 (510CBEC2)
        CheckSum:         0008C7E0
        ImageSize:        00091000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> .bugcheck
    Bugcheck code 00000133
    Arguments 00000000`00000001 00000000`00001e0d 00000000`00000000 00000000`00000000
    0: kd> l
           ^ Syntax error in 'l'
    0: kd> k
    Child-SP          RetAddr           Call Site
    fffff802`9720cb48 fffff802`96be1fa3 nt!KeBugCheckEx
    fffff802`9720cb50 fffff802`96aa6774 nt! ?? ::FNODOBFM::`string'+0x14600
    fffff802`9720cbd0 fffff802`97176eca nt!KeUpdateTime+0x2ec
    fffff802`9720cdb0 fffff802`96a5b01e hal!HalpTimerClockInterrupt+0x86
    fffff802`9720cde0 fffff880`0501694e nt!KiInterruptDispatchLBControl+0x1ce
    fffff802`9720cf70 fffff880`05016487 vmswitch!VmsPtNicPvtPacketRouted+0xae
    fffff802`9720cfe0 fffff880`050153e7 vmswitch!VmsExtIoPacketRouted+0x197
    fffff802`9720d070 fffff880`050190f4 vmswitch!VmsRouterDeliverNetBufferLists+0x2b7
    fffff802`9720d160 fffff880`05013a69 vmswitch!VmsExtMppIndicatePackets+0x34
    fffff802`9720d1a0 fffff880`05013652 vmswitch!VmsExtMpRoutePackets+0x339
    fffff802`9720d300 fffff880`05012fef vmswitch!VmsExtPtRouteNetBufferLists+0x272
    fffff802`9720d3d0 fffff880`014dcb06 vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
    fffff802`9720d490 fffff880`014dc605 NDIS!ndisMIndicateNetBufferListsToOpen+0x126
    fffff802`9720d540 fffff880`014dc843 NDIS!ndisInvokeNextReceiveHandler+0x6f5
    fffff802`9720d610 fffff880`05366695 NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
    fffff802`9720d6c0 fffff880`05366161 NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
    fffff802`9720d730 fffff880`014dcb06 NdisImPlatform!implatReceiveNetBufferLists+0x1a9
    fffff802`9720d7b0 fffff880`014dc5c9 NDIS!ndisMIndicateNetBufferListsToOpen+0x126
    fffff802`9720d860 fffff880`014dc843 NDIS!ndisInvokeNextReceiveHandler+0x6b9
    fffff802`9720d930 fffff880`051974c3 NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
    fffff802`9720d9e0 fffff880`05197a3b bxnd60a+0x154c3
    fffff802`9720da60 fffff880`00a9319a bxnd60a+0x15a3b
    fffff802`9720db00 fffff880`00a9573c bxvbda+0xb19a
    fffff802`9720db90 fffff880`00a9829e bxvbda+0xd73c
    fffff802`9720dc10 fffff880`00a9974f bxvbda+0x1029e
    fffff802`9720dca0 fffff880`00a98a79 bxvbda+0x1174f
    fffff802`9720dcd0 fffff802`96a8aca1 bxvbda+0x10a79
    fffff802`9720dd00 fffff802`96a8a8e0 nt!KiExecuteAllDpcs+0x191
    fffff802`9720de40 fffff802`96a5c3a5 nt!KiRetireDpcList+0xd0
    fffff802`9720dfb0 fffff802`96a5c1a9 nt!KxRetireDpcList+0x5
    fffff880`016bfa40 fffff802`96b4bf95 nt!KiDispatchInterruptContinue
    fffff880`016bfa70 fffff802`96a5ad13 nt!KiDpcInterruptBypass+0x25
    fffff880`016bfa80 fffff880`0501005d nt!KiInterruptDispatch+0x273
    fffff880`016bfc10 fffff880`00bdc916 vmswitch!VmsVmNicPvtKmclPacketSent+0x4d
    fffff880`016bfc40 fffff880`00bdb873 vmbkmcl!InpProcessQueue+0x236
    fffff880`016bfcd0 fffff880`0107807f vmbkmcl!InpProcessingWorkerRoutine+0x1b3
    fffff880`016bfd20 fffff802`96a34fd9 vmbusr!WPP_SF_+0xffffffff`ffffffef
    fffff880`016bfd50 fffff802`96ae97e6 nt!PspSystemThreadStartup+0x59
    fffff880`016bfda0 00000000`00000000 nt!KiStartSystemThread+0x16
    0: kd> analyze -show code
    Couldn't resolve error at 'nalyze -show code'
    0: kd> !analyze -show code
    Unknown bugcheck code (0)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000000
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    0: kd> ub fffff802`9720cdb0 fffff802`96a5b01e
                                                ^ Range error in 'ub fffff802`9720cdb0 fffff802`96a5b01e'
    0: kd> ub fffff802`96a5b01e
    nt!KiInterruptDispatchLBControl+0x1a9:
    fffff802`96a5aff9 740e            je      nt!KiInterruptDispatchLBControl+0x1b9 (fffff802`96a5b009)
    fffff802`96a5affb 65488b0c2520000000 mov   rcx,qword ptr gs:[20h]
    fffff802`96a5b004 e8e771ffff      call    nt!KiEntropyQueueDpc (fffff802`96a521f0)
    fffff802`96a5b009 488d4580        lea     rax,[rbp-80h]
    fffff802`96a5b00d 48898688000000  mov     qword ptr [rsi+88h],rax
    fffff802`96a5b014 488bce          mov     rcx,rsi
    fffff802`96a5b017 488b5630        mov     rdx,qword ptr [rsi+30h]
    fffff802`96a5b01b ff5618          call    qword ptr [rsi+18h]

    Server 2:


    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\pavel.dokov\Desktop\темп\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available

    Symbol search path is: SRV*C:\TEMP*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: Server, suite: TerminalServer DataCenter SingleUserTS
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    Machine Name:
    Kernel base = 0xfffff802`57c0e000 PsLoadedModuleList = 0xfffff802`57ed7a80
    Debug session time: Mon Jul 22 11:04:12.825 2013 (UTC + 3:00)
    System Uptime: 80 days 12:16:22.194
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols

    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 133, {1, 784, 0, 0}

    *** ERROR: Module load completed but symbols could not be loaded for bxnd60a.sys
    *** ERROR: Module load completed but symbols could not be loaded for bxvbda.sys
    Page d8bdc0 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : vmswitch.sys ( vmswitch!RndisDevHostDeviceIndicatePackets+1e1 )

    Followup: MachineOwner
    ---------

    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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:
    ------------------

    Page d8bdc0 not present in the dump file. Type ".hh dbgerr004" for details

    DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x133

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    TAG_NOT_DEFINED_c000000f:  FFFFF8025923EFB0

    LAST_CONTROL_TRANSFER:  from fffff80257de1747 to fffff80257c88040

    STACK_TEXT:  
    fffff802`592378f8 fffff802`57de1747 : 00000000`00000133 00000000`00000001 00000000`00000784 00000000`00000000 : nt!KeBugCheckEx
    fffff802`59237900 fffff802`57cb3f06 : fffffa80`2b791a00 00000000`1a93fd50 fffff802`59237a80 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13cdc
    fffff802`59237980 fffff802`58378eca : fffffa80`39486c60 00000000`00000000 fffff880`01d2b830 00000000`00000000 : nt!KeUpdateTime+0x41b
    fffff802`59237b70 fffff802`57c814de : 00003f44`1fafdc02 00000000`00000002 fffff802`583a2580 fffff880`01d2bb1e : hal!HalpTimerClockInterrupt+0x86
    fffff802`59237ba0 fffff802`57cb428e : fffffa80`2f0aa8a0 00000000`00000000 fffffa80`3ba9dc60 00000000`80000011 : nt!KiInterruptDispatchLBControl+0x1ce
    fffff802`59237d30 fffff880`04e82a31 : fffff802`59237e60 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KeReleaseSpinLock+0x1e
    fffff802`59237d60 fffff880`04e82810 : fffffa80`39486c60 00000000`00000030 fffffa80`ffffffff fffff802`59237f01 : vmswitch!RndisDevHostDeviceIndicatePackets+0x1e1
    fffff802`59237eb0 fffff880`04e82615 : ffffffff`ffffffff fffff802`59230000 fffff802`59237f60 fffff802`00000000 : vmswitch!VmsVmNicPvtPacketForward+0xb0
    fffff802`59237ee0 fffff880`04e860f4 : fffffa80`2b7b4000 00000000`00000000 fffffa80`2b55c001 fffffa80`2f1d64c0 : vmswitch!VmsRouterDeliverNetBufferLists+0x4e5
    fffff802`59237fd0 fffff880`04e80a69 : fffffa80`00000000 fffffa80`2b55c000 00000000`00000000 0000ffff`ffffffff : vmswitch!VmsExtMppIndicatePackets+0x34
    fffff802`59238010 fffff880`04e80652 : fffffa80`2b55c000 fffffa80`2b55c000 00000000`00000001 00000000`00000001 : vmswitch!VmsExtMpRoutePackets+0x339
    fffff802`59238170 fffff880`04e7ffef : fffff802`592381b0 fffffa80`2f170001 00000000`00000000 00000000`00000000 : vmswitch!VmsExtPtRouteNetBufferLists+0x272
    fffff802`59238240 fffff880`01494e4e : 00000000`00000000 00000000`00000000 fffffa80`00000001 fffffa80`0000025f : vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
    fffff802`59238300 fffff880`01494815 : fffffa80`307e2002 fffffa80`2f4c8b00 fffffa80`00000000 fffff880`0000025f : NDIS!ndisMIndicateNetBufferListsToOpen+0x373
    fffff802`592383a0 fffff880`01494a25 : fffffa80`2b62a1a0 00000000`00000000 00000000`00000001 00000000`00000000 : NDIS!ndisInvokeNextReceiveHandler+0x6f5
    fffff802`59238470 fffff880`0520f695 : 00000000`00000000 fffffa80`2fdf2000 fffffa80`2f4c8bb0 fffffa80`2fdd6e80 : NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
    fffff802`592384f0 fffff880`0520f161 : fffffa80`2fdd6ee0 fffffa80`2fdf2000 00000000`00000001 00000000`0000025f : NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
    fffff802`59238560 fffff880`01494e4e : 00000000`0001ff00 00000000`00000000 00000000`00001001 00000000`0000025f : NdisImPlatform!implatReceiveNetBufferLists+0x1a9
    fffff802`592385e0 fffff880`014947d9 : fffff802`59238902 fffffa80`2afe3900 0000926d`00000000 00000000`0000025f : NDIS!ndisMIndicateNetBufferListsToOpen+0x373
    fffff802`59238680 fffff880`01494a25 : fffffa80`2b5481a0 00000000`00000000 00000000`00001001 00000000`00000000 : NDIS!ndisInvokeNextReceiveHandler+0x6b9
    fffff802`59238750 fffff880`04e154c3 : fffffa80`2f17b320 00000000`0000025f fffffa80`2f17b480 fffff802`59238920 : NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
    fffff802`592387d0 fffff880`04e15a3b : fffff802`59238920 fffffa80`2dfbc070 00000003`00001001 fffffa80`2dbe8160 : bxnd60a+0x154c3
    fffff802`59238850 fffff880`00e0b19a : fffffa80`2ad06010 00000000`00000000 00000000`00000000 00000000`0000025f : bxnd60a+0x15a3b
    fffff802`592388f0 fffff880`00e0d73c : fffff802`59238a48 00000000`00000000 fffffa80`2ad06010 00000000`00000001 : bxvbda+0xb19a
    fffff802`59238980 fffff880`00e1029e : fffffa80`2ad06010 fffff802`59238a60 fffffa80`2ad06680 fffff880`010adbf1 : bxvbda+0xd73c
    fffff802`59238a00 fffff880`00e1174f : fffffa80`2ad06010 00000000`00000000 00000000`00010000 00000000`00000000 : bxvbda+0x1029e
    fffff802`59238a90 fffff880`00e10a79 : fffffa80`2ad06010 00003f44`1fad7a9e 00000000`00000000 00000000`00000000 : bxvbda+0x1174f
    fffff802`59238ac0 fffff802`57c7df38 : fffff802`57f05f00 fffff802`59238bf0 fffffa80`2ad1fd90 fffff802`59238ca0 : bxvbda+0x10a79
    fffff802`59238af0 fffff802`57caeeb0 : fffffa80`00000000 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiExecuteAllDpcs+0x198
    fffff802`59238c30 fffff802`57cb36ca : fffff802`57f03180 fffff802`57f03180 00000000`00183de0 fffff802`57f5d880 : nt!KiRetireDpcList+0xd0
    fffff802`59238da0 00000000`00000000 : fffff802`59239000 fffff802`59233000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    vmswitch!RndisDevHostDeviceIndicatePackets+1e1
    fffff880`04e82a31 48837dc000      cmp     qword ptr [rbp-40h],0

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  vmswitch!RndisDevHostDeviceIndicatePackets+1e1

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: vmswitch

    IMAGE_NAME:  vmswitch.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  510cbec2

    BUCKET_ID_FUNC_OFFSET:  1e1

    FAILURE_BUCKET_ID:  0x133_ISR_vmswitch!RndisDevHostDeviceIndicatePackets

    BUCKET_ID:  0x133_ISR_vmswitch!RndisDevHostDeviceIndicatePackets

    Followup: MachineOwner
    ---------

    0: kd> lmvm vmswitch
    start             end                 module name
    fffff880`04e7c000 fffff880`04f0d000   vmswitch   (private pdb symbols)  c:\temp\vmswitch.pdb\C3BB001449F5486880C49B8C87592D831\vmswitch.pdb
        Loaded symbol image file: vmswitch.sys
        Image path: \SystemRoot\system32\DRIVERS\vmswitch.sys
        Image name: vmswitch.sys
        Timestamp:        Sat Feb 02 09:22:42 2013 (510CBEC2)
        CheckSum:         0008C7E0
        ImageSize:        00091000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> .bugcheck
    Bugcheck code 00000133
    Arguments 00000000`00000001 00000000`00000784 00000000`00000000 00000000`00000000
    0: kd> k
    Child-SP          RetAddr           Call Site
    fffff802`592378f8 fffff802`57de1747 nt!KeBugCheckEx
    fffff802`59237900 fffff802`57cb3f06 nt! ?? ::FNODOBFM::`string'+0x13cdc
    fffff802`59237980 fffff802`58378eca nt!KeUpdateTime+0x41b
    fffff802`59237b70 fffff802`57c814de hal!HalpTimerClockInterrupt+0x86
    fffff802`59237ba0 fffff802`57cb428e nt!KiInterruptDispatchLBControl+0x1ce
    fffff802`59237d30 fffff880`04e82a31 nt!KeReleaseSpinLock+0x1e
    fffff802`59237d60 fffff880`04e82810 vmswitch!RndisDevHostDeviceIndicatePackets+0x1e1
    fffff802`59237eb0 fffff880`04e82615 vmswitch!VmsVmNicPvtPacketForward+0xb0
    fffff802`59237ee0 fffff880`04e860f4 vmswitch!VmsRouterDeliverNetBufferLists+0x4e5
    fffff802`59237fd0 fffff880`04e80a69 vmswitch!VmsExtMppIndicatePackets+0x34
    fffff802`59238010 fffff880`04e80652 vmswitch!VmsExtMpRoutePackets+0x339
    fffff802`59238170 fffff880`04e7ffef vmswitch!VmsExtPtRouteNetBufferLists+0x272
    fffff802`59238240 fffff880`01494e4e vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
    fffff802`59238300 fffff880`01494815 NDIS!ndisMIndicateNetBufferListsToOpen+0x373
    fffff802`592383a0 fffff880`01494a25 NDIS!ndisInvokeNextReceiveHandler+0x6f5
    fffff802`59238470 fffff880`0520f695 NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
    fffff802`592384f0 fffff880`0520f161 NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
    fffff802`59238560 fffff880`01494e4e NdisImPlatform!implatReceiveNetBufferLists+0x1a9
    fffff802`592385e0 fffff880`014947d9 NDIS!ndisMIndicateNetBufferListsToOpen+0x373
    fffff802`59238680 fffff880`01494a25 NDIS!ndisInvokeNextReceiveHandler+0x6b9
    fffff802`59238750 fffff880`04e154c3 NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
    fffff802`592387d0 fffff880`04e15a3b bxnd60a+0x154c3
    fffff802`59238850 fffff880`00e0b19a bxnd60a+0x15a3b
    fffff802`592388f0 fffff880`00e0d73c bxvbda+0xb19a
    fffff802`59238980 fffff880`00e1029e bxvbda+0xd73c
    fffff802`59238a00 fffff880`00e1174f bxvbda+0x1029e
    fffff802`59238a90 fffff880`00e10a79 bxvbda+0x1174f
    fffff802`59238ac0 fffff802`57c7df38 bxvbda+0x10a79
    fffff802`59238af0 fffff802`57caeeb0 nt!KiExecuteAllDpcs+0x198
    fffff802`59238c30 fffff802`57cb36ca nt!KiRetireDpcList+0xd0
    fffff802`59238da0 00000000`00000000 nt!KiIdleLoop+0x5a
    0: kd> ub fffff802`57c814de
    nt!KiInterruptDispatchLBControl+0x1a9:
    fffff802`57c814b9 740e            je      nt!KiInterruptDispatchLBControl+0x1b9 (fffff802`57c814c9)
    fffff802`57c814bb 65488b0c2520000000 mov   rcx,qword ptr gs:[20h]
    fffff802`57c814c4 e8a3a9ffff      call    nt!KiEntropyQueueDpc (fffff802`57c7be6c)
    fffff802`57c814c9 488d4580        lea     rax,[rbp-80h]
    fffff802`57c814cd 48898688000000  mov     qword ptr [rsi+88h],rax
    fffff802`57c814d4 488bce          mov     rcx,rsi
    fffff802`57c814d7 488b5630        mov     rdx,qword ptr [rsi+30h]
    fffff802`57c814db ff5618          call    qword ptr [rsi+18h]
    0: kd> u fffff802`57c814de
    nt!KiInterruptDispatchLBControl+0x1ce:
    fffff802`57c814de fa              cli
    fffff802`57c814df 488b0df27e2d00  mov     rcx,qword ptr [nt!_imp_HalPerformEndOfInterrupt (fffff802`57f593d8)]
    fffff802`57c814e6 ff11            call    qword ptr [rcx]
    fffff802`57c814e8 65488b0c2520000000 mov   rcx,qword ptr gs:[20h]
    fffff802`57c814f1 80792001        cmp     byte ptr [rcx+20h],1
    fffff802`57c814f5 7772            ja      nt!KiInterruptDispatchLBControl+0x259 (fffff802`57c81569)
    fffff802`57c814f7 0f31            rdtsc
    fffff802`57c814f9 48c1e220        shl     rdx,20h

    Please help!

    P.S. We can remove switch 2, but on Switch 1 we do not have enough interfaces to plug in the other 2 NICs of each server.

    Regards

    2013년 7월 22일 월요일 오전 10:12

모든 응답

  • Just to add - we have 3 more servers in similar configuration (we also used the new switch to plug their NIC) and they are running fine for now.
    2013년 7월 22일 월요일 오전 10:22
  • Hi,

    Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

    Regards,


    Arthur Li

    TechNet Community Support

    2013년 7월 23일 화요일 오전 7:55
  • Re-install update rollup 2855336 from Windows Update, if it is installed.
    2013년 7월 23일 화요일 오후 12:13
  • Be interested to know the nics you have.

    we are experiencing the same issue with a hp dl 160 with a the HP NC362i nics.

    Denis - that update seems just to fix live migration BSOD's we are experiencing the issue without performing those (server has little load). But I will certainly try the update.

    Cheers

    Dave


    David Hood www.consilium-uk.com

    2013년 7월 24일 수요일 오후 10:22
  • Hello Denis,

    On one of the server we have the update installed, but we do not have it on the other one (servers are in different patch groups), so I do not think this update is the issue - since on both server the problem occurred at nearly the same time, regardless of the patch being installed or not. Not to mention, patch is for live migration, not for replication - and at this point of time, we did NOT perform failover between primary and replica server.

    Nonetheless, we shall re-install the patch. We shall schedule a change and perform it in the next week or two.

    David,

    Our NICs are: HP NC382i DP Multifunction Gigabit Server Adapter.

    What we noticed is that since we added the new switch, we had hosts' MAC addresses flapping between interfaces of servers and of the trunk. This was due to the algorithm we were using - Switch Independent Address Hash. Since the hosts generate the most traffic due to the replication, the traffic from the hosts was coming out from different interfaces each time. So, in outbound traffic we had loss of packets and timeouts. Unfortunately, since the switches we use are not high-end Cisco products and we cannot stack them, there is no other solution how to fix this on 2 trunked switches. As solution, we changed the teaming to Switch Independent Hyper-V port. No MAC address flapping anymore. We are waiting to see if the issue will reoccur.

    In address hash algorithm we have additional layer of complexity in the outbound traffic - calculation on which interface the packet should go out from. While in Hyper-V port there is static mapping for the VMs and the host. May be (here I am speculating) this additional complexity, combined with the MAC address flapping, cause the issue with the vmswitch driver.

    David, what teaming mode are you using?

    Regards,

    Pavel


    • 편집됨 doKich 2013년 7월 25일 목요일 오전 8:17 missed not
    2013년 7월 25일 목요일 오전 8:11
  • Hi Pavel,

    I have been working on this issue with my colleague David Hood.

    The teaming mode is switch independent with load balancing set as Hyper-v port. Previously this was set to address hash but same issue persists.

    Below is an extract from the memory.dmp 

    *******************************************************************************
    *                                                                             *
    *                        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: 000000000000000a, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88001606fa4, address which referenced memory

    Debugging Details:
    ------------------

    *** ERROR: Module load completed but symbols could not be loaded for e1q63x64.sys

    READ_ADDRESS:  000000000000000a 

    CURRENT_IRQL:  2

    FAULTING_IP: 
    vmswitch!RndisDevHostDeviceIndicatePackets+754
    fffff880`01606fa4 41f6460a05      test    byte ptr [r14+0Ah],5

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  AV

    PROCESS_NAME:  System

    TAG_NOT_DEFINED_c000000f:  FFFFF8026A40DFB0

    TRAP_FRAME:  fffff8026a406bf0 -- (.trap 0xfffff8026a406bf0)
    .trap 0xfffff8026a406bf0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880052fa040 rbx=0000000000000000 rcx=fffff880052fa104
    rdx=00000200156611d8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001606fa4 rsp=fffff8026a406d80 rbp=fffff8026a406e80
     r8=0000000000000000  r9=0000000000000000 r10=00000000000000d2
    r11=fffff880052fa040 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac pe nc
    vmswitch!RndisDevHostDeviceIndicatePackets+0x754:
    fffff880`01606fa4 41f6460a05      test    byte ptr [r14+0Ah],5 ds:00000000`0000000a=??
    .trap
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80269c6a769 to fffff80269c6b440

    STACK_TEXT:  
    fffff802`6a406aa8 fffff802`69c6a769 : 00000000`0000000a 00000000`0000000a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff802`6a406ab0 fffff802`69c68fe0 : 00000000`00000000 00000000`000000c4 fffffa80`1a498800 fffff802`6a406bf0 : nt!KiBugCheckDispatch+0x69
    fffff802`6a406bf0 fffff880`01606fa4 : 00000000`00000000 fffffa80`1a8621a0 00000000`00000002 fffffa80`00000000 : nt!KiPageFault+0x260
    fffff802`6a406d80 fffff880`01606810 : fffffa80`3a7adc60 00000000`00000000 00000000`ffffffff fffffa80`1a8e0001 : vmswitch!RndisDevHostDeviceIndicatePackets+0x754
    fffff802`6a406ed0 fffff880`01606615 : ffffffff`ffffffff fffffa80`1b594788 fffffa80`196c77a0 00000000`00000001 : vmswitch!VmsVmNicPvtPacketForward+0xb0
    fffff802`6a406f00 fffff880`0160a0f4 : fffffa80`18f38000 00000000`00000000 fffffa80`1a665001 00000000`00000001 : vmswitch!VmsRouterDeliverNetBufferLists+0x4e5
    fffff802`6a406ff0 fffff880`01604a69 : fffffa80`18f38000 fffff802`6a4070d0 00000000`00000000 0000db4b`2c741f10 : vmswitch!VmsExtMppIndicatePackets+0x34
    fffff802`6a407030 fffff880`01604652 : fffffa80`1a665000 fffffa80`1a665000 00000000`00000001 fffffa80`00000005 : vmswitch!VmsExtMpRoutePackets+0x339
    fffff802`6a407190 fffff880`01603fef : fffff802`6a4071d0 fffffa80`196a0001 00000000`00000000 00000000`00000000 : vmswitch!VmsExtPtRouteNetBufferLists+0x272
    fffff802`6a407260 fffff880`0148ae4e : 00000000`00000800 00000000`00000000 fffffa80`00000001 fffffa80`00000002 : vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
    fffff802`6a407320 fffff880`0148a815 : fffffa80`1a54d802 fffffa80`1b31e000 00000000`00000000 fffffa80`00000002 : NDIS!ndisMIndicateNetBufferListsToOpen+0x373
    fffff802`6a4073c0 fffff880`0148aa25 : fffffa80`1aa651a0 00000000`00000000 00000000`00000801 00000000`00000000 : NDIS!ndisInvokeNextReceiveHandler+0x6f5
    fffff802`6a407490 fffff880`049e3695 : 00000000`00000000 fffffa80`3704f000 fffffa80`196c77a0 fffffa80`1a501870 : NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
    fffff802`6a407510 fffff880`049e3161 : fffffa80`1a5018d0 fffffa80`3704f000 00000000`00000801 fffff802`00000002 : NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
    fffff802`6a407580 fffff880`0148ae4e : fffffa80`1a01ffa0 00000000`00000000 00000000`00000801 00000000`00000002 : NdisImPlatform!implatReceiveNetBufferLists+0x1a9
    fffff802`6a407600 fffff880`0148a7d9 : 00000000`00000002 00000000`00000000 fffffa80`00000000 fffffa80`00000002 : NDIS!ndisMIndicateNetBufferListsToOpen+0x373
    fffff802`6a4076a0 fffff880`0148aa25 : fffffa80`1a5831a0 00000000`00000000 00000000`00000801 00000000`00000001 : NDIS!ndisInvokeNextReceiveHandler+0x6b9
    fffff802`6a407770 fffff880`04846264 : fffffa80`1a8bb000 fffffa80`1a5831a0 fffffa80`196c77a0 00000000`00000801 : NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
    fffff802`6a4077f0 fffff880`04846b3d : 00000000`00000001 fffffa80`196c77a0 fffffa80`1a8bb000 00000000`00000002 : e1q63x64+0x25264
    fffff802`6a407830 fffff880`048391b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : e1q63x64+0x25b3d
    fffff802`6a4078b0 fffff880`048395de : fffffa80`19789d00 fffffa80`1a8bb000 ffff0001`00000000 ffff0001`00000000 : e1q63x64+0x181b0
    fffff802`6a407920 fffff880`04838bd8 : fffff802`6a407a20 ffff0001`00000000 fffff880`04838b50 fffffa80`19a06000 : e1q63x64+0x185de
    fffff802`6a407980 fffff880`01489e4e : 00000000`00000002 fffff802`6a379e3b ffffd426`55f5cee8 ffffddbe`8c5f7673 : e1q63x64+0x17bd8
    fffff802`6a4079c0 fffff880`01489f5e : fffffa80`19a064e8 00000000`ffffffff fffffa80`19a06000 00000020`5d9e582d : NDIS!ndisMiniportDpc+0xfe
    fffff802`6a407a60 fffff802`69c93ca1 : fffff802`69f0bf00 00000000`00000031 00000000`00000000 00000000`00000000 : NDIS!ndisInterruptDpc+0x9e
    fffff802`6a407af0 fffff802`69c938e0 : 00000020`5d9e5745 fffffa80`1986f550 00000020`5d9e5745 fffff802`6a407c8c : nt!KiExecuteAllDpcs+0x191
    fffff802`6a407c30 fffff802`69c949ba : fffff802`69f09180 fffff802`69f09180 00000000`00183de0 fffff802`69f63880 : nt!KiRetireDpcList+0xd0
    fffff802`6a407da0 00000000`00000000 : fffff802`6a408000 fffff802`6a402000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    vmswitch!RndisDevHostDeviceIndicatePackets+754
    fffff880`01606fa4 41f6460a05      test    byte ptr [r14+0Ah],5

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  vmswitch!RndisDevHostDeviceIndicatePackets+754

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: vmswitch

    IMAGE_NAME:  vmswitch.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  510cbec2

    BUCKET_ID_FUNC_OFFSET:  754

    FAILURE_BUCKET_ID:  AV_vmswitch!RndisDevHostDeviceIndicatePackets

    BUCKET_ID:  AV_vmswitch!RndisDevHostDeviceIndicatePackets

    Followup: MachineOwner

    Thanks,

    Dave M

    2013년 7월 25일 목요일 오전 9:51
  • How often does the issue happen?
    2013년 7월 25일 목요일 오전 11:16
  • There is no set frequency to how often the BSOD occurs on the hyper-v host, sometimes the host is online for a few days and on a occasion its been online for a few hrs before failure.

    At the moment there is currently only test vm's running on guests on this host, and there isn't too much load placed on the server.

    Thanks,

    Dave M

     
    2013년 7월 25일 목요일 오후 2:38
  • Hello Dave, David,

    For me it happened only once (for now). I hope it will not occur again. That is why I have not done some more advanced troubleshooting and monitoring on the systems. Nonetheless, it seems that is an issue.

    Since I am in a partner organization, I am eligible to request assistance from MS. I would try to do that and provide them with the memory dumps. Hopefully, they will provide patch or some other form of fix. Will keep you updated on the development.

    Regards,

    Pavel

    2013년 7월 28일 일요일 오전 9:23
  • Hello Dave, David,

    I have been on the phone/email with MS. They checked my server and analysed the memory dump. Result is the following action plan:

          1. Apply the latest fix for vmswitch as per  http://support.microsoft.com/?id=2840681  
    2.   2. Update the bxnd60a.sys (HP) and bxvdba.sys (Broadcom) to the latest (probably your drivers are different).

    Since for me the problem happened only once, may you please also follow the steps in the action plan and update me on the result?

    Thanks,

    Pavel

    2013년 8월 2일 금요일 오후 4:34
  • Hello Friends,

    If we have Windows 2012 Hyper-v server OR server 2012 Hyper-v Cluster and receiving following bugchcek on nodes : DRIVER_IRQL_NOT _LESS_OR_EQUAL (vmswtich.sys) randomly , then try this.

    You may have configured "VM switch" on NIC teaming using Windows server 2012 inbuilt application or 3rd party application. Nic teaming is supported in Hyper-v.

    "But, TCP Chimney Offload is not supported with Server 2012 software-based NIC teaming."

    Therefore, you can try disabling TCP chimney offload in Windows and also disable TCP chimney from each NIC properties>Advance settings. {eg; IPV4 offload, TCP checksum offload etc..}

    If we still face same issue then it could be issue with physical NICs{hardware} , therefore try removing NIC teaming and use Hyper-v VM swtich with single NIC to isolate issue.

    Windows Server 2012 Hyper-V Best Practices : http://blogs.technet.com/b/askpfeplat/archive/2013/03/10/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form.aspx

    Hope this would help you,

    Yuvi,

    2013년 8월 13일 화요일 오전 12:20