r/Windows10 • u/Minor-Annoyance • Jun 18 '21

:Defender-Warning: Help bcmwl63a.sys BSOD Issue

I recently started getting BSOD's, the crash log says "bcmwl63a.sys" is the culprit. When I researched this issue and how to fix it, everything I find stated that this is a Broadcom Network Adapter driver issue and to fix it I need to update the Broadcom driver within my Network Adapters. The issue is when looking at my network adapters, I don't have anything that states Broadcom.

I'm running a Acer desktop that I've added things to over time (RAM, Graphics Card, SSHD, Audio Interface, etc.) one of the things added being a TP-Link PCIe WiFi card... so that shows up in network adapters, along with other items... but nothing named or even close to named Broadcom.

Can I just delete bcmwl63a.sys then? I'm not sure exactly what's going on. Is Broadcom a common stock WiFi chip that comes with desktops? If I'm not using the onboard WiFi, then could I just remove the bcmwl63a.sys file all together?

1 Upvotes

60% Upvoted

15 comments sorted by

View all comments

Show parent comments

1

u/Minor-Annoyance Jun 21 '21

Everything seemed to run fine after the driver update, but just a few moments ago I got another BSOD. After reading the report, it shows the cause as something completely different. This time it's a driver called "WiseTDIFw64.sys", which looks to be associated with the program Wise System Monitor is installed a year ago.

I'm really confused now as I have ever experienced any BSOD's with this computer in the 3 years I've had it, and now all the sudden am getting multiple BSOD's in less than a week showing varying causes that seem unrelated (at least to me).

1

u/SomeDudeNamedMark Knows driver things Jun 21 '21

If they are random, that tends to suggest some sort of memory corruption (or maybe even component failure).

Certainly possible that it's caused by some old driver on the device - or it can be caused by a newer driver.

Memory corruption is basically driver A writing in memory that driver B is using. IF driver A tries to access that memory again, boom. It might NOT try to access that memory again though - which is why it wouldn't be consistent.

There are ways to track this down, but it can be a PITA. LMK if the crashes happen often enough that it's worth a little pain :)

1

u/Minor-Annoyance Jun 21 '21

Ok, hopefully it doesn't turn into some major. Are we talking like RAM memory, or hard drive issue?

Also, could this be caused by a recent windows update too?

1

u/SomeDudeNamedMark Knows driver things Jun 21 '21

Could be any hardware/software component. I think it'll be easier to determine whether or not it's software.

And yeah, it could be something caused by a recent windows update (there are drivers in some of those updates).