Most challenging experience with computer assistive technologies I've encountered
Most challenging experience with computer assistive technologies I've encountered
You're facing a challenging situation with persistent BSODs that seem to be memory-related but don't respond to standard fixes. After exploring various solutions—ranging from hardware tweaks like underclocking and memory swapping, to software tools such as MemTest64 and MalwareBytes—you've already tried replacing components and even upgraded your power supply. The problem persists despite these efforts. It appears the issue may be tied to a failing SSD or other critical hardware. Since you're still stuck, consider consulting specialized repair services or advanced diagnostics that focus on memory and storage health.
This machine is likely plugged directly into a wall outlet or running on a UPS unit. Are there other devices in your home? It seems like you're dealing with two separate systems facing the same problem. Based on the analysis, an external influence—such as power grid fluctuations, nearby electronics, or electromagnetic interference—might be the cause. The simplest solution would be to move the PC to another location and see if the issue persists.
Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and transfer the Minidump folder to the Downloads folder (use your desktop if needed). Compress the copied folder and include it in a post. Please adhere strictly to instructions since Windows doesn't allow file changes there.
Thanks for your response. This suggestion seems reasonable, though it doesn’t address the core problem. I’ve encountered similar issues in both my apartment and my parents’ place, suggesting it’s likely not related to dirty wall power. My roommate’s computer is functioning properly, and I don’t rely on a UPS but use a surge protector instead. I’ll share all the details about the two machines, including my peripherals: Razor Huntsman, G703, Dell S2718D, LG 27GL850. My specs are R9 7900X3D, 32GB TridentZ 3600Mhz, CL16 RTX 3080ti, FE ASUS Prime X670E-Pro with Wi-Fi, and a 3TB Seagate Barracuda storage. New specs: R9 7900X3D, 32GB TridentZ 6400Mhz, CL32, RTX 3080ti, FE ASUS Prime x670E-Pro with Wi-Fi, plus a 2TB Samsung 990 Pro and a 3TB Seagate Barracuda. I’ve removed the GPU and ran it with integrated graphics, which produced the same crashes.
Thank you for your response. The files are included in the attachment. Minidump.zip
In about four cases it seems like storage is the issue. The last one activates when the command "nt!SwapContext+0x4b1" runs, and the swap file refers to a different page file name. I'm not a programmer so I'm unsure if I'm just searching for storage without evidence here. EDIT: In the other three instances the filter manager driver was involved. Its role is to manage files correctly, which often leads to storage problems. Ntfs.sys appeared, which makes sense why it raises suspicion about storage. Storage and RAM can look similar due to the page file, so mixing them up is common. We can run self diagnostics on the drive, but with modern SSDs (mostly NVMe) SMART data is not useful. The page file is usually on C:, and since this resembles RAM in some ways, the drive with the page file is likely the culprit. We can inspect which drive it's actually using by opening Disk Management, looking at partition sizes, and checking the bottom where drives appear. Under "Page file" you may find multiple entries—verify all of them. To obtain SMART data for review, follow this guide and visit the link provided. The copy feature automatically collects information from all connected drives without needing repeated actions.
Consider taking out the SSD and replacing it with a different drive for testing purposes. It’s important to ensure everything is clean before installing Windows on another system. Faulty drives can lead to unexpected problems even after simple connections.
I plan to remove every HDD and check if problems persist. The same error keeps occurring with the Corsair MP510, and the HDDs remain untouched so far. I’ll share an update when another crash happens. Thanks for all your support!