Event ID 41 (Kernel-Power) only tells that Windows detected an unexpected/dirty shutdown. In this scenario, the DRAM LED on the motherboard and the fact that the issue changes when RAM configuration changes strongly point to a hardware problem, most likely memory, memory configuration, or power/board-related.

Use Event ID 41 only as a symptom and focus on hardware isolation as in Scenario 3 from the documentation:

1. Treat this as a hardware stability issue (Scenario 3)
   • Event ID 41 with gaming load, black screen, and DRAM LED, and no clear bugcheck code typically indicates a hardware problem rather than a Windows/software issue.
   • According to Scenario 3, when Event ID 41 appears without useful bugcheck data, the common causes are power, memory, overheating, or platform/firmware issues.
2. Disable any overclocking or aggressive profiles
   • In BIOS/UEFI, reset everything to defaults (no CPU overclock, no RAM overclock/XMP/EXPO, no GPU overclock).
   • Ensure the system is running at JEDEC/default RAM speed and voltage.
   • The documentation explicitly recommends disabling overclocking and verifying if the problem reproduces at correct speeds.
3. Systematic memory checks
   • Because the DRAM LED lights and the system behavior changed when using a single stick, memory is a prime suspect.
   • Follow the guidance to “check the memory”:
     • Test each RAM stick individually in the same slot under gaming load.
     • Then test the same stick in each memory slot to see if a particular slot is faulty.
     • Use a memory checker (for example, bootable memory test) to stress the RAM.
   • Verify all memory modules are running at the same speed and correctly configured.
4. Check the power supply and power path
   • Scenario 3 highlights that an underpowered or faulty PSU can cause random restarts without a proper bugcheck.
   • Even with an 850 W PSU, there could be:
     • A defective unit
     • Bad PCIe power cable or loose connection
   • Reseat all power connectors (24‑pin ATX, 8‑pin CPU, GPU PCIe cables) and, if possible, test with a known-good PSU.
5. Check for overheating and platform stability
   • Scenario 3 also recommends checking for overheating:
     • Confirm CPU and GPU temperatures under load are within safe limits.
     • Ensure all fans are working and the case has adequate airflow.
   • Since the DRAM LED is involved, also inspect the motherboard physically for any visible damage around the DIMM slots (burn marks, bent pins, debris).
6. If running in a virtualized or clustered environment (not your case)
   • The documentation notes heartbeat-based restarts in Hyper‑V/VMware or clusters, but with a physical gaming PC this is not relevant; focus on physical hardware.
7. Use the event log only to correlate times
   • Event ID 41 confirms the time of the improper shutdown.
   • Also check for:
     • Event ID 6008 (unexpected shutdown)
     • Event ID 46 from volmgr (Crash dump initialization failed!) which would indicate dump configuration issues, not the root cause.

If, after disabling overclocks, thoroughly testing RAM (sticks and slots), verifying PSU and power connections, and confirming temperatures, the issue persists, the remaining likely culprits are the motherboard (memory controller/slots or power delivery) or the PSU. At that point, replacing or testing with known-good RAM and PSU, then the motherboard, is the standard next step to avoid “blind” replacement.

References:

• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"