Broadcom 802.11n Network Adapter Driver Windows 8.1

[Tabita Knezevic]

Onsuch a computer, when you update the in-box Broadcom network adapter driver to a later version or when you install the Intel chipset driver, the computer experiences a Stop error (also known as a blue screen error or bug check error).

The operating system media for Windows Server 2019, version 1809, contains version 17.2 of the Broadcom NIC driver. When you upgrade this driver to a later version, the process of uninstalling the version 17.2 driver generates an error. This is a known issue.

This procedure describes how to use Device Manager to disable and re-enable the Broadcom network adapter. Alternatively, you can use the computer BIOS to disable and re-enable the adapter. For specific instructions, see your OEM BIOS configuration guide.

Has there been ANY update on this? I have seen many people (myself included) still getting blue screens while running Windows 10 using Boot Camp thanks to this driver. I am also unable to now roll back to an earlier version and am weary of getting the old driver from a 3rd party site.

I tried downloading and "repairing" using the Apple Support software for Windows 10 on the off chance they rolled back the driver but nothing changed. The Broadcom site is also abysmal with no way of getting old versions of drivers. Someone on an old thread suggested removing every device under network adapters, but didn't know if anyone else had success doing this?

The safest method is on the macOS side, BC Assistant -> Action -> Download. Also, see Download and install Windows support software on your Mac - Apple Support for reference. Check Bootcamp.xml before you try to re-install the drivers.

This method - -us/help/2500967/how-to-stop-windows-7-automatically-installing-drivers - should also work on W10. You will first need to uninstall and remove the adapter and driver, and remove the corresponding files from the DrvStore using pnputil.exe.

Thank you for the detailed response Loner T! My current driver version is: 100.10.459.0 from 12/13/2018. I believe the one you're using is the one I had most success with before the most recent Windows update. The same update which unfortunately has prevented me from reverting the driver back. Do you know of a safe way to obtain the older version of the driver? As I've said before it's not available directly from Broadcom(as far as I know), and I have little experience with third-party distributers.

I know how to prevent automatic driver updates for all devices, but would you also happen to know of a way to lock the driver version of the Broadcom adapter specifically, or prevent it from updating in the future?

Out of curiosity, how did you personally prevent your driver from updating? Or did you simply prevent all automatic updates? There are some ways to accomplish this like you said using the hardware ids and the command line, but I didn't want to mess with it at this time. There doesn't appear to be any built-in feature to accomplish this unfortunately.

Frustrating followup: I just recevied another blue screen with stop code 0x00000827. I thought this was the error caused by the Broadcom adaptor's newest driver, but I went back and confirmed that it was still using the old driver. So now, I have NO clue what is causing this.

Is Apple going to actually fix this or am I going to have to download debugging software and teach myself how to parse through minidump files just to ensure my computer can actually run? Error code 0x00000827. Seriously struggling to find time to look into their hardware issues.

Here's where I'm currently at. I examined the .dmp file created as a result of the most recent bsod. I determined that the issue is still pertaining to the Broadcom driver. WinDbg pathed the error specifically to the file "bcmpciedhd63.sys". So what I did was first turn off automatic driver updates and then uninstall and remove the driver through device manager(what I did previously). However, after doing this, I noticed that this file "bcmpciedhd63.sys" was still present in my system directory. So, just for good measure, I changed it's permissions to allow me to remove it completely. I'm suspecting that perhaps this file contained info for the updated (unstable) version, and was still being utilized by the system? I could be completely wrong on that, but regardless, I re-ran the windows support for boot camp and re-installed the driver once again. I will have to wait and see if this works (It probably shouldn't take long, my faithful computer likes to bsod at least once a day).

The odd thing is, out of curiosity, I went into device manager, verified the adapter as the old version, and hit update just to see if one was available. To my surprise, it said the driver was up to date. So either something is still wrong, or they removed the latest version. However, I CAN verify that the version I currently have is the one you also have. Or at least that is what device manager is telling me.

Well I should clarify, I tried everything pertaining to the BROADCOM driver haha...I had issues with the Audio Driver early on but was able to resolve that fairly quickly. I will continue to work and report back anything that happens. I suppose one nice thing is to definitively know it's still the Broadcom driver, thanks to your suggestion to examine the .dmp file. I just wish someone would finally address this. It's a shame because it truly is the sole thing ruining the Boot Camp experience for me.

Sure, I'll email it to you next time it blue screens in this way (which will likely be soon). I removed some drivers I suspected might be problematic, so I want to provide the most accurate .dmp file.

At this point, this computer is becoming a liability and if the issues persist I will have to seek a replacement. I really would rather it not come to that so any help you could provide would be most welcome!

Did you ever have a chance to look at the minidump? I think I may have narrowed down where the issue is stemming from, but I'd like to see if you reached the same conclusion. I am noticing that whenever I have my computer hooked up on my desk, to my monitor, mouse, keyboard, etc...I never get the blue screen. Therefore, I have started completely removing the devices before disconnecting them. SO FAR I have not received any bsods after being diligent and removing them. However, I haven't tested it out nearly enough. If this solves the problem, that would be great, though it is an absolute pain having to reconnect my wireless devices every time I want to use my laptop at my desk.

I got my MP mini 210 a few days ago with XP home. I upgraded it to WIndows 7 yesterday. After install everything was humming just fine, even the wireless. I thought this is to good to be true. Then Windows installed 21 updates. It was after the updates that my wireless was hosed. Same problems everybody else has documented ihere. I think it something in those updates is conflicting with the Broadcom 4313 driver.

The older version of the Broadcom wireless driver did not fix the problem. Wireless connection was still intermitent. Sometimes it would see my home wireless and sometime it would report no wireless available. I tried various things all weekend.

Well after I did this update all my wireless problems went away. Perhaps the Realtek driver was clobbering the Broadcom wireless. I think HP knew there was a problem and got Microsoft to send out update to fix.it. Just my guess.

Please mark this thread as solved by clicking on ' Accept as Solution ' button in this post which have correct solution written by You. This will help other users with the same problem to find this answer much more easier.

Well after my last post, after installing windows update, my wireless was fine for a few days and then the problem came back. Sometimes it sees wireless networks and sometime it says none available. Once it see none available repeated restarts do not help.

I have the HP Mini 210 HD, WG924AV. I ordered it with XP and installed a legit copy of WIndows 7 Enterprise 32 bit. At this point I'm thinking of trying a USB wireless adapter or going back to XP. It's very frustrating. At this point all I have is a $400 "mini" Boat Anchor. So my problem is not solved, and I'd tag it such if I know how on this thread.

In the Windows Update I found that Realtek lan driver update, did it, *NOTHING* changed, still the same... I just tried hibernating it and waking it up and now the wireless just connected, then I started downloading and installing the Live Messenger (it's a brand new fresh install of Win7 after format) and BAM, disconnected again in the middle of the download!!

I started looking at the advanced properties in device manager for the Broadcom 4313. The setting for Mixed Cell support was set disabled. From reading other blogs they indicated it should be set to enabled. I checked my other dell laptop and my wifes (which use Dell wireless controller, probably a quallcom) and they were set to enable. So I enabled it, rebooted and wahla the wireless saw my wireless router and connected. I''ve rebooted about 5 times now and it's still connecting. I'll see how it go's over the next few days and see if it connects to my work secure wireless.

3a8082e126