The system shuts down upon changing the FLCK setting to 1800MHx
The system shuts down upon changing the FLCK setting to 1800MHx
Hello. Recently I assembled my initial PC. Upon first startup, I noticed one RAM module wasn't seated correctly. I powered down the system and removed the case panel. When I extracted the RAM, a brief spark was observed between the two memory units. Concerned about potential damage, I reinserted the stick and restarted the computer. It successfully booted into BIOS. I adjusted the memory clock speed to 3600MHz without changing the FLCK setting (it was likely set to auto) and proceeded to install Windows. The following day, I updated the BIOS and configured my DOCP profile to match the new speed. With DOCP enabled, my PC would launch Windows and then reboot smoothly after a short delay. I experimented further and discovered that I could fine-tune the RAM speed to 3600MHz with FLCK at 1600MHz. I also learned that I could adjust the memory frequency to 3466MHz and the FCLK to 1733MHz. I sought advice on Reddit, where someone who had previously helped me set up similar configurations shared that the spark might have caused damage to the chip's memory controller. Now I'm anxious, wondering if my initial PC could have been harmed. My system specifications are as follows:
- **CPU**: AMD Ryzen 7 3700X, 3.6 GHz, 8-core
- **Motherboard**: Asus TUF GAMING B550M-PLUS (Wi-Fi), Micro ATX AM4
- **Memory**: G.Skill Trident Z RGB, 16 GB (2 x 8 GB), DDR4-3600 CL18
- **Storage**: Samsung 970 Evo Plus, 500 GB M.2-2280 NVMe SSD
- **Video Card**: Asus GeForce RTX 2080 SUPER, 8 GB dual EVO OC
- **Case**: Asus TUF Gaming GT301 ATX Mid Tower
- **Power Supply**: Asus ROG Strix 750W, 80+ Gold certified, fully modular
I’m relieved my RAM is functioning at 3466MHz, but the worry remains about potential damage from that spark.
When the PC operates smoothly at 3466MHz, memory controller issues are unlikely. The problem might stem from a subpar RAM module rather than a performance bottleneck. A crash or freeze at any speed would indicate a different issue. You can run memcheck to detect problems—available in Windows 10 and built into the OS.
I previously executed membench86 several times. The most recent run used a memory frequency of 3466MHz and showed no issues. I’ll also test memcheck just in case. That’s helpful if the problem remains minor. It didn’t reappear, which is good and my system is running smoothly. I’ll keep you updated if anything arises. Thank you.
Hello! Your concern is valid. The spark from the PC's power supply might affect the DIMM slots you're not using, especially if they're exposed or damaged. It's wise to avoid testing them until you're sure. If you decide to upgrade, ensure proper installation to prevent any issues.