TechClassy

Error Checker · reviewed 2026-09-01

bad_module_info stopped working diagnostic

bad_module_info is an application-crash label seen in some Windows error records. It is not a uniquely identifying Windows component or a root-cause verdict.

Moderate for the crash-label interpretationLow until a time-matched Application Error event is available

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 recorded an application failure under the bad_module_info label.

Not confirmed

  • The label does not identify the failing DLL, driver, game, or hardware component.
  • It does not justify compatibility changes, registry edits, or disabling security software without the faulting application and event data.
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
Faulting application; Exact crash time; Event Viewer Application Error entry; Faulting module name and version; Recent app, driver, or overlay change

Context changes the route

Where does the crash occur?

One app or game

Likely layer: Application, overlay, graphics, or dependent module

First safe check: Capture the time-matched Application Error event

Expected: The generic label becomes a specific application/module event that can be checked against the app or vendor.

Several unrelated apps

Likely layer: System-wide driver, memory, storage, or Windows component path

First safe check: Confirm whether the same exception or module repeats

Expected: A repeated module or exception across unrelated apps provides a stronger system-wide clue.

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

  • Windows version/buildExample: Windows 11 24H2, build 26100
  • Where it appearedSettings, installer, app, command, or another surface
  • Exact operation in progressWhat you clicked, opened, installed, copied, or ran
  • Most recent relevant changeUpdate, driver, app, hardware, policy, or none known

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

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