none
Hyper-V clusters and bluescreens RRS feed

  • Question

  • Hi!

    The last few months, we have had four Blue Screens on our three node Windows Server 2008 R2 SP1 Hyper-V Cluster:

    Two of them have been caused by driver: netft.sys, and two of them have been caused by driver hvboot.sys.

    Is any of this known issues? I have been looking for post-SP1 updates for Hyper-V on Windows Server 2008 R2 SP1, but have not managed to find any.

    Monday, July 4, 2011 6:08 AM

Answers

  • Please let us know if the above mentioned fixes resolved the problem.  If they did not help in resolving the thread please re-open it.
    --------------------------------------------------------------------------------
    Regards, Michael V [MSFT] - This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, January 19, 2012 6:42 PM
    Moderator
  • Although this is an older post i would like to let you know that i was experiencing the symptoms described above and in KB2550569. This was on a new Hyper-V cluster using Dell R620 servers. In my case it was a Linux VM based on Debian 5. But Migrate to a physical computer with a different processor version  was enabled and sure enough the node crashed the moment this VM was started.

    After installing KB2550569 on all nodes it was possible to start the Linux VM without crashes.

    Friday, June 15, 2012 12:37 AM

All replies

  • Have you installed KB2494016  and KB2494162 on your Hyper-V?
    Wednesday, July 6, 2011 11:07 AM
  • Thank you, I have not installed them, but the issue does not appear when running backups, neither is the guests bluescreening, it's the cluster nodes.

    The hotfixes also updates Csvfilter.sys and Clussvc.exe, not netft.sys or hvboot.sys.

    However, I found an update to hvboot.sys: http://support.microsoft.com/kb/2263829. I will try this hotfix at the next service window.

    Anyone else been having issues with netft.sys?

    Friday, July 8, 2011 6:54 AM
  • Do you have any memory.dmp or minidump.dmp information for us? This usually has a lot of usefull information like the stop code of the BSOD.
    Just a guy who thanks Bill for paying his bills! :-)
    Tuesday, July 12, 2011 6:14 PM
  • Hi, sorry for not adding this. I have minidump.dmp files:

     

    STOP: 0x00020001 (0x0000000000000011, 0xfffff80006266a66, 0x0000000000001004,
    0xfffff885002adc10)
    
    *** hvboot.sys - Address 0xfffff88002f6682e base at 0xfffff88002f64000 DateStamp
    0x4ce792cc

     

    And

     

    *** STOP: 0x0000009e (0xfffffa80195725c0, 0x00000000000004b0, 0x0000000000000000,
    0x0000000000000000)
    
    *** netft.sys - Address 0xfffff88004a586a5 base at 0xfffff88004a56000 DateStamp
    0x4a5bc48a


     


    Wednesday, July 13, 2011 9:12 AM
  • Hi,

    For

    STOP: 0x00020001 > you might want to check if EXECITE DISABLE BIT is enabled in your BIOS. Mayby it is alos wise to check if your BIOS version is up-to-date. Sometimes this fixes some of those hard to understand errors.

    From http://www.microsoft.com/hyper-v-server/en/us/system-requirements.aspx see Hardware Data Execution Prevention (DEP), specifically Intel XD bit (execute disable bit) or AMD NX bit (no execute bit), must be available and enabled. 

    and

    STOP: 0x0000009e  see http://support.microsoft.com/kb/2135160/en-us

     


    Just a guy who thanks Bill for paying his bills! :-)
    Wednesday, July 13, 2011 11:12 AM
  • Thank you for your answer, but NX bit support is turned on in Bios on all hosts in the cluster. However, I found the following KB, dated July 4: "0x20001" Stop error when you start a Linux VM in Windows Server 2008 R2 SP1 that applies to my scenario as well: "This issue is not specific to Linux VMs and may occur on Windows VMs. However, the 0x20001 Stop error is not generated when you start the Windows VM. This error is instead randomly generated after several days, weeks, or months of uptime."

    I will install the fix at the earliest service window.

    I will have a look at http://support.microsoft.com/kb/2135160/en-us as well, it was released July 7th, so obviously someone else have had the same issue :)

     

    Friday, July 15, 2011 7:42 AM
  • Please let us know if the above mentioned fixes resolved the problem.  If they did not help in resolving the thread please re-open it.
    --------------------------------------------------------------------------------
    Regards, Michael V [MSFT] - This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, January 19, 2012 6:42 PM
    Moderator
  • Although this is an older post i would like to let you know that i was experiencing the symptoms described above and in KB2550569. This was on a new Hyper-V cluster using Dell R620 servers. In my case it was a Linux VM based on Debian 5. But Migrate to a physical computer with a different processor version  was enabled and sure enough the node crashed the moment this VM was started.

    After installing KB2550569 on all nodes it was possible to start the Linux VM without crashes.

    Friday, June 15, 2012 12:37 AM
  • we have the server geting rebooted by a bugchk error for netft.sys "0x0000009E" Stop error  Please let me know if we have any fix for this issue. i am not sure wht is causing the issue on the server

    the server is windows 2008 R2 Datacenter and it is on the HyperV cluster

    did any one get a fix for this issue ?

    Friday, March 8, 2013 8:30 PM
  • we have the server geting rebooted by a bugchk error for netft.sys"0x0000009E" Stop error Please let me know if we have any fix for this issue. i am not sure wht is causing the issue on the server

    the server is windows 2008 R2 Datacenter and it is on the HyperV cluster

    did any one get a fix for this issue ?

    Friday, March 8, 2013 8:37 PM