locked
Repeatable Bootloop BugCheck after enabling Hyper-V in Windows 10 Build 10240 RRS feed

  • Question

  • Windows 10 RTM Build with all updates as of 09/01/2015 on a Dell M3800 workstation with latest bios (A09) and Virtualization enabled.

    When Hyper-V services are installed and a reboot is performed. The system will come online and allow login and after between 2-8 minutes the system will BSOD with a paged pool error. The bugcheck gets to 100% but never does automatically reboot the system. I then hard reset the system and again can login to windows and eventually it will bugcheck again. I then disable the virtualization option in the Dell BIOS, restart and rush into windows to uninstall the Hyper-V services before the system bugchecks again. The system returns to stability once the Hyper-V services are removed.

    Some WinDbg information follows from the DMP I found in the windows folder from today.

    //////////////////////////////////////////////////////////////////////////////////////////////////////

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except.
    Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: fffff6fb400037a8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000006, (reserved)

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


    SYSTEM_SKU:  Dell Precision M3800

    SYSTEM_VERSION:  A09

    BIOS_DATE:  01/08/2015

    BASEBOARD_PRODUCT:  Dell Precision M3800

    BASEBOARD_VERSION:  A09

    BUGCHECK_P1: fffff6fb400037a8

    BUGCHECK_P2: 0

    BUGCHECK_P3: 0

    BUGCHECK_P4: 6

    READ_ADDRESS:  fffff6fb400037a8 

    MM_INTERNAL_CODE:  6

    CPU_COUNT: 8

    CPU_MHZ: 8f7

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3c

    CPU_STEPPING: 3

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  AV

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ANALYSIS_VERSION: 10.0.10240.9 amd64fre

    TRAP_FRAME:  ffffd0013838e600 -- (.trap 0xffffd0013838e600)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000033a32090 rbx=0000000000000000 rcx=0000000033a32f7f
    rdx=00000000deadb000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800594c2198 rsp=ffffd0013838e790 rbp=0000098000000000
     r8=ffffe0000d000030  r9=00000000006f56d8 r10=ffffe0000d000000
    r11=ffffe00012180000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!MmBuildMdlForNonPagedPool+0x88:
    fffff800`594c2198 498b06          mov     rax,qword ptr [r14] ds:00000000`00000000=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff8005956de8e to fffff8005954f240

    STACK_TEXT:  
    ffffd001`3838e318 fffff800`5956de8e : 00000000`00000050 fffff6fb`400037a8 00000000`00000000 fffff6fb`7da00018 : nt!KeBugCheckEx
    ffffd001`3838e320 fffff800`59420170 : 00000000`00000000 fffff6fb`400037a8 ffffd001`3838e580 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1008e
    ffffd001`3838e4b0 fffff800`595582bd : ffffe000`0d000000 00000000`00000801 00000000`0019e000 ffffe000`00000000 : nt!MmAccessFault+0x2d0
    ffffd001`3838e600 fffff800`594c2198 : ffffe000`00000200 00000000`0019d1c0 00000000`00000eef fffff801`c140ad56 : nt!KiPageFault+0x13d
    ffffd001`3838e790 fffff801`bd03c351 : ffffe000`0d000000 00000000`deadbeef ffffe000`11c42000 00000000`00000003 : nt!MmBuildMdlForNonPagedPool+0x88
    ffffd001`3838e7e0 fffff801`c1d8e64f : ffffe000`121d3610 ffffe000`121d3610 00000000`00000000 fffff800`59c5546b : ndis!NdisAllocateMdl+0x31
    ffffd001`3838e820 fffff801`c1d70a6c : ffffe000`121bbbc0 ffffe000`1250cf80 00000000`0000009c ffffe000`121bbbc0 : bcmwl63a+0x8e64f
    ffffd001`3838e850 fffff801`c1d6d8bd : 00000000`00000000 00000000`00000000 ffffe000`121bbbc0 00000000`00000000 : bcmwl63a+0x70a6c
    ffffd001`3838e910 fffff801`c1e1e059 : ffffe000`0e979140 00000000`00000000 ffffe000`11c49bf0 00000000`00000000 : bcmwl63a+0x6d8bd
    ffffd001`3838e9c0 fffff801`c1e5dfa1 : ffffe000`00000020 ffffe000`11c42000 ffffe000`0e979140 ffffd001`3838ead0 : bcmwl63a+0x11e059
    ffffd001`3838ea30 fffff801`c1d193ac : fffff800`594d12dc ffffe000`11c42000 ffffe000`11c42000 00000000`00000000 : bcmwl63a+0x15dfa1
    ffffd001`3838eaa0 fffff801`c1d2b370 : 00000000`00000000 00000000`00000000 ffffe000`11c42000 00000000`00000000 : bcmwl63a+0x193ac
    ffffd001`3838ead0 fffff800`59479f94 : ffffe000`121fa900 ffffe000`11900050 fffff800`597da340 00000000`00000000 : bcmwl63a+0x2b370
    ffffd001`3838eb00 fffff800`594796a9 : fffff800`597da340 ffffe000`0e979040 fffff800`59479ea0 fffff800`597da340 : nt!IopProcessWorkItem+0xf4
    ffffd001`3838eb70 fffff800`594e7e88 : ffffe000`0c8b1780 00000000`00000080 fffff800`597da340 ffffe000`0e979040 : nt!ExpWorkerThread+0xe9
    ffffd001`3838ec00 fffff800`59554326 : ffffd001`38604180 ffffe000`0e979040 ffffd001`38610cc0 49ffe033`0de83024 : nt!PspSystemThreadStartup+0x58
    ffffd001`3838ec60 00000000`00000000 : ffffd001`3838f000 ffffd001`38389000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    bcmwl63a+8e64f
    fffff801`c1d8e64f 488bd8          mov     rbx,rax

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  bcmwl63a+8e64f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: bcmwl63a

    IMAGE_NAME:  bcmwl63a.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  55a06cd7

    BUCKET_ID_FUNC_OFFSET:  8e64f

    FAILURE_BUCKET_ID:  AV_R_INVALID_bcmwl63a!Unknown_Function

    BUCKET_ID:  AV_R_INVALID_bcmwl63a!Unknown_Function

    PRIMARY_PROBLEM_CLASS:  AV_R_INVALID_bcmwl63a!Unknown_Function

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:av_r_invalid_bcmwl63a!unknown_function

    FAILURE_ID_HASH:  {d1296efd-0617-c4de-4b82-59e056c62646}

    Followup:     MachineOwner
    //////////////////////////////////////////////////////////////////////////////////////////////////////

    bcmwl63a appears to be a driver related to the pretty popular Broadcom "BCM4352 802.11ac" chip that ships in alot of new laptops.

    Ideas or paths I can pursue? I can make the DMP available to a Microsoft resource if necessary.

    This is affecting my productivity on the Windows 10 platform as I cant run my dev/test VMs.


    SIDE NOTE:

    When you uninstall Hyper-V and reboot it leaves behind the "Microsoft Bridge Adapter" and you wont be able to access any network shares until you remove that bridge adapter (even though your network will look active) and perform another restart. Then your network adapter will behave and you will be able to access your shares again.


    • Changed type Michael_LS Tuesday, September 8, 2015 6:30 AM
    • Changed type TechNet-AC Friday, September 25, 2015 2:59 PM Found answer
    Tuesday, September 1, 2015 3:49 PM

