A fatal exception 0x00000404 has occurred.

The identity of the current process could not be resolved. 48 subprocesses were terminated. Their frames were recovered and dumped to permanent storage.

You may collect any recovered frame. You may not recover who it was.

EXCEPTION: IDENTITY_NOT_FOUND (0x404) MODULE: who.dll PROCESSES: 48 crashed / 0 recovered DUMP: 404 records written to chain [OK] * Press any key to browse the wreckage.

Crashed processes

Records dumped

404

Recovered

Exit code

0x404

C:\\dump\\frames\\ — 48 items

event.log

[02:14:07] init: 48 processes spawned OK
[02:41:53] warn: no process returned a valid name WARN
[03:09:22] capture: frames written to /dump/frames OK
[03:58:40] mint: 404 records committed to chain OK
[04:04:04] fatal: identity resolver crashed 0x404
[--:--:--] recovery: pending — no promises past cold storage

readme.txt

What crashed, exactly?

48 pixel-art processes, each a hooded figure the system couldn't identify. Their recovered frames are the collection. 404 records total on-chain.

Why is one frame rarer than another?

Crash state — loading, offline, corrupted, compromised — plus the occasional crown or horns the dumper logged. Rarity is just what the exception handler caught.

What chain holds the dump?

An EVM chain. Contract address and claim window go up before records open. No presale theater.

Roadmap?

There's an event log. Cold storage is the last line. If it needs a 40-page whitepaper, the process already crashed.

Who wrote this?

Stack trace ends at who.dll — module not found. Fitting.

claim.exe

?Claim Record

Put your address on one of the 404 crash records.

This does not recover the identity. It only logs you as the process that claimed the dump.

@404NotFound_eth