Crash Diagnosis
Quick answer
Isolate first, read the error second, change configuration last. Most wasted time on clothing crashes comes from applying a fix before knowing which resource is involved.
Difficulty: Core procedure · Affects: both
INFO
Search: how to diagnose, isolate, binary search, which pack, decision tree, find the cause.
Step 1 — Isolate
Disable all clothing resources. If the crash persists, clothing is not the cause and this section of the docs will not help you.
If it stops, binary search:
- Back up
server.cfg. - Re-enable half of the clothing resources.
- Test: join, load a male character, load a female character, open the clothing menu.
- Crash → the cause is in that half. No crash → it is in the other half.
- Halve again and repeat until one resource remains.
Twenty resources take about five tests this way. Disabling them one at a time takes twenty and tells you less.
WARNING
Never decrypt an escrowed resource to inspect it. If the search ends on an escrowed pack, gather evidence and contact the seller.
Step 2 — Read the exact error
| Log contains | Cause | Page |
|---|---|---|
TxdStore Pool Full, Size == <n> | Texture dictionary pool | TxdStore |
Invalid fixup with a .ydd name | One corrupt file | File & Resource Crashes |
ERR_MEM_MULTI_ALLOC_FREE | Alternate variations | Alternate Variations |
You lack the required entitlement | Escrow licensing | Asset Escrow |
Error executing native 0x00a1cadd00108836 | Collection capacity | Capacity Crashes |
| A three-word hash only | Build fingerprint | Known Crash Hashes |
Step 3 — Match the timing
| When it crashes | Look at |
|---|---|
| Joining the server | Capacity Crashes |
| Character loading, after a successful join | Capacity Crashes |
| One gender only | YMT budget for that gender |
| Equipping one specific item | File & Resource Crashes |
| Immediately after a build change | Changing Game Build |
| Immediately after installing a pack | Capacity — verify with a count, not by blaming the pack |
Step 4 — Confirm before fixing
Two tests settle most cases:
- Revert the game build. If the crash disappears, it was capacity.
- Count YMTs per gender. If a gender is at or below zero remaining, you have your answer.
What not to do
WARNING
Clearing cache first
It does not return slots or pool capacity, and it destroys evidence about which files were actually downloaded.
WARNING
Maxing every pool
Oversized pools have crashed other pool types. Diagnose the specific pool that is full.
WARNING
Disabling resources one at a time
Slow, and it tells you nothing about combinations.