A custom weapon that crashes the client
A weapon that drops players to desktop is usually a texture format, a broken mip chain or a collision with another pack. How to isolate which.
A weapon that crashes on equip is doing something the renderer cannot recover from. There are three usual causes, and they can be told apart in about ten minutes.

#Rule out the collision first
Two resources streaming different files under the same asset name is the most common cause of a crash that appeared after an unrelated install. Stop every other weapon pack, restart, and try again. If the crash stops, the problem is a name and not the model.
#Then the texture format
A texture saved in a format the game does not expect for that slot — an uncompressed image where a BC-compressed one belongs, or a normal map written as sRGB — can take the renderer down rather than simply looking wrong. This is the usual outcome of a hand re-import that skipped the compression step.
The fix is to write the texture back in the format the original used. Not a similar one, the same one. If you no longer know what that was, the original pack is the reference.
#Then the model itself
A .ydr exported with a shader the game has no material for, or with a bone structure that does not match a weapon, will crash on equip rather than fail gracefully. This is a model problem and it needs the model rebuilt, not a texture edit.
- Reproduce on a clean server with only the weapon resource running.
- Swap the .ytd for the original, unedited one. If the crash stops, it is a texture.
- Swap the .ydr for another weapon's. If the crash stops, it is the model.
- Check the client crash log for the asset name it died on.
Questions
Why does it only crash for some players?
Does editing a texture risk this?
Where is the client crash log?
Ready to pick a map?
Twelve themes on three base map styles, $8 each, instant download.
Relevant to what you just read