Taikutsu Lyrz (Salim Noor)
MT7925 Wi-Fi Investigation

Technical case study · PROJECT BREAKDOWN

Trace the failure. Find the pattern.

An evidence-led investigation into a Wi-Fi Code 10 startup failure on one Lenovo Legion laptop. Driver traces, recovery tests, and a documented configuration workaround.

PLATFORM
Windows · MediaTek Wi-Fi 7
STATUS
Single-system investigation
BUILT BY
Taikutsu Lyrz (Salim Noor)

The idea
behind the build.

The adapter failed during startup while the original signed driver package remained installed. The investigation follows the failure through device state, trace evidence, and controlled recovery tests.

WHO IT'S FOR
Developers and readers examining a documented Windows driver failure
THE FOCUS
Separate captured evidence, static-analysis inferences, and recovery observations
01

Capture before recovery

Failed-device state and traces preserve evidence that a removal or reinstall could otherwise reset.

02

Compare the same driver

The investigation compares failing and working states while retaining the original signed driver package.

03

Distinguish evidence from inference

Captured events, static country-table reconstruction, and user-reported follow-up are documented as different forms of evidence.

How the investigation was built.

Single-system research · Vendor traces · Binary analysis · Recovery experiments

The core parts of the project, and the responsibility of each.

PART 01

Failure capture

Windows device state · WPP / ETL

Collects Code 10 startup information and vendor trace events around a controlled restart.

PART 02

Static analysis

Python · pefile · Capstone

Examines the matching driver binary's control flow and country-table structures.

PART 03

Recovery comparison

PowerShell · Restart / rescan tests

Compares recovery behavior and saved configuration across adapter restart and reboot.

The workflow

  1. Record the failed state

  2. Capture a controlled restart

  3. Compare traces and code

  4. Document results and limits

The decisions
in the details.

The features, boundaries, and implementation choices that shape the project.

Observed failure

The present MT7925 adapter reported Code 10 and status 0xC000009E. A command returning success did not by itself establish device recovery.

Trace finding

The captured failing start reached firmware-ownership acknowledgement before a later band-capability initialization failure.

Recovery evidence

Removing the exact Wi-Fi device node and rescanning recovered the device while keeping the existing signed driver package.

Separate experimental work

An offline binary candidate was constructed and checked but never installed. It is distinct from the configuration workaround used on the investigated laptop.

What was observed.

A summary of the documented case. The repository contains the full trace analysis and test context.

System
Lenovo Legion Pro 5 16ADR10 · MT7925
Startup failure
Code 10 · CM_PROB_FAILED_START
Problem status
0xC000009E
Driver package
Original signed package; no patched driver installed
Observed recovery
Configuration override survived adapter restart and full reboot
Scope
One system; not a universal fix

Tools & methods.

What the project uses, and where each technology fits.

Windows diagnosticsDriver analysisTechnical research
Diagnostics
Windows PnP · WPP · ETL

Captures device state and vendor startup events.

Experiment tooling
PowerShell

Runs documented tracing and controlled recovery comparisons.

Binary analysis
Python · pefile

Inspects the matching Windows PE driver and its data structures.

Control-flow analysis
Capstone

Disassembles selected routines to compare embedded diagnostics with trace events.

Availability
& next steps.

How to explore the project, what it needs to run, and the current release status.

Published material

The public repository contains findings and source tools. Raw system captures and vendor binaries remain local.

Scope

One Lenovo Legion Pro 5 16ADR10 with a MediaTek MT7925 adapter; findings do not establish a universal repair.

Current boundary

The original signed driver remained installed. The experimental binary candidate was not deployed, and no driver package is distributed here.

GitHub repository

Read the full report for the evidence, configuration context, and limitations. This page does not distribute driver packages or present the workaround as a general recommendation.