Your computer is acting strangely and it's hard to figure out what to do.
Your computer is acting strangely and it's hard to figure out what to do.
The only thought I had about going further was halted because the needed symbols are private. Symbols act like a dictionary that helps the debugger view dump files. Public symbols come from Microsoft's server, while private ones stay hidden and not shared. Each driver requires its own symbols for the commands it uses so the debugger can be readable.
This indicates everything is back to normal, but the system keeps failing. Western Digital confirms the disks are okay and CHKDSK shows no issues. I can reproduce the crashes consistently. A full Windows reinstall might help, but I prefer to stay away since all my necessary programs are present and would need reinstalling again.
Consider a fresh start by booting cleanly (make sure to hide MS services before disabling everything). Then run Forza. If it runs without issues, repeat the clean boot but maintain 2-3 services active. Increase the number of enabled services gradually until you identify the problem. If needed, capture a screenshot of the SMART data (use CrystalDiskInfo if the WD tool isn't showing it). With CDI, you can also supply these details for all drives. The relevant entries are:
The C: drive employs the latest SMART technology for SSDs, but it seems ineffective in practice. I've observed numerous faulty units using these features without any SMART failure indicators. The D: drive records five command timeouts, which could indicate a problem, though only five were logged so far—possibly unrelated to your concern. The E: drive appears normal, as does the G: drive. The H: drive also has command timeouts; its format splits timings into three 4-byte segments, each representing a distinct duration. Manufacturers often use varying units, making it hard to pinpoint Seagate's specifics. A potential match exists with I: and H:—three drives with command timeouts and no other significant issues. This might suggest external causes unless crashes occur from storage, in which case it points to a specific drive. Generally, such errors are minor and often dismissed if storage performance isn't affected.
The culprit might have been eliminated by removing all SSDs and reinstalling 3DMark on my NVMe drive. It now runs smoothly. If installing Forza on the NVMe works without problems, the issue likely lies with the SSD I use for gaming, which is the E: drive.
The drive is functioning without issues, which occurs in roughly 20% of failed cases (based on Backblaze data). You might want to test another SATA cable. It lacks a CRC error indicator, which typically signals transfer problems—often due to the cable itself. The H and I drives can be reconnected, since they’re external and errors are more frequent there.
It might be an electrical problem, not related to the NAND chip.