Why does XMRig crash my system or blue screen Windows?

XMRig can expose an unstable setting, overheating, or a driver problem because it keeps your processor and memory working hard. If Windows shows a blue screen or your whole computer restarts, that is different from XMRig simply closing: a full-system crash usually points to a problem below the mining program itself.

First, identify what actually crashes

Before changing settings, note what you see:

• XMRig closes, but Windows keeps working: look for an error in XMRig’s console output or log. A configuration problem, missing memory, or a security-software block may be involved.
• Windows shows a blue screen: photograph the stop code and any named driver. Codes such as WHEA_UNCORRECTABLE_ERROR can suggest hardware instability, but they do not identify one failed part.
• Your computer freezes or restarts without a blue screen: heat, unstable hardware settings, or power delivery deserve attention.

Windows Reliability Monitor gives you a timeline of crashes. Event Viewer contains more details, but a “Kernel-Power” event only says Windows shut down unexpectedly—not why.

Check processor and memory stability

Monero uses RandomX, a mining method that puts substantial load on your processor, or CPU, and memory. Settings that seem fine during browsing or gaming may fail under this workload.

Start by returning your hardware to its standard settings:

• Remove CPU overclocks, which run the processor faster than its standard settings.
• Remove undervolts, which reduce its operating voltage.
• Temporarily disable XMP or EXPO, optional profiles that run memory faster than its basic settings.

Change one thing at a time and keep notes. Do not raise voltages blindly to make mining stable.

RandomX’s fast mode uses a dataset of about 2,080 MB, plus other working memory. Each mining thread—a separate stream of work—also benefits from about 2 MB of L3 cache, the processor’s built-in fast memory. Too many threads usually hurts performance rather than causing a blue screen, but reducing the thread count is a useful load test.

Look for heat and power problems

Watch CPU temperature with a reputable monitoring tool. Compare it with your processor manufacturer’s limits rather than relying on one universal “safe” temperature.

Check that fans work and vents are clear. On a laptop, use a hard, open surface rather than bedding. Stop mining if the machine overheats, smells unusual, or repeatedly shuts itself off.

Try fewer mining threads. If crashes stop, that suggests the problem depends on workload, but it does not prove overheating. An unstable undervolt or a weak power supply can behave similarly.

Isolate XMRig’s privileged features

Use an official XMRig release, not a repackaged download. Mining software is often flagged by security tools, but that does not make every warning harmless.

XMRig can use MSR tuning, changes to special processor registers that may improve RandomX performance. On Windows, this can involve a low-level driver. If crashes coincide with that feature:

• Disable MSR tuning and test again.
• Run without administrator privileges as a comparison.
• Update Windows and obtain chipset drivers from your hardware maker.

Huge pages, larger blocks of memory used for better performance, are a separate feature. Failure to enable them normally means lower speed, not a blue screen. Do not disable Windows security protections just to force mining optimizations to work.

The bottom line

Stop repeated crash testing with important files open. Start with standard hardware settings, fewer threads, temperature checks, and MSR tuning disabled. If Windows still crashes—especially outside mining—use memory diagnostics and seek hardware or driver troubleshooting before mining again.