I spent the last couple of years saving for my first custom-built PC and finally assembled it myself using build guides and the instructions included with the parts. The build went smoothly, and I was able to install Windows, but after that nearly everything started going wrong. It crashes frequently, the audio quality is poor, game files become corrupted, and some textures appear blurry. I've reseated the graphics card, RAM, 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. This is my first build, so I'm willing to believe I made a mistake somewhere, but I'm having trouble figuring out whether the problem is Windows, drivers, the storage drive, memory, or another component. I'm using Corsair Vengeance memory and an M.2 SSD. What should I test first?
4 Answers
Corrupted files and crashes on a brand-new installation make the SSD or RAM worth investigating before assuming the whole build is bad. Try running with one memory stick at a time, and temporarily disable XMP or EXPO in the BIOS. Check the M.2 drive’s health and run a memory test. If the drive was reused rather than purchased new, I’d be especially suspicious of it.
Start by checking Windows Event Viewer under Windows Logs > System and Application. Look for critical errors around the times of the crashes. Also check Task Manager while the system is running to see whether a drive, memory, or CPU is behaving strangely. A clean graphics-driver installation, updated motherboard BIOS, and current chipset and storage drivers would also be good steps. More complete hardware and operating-system details would make troubleshooting much more specific.
A clean Windows reinstall may be the fastest way to rule out corrupted system files, especially since the built-in reset is already complaining about missing recovery files. Create a fresh installation USB on another computer and install Windows from scratch, then install the motherboard chipset, network, audio, and graphics drivers from the manufacturers’ websites. Update the BIOS afterward if the board has a newer stable version.
This isn’t a normal first-build experience, but it also doesn’t mean the entire PC is ruined. Before replacing parts, test the basics methodically: verify every power connection, test each RAM module individually, check the SSD, run a memory diagnostic, and monitor temperatures. A Linux live USB can also help distinguish a Windows or driver problem from a hardware fault, since a stable session there would point more strongly toward the Windows installation.
The M.2 drive was added to my parts list afterward because I forgot to include it originally, but I’ll check its health and test the memory separately.