Recent GPU leading to suspected memory issues
Recent GPU leading to suspected memory issues
I’ve upgraded my GPU and quickly noticed major issues: random file integrity failures in several installers—especially the nvidia drivers, browser crashes during media processing, and various BSODs involving network, graphics, and kernel components. I’ve also experienced intermittent crashes, particularly with Google Meet tabs. The system shows multiple errors across drivers, and despite running Pure Power 600 Memory with XMP enabled, the CPU remains stable. Adding an RTX 5060Ti helped temporarily, but glitches persist. Because my PSU is only 600W, I switched to an 850W unit, which resolved most problems and reduced crashes somewhat. I’ve tried clearing CMOS, updating BIOS, reinstalling Windblows 10, and disabling XMP, but nothing fully fixes it. I’m wondering if there’s a power delivery issue on my motherboard and would appreciate a second opinion.
DDR4-3600 is performing slightly better than expected on a 3600X. I’d test it at DDR4-3200 first to check stability. If that doesn’t work, go down to DDR4-3000. Stability in the lower speeds usually means it’s okay. If issues persist, consider installing an older driver manually from Nvidia’s website. If problems continue, the GPU might need replacement.
Ah, yes, the memory speed was DDR4-3200, which fits perfectly with the R5 3600X. It's been stable in this PC since January 2020. There were signs of trouble even before I updated the NVIDIA drivers. The first issue I saw was a "7-Zip: CRC error" popup during driver installation, occurring roughly half the time. Also, it doesn’t seem to be a GPU problem—running FurMark didn’t reveal any problems within about 20 minutes.
It seems like you're looking for guidance on handling memory controller issues with four sticks. The information suggests checking for existing minidump files and possibly moving them to a different location for easier access. Make sure to verify compatibility by reviewing system logs or documentation. If needed, follow the steps to organize your files properly.
Latest update notes: the most recent kernel panic occurred in Ntfs.sys. It seems unrelated to the actual issue, just a coincidence. Would be amusing if a bad SATA controller or faulty drive caused filesystem driver errors.
Checked CrystalDiskInfo – it shows overall health as good, but the specific drive reports many read errors.
I attempted to disconnect the system drive and reinstall Windows on another SSD. Right after startup I encountered a CRITICAL_PROCESS_DIED BSOD, followed by another shortly after logging in. I might try using a different SATA port, though it appears the problem is more serious.
How many passes did you perform with MemTest86? A brief run may miss subtle memory issues—unless they appear right away. MemTest86 is comprehensive if you stay consistent... Obtain a copy of AIDA64 (even the free or trial edition) and execute the Memory Stability test. Let it run for 30 minutes or an hour. Based on the results, it seems one of the memory drives might be malfunctioning.
It seems to be remnants from the dump files. Memory isn't always about RAM, but that's typically where it starts. Windows moves low-priority RAM data into the page file and retrieves it when needed, making storage appear like memory. The memory controller is built into the CPU, and if it fails, it can mimic memory behavior. In dumps, roughly half point to storage or storage drivers. Since two entries reference ntfs.sys, I can't entirely exclude it, but it's unlikely to be storage. If there are any overclocking or undervolting issues, remove them. To check RAM, run the machine normally with one stick at a time. If only one stick causes crashes, that stick is faulty. If it crashes with either stick, the CPU is likely the issue. Memory testers often miss defective RAM, especially DDR4 and newer types, so I'm not confident in their results.
In fact, I hadn't noticed it before, but I've faced problems with this device. I installed a second partition on the same SSD and used dual-boot Linux. A few months ago, the system began crashing. Not wanting to dig in, I let it sit on that portion of the drive. After a Windblows patch, the bootloader vanished from the boot menu and I completely overlooked the issue.