none
"Memory Management" Blue Screen Of Death On Host RRS feed

  • Question

  •  

    I have a problem where about every 2 days or so, my host operating system blue screens with a "Memory Management" error. I have run the memory diagnostics on the system and manully set the timings on my RAM, everything checks out OK. All RAM sticks are matched with the same model and speeds. The host is Windows Server 2008 Standard RTM x64.
    Tuesday, February 26, 2008 4:40 AM

Answers

All replies

  • Is this when the system is running Hyper-V, or any other server role?

    Tuesday, February 26, 2008 4:53 PM
  • It's currently running the Hyper-V role and Files Services role.

    Tuesday, February 26, 2008 6:36 PM
  • Can you try uninstalling Hyper-V and seeing if the problem persists?

     

    Cheers,

    Ben

    Tuesday, February 26, 2008 10:42 PM
  • I uninstalled Hyper-V on Tuesday night and I haven't seen the blue screen since.

    Monday, March 3, 2008 3:04 AM
  • Can you see if you can get a memory dump and report a bug?

     

    Cheers,

    Ben

    Monday, March 3, 2008 10:15 PM
  • Can you tell me where I can report the bug? And how big a memory dump do you need?

    Tuesday, March 4, 2008 2:15 AM
  • I ran the debugger tool on the last dmp file on the system. Let me know if you need more info, I can send it in a bug report, if you let me know how. Thanks.


    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\username\Desktop\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
    Kernel base = 0xfffff800`0180e000 PsLoadedModuleList = 0xfffff800`019d3db0
    Debug session time: Tue Feb 26 15:55:08.307 2008 (GMT-6)
    System Uptime: 0 days 18:00:39.735
    Loading Kernel Symbols
    .....................................................................................................................................
    Loading User Symbols

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffffa600261118f, 0, ffffffffffffffff}

     

     

    Probably caused by : vmswitch.sys ( vmswitch!VmsPtNicSendNetBufferListsCompletePrivate+83 )

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

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffffa600261118f, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

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

     

     


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    vmswitch!VmsPtNicSendNetBufferListsCompletePrivate+83
    fffffa60`0261118f 488b4010        mov     rax,qword ptr [rax+10h]

    EXCEPTION_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  ffffffffffffffff

    READ_ADDRESS:  ffffffffffffffff

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x1E

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff8000183ce67 to fffff80001863390

    STACK_TEXT: 
    fffff800`02a70728 fffff800`0183ce67 : 00000000`0000001e ffffffff`c0000005 fffffa60`0261118f 00000000`00000000 : nt!KeBugCheckEx
    fffff800`02a70730 fffff800`018631e9 : fffff800`02a70e68 fffffa80`03fdbda0 fffff800`02a70f10 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x29317
    fffff800`02a70d30 fffff800`01861dcd : 00000000`00000046 fffff800`01d2b399 0002d288`0002d288 00000000`00000003 : nt!KiExceptionDispatch+0xa9
    fffff800`02a70f10 fffffa60`0261118f : fffffa80`03b1a120 fffffa80`03c5f050 fffffa60`051c782c fffff800`01d2a5df : nt!KiGeneralProtectionFault+0xcd
    fffff800`02a710a0 fffffa60`009aa0b2 : e16d6553`02060026 fffffa60`00809589 fffffa80`03c5f1a0 fffffa80`03c5f1a0 : vmswitch!VmsPtNicSendNetBufferListsCompletePrivate+0x83
    fffff800`02a71120 fffffa60`009aa1ac : fffffa80`03c5f1a0 00000000`00000000 fffffa80`03c5f1a0 fffffa80`0593a690 : NDIS!ndisMSendCompleteNetBufferListsInternal+0xa2
    fffff800`02a71190 fffffa60`020939d7 : 00000000`00000000 fffffa80`03f65010 00000000`00000000 00000000`00000003 : NDIS!NdisMSendNetBufferListsComplete+0x7c
    fffff800`02a711d0 fffffa60`0208f618 : 00000000`00000000 fffffa80`05200000 fffffa80`05116000 fffffa60`00000014 : Rtlh64!MiniportSendNetBufferList+0x247
    fffff800`02a71250 fffffa60`0208f425 : fffffa80`03fe8000 00000000`00000002 fffffa80`05116030 fffff800`0194110e : Rtlh64!MPSendNetBufferListsNPQ+0x1e8
    fffff800`02a712c0 fffffa60`009ac31a : fffff800`019a1160 fffff800`01943781 fffffa80`056b7d40 fffff800`019a1160 : Rtlh64!MPSendNetBufferLists+0x25
    fffff800`02a712f0 fffffa60`009aa27a : 00000000`00000000 fffffa80`03c5f1a0 fffffa80`0593a690 00000000`00000000 : NDIS!ndisMSendNBLToMiniport+0x9a
    fffff800`02a71340 fffffa60`02617f09 : fffffa80`03fdbda0 00000000`00000000 fffff800`02a71408 00000000`000000f3 : NDIS!NdisSendNetBufferLists+0x9a
    fffff800`02a71390 fffffa60`026187b9 : 00000000`00000000 fffffa80`03fdbda0 fffffa80`03fdbda0 fffffa80`0593a840 : vmswitch!VmsRouterPvtDoSoftwareOffload+0x151
    fffff800`02a713c0 fffffa60`026110dc : 00000000`00000000 fffffa80`03fdbda0 fffffa80`0593a690 fffffa80`00000000 : vmswitch!VmsBalSendNbls+0x195
    fffff800`02a71460 fffffa60`026172c9 : fffffa80`03fe8000 fffffa80`03fe8000 fffff800`00000000 fffffa80`05a903b0 : vmswitch!VmsPtNicPvtPacketForward+0x22c
    fffff800`02a714e0 fffffa60`02616dec : fffffa80`05a903b0 fffffa80`0512d000 00000000`00000000 00000000`00000000 : vmswitch!VmsRouterPvtRoutePackets+0x3e5
    fffff800`02a716e0 fffffa60`02613e4b : 00000000`00000000 fffffa80`0512d000 fffff800`02a71970 fffffa80`05a90570 : vmswitch!VmsRouterRoutePackets+0x210
    fffff800`02a71900 fffffa60`0261aca0 : 00000000`00000000 00000000`00000000 fffffa80`05a903b0 00000000`00000000 : vmswitch!VmsVmNicPvtRndisDeviceSendPackets+0x15f
    fffff800`02a71970 fffffa60`0261342f : 00000000`00000000 fffffa60`00000000 00000000`00000000 00000000`00000000 : vmswitch!RndisDevHostHandlePacketMessages+0x1c4
    fffff800`02a719f0 fffffa60`02612bd7 : fffffa80`043e37b8 fffffa80`043e3798 00000000`00000000 00000000`00000000 : vmswitch!VmsVmNicPvtVersion1HandleRndisSendMessage+0x30f
    fffff800`02a71aa0 fffffa60`0261e996 : fffffa80`043e3770 fffffa80`05134030 fffffa80`05134678 00000000`00000001 : vmswitch!VmsVmNicPvtKmclParseOtherPacketBatch+0x15b
    fffff800`02a71ad0 fffffa60`0261d743 : fffffa80`05134030 fffffa80`05134678 fffffa80`05134030 fffffa80`043e0048 : vmswitch!IncomingParsePackets+0x2aa
    fffff800`02a71b20 fffffa60`0261daae : 00000000`00000000 fffffa80`0562ae80 00000000`00000001 fffffa80`05134030 : vmswitch!IncomingStateMachine+0x227
    fffff800`02a71b80 fffffa60`0262395d : fffffa80`0562ae80 00000000`00000001 fffffa80`05134030 00006e14`595bd3a1 : vmswitch!IncomingPollForWork+0xce
    fffff800`02a71bb0 fffffa60`025ae2f6 : fffffa80`0562ae80 00000000`00000000 00000000`00000040 00000000`00000000 : vmswitch!ServerIsr+0xfd
    fffff800`02a71be0 fffffa60`025ae551 : 00000000`00000001 00000000`00000000 fffffa80`03c77050 fffffa60`020095ee : vmbus!ChRegisterIsr+0x19a
    fffff800`02a71c10 fffffa60`025b3580 : fffffa80`03cb1210 fffffa60`04e50800 00000000`00000001 fffffa60`00000000 : vmbus!ChReceiveChannelInterrupt+0x129
    fffff800`02a71ca0 fffff800`0186c9d7 : 00000000`00000000 fffffa80`03cb1000 fffff800`01985a80 fffff800`01985a80 : vmbus!ParentInterruptDpc+0xb8
    fffff800`02a71d10 fffff800`0186db72 : fffffa60`025b34c8 fffff800`01982680 00000000`00000000 fffff800`01987b80 : nt!KiRetireDpcList+0x117
    fffff800`02a71d80 fffff800`01a3b5c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
    fffff800`02a71db0 00000000`fffff800 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
    fffff800`02a6b0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00680000`00000000 : 0xfffff800
    fffff800`02a6b0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00680000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b0c0 00000000`00000000 : 00000000`00000000 00680000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b0c8 00000000`00000000 : 00680000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b0d0 00680000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b0d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x680000`00000000
    fffff800`02a6b0e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b0f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b100 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b110 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b118 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b128 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b130 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b148 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b150 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b160 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b168 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b178 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b180 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b188 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b190 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b198 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b200 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffff800`02a6b208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    vmswitch!VmsPtNicSendNetBufferListsCompletePrivate+83
    fffffa60`0261118f 488b4010        mov     rax,qword ptr [rax+10h]

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  vmswitch!VmsPtNicSendNetBufferListsCompletePrivate+83

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: vmswitch

    IMAGE_NAME:  vmswitch.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  473fab32

    FAILURE_BUCKET_ID:  X64_0x1E_vmswitch!VmsPtNicSendNetBufferListsCompletePrivate+83

    BUCKET_ID:  X64_0x1E_vmswitch!VmsPtNicSendNetBufferListsCompletePrivate+83

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

     

    Tuesday, March 4, 2008 3:44 AM
  •  

    What network card do you have in your machine?
    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:40 AM
    Tuesday, March 4, 2008 6:45 PM
  • Windows reports it as a Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet NIC (NDIS 6.0) and D-Link DFE-530TX PCI Fast Ethernet Adapter (rev.A).

     

    The Realtek is integrated on my Gigabyte P35-DSR3. http://www.giga-byte.com/Products/Motherboard/Products_Overview.aspx?ProductID=2543

    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:40 AM
    Tuesday, March 4, 2008 10:30 PM
  • We have encountered this internally as well it appers to be a problem with the Realtek driver.  I would recommend using a different adapter for Hyper-V.

    • Proposed as answer by Code Chief Wednesday, September 26, 2012 10:49 AM
    Wednesday, March 5, 2008 4:27 PM
  • Thank god, at least I know what the problem is. I've tried downloading and installing the driver from the Gigabyte site for the LAN card. There was one released on Feb. 15th for x64 Vista. If that fixes my problem, I'll let you know, and if it doesn't, I'll find a different card.

     

    Thanks for all the help guys.

    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:40 AM
    Wednesday, March 5, 2008 4:50 PM
  • FYI I have the same exact motherboard (with an Intel E8400) and was trying to do the same thing by using Enterprise 2008 Core to run VMs.

    Luckily I was able to debug the MEMORY.DMP and track the problem back to the VMSWITCH.SYS driver as well which lead me here. /phew

     

    I will try the new network driver as well (they posted one on 3/7/08).

     

     

     

    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:39 AM
    Saturday, March 8, 2008 7:44 PM
  • I have been able to install 3 different VMs using the native DVD drive now w/o having the server blue screen. All I did was update the network card driver. So it looks like the update resolved it.

     

    MSFT would probably be better off to get that NIC driver update from Realtek (and other Realtek NIC drivers) up on their MSFT Update website. It would probably prevent others from running into the same thing.

    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:39 AM
    Saturday, March 8, 2008 10:57 PM
  •  

    Just had a similar issue - BlueScreen reporting an error with vmswitch.sys. 2008 x64 RTM. I'm using a Gigabyte board with dual Realtek 8111's, Once for the host OS, and the second dedicated to the VMs with only the virtual switch protocol enabled. Its been running for about a month without any issues with Hyper-V installed and running serveral VMs 24/7. The driver I had was dated Jan 25, v6.202.125.2008. After reading this thread I updated the driver to one dated Jan 24, v6.203.214.2008 and we'll see how it goes.
    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:39 AM
    Thursday, March 13, 2008 5:09 PM
  • I have the same issue as well. It was much worse with RC1 but now with the RTM image the server still Blue Screens every two days more or less.

    Downloading the driver now and looking forward to having a more stable server.

    As a curiosity, if you look at the Idle processor time to determine when was the last time your server restarted, watch out if you have a multi-core CPU since the iddle time runs faster than a regular clock.
    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:39 AM
    Sunday, March 16, 2008 5:50 PM
  • I have 2 Realtek 8169 pci cards and one Marvell on the Asus P5Q PRO board. I had experienced 2 BSOD, one yesterday and one the day before, when making system updates on VM Vista.
    Since the dumpfile pointed the same problem as yours, I decided first to update the drivers on my Windows 2008. The Marvell driver, ACPI and other I cant remember, were not correctly configured. I had done that with the original Asus CD and on my system properties, all drivers are with no errors.
    I'm making updates now again on my VM Vista and so far, so good. I suspect that for some reason the Hyper-V didnt liked the 'missing' drives, even if they had nothing to do with Vista. It looks stupid, but that's my point for now.
    So, it may not be only because the Realtek cards... you shound verify your 2008 system device drivers and see if there are any new updates or if all are correctly installed.

    Adelino Araujo
    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:39 AM
    Thursday, July 9, 2009 8:42 AM
  •     Hi guys. I also have this problem with the blue screen from time to time.


        BAD_POOL_HEADER    0x00000019    0x00000003    0xa63a10e8    0xa63a10e8    0xa63a10e9    ntkrnlpa.exe    ntkrnlpa.exe+120996    NT Kernel & System    Microsoft® Windows® Operating System   


       MEMORY_MANAGEMENT    0x0000001a    0x00041790    0xc0802068    0x0000ffff    0x00000000    ntkrnlpa.exe    ntkrnlpa.exe+b9b1d    NT Kernel & System    Microsoft® Windows® Operating System   
       
       MEMORY_MANAGEMENT    0x0000001a    0x00041287    0x00000000    0x00000000    0x00000000    halmacpi.dll    halmacpi.dll+5ba9    Hardware Abstraction Layer DLL    Microsoft® Windows® Operating System



    Is this the damaged ram or just a driver? Can somebody help ? Thanks.
    • Proposed as answer by TM-naiman Saturday, April 24, 2010 12:39 AM
    Saturday, February 27, 2010 12:26 AM
  • @nicu81 -  same here. I started to use utorrent as my bittorent client so I am personally wondering if that is doing it. I have also installled 2 new optional updates from the windows updates that seems to only effect IE... so there's another possibility for myself... and i'm actively lurking the internet for more information as well.
    Saturday, July 2, 2011 5:36 PM
  • Same problem with ASUS P9X79 motherboard with built-in RealTek PCIe GBE adapter on Windows Server 2012 RTM (with a GUI) Hyper-V.

    Have proposed the other comment above as the answer, because uninstalling Hyper-V (the current answer) is not a solution. We need to use Hyper-V.

    Have changed settings on the cards (also have an Intel port with better spec on the same motherboard - it's the Deluxe version from ASUS), disabled power management on the host and increased buffer sizes and queues on the Intel to max. the Realtek looks like a much more basic card with fixed low buffer sizes compared to the Intel.

    If it continues to give me trouble I will disable the Realtek and buy a proper PCIe server card which has specific hypervisor virtualization extension support.

    FYI: This also fixed my corruption issue checking in large ZIP files to TFS 2012, which happened shortly before the blue screen. So far with different settings it seems stable for a few hours. I think the lesson is to avoid built-in cheapo NICs, or at least Realtek hardware till they stabilize this issue (I will totally avoid them from now).

    http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/3000b6f7-f029-46e6-98c8-f0f7a21e5fec


    Key Artefacts


    • Edited by Code Chief Wednesday, September 26, 2012 12:19 PM Additional info
    Wednesday, September 26, 2012 10:55 AM
  • A new Realtek Win8 driver 8.3 is available below, the build date of the rt630x64.sys driver is 30th July 2012 (UTC). There is an older "Windows 8 WHQL" driver dated 16th June 2012 knocking around, but beware that version still blue screens with the MEMORY_MANAGEMENT issue.

    http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false#1

    One important point is that only the driver has been updated in this "auto install" package, not the installer itself! So when you install on top of an older driver installed via the "auto install" package it will not recognize this as an upgrade, displaying the Change/Repair/Uninstall dialog instead. Just choose "repair" then to upgrade.

    If you are successful the "Realtek PCIe GBE Family Controller" driver in Device Manager should have version 8.3.730.2012.

    Now as for the answer, is this stable? That is another question. Actually the old driver has been okay for a day already with power management settings disabled on the host. I'll post back here if the problem persists...


    Key Artefacts

    Thursday, September 27, 2012 10:34 AM
  • Googling my motherboard and Rt630x64.sys from the BSOD I just had got me here. Although I'm a Windows 8 user (just installed a few days ago) I was getting BSOD because of realtek network driver ever since I got my machine. I hope the driver above for windows 8 will fix that issue. 

    I do however got a little question. I've updated the network driver (did repair like @Code Chief suggested) and i can see that it's now 8.3.730.2012. My question is, I did this update from a remote computer. Wasn't I suppose to lose connection doing so? The connection stayed stable the all time .


    Wednesday, November 7, 2012 8:51 AM
  • Random BSOD on Lenovo G50-45 Laptop.

    MEMORY_MANAGEMENT (0x0000001A)

    Lenovo G50-45
    AMD A8 Processor
    16GB DDR3 RAM
    128GB SSD
    AMD Video Card
    100 Mbps Ethernet Card
    Windows Server 2008 R2
    DNS Server
    IIS Server
    Exchange Server 2010
    Norton Anti Virus
    Norton Smart Firewall

    Memtest86 checks clean
    sfc /scannow checks clean
    chkdsk /r /f checks clean
    Wednesday, February 1, 2017 12:33 PM
  • You responded to a post that was marked as answered almost 9 years ago. 

    Suggest that you open a new post.  Also remember that you are running Windows Server on an unsupported platform.  The best you can do is make sure you have the most recent firmware/BIOS/driver/chipset updates for your system.

    And you posted to the Hyper-V forum, yet you do not mention anything about Hyper-V in your post.  In your future post, you may want to include more information about how your issue is related to Hyper-V.


    . : | : . : | : . tim


    Wednesday, February 1, 2017 12:54 PM