Answers

  • @doynton thanks for sharing your experience with Hyper-V on Windows 10 and the Broadcom wireless driver because it looks like you helped find a solution I could use in the meantime that does not crash/BSOD the Dell Precision M3800 laptop.

    I used "Update Driver">"Browse My Computer">"Let me pick from a list of device drivers on my computer" to list the drivers on my machine and I happened to have a 6.x version of the driver already on my machine.

    Specifically I changed drivers from/to:

    -- Before -- "Dell Wireless 1560 802.11ac Version: 7.35.295.0 [7/30/2015]"

    -- After -- "Dell Wireless 1560 802.11ac Version: 6.30.223.259 [11/28/2014]"

    After picking the 6.x driver I reinstalled the Hyper-V role, created a Virtual Switch(had to do it twice) and added it to the imported VM. I've been working with it all day and haven't had a BSOD/crash yet where as before it would crash with in minutes and continue to crash after every startup.

    @Michael Shao what.s the proper way to report this issue with MS and Broadcom as far as this driver compatibility issues in the 7.x version?

    My post is wordy and verbose on purpose so the search engines can pick this up to save the next guy like doynton did for me.


    • Edited by TechNet-AC Wednesday, September 23, 2015 10:28 PM a detail
    • Marked as answer by TechNet-AC Friday, September 25, 2015 2:59 PM
    Wednesday, September 23, 2015 10:24 PM

