The issue stems from conflicts in System32 files during reinstalls.
The issue stems from conflicts in System32 files during reinstalls.
2023-11-20 - UPDATE: The SSD was failing. After replacement, everything seems fine. Recent Windows installs have repeatedly failed due to System32 errors, requiring weekly reinstalls. My one-week-old setup completely stripped internet features, forcing a full reinstall now. This process is becoming increasingly difficult to complete successfully. Photos show several failed installation attempts and the corresponding Windows update logs. The last two images reflect my current setup. Interestingly, Mabinogi continues to function without the problematic DirectX component. All diagnostic scans passed—chkdsk, DISM, and sfc—but repairs remain unsuccessful across attempts. I ran the built-in memory tester on Windows 10 a few weeks back and it reported good results. My SSD’s health is at 94% in CrystalDiskInfo, down slightly by 1% over the past two weeks. Is this a standalone SSD issue or could there be other factors at play? Any advice would be greatly appreciated.
BUILD: Windows 10 Home BIOS: F1
(Notified prebuilders about a potential BIOS update; awaiting their response.)
GPU: MSI GeForce GTX 1660 SUPER GAMING X w/ TWIN FROZR 7
CPU: Intel i5-10400F
RAM: Team T-FORCE VULCAN Z 16GB 3000mhz DDR4 (2 x 8GB)
Motherboard: Gigabyte B460M DS3H AC-Y1
SSD: Team Group GX2 2.5" 512GB SATA III (T253X2512G)
PSU: Raidmax RX 500XT
CPU Cooler: Thermaltake UX100 5V ARGB
Case: Rosewill SPECTRA C100
Case Fans: Rosewill RFA-BL1201 120mm Silent Dual Ring of Blue LED PWM
Fans: Rosewill RFA-BL1201 120mm
My PC in parts: https://pcpartpicker.com/user/Frikinhel/saved/LgbsLk
Display crystaldiskinfo (smart values) on the SSD. Consider running Intel's CPU diagnostic, though defective CPUs are less common than SSDs/memory.
Check the SATA cable or controller on the motherboard. Switch to another port and cable, if this doesn't resolve the issue, it might be the drive itself.
I'll get a fresh USB installation by cleaning the drive beforehand and then testing it again. I'll also try swapping the SATA cable to another port to see if that resolves the issue. Looking forward to your update!