Windows 10: BCM43xx S3 resume firmware initialization problem (MacBook Pro 15 mid 2014)

Here are my testing results on BootCamp Windows 10 x64:

1. My Device Manager configuration prior to first Sleep test (you have to select the "View->Show hidden devices" menu option!). As far as I assume it looks like yours if you would have deleted the "Broadcom 802.11ac Network Adapter #2" device instance which is hidden on your screenshot. I can Reboot/PowerOn/Hibernate my computer many times to see the same picture, but not Sleep.

2. My Device Manager configuration after first Sleep test (you have to select the "View->Show hidden devices" menu option!). Now you can see the phantom "Broadcom 802.11ac Network Adapter #2" device instance which is active, but the first one is inactive (failed adapter firmware S3 Resume initialization). In this case I have lost network connection until Reboot/PowerOn. As far as I can see you have one more phantom "Broadcom 802.11ac Network Adapter #3" device instance, so you have the same bug in Apple Airport Adapter firmware.

3. Here is the same test with no driver installed with the same result, so we have the S3 resume firmware initialization bug of built-in Apple Airport Adapter.

Loner T wrote: "On the OSX side, the same adapter and EFI and firmware seems to wake-from-sleep correctly".

Are you sure?! So what do you say on this Re: Slow WiFi issues after 10.10.2 or this Re: Late 2013 Macbook Pro Retina 13'' Wifi Issues ?

Absolutely the same symptoms, and I should repeat it's a hardware problem from manufacturer. Also I provided exact explanation with 100% reproducible test, and pictures. What more do you (the Apple) need to solve this problem for valued customers?

"This is not EFI, but the interaction between EFI and a Driver, and a specific state transition. Your suggestion that it is an EFI issue, is not quite right. The same EFI works as designed on the OS X side, so why is the EFI an issue?"

I also provided the screenshots of test with no driver installed with the same result (diplicated Apple Airport device instance ) here Re: Windows 10: BCM43xx S3 resume firmware initialization problem (MacBook Pro 15 mid 2014)

Could the Apple be so kind to contact the Broadcom to request a firmware update for built-in Apple Airport Adapter of my MBP Retina 15" mid 2014 (A1398) that corrects the S3 resume initialization bug of built-in Apple Airport Adapter?

Adapter details from MAC OS X El Capitan v10.11.3:

Card Type: Airport Extreme (0x14E4, 0x134)

Firmware Version: Broadcom BCM43xx 1.0 (7.21.94.136.1a1)

Adapter details from BootCamp Windows 10:

Broadcom 802.11ac Network Adapter

PCI\VEN_14E4&DEV_43A0&SUBSYS_0134106B&REV_03

Do you see the hardware id PCI\VEN_14E4&DEV_43A0&SUBSYS_0112106B&REV_03) on your screenshots? If it changed to the same value after Sleep could you explain me what were you testing?

My Air Port card has the hardware id PCI\VEN_14E4&DEV_43A0&SUBSYS_0134106B&REV_03

Do you see the difference between 12 and 34?

Cold you please be so kind to read my previous post Re: Windows 10: BCM43xx S3 resume firmware initialization problem (MacBook Pro 15 mid 2014) carefully?

This model Re: Windows 10: BCM43xx S3 resume firmware initialization problem (MacBook Pro 15 mid 2014) is much closer to my 15'' mid 2014. Could you please show me the Hardware Id of AirPort card (especially SUBSYS value) on each step of your test in linked post?

This model Re: Windows 10: BCM43xx S3 resume firmware initialization problem (MacBook Pro 15 mid 2014) is much closer to my 15'' mid 2014. Could you please show me the Hardware Id of AirPort card (especially SUBSYS value) on each step of your test in linked post?

PS: your MBP late 2013 http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.6- 15-dual-graphics-late-2013-retina-display-specs.html

my MBP mid 2014 http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.5- 15-dual-graphics-mid-2014-retina-display…

This model Re: Windows 10: BCM43xx S3 resume firmware initialization problem (MacBook Pro 15 mid 2014) is much closer to my 15'' mid 2014. Could you please be so kind to show me the Hardware Id of AirPort card (especially SUBSYS value) on each step of your Windows test (before and after Sleep) in linked post? It would be important to know because you have different board revision. I need this information to decide is it EFI or adapter firmware bug.

PS: your MBP late 2013 http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.6- 15-dual-graphics-late-2013-retina-display-specs.html

my MBP mid 2014 http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.5- 15-dual-graphics-mid-2014-retina-display…

As far as I already described above, the Broadcom wireless driver was completely removed to perform clear test for just device (no driver) initialization and detection to avoid confusion. Device initialization test passed with "Power-On", "Reboot" and "Resume from Hibernate" modes, but this test failed with "Wake-Up from Sleep" mode, so I got duplicated "Network Adapter" instances for one physical device. It looks like the adapter firmware doesn't perform correctly EFI specification S3 Resume algorithm that results in failed hardware device initialization. In this case I have no idea except the Apple should provide firmware update to correct this serious hardware issue.

It would be interesting also to get reports on test (in the first post) from the MacBook Pro late 2013 users, and probably from MacBook Pro 2015 users as well.

Here is it. In addition I have attached test report in pictures with the latest available Broadcom driver 7.35.338.0 and without driver also http://rghost.net/6B4Km6CD6

powercfg.exe /A

The following sleep states are available on this system:

Standby (S3)

Hibernate

Hybrid Sleep

Fast Startup

The following sleep states are not available on this system:

Standby (S1)

The system firmware does not support this standby state.

Standby (S2)

The system firmware does not support this standby state.

Standby (S0 Low Power Idle)

The system firmware does not support this standby state.

Looking at "Device Manager" window as well I can say that only second instance of device initialization successful, but why not the first one? I don't have the full project of Apple EFI for my platform, so I guess the right way to address such questions to the Apple Engineers. For example, I don't know why Apple still use old Intel ME firmware v9.0.5.1367 while v9.0.50.1022 is the newest one for Haswel microarchitecture. Even better, Intel released ME v9.1.37.1002 (for Broadwel and Haswell) to support ME Software v11.0 for the Windows 10 launch http://www.win-raid.com/t596f39-Intel-Management-Engine-Drivers-Firmware-amp-Sys tem-Tools-101.html#msg19370 and http://www.win-raid.com/t832f39-Intel-Converged-Security-Engine-Firmware-Reposit ory.html

Most of problems could be solved better by keeping EFI and its OEM components firmware up to date, than by dreaming about bugs. In my opinion, if I pay gorgeous price to Apple then I consider to get reciprocal support. Is it right condition?

This problem is independent of an operating system because the device initialization is incorrect after S3 resume (wake up from sleep).
Could you provide a firmware update to solve this issue?

Adapter details from MAC OS X El Capitan v10.11.3:

Card Type: Airport Extreme (0x14E4, 0x134)

Firmware Version: Broadcom BCM43xx 1.0 (7.21.94.136.1a1)

Its a hardware problem from manufacturer that probably could be fixed by firmware update. The "EFI and firmware" must report single device instance for single Broadcom Wireless network adapter (NOT TWICE!) after S3 resume (wake up from sleep) , no matter which operation system is booted. I discussed this situation with Nikolaj Schlej (Software Engineer BIOS) http://www.win-raid.com/u464_CodeRush.html and he completely agreed with my investigations. You could invite him to discussion if you need. I think the Apple must solve this hardware problem.