All replies

  • Try the following (from a similar thread):

    There is a known issue where the machine will fail to boot when Hyper-V is installed but DEP/NX/XD is disabled in BIOS. You mentioned that you have enabled these options, but you are continuing to see the same problem.
    One other thing we can try is disabling the IOMMU policy and see if that helps. (The hypervisor's usage of the IOMMU device by default is new in Windows 10, and might explain why you are seeing this only on Windows 10).
    You can disable IOMMU usage by the hypervisor by running the following command from an elevated cmd window & rebooting your machine:
    bcdedit /set {default} hypervisoriommupolicy disable


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    Tuesday, September 1, 2015 4:32 PM
  • Ran "bcdedit /set {default} hypervisoriommupolicy disable" without error and unfortunately this did not resolve the issue and a bugcheck is still happening.

    Upon uninstall of Hyper-V the bridge again was not removed but slight difference this time as the Microsoft Bridge was not removable. I had a bugcheck before I could remove this MS Bridge. Next boot it still was not removablee and I had to enter the bridge properties and un-check the wifi adapter then it was removed.

    System seems to be stable since removing that bridge adapter. I'm looking at some third-party solutions until this stabilizes. I'll be monitoring this thread.

    Tuesday, September 1, 2015 7:28 PM
  • Hi AC,

    Thank you for your feedback.

    I will take a further discussion on this, if any update, I will post back.

    Thank you for your patience and understanding.

    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.

    Friday, September 4, 2015 2:31 AM
  • Had exact same problem with Broadcom 802.11n driver bcmwl63a version 7.35.118.40 (24/7/2015) on both 10240 and 10527. 

    Based on this thread (I can't post links)

    h t t p://www.itexperience.net/2015/08/31/windows-10-in-bootcamp-crashes-when-enabling-external-nic-in-hyperv/

    I installed version 6.30.223.215 (13/12/2013).  This resolved it - I can create external switch fine now in Hyper-V.

    I downloaded it from Apple as per the above link - note this is a 1.2GB download for just one 6MB driver. 



    • Edited by lx07 Monday, September 21, 2015 11:47 PM
    Monday, September 21, 2015 11:39 PM
  • @doynton thanks for sharing your experience with Hyper-V on Windows 10 and the Broadcom wireless driver because it looks like you helped find a solution I could use in the meantime that does not crash/BSOD the Dell Precision M3800 laptop.

    I used "Update Driver">"Browse My Computer">"Let me pick from a list of device drivers on my computer" to list the drivers on my machine and I happened to have a 6.x version of the driver already on my machine.

    Specifically I changed drivers from/to:

    -- Before -- "Dell Wireless 1560 802.11ac Version: 7.35.295.0 [7/30/2015]"

    -- After -- "Dell Wireless 1560 802.11ac Version: 6.30.223.259 [11/28/2014]"

    After picking the 6.x driver I reinstalled the Hyper-V role, created a Virtual Switch(had to do it twice) and added it to the imported VM. I've been working with it all day and haven't had a BSOD/crash yet where as before it would crash with in minutes and continue to crash after every startup.

    @Michael Shao what.s the proper way to report this issue with MS and Broadcom as far as this driver compatibility issues in the 7.x version?

    My post is wordy and verbose on purpose so the search engines can pick this up to save the next guy like doynton did for me.


    • Edited by TechNet-AC Wednesday, September 23, 2015 10:28 PM a detail
    • Marked as answer by TechNet-AC Friday, September 25, 2015 2:59 PM
    Wednesday, September 23, 2015 10:24 PM
  • Hi,

    Thanks for the update.

    Please try to take use of the Feedback Tool, with the dump files.

    I have already collected this at my side.

    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.

    Monday, September 28, 2015 12:54 AM
  • Thanks for sharing this. I'm encountering the same issue and have spent a fair bit of time trying to figure out what was going on.

    I've installed those drivers so hopefully I won't get that BSOD again. Very very frustrating!

    Monday, October 26, 2015 8:25 PM
  • This solution didn't work for me. Same exact issue as the OP with Windows 10. When I roll back the driver to the previous version, the machine no longer crashes, but the neither the host machine nor the guest machine have internet access. Access to the LAN is fine. Running the command bcdedit /set {default} hypervisoriommupolicy disable

    Had no effect. Any other thoughts?

    Thursday, April 7, 2016 12:03 AM