Bridge.sys failure (Multiple BSOD)

Log File Download: Log File
Windows Version: 21H1 (OS Build 19043.1110)
FAILURE_BUCKET_ID: AV_bridge!unknown_function

I have recently been receiving multiple BSOD errors for Bridge.sys Failure here are some information and some of the things I have done to solve this issue:

Update all Drivers
Update all Windows and optional updates
Reset Windows (Reset this PC)
Re-Installed Windows (deleting the partition and reinstalling)
Bought and installed another MB
Bought and installed another (8x4) set of RAM
Updated to ASUS MB to latest BIOS (ver. 2.00)
Ran GPU Stress test for at least 1 hour
Ran RAM Stress test for at least 1 hour
Ran SSD Stress test for at least 1 hour
Ran CPU Stress test for at least 1 Hour

Commands ran:
DISM /Online /Cleanup-Image /CheckHealth - no errors
DISM /Online /Cleanup-Image /ScanHealth - no errors
DISM /Online /Cleanup-Image /RestoreHealth - no errors
SFC /SCANNOW - 3 errors fixed
CHKDSK C: /F


Failed:
Bridge.sys (Most Common)
regsvr32.exe

Error codes:
IRQL_NOT_LESS_OR_EQUAL (Most Common)
SYSTEM_THREAD_EXCEPTION
UNEXPECTED_STORE_EXCEPTION

MEMORY.DMP Errors:
- FAILURE_BUCKET_ID: AV_bridge!unknown_function
- BUCKET_ID: AV_bridge!unknown_function
- PRIMARY_PROBLEM_CLASS: AV_bridge!unknown_function

Notes:
- I ran Driver Verifier for one of the first steps and couldn't boot into windows due to instant
BSOD and boot into safe mode turned it off, queried the MEMORY.DMP file, updated some drivers,
after 2nd run there were no BSOD while running Driver Verifier.

- After a bit more troubleshooting I found the "AV_bridge!unknown_function" I assumed it was
the network bridge between my desktop and laptop that was causing the issue. I plugged a USB
to Ethernet adapter into the USB-Port on the motherboard and the BSOD seemed to stop for
about 10 hours before continuing again.

Conclusion:

I have been troubleshooting this issue for about a week now. Before I knew bridge.sys was a network issue, I had invested in a new Motherboard (Asus B550 Phantom Gaming 4 -> B550 Asus Steel Legend) and new RAM (32GB (8x4) Crucial Ballistix @ 3200MHz) trying to find a hardware issue, but this obviously didn't resolve it. I don't have any good options for Internet speeds where I live, so I have my Samsung Galaxy Note20 Ultra 5G providing a hotspot connection via a USB-C connection to the USB-C port on the front top of my case (Installed with the latest drivers). I had a TP-Link 5-Port Gigabit Desktop (unmanaged) switch between my desktop and laptop connected by two straight-through Cat-6 ethernet cables but removed it and directly connected my two PCs using one of the Straight-Through cables from before (this again obviously didn't solve the issue). I understand Straight-Through ethernet cables are not used for connecting two devices together, I have read somewhere that most modern routers and switches can handle not being connected using cross-over cables, but as my last step for troubleshooting, I have ordered some cross-over cables to see if it will resolve my bridge.sys failure.

Any other troubleshooting steps or help will be much appreciated,
Thank you in advance!

Combatcollier

Hmm, kind of a strange thing. Maybe you use some VPN software, third party antivirus or other software that installs its own virtual network card?

MrPepka said:

Hmm, kind of a strange thing. Maybe you use some VPN software, third party antivirus or other software that installs its own virtual network card?

If that were the case I would see it in the adapters inside of the control panel, correct? I don't see any other adapters of that nature.

- - - Updated - - -

My 10ft Cat 6 Cross-over cable has been delivered and set up today, I will see how it goes and see if this fixes my issues, any other ideas to fix this would be greatly appreciated!

- - - Updated - - -

Update: changing to the Cross-Over Ethernet cable did not work, I just received another BSOD. Here is the link to the updated log file: Log

What settings did you run Driver Verifier with? Restart it with standard settings, but give this bridge.sys driver for verification in addition to third-party drivers. We'll see which driver can't call bridge.sys

MrPepka said:

What settings did you run Driver Verifier with? Restart it with standard settings, but give this bridge.sys driver for verification in addition to third-party drivers. We'll see which driver can't call bridge.sys

I ran driver verifier with the settings you asked for without getting a BSOD, here is the log for that: log

I also ran verifier with ALL drivers checked and received a BSOD as soon as bridge.sys was loaded, here is the log for that: log

Driver Verifier with verified absolutely all drivers (i.e. those from third parties and from Microsoft) is ineffective, hence probably the same results as when it is turned off
If you disconnect the smartphone from the computer, do you also have BSODs? You also wrote that you got rid of them by plugging in the network card to USB and using it, so maybe the network card integrated with the motherboard also causes these problems? On the other hand, you replaced the motherboard, so it's probably a problem with the smartphone's firmware (you use it as a virtual network card)

MrPepka said:

Driver Verifier with verified absolutely all drivers (i.e. those from third parties and from Microsoft) is ineffective, hence probably the same results as when it is turned off
If you disconnect the smartphone from the computer, do you also have BSODs? You also wrote that you got rid of them by plugging in the network card to USB and using it, so maybe the network card integrated with the motherboard also causes these problems? On the other hand, you replaced the motherboard, so it's probably a problem with the smartphone's firmware (you use it as a virtual network card)

I do not get BSODs when unplugging the phone, I only THOUGHT I got rid of the BSODs with the USB to Ethernet adapter but that's not the case, the BSODs continued after about 10 hours.

I have found a temporary solution to my issue though, connecting my Phone to a USB-C to ethernet adapter and connecting that to one of the ethernet ports on my switch with a cross-over cable and connecting another cross-over cable to my pc from the switch has been BSOD free. This turns my phone over to "Hotspot over ethernet" and no longer "Hotspot over USB".

As for fixing this issue, I assume this is a bug in the windows 10 Bridge.sys or like you said, my phone's firmware. Is there a way to test out which one?

Yes, check if you connect another smartphone and set it to "USB Tethering" mode is similar