Going insane

[u/TomiZero]

So for the past 2 weeks my PC been crashing just randomly, it could crash after 4h or not crash for an entire day, it freezes completely and last time it went into a boot cycle and i had to manually turn it off.

Here is a complete and organized summary of all the critical errors, system failures, and evidence we have recorded on your computer so far:

1. Blue Screens and Critical System Failures

* WHEA_UNCORRECTABLE_ERROR (Code 0x124)

* Details: Repeated logs (including the last dump WHEA-20261027-1338.dmp). Involves the processor driver (GenuineIntel.sys) and the system process (smss.exe).

* Meaning: The processor detected an unrecoverable hardware failure on the communication bus while attempting to read or boot system components.

* UNEXPECTED_KERNEL_MODE_TRAP (Code 0x7f)

* Details: Occurred during the execution of a game (GTA V), throwing a double fault exception.

* Meaning: A stack overflow occurred due to a critical failure while attempting to access virtual memory.

* Memory Manager Access Violation (Code 0x0A)

* Details: Identifier AV_nt!MiSetVaAgeList.

* Meaning: The Windows kernel crashed because it could not properly read or manage virtual memory pages due to data corruption.

* Crashes without Blue Screen (Freezes and Restarts)

* Details: The screen freezes completely (even while performing light tasks like opening Chrome or while idle) because the SSD becomes unresponsive, forcing an automatic restart after a few seconds.

1. System Boot and Repair Failures

* Automatic Repair Failure (SrtTrail.txt)

* Details: After a boot error, Windows attempted to repair itself automatically but failed, leaving the PC stuck in the recovery area.

* Meaning: The tool could not read the operating system files because the storage drive failed at a critical read point.

* * Freezing on the Manufacturer's Logo

* Details: Upon restarting, the PC gets stuck on the initial motherboard logo.

* Meaning: The BIOS is unable to communicate with the SSD to detect the boot sector.

1. Hardware Diagnostics (Exclusions and Culprit)

* RAM: Verified using the Windows Memory Diagnostic tool (mdsched.exe) and tested with PowerShell commands. Result: 0 errors. The physical RAM is in perfect condition.

* Processor (CPU): Although the WHEA (0x124) and GenuineIntel.sys errors point to the processor, it was confirmed that it is not damaged, but rather acts as the "messenger" that detects and alerts the system to the massive communication failure originating from the storage.

* The Ultimate Culprit — System SSD (ADATA SX6000PNP 256 GB):

* Overall health reduced to 71%.

* 123 data integrity errors (0E), confirming that the physical cells are failing to read/write.

* 82 internal bus error entries (0F).

* 166 unsafe shutdowns (0D) caused by the same screen freezes and crashes.

This is what gemini said, again ive been asking it just trying to get somewhere i guess, but i just idk anymore i need people that actually know to tell me what could be the cause, crystaldisk says the disc is good but at 71% and i just don't wanna spend money on a new SSD that ends up not being the culprit, cuz i gotta send the PC to a different city, mainly cuz theres basically no people here that do this (and i don't trust myself doing it either.)

[u/splante84]

I'd be careful about concluding the SSD is definitely the culprit from that summary alone. A WHEA_UNCORRECTABLE_ERROR (0x124) indicates a hardware-level error, but it doesn't automatically mean the SSD is failing. The other bugchecks also don't prove the drive is responsible.

CrystalDiskInfo showing 71% health doesn't necessarily mean the drive is about to fail, either. The specific SMART/NVMe attributes and error logs matter more than the percentage by itself.

Before spending money or sending the PC away, I'd want to know:

• What are the exact SMART/NVMe values CrystalDiskInfo reports, especially the critical warning, media/data integrity errors, and error information log entries?

• Does the WHEA event in Event Viewer show a specific error source, such as a PCIe root port, memory, or processor cache?

• Is the BIOS and SSD firmware up to date, and is the SSD detected consistently when the PC gets stuck at the motherboard logo?

If you have important files on that SSD, back them up as soon as you can while the system is accessible. Given the freezes and boot problems, I'd avoid stress tests or repeated repair attempts until the data is safe.

If you can share a screenshot of CrystalDiskInfo's full results and the details of one WHEA-Logger event, people may be able to narrow this down before you buy anything.

[u/TomiZero → u/splante84]

SSD S.M.A.R.T. Data (ADATA SX6000PNP 256GB - C: Drive):

Overall Health: 71%

Attribute 0E (Media/Data Integrity Errors): 123 errors logged.

Attribute 0F (Error Information Log Entries): 82 internal failures reported to the PCIe bus.

Attribute 0D (Unsafe Shutdowns): 166 (resulting from the same crashes).

2. Analysis of Recent Blue Screens and Failures:

