My MSI Vector 16 HX A14VHG has become increasingly unstable. It has an Intel Core i9-14900HX, RTX 4080 Laptop GPU, 32 GB of RAM, and a 1 TB Samsung NVMe SSD running Windows 11 Home 25H2. I have experienced game crashes, occasional overheating shutdowns, Windows servicing problems, and several different blue screens, including PAGE_FAULT_IN_NONPAGED_AREA, SYSTEM_SERVICE_EXCEPTION involving Ntfs.sys, and EXCEPTION_ON_INVALID_STACK. Some dumps also referenced FLTMGR.sys and fileinfo.sys.
I performed a clean Windows installation using official installation media and reinstalled VALORANT and Vanguard, but VALORANT still frequently crashes with "A critical error has occurred and the process must be terminated," sometimes before the lobby loads.
CHKDSK found no filesystem errors or bad sectors, offline SFC reported no integrity violations, Windows Memory Diagnostic completed two passes without errors, and the SSD reports a healthy status with no wear. The Intel RST/VMD driver is installed, and I have not found any obvious third-party filesystem filter drivers.
DISM is concerning: CheckHealth says the component store is repairable, while RestoreHealth and ScanHealth repeatedly fail with error 1726/0x800706BE, and one RestoreHealth attempt caused a blue screen. I also found one older Disk Event ID 11 controller error for Harddisk1, although the current internal SSD appears as Harddisk0.
I would like to narrow down whether this is unstable RAM, an NVMe or storage-controller problem, CPU or motherboard instability, overheating, firmware, or a driver/Windows servicing issue. What should I test next, and which logs or dump files would be most useful?
4 Answers
DISM error 1726 is worth investigating, but it may be a symptom rather than the root cause if the system is crashing during repair. Check the DISM and CBS logs, Event Viewer around each failure, WHEA hardware-corrected errors, and storage/controller events. Before changing VMD or disk-mode settings, make a verified backup because switching storage configuration can make Windows unbootable or affect access to the existing installation.
The next useful step is to collect the actual crash dumps rather than relying only on the bug-check names. Copy the files from C:\Windows\Minidump, zip them, and analyze several dumps together. If no files are being created, configure Windows to use Small memory dumps and verify that the page file is enabled on the system drive. Different stop codes can all result from one underlying hardware or memory-corruption problem, so the stack traces and loaded drivers matter much more than the labels alone.
The clean installation makes ordinary Windows file corruption less likely, especially since the crashes continued afterward. I would test the machine at stock settings with a longer, more thorough memory test than Windows Memory Diagnostic, then stress the CPU, GPU, and SSD separately while monitoring temperatures and clocks. If a component-specific test produces errors or a crash, that gives you a much stronger lead than VALORANT alone.
Update the laptop BIOS, chipset and Intel VMD/RST packages, GPU drivers, and the Samsung SSD firmware using the laptop and component manufacturers' official tools. Also load BIOS defaults temporarily and remove any CPU, GPU, RAM, undervolting, or overclocking settings. Firmware and platform-driver problems can affect storage, Vanguard, and Windows servicing at the same time.
Related Questions
Lenovo Thinkpad Stuck In Update Loop Install FilterDriverU2_Reload