It seems like you're questioning the situation and wondering if others might offer more assistance.
It seems like you're questioning the situation and wondering if others might offer more assistance.
I contacted MSI support yesterday to check for assistance with certain Event Viewer errors. Instead of specific guidance, I received a generic troubleshooting list unrelated to my request. I made sure nothing was altered on the system before the problem began—Windows was reinstalled and a BIOS update was applied prior to the issue.
The automated reply suggested verifying the CPU socket for bent pins, clearing CMOS settings via Jbat1 jumper/SW1 Switch, removing the battery for a minute, and testing components outside the case. It also recommended swapping parts like the processor, memory, power supply, or video card to isolate defective components. Additional steps included removing add-on cards, drives, and cables, using only bare minimum hardware, and checking manufacturer warranty info via their website if the problem persists.
I confirmed no hardware faults were present and everything functions normally in that area. I’ve already tried all those steps and the issue remains unresolved. It seems my message might not have reached them, or they may need more specific details.
If you encounter similar problems, consider sharing more context about the symptoms and any recent changes. For persistent issues, consult the manufacturer’s support resources or warranty procedures.
Based on a brief review of your message, it seems MSI thinks the problem might be related to a hard drive issue. You could try removing the CMOS battery for 5-10 minutes, though it might not solve everything. Also, @Sauron mentioned trying safe mode to avoid Windows problems.
Sure, I’ll give it a shot. I thought everything was fine before I updated the BIOS and reinstalled Windows. I hoped they’d recommend going back to an older BIOS version for better stability instead of walking me through generic hardware fixes. I guess completely taking the machine apart and rebuilding it would be a bit too drastic for what I was expecting.
Just out of curiosity, is there a reason that you updated your BIOS? Generally speaking, you shouldn't really do anything with BIOS unless there is a known issue that is causing hardware to fail or malfunction, or unless the manufacturer has suggested doing so due to some upcoming hardware / software release that will require it. "If it isn't broken, don't fix it". From what I have read, it's one of 2 things. The BIOS update is corrupt or failed in some way that is triggering your USB ports to go haywire, revert back to the original BIOS that came with board, or whatever version you upgraded from . Or, the windows install is somewhat corrupted and will need to be redone. I would try doing a windows repair to see if that fixes the issue. Also, I would triple check your hardware to make sure that when you built machine you didn't bend any of the hard mounted USB connection that could have caused their connection to be skewed in way that they aren't making good contact with the motherboard. Hope this helps.
I might try reverting back to an older bios but I'm honestly scared to brick my board because I know that some boards don't like it if you try to flash an older bios. It's not the windows install. I tried reinstalling windows 3 times now. Even downloaded it again to make sure that the installer wasn't corrupt. There is a chance that a couple of my USBs are loose though. I didn't anchor my USB and HDMI cables down at first when I first got my Oculus rift so there were a few times where I pulled on the ports with the cable tripping on it or walking too far in one direction. I've since anchored the cables down to a table leg with a cable management strap. (anyone using a VR device should do this immediately)
So it happens even without any driver installed? In that case it probably is a problem with the new bios (unless there's physical damage on the board). Try flashing back, it shouldn't be any more damgerous than flashing forward. If that also doesn't solve it you may have broken your board and in that case only a replacement or precision electronic repair (which would require a schematic and some expertise) will fix the issue. -by the way, use the quote function when replying to someone or they won't get a notification.
I’m unsure if I caused any harm to the board beyond possibly stressing the USB ports by pulling on them. I’m very cautious. I wear anti-static wrist bands and kept my hands away from anything when this began. Probably best to switch to an older BIOS version and ease the pressure. At least it’s a budget model.
I went back to the original bios, but the issue kept appearing. It seems unrelated to any real impact at the moment. It only appears when the computer starts and disappears afterward. My USBs seem to connect and disconnect at boot, which is mostly the case. It’s not happening randomly anymore since I added another USB and adjusted how my Oculus sensors are split. I suspect the random disconnects were caused by high bandwidth or power demands from the four sensors. This error likely tries to act before the system is fully ready, similar to how OVRservice for Oculus shows a startup error in the event viewer. None of these issues are showing up in the reliability monitor, so they probably aren’t serious. It’s not affecting anything right now, so unless it gets worse, I don’t think replacing the motherboard is necessary. I wish I understood those other errors better, but everyone probably has minor ones too—especially if you check the event viewer. Overall, it doesn’t seem like a big deal, and I’m not sure what those other warnings mean. Maybe I’ll consider getting a new hub for my keyboard and mouse USBs, since the driver warning on that hub disappears during startup. That could be the root cause. I might test it by buying a new hub just in case. Either way, I’m fine either way.