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!
I had same trouble (0x0000082d blue screen), and probably found solution.
Open "Device Manager" -> "Network Adapter" -> "Broadcom 802.11ac Network Adapter" -> Open "Property" -> "Driver" tab -> Click "Roll back driver" -> Reboot
Probably, Windows Update Broadcom driver is not suitable for Macbook bootcamp.
(I use MacBook Air Late 2018)
My advice - buy a refurbished 2017 MBP from Apple, which is a lot better than any 2018 or later (Apple T2) Macs at this point.
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 :(
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!
It looks like the WiFi driver issue is gone after rolling back the driver. However, the laptop crashed a couple of times (in about 10 hours of use) because of the audio driver! :( Additionally, video playback and audio wouldn't work after a few hours of rebooting the laptop (happened twice, so it's repeatable). The following is the Apple Audio driver version information:
Driver Provider: Apple Inc.
Driver Date: 11/6/2018
Driver Version: 6.1.7300.0
Driver Details: AppleAudio.sys
Unfortunately, there's no rollback option for this driver nor am I able to find a prior version to install. Looks like this may be a showstopper issue for me. Any ideas?
I read both of the posts and my issue is similar to (if not the same as) what those poor Macbook Pro users have described. I'm leaning toward dumping this laptop for now as I don't have any more time nor the patience to deal with driver issues. I spent north of 4 grand for this laptop so I'm totally dismayed at the experience.
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.
Thanks for all your suggestions. After reading about many audio issues faced by various folks on the 2018 version of the Macbook Pro (including the MacOS), it appears there's some architectural issues with various drivers. My issue is likely caused by the battery management driver (just a hunch) interfering with the audio driver. I also notice my trackpad jerky at times, yet another driver issue but doesn't crash the operating system (like the audio driver does). I've decided not to live with these issues and may never buy another Macbook Pro to run Windows - which was my fault to begin with. However, Apple should stop supporting Bootcamp to lure innocent victims into buying this but comes with nearly zero support. This is a big let down for me as I've been a huge apple fan but this one does it for me - I'm not willing to waste any more time dealing with this. It's truly sad that I had to dump this laptop after I fell in love with it initially! :(
Good luck folks! I appreciate your time trying to help me.
Just a quick update: After a day-and-a-half of running without any (visible) issues, audio and video stopped working again. However, the Windows OS didn't crash this time, which is an improvement. I disabled the audio driver and re-enabled without rebooting the laptop and the audio/video started working again.
I called apple for support knowing fully well from past experience (I own a 2012 Macbook Pro 15" on which I have successfully installed Windows 10 directly and working without any issues except it doesn't have enough memory, hence my new purchase) that I would not get any support. The kid who answered my support call didn't have a clue what I was talking about initially and insisted that I needed to call Microsoft for support even though I protested how I could expect Microsoft to support a device driver that was developed by apple for its own hardware! I hung up after expressing my displeasure.
I'm not sure what I want to do with this laptop as I h ave a few days to decide. I definitely need a new laptop but I don't think I want to spend so much for a laptop that has so many issues...
Thanks for the response. I did that already to resolve the 82d crash. Now my problem is with audio and video, no crashes but they randomly stop working. I think the problem is primarily with the audio driver, which has no rollback option.
It's too bad you couldn't make it work. I've got the same model and while I did share the network driver crashes (which we rectified over the course of this discussion thread) I never shared your machine's other issues. It does make me nervous that such a problem will rear it's head down the line, but I'm hoping I escaped suffering because I'm running a preview build of Windows.
Anyway, good luck to you on your next machine.
Cool, thanks! You're truly awesome!!
Nice.
Eventually, since it is your money, spend it the way that best serves your needs.
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
Frequent BSOD using Bootcamp on bcmpciedhd63.sys
