I've just bought a new desktop PC, the MSI Aegis ZS2 B, with 32GB of RAM and an AMD Ryzen 9 9900X processor, but I'm facing some frustrating issues. Initially, after a short sleep mode, it completely crashed with a message saying my computer needed to restart. When I came back, my Ethernet and Wi-Fi networks had vanished. I've tried several fixes like a network reset and utilizing the device manager to disable and re-enable my Realtek PCIe LAN controller. While this seemed to temporarily fix the Ethernet issue, it happened again after a second sleep mode, forcing me to go through these steps repeatedly. Additionally, I encountered a 'Watchdog violation' message during one of the crashes. I'm considering a factory reset, but before that, I'd like to see if anyone else has experienced these kinds of problems and whether you think it might be a hardware or software issue. Should I just exchange the PC instead?
3 Answers
Have you looked into the reliability history or event viewer? They can give you detailed info on what went wrong during those crashes. The reliability history is much easier to read and might outline the critical errors you're getting. Just a thought!
This sounds really frustrating, but it might not be a hardware fault. Since the network issues seem to happen after sleep, it could be a driver issue or something with your BIOS settings. I recommend updating your BIOS and the Realtek LAN drivers straight from MSI’s site. After that, try disabling Fast Startup in your power settings and see if that helps. You might also want to check the box in Device Manager that says 'Allow the computer to turn off this device to save power' for your Realtek adapter. If these don’t work quickly, considering it's brand new, I would seriously look into exchanging it.
I'm curious about the "network commands" you mentioned. Did you check Device Manager for any warning icons next to the network adapters? That could give more insight into what's going on.
I checked and saw several critical errors since I got the PC, including Kernel-Power errors. Looks like something’s definitely off.