System restarted after a single failure (code 0xc0000225). It is now functioning properly.
System restarted after a single failure (code 0xc0000225). It is now functioning properly.
Yesterday (June 24) at around 9pm, something went wrong. Here’s what happened the day before: June 23 I visited my friend’s place. We used Clonezilla to copy my main SSD (500GB) onto a smaller 1TB Samsung drive so I could use it as my primary storage. After formatting the 500GB drive, I deleted the system recovery partition to free up space for the larger SSD. On June 24, after playing some League and other games, I came home around 1pm. My PC started up, I played more games, downloaded files, watched Netflix, and stayed active on Discord and voice calls. Around 9:40pm I tried launching League again, but it refused to start. I couldn’t delete the game, but everything else worked fine. I restarted the PC multiple times without any issues. The system logs show repeated warnings in the Applications section about service failures. There were also errors with Windows services like WMI, MSDTC, ESENT, and others. Overall, everything seems to be functioning properly now. This is quite strange—what’s happening? My 2022 TUF A15 6800H with 3060 performance is running on a new Samsung 970 EVO Plus drive. I attached a screenshot of the logs for reference.
It's essentially a BCD problem that might have resolved itself on its own. When you switched your system from one drive to another, the boot drive changed and the error appeared. If warnings keep showing up, open Command Prompt as Administrator and execute sfc /scannow—it’s a straightforward way to fix the boot issue and any damaged files. If it doesn’t work, you can try running BCD commands. The official Microsoft site has detailed instructions for these commands. You probably don’t need to dig too deep unless the problem persists.