Hello,
I just bought a Macbook Pro 15" 2018 and installed Windows 10 using Bootcamp. My laptop crashes every few minutes on module bcmpciedhd63.sys. It also crashes on the Apple Audio driver occasionally, Please HELP!
If you can find a pre-T2 Apple Mac like https://www.apple.com/shop/refurbished/mac/1tb-2017-15-inch-macbook-pro-16gb , it is much better than a 2018 or later model.
I refuse to buy any Apple T2 laptop for the next 24 months. I use a Mini 2018 instead.
A few more details:
No, I didn't have any issues with macOS.
However, following your questions:
So far my Windows 10 has been up without any crashes! My fingers crossed - will update after I've had a chance to test this out for some time.
Thanks so much for your help! Let's hope this resolves it!!
After battling with the driver issues causing stability problems in Windows 10 (W10) on MacBook Pro (MBP), I decided to give in and return the laptop. With neither Apple nor any other company backing the configuration, it's a huge risk I'm taking for a premium product. I'm a bit peeved that I spent countless hours debugging the issues and have nothing to show for it. Here are the reasons for my decision to return the laptop back to Apple:
I can go on and on but these are the key reasons for my giving up on MBP 2018 edition. I'm back to using my old MBP as long as it lasts...
Adios Amigos!!
PS: With the experience I've gained debugging W10 on MBP, it feels like I can start providing BootCamp consulting in lieu of Apple as it's very frustrating to deal with the issues right after one purchases a new laptop without any support from the OEM!
An extract from the windows dump file:
MODULE_NAME: bcmpciedhd63
IMAGE_NAME: bcmpciedhd63.sy
DEBUG_FLR_IMAGE_TIMESTAMP: 5c12e552
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 376ef
FAILURE_BUCKET_ID: 0x82D_bcmpciedhd63!unknown_function
BUCKET_ID: 0x82D_bcmpciedhd63!unknown_function
PRIMARY_PROBLEM_CLASS: 0x82D_bcmpciedhd63!unknown_function
TARGET_TIME: 2019-04-19T00:27:42.000Z
OSBUILD: 17763
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2005-12-02 02:58:59
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 129c
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x82d_bcmpciedhd63!unknown_function
FAILURE_ID_HASH: {94952c96-62e4-24a4-527f-e19ff8a1b2ee}
Some more windbg information:
8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (82d)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
DUMP_TYPE: 1
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: c
CPU_MHZ: b58
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: a
CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 9A'00000000 (cache) 9A'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x82D
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DNATARAJ-BC
ANALYSIS_SESSION_TIME: 04-18-2019 20:41:17.0864
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff807454176ef to fffff8072c64c730
STACK_TEXT:
ffffbd8b`acea05b8 fffff807`454176ef : 00000000`0000082d 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbd8b`acea05c0 fffff807`4542ab5f : 00000000`00000000 ffffad8f`db861040 ffffad8f`db861040 00000000`00000000 : bcmpciedhd63+0x376ef
ffffbd8b`acea0640 fffff807`4543b0a1 : fffff807`454e4cf0 ffffad8f`db861001 fffff807`454e4cf0 00000000`00000002 : bcmpciedhd63+0x4ab5f
ffffbd8b`acea06f0 fffff807`4543c304 : ffffad8f`db861040 00000000`00000000 ffffad8f`db861040 00000000`00000000 : bcmpciedhd63+0x5b0a1
ffffbd8b`acea07a0 fffff807`4543c440 : ffffad8f`e03a5020 ffffad8f`db861040 ffffad8f`dc2b8000 ffffd081`91349180 : bcmpciedhd63+0x5c304
ffffbd8b`acea0830 fffff807`45439dd7 : 00000000`00000000 ffffad8f`db861040 ffffad8f`dc2b8050 00000000`00000000 : bcmpciedhd63+0x5c440
ffffbd8b`acea08b0 fffff807`45418f96 : 00000000`e03a5000 ffffad8f`dd79b040 ffffad8f`db92e000 00000000`00000000 : bcmpciedhd63+0x59dd7
ffffbd8b`acea0970 fffff807`45450b8c : ffffad8f`db92e000 00000000`00000000 00000000`00000000 ffffad8f`d709eb90 : bcmpciedhd63+0x38f96
ffffbd8b`acea09a0 fffff807`3f922662 : ffffad8f`d7ebc540 ffffad8f`db826e20 00000000`00000000 fffff807`00000000 : bcmpciedhd63+0x70b8c
ffffbd8b`acea09d0 fffff807`2c4bebcc : 00000000`00000000 00000000`00000000 ffffad8f`db93d080 00000000`00000000 : ndis!ndisDispatchIoWorkItem+0x12
ffffbd8b`acea0a00 fffff807`2c50dafa : ffffad8f`d709eb90 ffffad8f`d7ebc540 fffff807`2c4beaa0 fffff807`00000000 : nt!IopProcessWorkItem+0x12c
ffffbd8b`acea0a70 fffff807`2c4d6a45 : ffffad8f`d7ebc540 ffffad8f`d7081300 ffffad8f`d7ebc540 000024ed`bd9bbfff : nt!ExpWorkerThread+0x16a
ffffbd8b`acea0b10 fffff807`2c653b8c : fffff807`2b3df180 ffffad8f`d7ebc540 fffff807`2c4d69f0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffbd8b`acea0b60 00000000`00000000 : ffffbd8b`acea1000 ffffbd8b`ace9a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c
THREAD_SHA1_HASH_MOD_FUNC: 1e51dba09ee4bf0a1b68c2da51378251b39bc7a6
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ffe28f5fb39af5930e3a58f3f2997fc4c6e958aa
THREAD_SHA1_HASH_MOD: 7ff187d64a8383209616e8c1d350cc64457d53b2
FOLLOWUP_IP:
bcmpciedhd63+376ef
fffff807`454176ef cc int 3
FAULT_INSTR_CODE: 4c8b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: bcmpciedhd63+376ef
djssna wrote:
So far my Windows 10 has been up without any crashes! My fingers crossed - will update after I've had a chance to test this out for some time.
If you do get any crashes, I suggest looking the Windows event viewer. 🤞🏻
The crashes are less frequent than before (crash after an hour of use vs every 10 minutes or so before). The first one happened after I realized that my speakers weren't working. I was trying to play some audio to look into the problem but in the process (I wasn't changing any settings though) the system crashed and the culprit was Apple Audio driver. I rebooted now the previous problem has returned. Random crashes except after about an hour or so. I looked at the event viewer but the errors reported were in DCOM launch permission errors. Not sure what they are though. This is a brand new laptop with WIndows 10 installed using Bootcamp and nothing else. This is very frustrating. Please let me know if you have any ideas. I will pick it up tomorrow morning to to see if there's any respite to this problem before I return this laptop to where it came corm :(
The 2018 Macs with Apple T2 controller have many teething issues with Bootcamp. The Audio issue is well known and there are a few posts about it. If you use BT audio, the issue can be worse.
The only T2 Mac I have is a 2018 Mini, which currently does not run Windows.
OK, it's almost time to give up on this laptop. It looks like the crappy Broadcom WiFi driver is crashing windows but a search on the Broadcom support website is completely useless. I'm not even sure what Broadcom WiFI model is used on this 2018 Macbook Pro 15'. Starting in 2012, I have put in a healthy amount of time trying to make Windows work on Macbook Pros. I'm totally disappointed to say the least....
Finally someone else experiencing this. I'm seeing (mostly) the same problem with the same machine. The frequency is a bit lower for me, with crashes happening about twice a day, and I haven't noticed any audio driver crashes. I too noticed that Broadcom's website is worthless. This iFixit teardown of a 13" TouchBar model indicates the WiFi chip is a "Apple/Universal Scientific Industrial (USI) 339S00428 Wi-Fi/Bluetooth module", but I don't know if that applies to the 15". Searching for drivers for that chip was fruitless for me.
I also used brigadier to download the drivers. Digging through the folders, I didn't notice anything obviously related to Broadcom WiFi worth re-installing.
I've tried messing with the WiFi power management settings but haven't found anything reliable yet. Will keep an eye out for audio driver crashes. Let me know if I can provide any information.
One unusual thing about my setup is that I am on the Windows Insiders Slow Ring, so I already have the May 2019 update. Also, I develop regularly with Hyper-V (via Docker for Windows) and I've noticed on other machines it can interfere with networking - though not lead to driver crashes.
From Bootcamp.xml downloaded for a MBP 15,1 using Brigadier,
This is the Product version...
<ProductManufacturer>Apple Inc.</ProductManufacturer>
<ProductVersion>6.1.7071</ProductVersion>
<ProductCode>{FCFFE6B6-BAE8-490E-88D0-097A9DA1C43D}</ProductCode>
and the specific driver you should have is
<Name>Broadcom 802.11ac PCIE Network Adapter Driver
<InfName>bcmwdidhdpcie.inf</InfName>
<Class> Net</Class>
<ClassGUID> {4d36e972-e325-11ce-bfc1-08002be10318}</ClassGUID>
<CatalogFile> bcmpciedhd63.cat</CatalogFile>
<Provider>Broadcom</Provider>
<DriverVer>06/25/2018, 100.10.200.18</DriverVer>
<ServiceBinary>bcmpciedhd63.sys</ServiceBinary>
<HardwareID></HardwareID>
<isX64>yes</isX64>
</Name>
You can also find the exact PID/VID of the card on the macOS side, in About This Mac -> System Report -> WiFi. It is a Broadcom BT/WiFi card. The iFixit teardown can be confusing between chipsets and modules.
I see, I'll take a look at the macOS resource once my workday is done.
I also have the same info in the Bootcamp driver archive I downloaded.
Interestingly, Device Manager reports the driver details as follows:
Name: Broadcom 802.11ac Network Adapter
Date: 12/13/2018
Version: 100.10.459.0
I have now managed to install the drivers from the Bootcamp driver archive. Hopefully this resolves things.
Thanks again for all your input! You're terrific!! I will provide a bit more details in my response to lunalot as to what has happened since my last update! Things are looking up a bit...oops, I hope I haven't jinxed it already!
I'm sorry to hear that there's another person having similar issues -- good and bad :)
Just before I decided to format my hard disk in preparation for a return, I wanted to try one more thing, which was to doubly making sure the version of the WiFi was the same as what came with BootCamp (BC). Since I couldn't figure that out (but thanks to loner T, we now know). I spent a bit of time in Device Manager to review all the settings for the WiFi driver. While doing so, I accidentally clicked on the "rollback driver" button and it appeared to do something! Now my WiFi driver info reads like this:
Driver Provider: Broadcom
Driver Date: 9/25/2018
Driver Version: 100.10.330.6
I haven't experienced any crashes since!!! I will keep you posted as I will test this one out for a few days before I decide what to do with this laptop!
Give it a shot and post what you see as well.
Best!
Frequent BSOD using Bootcamp on bcmpciedhd63.sys