TechClassy

BSOD · reviewed 2026-09-01

Windows memory dump evidence helper

A small memory dump can preserve bug-check parameters and a limited view of the crash state. It can support diagnosis but does not automatically prove a root cause.

High for dump location and evidence handlingNot determined by dump presence alone

The reviewed result loads below this input and changes only when you select a relevant context.

Runs in this browser — no upload, no account, nothing stored

Ctrl/⌘ + Enter

Real cases
Resume a saved session — paste a Resume Capsule

The capsule is validated and restored only in this browser. An invalid capsule changes nothing.

Crawlable evidence ledger

What this diagnostic record establishes

Confirmed

  • Windows can store small dump files under %SystemRoot%\Minidump when crash-dump settings and the page file permit it.

Not confirmed

  • The presence of a dump does not mean an online tool can safely or correctly identify the root cause.
  • A highlighted module is not automatically the component that initiated the crash.
Applicable versions
Windows 11 on a currently supported release; Windows 10 only where Microsoft or the device vendor still supports the installed edition
Review status
verified · 2026-09-01
Evidence still needed
Crash time; Dump timestamp; Stop Code; File size; Whether dumps are created repeatedly

Context changes the route

What evidence do you have now?

A minidump exists

Likely layer: Crash evidence

First safe check: Match the dump to the crash before sharing it

Expected: You will know whether the file belongs to the incident you are diagnosing.

No minidump appears

Likely layer: Crash-dump configuration or page-file boundary

First safe check: Check the current dump setting without changing it yet

Expected: You will identify whether the system is configured to create a small dump and where Windows expects to write it.

Before any second repair step

Verify the observation and preserve the evidence

After the first safe check, record whether the reviewed intermediate result occurred, whether the original problem was retested, and the exact output. An expected observation is not automatically a repair.

Outcome boundaries

  1. Observed as expected
  2. Observed something different
  3. Result unclear
  4. Could not complete the check

Then separately record whether the original problem still occurs, was not reproduced once, or has not been retested yet. Every session ends in stop, one repeat of the same check, one named missing fact, or escalation—never an open-ended repair sequence.

Evidence fields for this task

  • Exact crash timeLocal date and time from the most recent crash
  • Trigger or workloadStartup, sleep/wake, game, update, idle, or unknown
  • Recurrence patternOnce, count, frequency, and whether the Stop Code repeats
  • Minidump statusExists/missing and the time shown; do not upload it here

The browser-local Evidence Pack combines the selected context, safe action, actual observation, sources, review date, missing evidence, and stop boundary. It can be copied or printed without creating an account or uploading a log.

After you perform the safe check

Read the evidence you collected

Paste a bounded msinfo32 or DxDiag text report and extract the Windows build, system model, firmware mode, memory, DirectX, display-driver, and explicitly reported problem-device facts without uploading the report.

Windows System Information Snapshot ReaderOne bounded excerpt · no upload · no root-cause ranking

Review trail

Official and first-party sources

Same task chain

MEMORY_MANAGEMENTSevere memory-management errorIRQL_NOT_LESS_OR_EQUALInvalid kernel memory access at a raised IRQLDRIVER_POWER_STATE_FAILUREDriver did not complete a power-state transitionDPC_WATCHDOG_VIOLATIONA high-priority kernel task exceeded its time limit

Local-first utility

Privacy

The diagnostic parser, evidence readers, verification loop, and Evidence Pack run in your browser. TechClassy does not intentionally store the raw text you paste, Event Viewer or update-log excerpts, full command output, usernames, local file paths, dump files, device serial numbers, observations, parsed summaries, or generated Evidence Packs.

No advertising, analytics, session replay, account system, upload surface, or third-party diagnostic script is loaded in this release. Standard hosting security logs may contain request metadata such as time, requested path, and network information; diagnostic and evidence text is not sent as a URL parameter or API body by the tool.

Use boundary

TechClassy organizes evidence and reviewed next checks. It is not a substitute for Microsoft, an OEM, an employer's IT team, or a qualified repair professional. Results distinguish confirmed facts from possible causes and do not guarantee a repair.

Back up important data before making system changes. Stop when an action requires credentials, firmware changes, disk work, account recovery, or a command whose prerequisites you cannot verify.

Independent operation

This is a newly researched, independently operated diagnostic product. It does not claim to be the prior TechClassy editorial team or a continuation of prior authorship.

Open the permanent page