I spent the last couple of years saving for my first custom PC, finally bought the parts, and built it myself using assembly guides and the instructions that came with the components. The build went smoothly and I was able to install Windows, but ever since turning it on I've had nonstop problems: crashes, poor audio, corrupted game files, and blurry textures. I've reseated the graphics card, memory, and M.2 drive several times, tried different power cables, and even attempted to reset Windows, but the reset failed because recovery files were missing. I'm new to building PCs and realize I may have made a mistake somewhere, but I'm not sure how to diagnose this. What should I check first, and is this more likely to be Windows, drivers, the storage drive, or the RAM?
4 Answers
Corrupted files and crashes on a fresh build usually point to the storage drive, memory, Windows installation, or drivers rather than meaning the entire PC is ruined. Start by checking Event Viewer under Windows Logs, especially the System and Application sections, and look for repeated critical or error entries around the crashes. It would also help to post the complete parts list, Windows version, and which drivers and BIOS version you’re using.
The memory appears to be Corsair Vengeance, so make sure the kit is running at default settings while troubleshooting. Disable XMP or EXPO temporarily, then test stability before enabling the advertised memory profile again. If the crashes continue even with default settings, run a proper memory test and inspect the drive for errors.
I’d do a clean Windows installation before chasing too many individual issues. If that doesn’t solve it, update the motherboard BIOS and install fresh chipset and graphics drivers. Test the RAM sticks individually with XMP or EXPO disabled, and check the M.2 drive’s health. Since the reset is reporting missing recovery files, the current Windows installation may simply be corrupted.
Don’t give up on the whole system yet. Try running the PC with one memory stick at a time and verify that the M.2 drive is firmly installed and detected correctly. Also confirm whether the drive is new or reused, because a failing or previously problematic drive could explain the corrupted game files and failed Windows reset.
The M.2 drive was added to my parts list afterward because I forgot to include it originally. I’ll check the drive details and health as well as testing the memory individually.