Good afternoon everyone, I know that sometimes it's not the intention of this forum to ask this type of question but I've been looking for a solution to a problem with my computer for two days and I can't find it, let's go. I have a PC with an MSI B450M Pro M2 Max motherboard that I previously used together with a Ryzen 3 2200g. I recently purchased a Ryzen 5 5500, updated the BIOS and installed it and the network card no longer works, it doesn't blink or anything like that, so I put the BIOS on the Ryzen 3 2200g and installed it back on the PC and The card worked normally, then I put the newer BIOS and put the Ryzen 5 5500 and the card doesn't work, it doesn't blink or anything, can you help me?
Problem with my PC.
- Thread starter Radahh_
- Start date
- Status
Juhku
Power Member
- Jul 9, 2020
- 598
- 3,936
Your network card's MAC address might've been wiped from the BIOS update.
Check your card's MAC address. If it doesn't match with the address on the sticker/label on the card, you need to 'reprogram' it to its original state. Google how to do so, or contact the network card's manufacturer.
Check your card's MAC address. If it doesn't match with the address on the sticker/label on the card, you need to 'reprogram' it to its original state. Google how to do so, or contact the network card's manufacturer.
ViralMagnet
Power Member
- Jul 29, 2023
- 617
- 316
Check MSI's website for the latest drivers for your motherboard, specifically for the Ryzen 5 5500.
- Oct 28, 2023
- 208
- 30
I think, you run a complete test to determine if is an issue with the hard drive, first you computer will shut doen, other common casue your pc faiing linked to viruse,bad power source & damage hardware.
theusualkeysersoze
BANNED - Failed to resolve a dispute
- Oct 11, 2025
- 901
- 511
This is a zombie thread but none the less one of the interesting threads here, my best guess is that bios build is broken.
This is a common issue unfortunately and there's are roughly 5 approaches to fix, from meek to radical, but it's moot to do remote ts attempts on an otherwise dead thread.
This is a common issue unfortunately and there's are roughly 5 approaches to fix, from meek to radical, but it's moot to do remote ts attempts on an otherwise dead thread.
- Status