My system has 32GB of RAM, yet it fails when it reaches 16GB.
My system has 32GB of RAM, yet it fails when it reaches 16GB.
I configured 16 GB of my 32 GB RAM into VRAM since I didn’t have a GPU running. Recently, adding just 2 GB caused frequent BSODs during extended gaming sessions. After removing the CMOS battery to undo any overclocking, the issue persists—especially when playing for more than ten minutes. I attempted driver updates and reinstalls, but it’s still not working. No overheating detected yet, so next steps are unclear.
Specs: CPU – Ryzen 5 5700G overclocked to 4650MHz/4.6GHz; water cooling max 75°C at idle, 30°C under load. Motherboard – B550-f gaming. RAM – Vengeance RGB PRO 32GB 8x4. Storage – Seagate BarraCuda 2TB and Crucial P3 500GB M.2 PCIe. Power supply – generic 700W unit. GPU – MSI Radeon RX 6800 GAMING Z TRIO, not overclocked.
You used all four PCIe lanes over two months before the GPU failed, and now you're wondering how to maintain those channels without running into crashes.
The issue isn't about having four RAM sticks but a potential CPU RAM controller problem. You can't easily fix it, so using two 16GB sticks to reach 32GB might help. Since you've already managed four sticks without issues, it's less likely the cause is here. Check the BSOD message and review the Windows Event Viewer logs under System for any critical errors.
The computer restarted after a bugcheck identified issue 0x00000050. A dump was created at C:\WINDOWS\Minidump\102423-16390-01.dmp. This failure happened without a full shutdown. Possible causes include the system failing to respond, crashing, or losing power suddenly.
This signifies invalid memory usage, often due to incorrect address or freed space. It might not be a power supply issue; Microsoft states it reflects a failed write operation. After testing with another PSU, the issue persists. Possible solutions include:
1a. System instability from software – Run CMD as admin, execute DISM /Online /Cleanup-Image /RestoreHealth, then SFC /Scannow. The first option checks for image corruption; the second verifies system files. If successful, the problem is less likely hardware-related.
2b. Inspect Event Viewer for driver warnings before BSOD.
3. Examine storage devices, especially the system and game drives. Right-click the drive, select Properties, then Tools to check health.
4. RAM concerns – Ryzen may struggle with multiple XMP sticks. Remove two and test stability. If stable, run Windows Memory Diagnostic. If not, consider replacing the RAM or upgrading to 2x16GB instead of four 8GB modules.
5. Disable IGPU and restart to see if it resolves the fault.