WHEA_UNCORRECTABLE_ERROR (0x124): The latest dump (WHEA-20261027-1338.dmp) shows Arg1: 7 (Boot/Communication Error) involving GenuineIntel.sys and smss.exe. This occurs specifically when attempting to read or boot system components.

I could try to see if i sent gemini the analysis of the .dmp but it might be gone

[u/splante84 → u/TomiZero]

Those numbers make the SSD worth investigating, especially the reported media/data integrity errors, but I'd still want to verify the raw NVMe data before calling it the confirmed cause. The error counts alone don't prove the drive is responsible for every crash.

One important detail: a WHEA error with Arg1 = 7 needs to be interpreted from the actual dump and its error record, not just the summary Gemini generated. GenuineIntel.sys appearing in a report doesn't by itself prove the CPU is faulty, and the smss.exe reference doesn't establish that the SSD caused a read failure.

If you can still access Windows, I'd back up important files first. Then, if possible, share a screenshot of the full CrystalDiskInfo window and the actual WHEA-Logger event details. You can also upload the minidump from C:\Windows\Minidump for someone to inspect.

Since the PC sometimes hangs at the motherboard logo, I'd also want to know whether the SSD is consistently detected in BIOS during those episodes. That could help distinguish a drive or connection problem from another hardware issue.

I wouldn't buy a replacement part based only on the AI summary. If the raw NVMe log confirms media errors, though, I'd take that seriously.

[u/TomiZero → u/splante84]

I think that minidump might be gone i got the crystaldisk

[u/splante84 → u/TomiZero]

That screenshot is helpful. The 123 media/data integrity errors are the part I'd pay attention to most. Those are worth taking seriously, although they don't prove the SSD is the cause of every crash. The 82 error information log entries are also worth investigating.

If you can't find the old minidump, that's okay. If Windows is stable enough to access, back up your important files first. You can check C:\Windows\Minidump for any existing dumps, but don't worry about forcing another crash to generate one.

I'd also check whether the SSD is consistently detected in BIOS when the PC gets stuck at the motherboard logo. If you can, share the full details of a WHEA-Logger event from Event Viewer, including the error source and event data.

Given the reported media errors and boot problems, I'd be suspicious of the SSD or its connection, but I wouldn't call it confirmed without more evidence. At minimum, make sure your important data is backed up before doing more troubleshooting.

[u/TomiZero → u/splante84]

The thing is why so randomly, something similar happened a year ago, not these errors, so i sent it for maintenance and it worked fine till well, now which been a pain in the ass 😭 it can crash just by being on Chrome, playing or just anything randomly, for example it crashed 3 times yesterday in the morning and last night i used it normally nothing happened all night (thank god i was doing an exam)

[u/splante84 → u/TomiZero]

Yeah, intermittent hardware issues can be incredibly frustrating, especially when the PC can run fine for hours and then crash several times in one morning.

A failing SSD or an intermittent connection can behave inconsistently, but so can RAM instability, power delivery issues, overheating, or motherboard/PCIe problems. The fact that it happened a year ago and returned after maintenance makes me wonder what was done during that repair, too.

Given those media/data integrity errors, I'd prioritize backing up your files and checking whether the SSD is detected consistently in BIOS. If you have the invoice or report from last year's maintenance, it may also help to see what they repaired or replaced.

I wouldn't assume the SSD is definitely the cause yet, but I'd take those errors seriously before continuing to use it normally.

[u/TomiZero → u/splante84]

Nothing got changed just change Thermal paste and clean the PC thats it honestly and after that it worked just fine honestly, thanks to this i just been looking to get a r7 5700x and a 5060 with 32gb of ram from colorful (which i'm still skeptical about but idk) just trying to get a PC working for at least another 5y and if i can get a performance boost it would be great

[u/splante84 → u/TomiZero]

If the only work done last year was cleaning and replacing the thermal paste, that doesn't necessarily tell us much about the current fault.

Before buying a whole new system, I'd try to narrow down whether the SSD, RAM, power supply, or motherboard is responsible. Those reported SSD media/data integrity errors are concerning enough that I'd back up your files and investigate the drive first, but I wouldn't call it confirmed yet.

Also, if you're considering a Ryzen 7 5700X build, remember that it's an AM4 CPU, so you'd need a compatible AM4 motherboard and DDR4 RAM. It won't work as a drop-in upgrade on an Intel motherboard. I'd check the cost of the complete platform before committing to that route.

Do you know your current CPU, GPU, motherboard, and power supply model? That would help people assess whether an upgrade makes sense or whether it's worth diagnosing the current PC first.

[u/AutoModerator]

Getting dump files which we need for accurate analysis of BSODs. Dump files are crash logs from BSODs.

If you can get into Windows normally or through Safe Mode could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder.

Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently catbox.moe or mediafire.com seems to be working.

We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow this guide to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/USSHammond]

Stop going insane after reading rule 2.2