Device turns off automatically without intervention
Device turns off automatically without intervention
After manually installing the drivers, the crashes decreased significantly. However, they continued to rise and shorten—from about 2 hours to as little as 15 minutes or even 30 minutes, which hadn’t happened before. The MOBO swap finally occurred. (I’ve never seen such a large amount of aluminum for M2 drives, wow!) So far, network crashes are nearly gone, and I’m only using Ethernet so far. But I’ve had two crashes now. After putting the computer to sleep, this version seems much more stable than before. When I tried to turn it on, it showed 47/48 code and didn’t wake up. Looking it up, some posts mention CPU temperatures? But it was in sleep mode and the cooling never exceeded 70°C / 158°F, so I’m unsure what’s going on. After a forced restart lasting about an hour, Issue B reappeared. (Is this normal now with the new motherboard?) Also, if I don’t manually shut it down after that problem, it keeps stuck in that ramping state. Now I have doubts—could my CPU be the cause of all this? It seems like the NIC was the main problem on that board, but were there other issues? Even the RAM doesn’t seem to be involved, and the GPU only increases when something sends a signal. I’m leaning toward the CPU or motherboard being the culprit. Hopefully, I’ll find a clear fix soon.
After extensive testing, the internet problems disappeared. I tried it on an ASUS ROG Strix X870E-E and at some point everything seemed resolved, though issue B kept appearing more often. The new board still worked fine overall. I received a fresh unit of my first MB Asus ROG STRIX B650E-E and reported that all NIC issues were gone. However, the system now crashes constantly—even during writing this post it crashed—and I frequently encounter an MSN page when starting up. In summary, I’ll write another post focusing solely on issue B, as it appears to stem from a damaged or failing NIC.