My PC has had worsening stability problems for about a year. DRM-protected streaming services such as Netflix, Max, and Crunchyroll periodically become pixelated or corrupted before the page fails, while YouTube and Twitch generally work normally. More recently, Chrome tabs—or sometimes the entire browser—crash, and the same behavior occurs in Firefox. The computer also occasionally reboots by itself when left idle.
I used DDU and tried reinstalling the graphics drivers, but the installer produced a 7-Zip CRC error. I managed to get the driver installed by temporarily configuring Windows to use a single CPU core, then restoring the normal setting afterward. Windows Memory Diagnostic reported no problems. When I ran DISM RestoreHealth, the system reached 64.1% and then crashed with a BSOD.
The system uses a 14th-generation Intel processor. I have already updated the BIOS to a version containing the relevant microcode fix, although the processor may have operated for roughly nine months before that update. What diagnostics should I run to determine whether this is CPU degradation, a graphics issue, storage or Windows corruption, or another hardware fault?
3 Answers
The memory diagnostic result is useful, but it does not rule out every hardware problem. Run a longer bootable memory test, check storage health and system event logs, and test the system at default BIOS settings with any overclocking or undervolting disabled. Also try a clean graphics-driver installation using a freshly downloaded installer; a CRC error can indicate a damaged download, storage corruption, or instability during extraction rather than only a graphics-driver problem.
Because this is a 14th-generation Intel processor, CPU degradation is worth considering. Updating the BIOS prevents further exposure to the known voltage and microcode issue, but it cannot reverse damage that may already have occurred. The symptoms are not proof of a bad CPU, though—browser crashes, driver installation failures, spontaneous reboots, and a BSOD during DISM can also come from unstable RAM, the motherboard, storage, power delivery, or the graphics card. Dump analysis and testing with known-good components would be needed before replacing the processor.
The BSOD dump files are the best place to start. Check C:WindowsMinidump and look for several recent .dmp files. Copy them somewhere convenient, compress them, and inspect them with a debugger or have someone analyze the stop codes and modules involved. If no dumps are being created, configure Windows for small memory dumps and make sure the page file is enabled on the system drive. Multiple crashes are much more useful than a single dump because they can show whether the same driver or hardware component is repeatedly involved.
The processor may have been running for about nine months before I applied the BIOS update, so possible prior damage is my main concern. I will collect the dump files and continue with hardware testing rather than assuming the microcode update fixed everything.