MINECRAFT DUNGEONS II - SANITIZED NATIVE DIAGNOSTIC SUMMARY
Prepared 2026-10-26. No external submission has been performed.

Environment
Game version: 1.1.3.0; Steam build: 25910487; Windows x64.
Windows 11 25H2, build 26200.9457.
CPU: 12th Gen Intel Core i7-12700KF. GPU: AMD Radeon RX 9060 XT.
Existing offline hero, level 100 / power 151.
Game executable SHA256: 3842102bb05fc532b22e97992d61c2248d115be80ff752ff9b6843bf4acd7005.
Installed executable/launcher and Visual C++ runtime signatures validated to Microsoft.

Scope
All eight crash dumps summarized here predate any experimental in-memory code correction. They show the same original merchant-refresh failure. A separate later main-menu self-exit after an experimental correction is not included as a baseline crash.

Observed failure
Exception: 0xc0000005, invalid READ in the Visual C++ runtime AVX copy loop.
Runtime file version: 14.51.36247.0.
First game return RVA: 0x617219e; game call instruction RVA: 0x6172199.
Reconstructed original unsigned size_t count: 0xffffffffffffff38
(unsigned 18446744073709551416; signed interpretation -200).
Source minus destination: 200 bytes.

Matching Microsoft runtime symbols/disassembly confirm RAX preserves the original destination; alignment and forward-copy instructions preserve the invariant R8+RCX-RAX. Thus the original count, not merely the remaining count after loop progress, is reconstructed as -200 in every dump.

Compiled caller and dump-local state
Read-only inspection of actual running code identifies a nested relationship-filtering loop over 200-byte temporary records. It selects an outer candidate at index i, compares it with earlier records, destroys/removes the OUTER candidate on a true predicate, decrements Num, and continues the inner loop without stopping or updating that outer candidate/index. Another match removes the stale index again.

Every baseline dump has removal-attempt counter R12=2 and outer index R14 equal to current Num at [RBP+0x458]. Therefore:
    remaining = Num - i - 1 = -1
    copy count = signed_extend(remaining) * 200 = -200
The code skips the copy only for remaining==0, allowing the negative count to reach the runtime. See CRASH_SUMMARY.csv for the eight non-identifying observations.

Relevant game RVAs
0x6172144 predicate call; 0x617215f removal-counter increment;
0x617216f record destructor; 0x6172174-0x6172181 tail calculation;
0x6172184 zero-only check; 0x6172186-0x617218f sign extension/multiply;
0x6172199 runtime copy call; 0x61721d1-0x61721e2 inner continuation.

Interpretation and limits
The predicate looks up two registry relationship lists; it is not simple equality. Private game symbols, the source function name, record type and triggering keys are unavailable. These temporary records must not be equated with merchant sale slots, affixes, effects, or duplicate owned items without additional evidence.

A source-level repair should ensure that a removed outer candidate/index cannot be reused while the inner scan continues, while preserving the intended relationship rules. Merely clamping the copy length would leave invalid repeated destruction/removal. This is a developer repair proposal, not a validated game patch.

Save and sequence observations
Backed-up hero data parses consistently; there are nine merchant stock items, three per tier. Original sold slots have matching purchased ordinary entries; these are not demonstrated corrupt duplicates. In the fresh user-operated sequence, an initial refresh succeeded and persisted nine replacement items plus a three-SpringStone charge. All previously owned ordinary items/progression remained unchanged. Purchase followed by another refresh then produced the eighth matching crash. Persistent sold flags alone are insufficient to make every refresh fail. No fresh hero was tested; character-specificity is unknown.

Steam overlay settings were off, but Steam's overlay DLL remained loaded in the baseline dumps. Overlay presence is not proven causal, and an overlay-free crash is not claimed. No relevant new Windows hardware/storage/display errors were found in the targeted inspection. These limited negative checks do not certify the hardware or establish that every save semantic is valid.

Subsequent failed workaround (separate from baseline)
A reviewed 15-byte temporary correction was later applied only in the running game at the user-confirmed main menu. The game exited on its own about nine seconds later, with Steam exit code 0 and no new Unreal crash report. The attempt was retired and cannot be reapplied through the local tool. No persistent patch or launcher was installed; the original game executable retains its hash/signature. No hero or Cloud data was manually edited. No specific anti-tamper mechanism is established by that exit.

Attachments and privacy
This package contains only written observations and selected derived numeric fields. It contains no saves, authentication/entitlement files, tokens, account/machine/login identifiers, personal paths, raw process memory, game binaries, raw crash XML or raw debugger logs. Original minidumps and reports remain available locally for an appropriate private support request; they have not been uploaded.
