Prepare a Windows 11 crash dump that support can actually analyze

An intermittent blue-screen report becomes easier to investigate when Windows saves a usable memory dump, stop code and time. A dump can be absent if storage is full, the page file is unsuitable or settings were changed by a so-called optimizer. Microsoft's guidance describes automatic, kernel and complete dump options and their disk requirements. Prepare collection before the next crash, then share only with a trusted support channel because dumps can contain sensitive fragments of memory.

Before you start​

Back up important data and record the stop code, recent driver or update changes and exact crash time. Check system-drive free space and whether the page file is system managed. Decide who will receive the evidence; a public upload of a memory dump may reveal document text, secrets or browsing data. If hardware is unstable, do not deliberately induce a crash.

Do it step by step​

1. Open Advanced system settings > Startup and Recovery > Settings. Record the current Write debugging information selection and dump file path.
2. Choose Automatic memory dump as a practical default unless a qualified support engineer requests another type. Verify the system-managed page file and adequate free space.
3. After a natural repeat crash, note the stop code and restart time. Do not repeatedly force power cycles merely to generate data.
4. Check whether Windows wrote a dump at the configured path and whether its timestamp matches the incident. Look at Event Viewer for related system errors without assuming the first red event is the cause.
5. Keep the dump securely. Send it only to the PC maker, Microsoft or a trusted professional through their approved private channel, along with model, build, stop code and repro steps.
6. Apply one supported driver or firmware change at a time and watch whether the crash recurs. Retain the original dump until the root cause and stable fix are established.

Check the result​

A matching dump exists after a naturally occurring crash and support has enough context to analyze it without exposing it publicly.

If something goes wrong​

If no dump appears, inspect page-file configuration, free space and write path. If the PC loses power abruptly, Windows may be unable to write a dump; investigate hardware and power separately. Do not change obscure CrashControl registry values on a hunch.

Know the limit​

A memory dump is diagnostic evidence, not a repair. It can contain private data and may still be inconclusive without symbols, hardware history and a repeatable symptom. Microsoft crash dump guidance Page-file sizing

Decision checkpoint​

Gather a crash timeline before blaming the last installed update. Check whether the stop code repeats and whether the same driver or peripheral was present each time. Hardware diagnostics matter when crashes also occur outside a specific application. Avoid running a crash-inducing test on a system with unsaved work or suspected storage failure. A protected dump and an accurate timeline give support a far better starting point than an image of the blue screen alone.

Aftercare​

Once support has analyzed the dump, remove copies from temporary or shared locations. Keep a private case number and the tested fix, then monitor for recurrence under the original workload.