Ram (maybe) died after installing WSL #13708
Unanswered
nikolaylyudmilov
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Sorry, my English is not my primary language. I did a summary and I can provide more context if needed.
Can someone help?
Specs:
Motherboard: ASUS ROG Strix X470-F Gaming (latest BIOS)
Symptoms:
PC boots fine, runs BIOS indefinitely with no issues.
Once Windows loads, after ~40–60 seconds the monitor goes black, fans keep spinning.
DRAM Q-LED starts blinking yellow.
No full shutdown or reboot – just black screen and frozen state.
Temperatures normal (CPU/GPU fine).
What happened before the issue:
Installed WSL, Docker, Ubuntu, and Kali Linux.
Enabled SVM Mode (virtualization) in BIOS → Advanced > CPU Configuration.
After that, Windows started crashing.
Disabled SVM and stopped all WSL instances, but issue persisted.
Troubleshooting done so far:
Disabled SVM Mode and IOMMU in BIOS.
Verified temps, PSU, GPU – all normal.
BIOS stable for hours.
Windows still crashes after boot with blinking DRAM LED.
Task Manager still shows “Virtualization: On” even with SVM disabled.
Suspected cause:
Windows still running Hyper-V / WSL virtualization layer even though BIOS virtualization is off → causes memory mapping conflict that triggers DRAM LED / system freeze.
Fix steps (so far):
Disable all Hyper-V/WSL features in Windows Features:
Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, Windows Subsystem for Linux, Containers.
Run this in admin CMD:
bcdedit /set hypervisorlaunchtype off
Optional cleanup:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All /NoRestart
dism.exe /Online /Disable-Feature:VirtualMachinePlatform /NoRestart
dism.exe /Online /Disable-Feature:HypervisorPlatform /NoRestart
dism.exe /Online /Disable-Feature:Microsoft-Windows-Subsystem-Linux /NoRestart
Disable services:
sc config vmms start= disabled
sc config vmcompute start= disabled
sc config LxssManager start= disabled
Reboot → verify in Task Manager → Virtualization: Disabled.
Reference (manual link):
ROG Strix X470-F Gaming User Manual – Q-LEDs
Q-LED meanings:
DRAM (yellow) – memory detection error / instability
CPU (red) – CPU not detected / power issue
VGA (white) – GPU not detected
BOOT (green) – boot device not found
Goal:
Confirm whether virtualization layers in Windows can trigger DRAM LED blinking / black screen on the X470-F, and whether anyone else has seen similar behavior after enabling WSL or Hyper-V.
Beta Was this translation helpful? Give feedback.
All reactions