Your computer is acting strangely right now. Please assist me! ðŸ˜ðŸ˜ðŸ˜
Your computer is acting strangely right now. Please assist me! ðŸ˜ðŸ˜ðŸ˜
I’m not sure what transpired or triggered this, but last night I applied a Windows update. It was likely a cumulative update for Windows 10 version 22H2 (KB5033372). Everything proceeded normally until after the restart. The ASUS TUF splash appeared, along with a small loading indicator, then it froze for roughly 10 to 15 seconds. After that, it launched into the Windows login screen but ran extremely slowly. Then it triggered a BSOD and displayed an error stating "kernel security check failed." It restarted once more, this time without the blue screen, though the system became very sluggish—slow, choppy, and stuttering. The cursor skipped, moved sluggishly despite a high DPI setting, and there were noticeable screen distortions on the desktop (resembling a cracked LCD).
Given that I recently upgraded my motherboard from a B450 to an ASUS TUF B550 and hadn’t performed a clean OS install before, I suspected a driver conflict from the new hardware. I also recall updating my BIOS about a week prior, which seemed to resolve the problem temporarily. Before any of this, games ran smoothly, booting from sleep, restarting, and everything worked well.
After reinstalling Windows, I applied all available updates and drivers. The process was smooth until I woke the PC back on sleep later that day. It displayed a black screen with no video output, then rebooted itself. This time it was also black, and the signal returned slowly. Eventually, the TUF splash appeared again, but the loading circle stalled and hung. My frustration grew—this was happening too often!
I ran sfc /scannow, which repaired some files, but the problem lingered after another reboot. I then applied a .NET framework update via Windows Update. After rebooting, the system felt normal and stable. I performed stress tests with 3D Mark Timespy DX12 (99.2% frame stability) and Speedway (also stable). Even after a full reboot, no crashes or BSODs occurred.
However, when I tried to restart again, the same issues resurfaced—slow splash, laggy performance, and screen artifacts returned. It became clear this was a recurring problem. In Event Viewer, I logged numerous "Metadata staging failed" errors around these incidents. While not always present, they seemed significant.
This behavior is unusual. Every now and then my system acts strangely after a reboot. Could the BIOS update be the cause? It worked well until that point. I’m seeking advice—anyone know what might be going on? This is really puzzling!
No other devices are connected besides my mouse and keyboard. My kb has a USB passthrough, and I'm using a 2.4GHz wireless dongle for the mouse with my phone, plus a power USB cable for the speakers. I even took it out of the VR headset before updating Windows. I'm also running memtest86 to check for RAM problems. It's about halfway through pass #2 and hasn't found any errors yet. This is really confusing me.
Set the mouse and keyboard to their default positions, unplug the speakers while keeping them connected, remember that MemTest isn't the complete solution for RAM issues. Your issue seems more related to a file system problem rather than RAM. It might be useful to install Windows on another drive for testing, regardless of speed, just to check stability.
Thank you for your feedback. It seems the issue persists even after reinstalling Windows. If you prefer not to proceed with diagnostics, kindly inform us in advance.
You're asking about how a seemingly minor USB dongle could lead to unexpected problems. It's definitely puzzling, but there are several factors that might be at play here. The dongle itself could be outdated or incompatible with the current system settings, causing conflicts. Alternatively, it might be interfering with background processes or drivers that weren't previously an issue. Sometimes, even small hardware changes can affect software behavior in subtle ways. It's worth checking the device's specifications, updating its drivers, or testing it on a different machine to see if the problem persists.
All devices need to start up at least once, even USB ones. If one device keeps failing to initialize, it can cause the whole system to slow down or stop working properly. Those who skip checking often blame something missing before a failure. Most bulbs you’ve replaced before were fine until they stopped working suddenly. The key is to troubleshoot and fix the problem instead of trying to figure out why it broke.
Lightbulbs and USB dongles are entirely different items... But once the memtest is done (only one and a half passes remain, so I’ll let it run through), I’ll give your idea a shot. What might happen at this stage? I’m pretty sure nothing will go wrong—probably just no change at all.