Crash when using the cheat

[daring sonnet]

Hello,

I’m having a serious issue when using the cheat.
It works fine the first time, but when I try to play again, the game crashes and my entire PC freezes, forcing a restart.

This happened in two different games (R.E.P.O and Lethal Company).
I’m using Windows 10 and my PC specs are Ryzen 5 8400F with RX 7600, so hardware is not the issue.
I already reinstalled the games, but the problem persists.

Is this a known incompatibility or is there a fix for this issue?

[vital gulch]

Hey @daring sonnet Unfortunately, this is likely isolated to your PC. If your computer is freezing completely and you can’t tab out or even open Task Manager, that’s a strong indicator something on the system side is hanging (driver/overlay/hardware) rather than just the trainer itself.

Have you checked Windows Event Viewer around the time of the freeze to see if any critical errors or warnings were logged?

[daring sonnet]

No, I haven’t been able to check Event Viewer yet because the issue happens very suddenly.

What happens is this: I open the game, stay a few seconds on the loading screen, and then everything freezes completely. The mouse does not move, I can’t Alt+Tab, and I can’t open Task Manager. It’s as if the PC completely dies. Sometimes I can still hear my friends on voice chat, sometimes I can’t, and the only option is to force a restart.

I already reinstalled the games, but it didn’t help at all.

The important detail is that this started only after I used the cheat. Before that, both games worked normally. Now, even if I open the game without the cheat, it still crashes the same way. This is happening in two different games (R.E.P.O and Lethal Company), which makes it feel like too much of a coincidence.

I don’t know if this is happening only to me or if other users are experiencing something similar, but since it started after using the cheat and affects multiple games, I’m really confused about what could be causing this.

[vital gulch]

Hey @daring sonnet Thanks for the reply. Unfortunately, even if the trainer wasn’t working correctly on our side, it sounds like you’ve been trying to use it in multiplayer/co-op sessions, which we don’t support our trainers are designed for single-player use only.

Also, since you’re seeing the issue even when Wand isn’t running, that strongly suggests the problem is coming from your PC/game setup rather than the trainer itself.

[daring sonnet]

Just to explain my side a bit better: I understand the trainer is officially meant for single-player, and I know there are games where it doesn’t work properly in multiplayer. However, in my case, I’ve always used the trainer in single-player only.

For R.E.P.O and Lethal Company, I’ve been playing these games for years with a friend, and I’ve always used the trainer in these games without any issues. Even though they are online/co-op games, I never had crashes, freezes, or “not supported” problems before. Everything always worked fine.

What concerns me now is that this started out of nowhere, after years of using it the same way. Before this, both games worked normally. After that, the severe freezes began, and now the issue happens even with Wand completely closed, including after reinstalling the games.

I’m not saying the trainer is definitely the cause, but since the problem only started after using it and affects two different games that always worked before, from my perspective it feels like too big of a coincidence.

If you have any suggestions on what I could check or reset on my system to rule out possible conflicts (drivers, overlays, etc.), I’d really appreciate it, because at this point I’m not sure what else to try.

[vital gulch]

The fact that it “started out of nowhere” makes me think this is more likely coming from your PC/hardware or system environment rather than Wand itself. As mentioned earlier, the best next step is to check Windows Event Viewer around the time of the freeze to see if anything critical was logged, and to run a couple basic benchmarks/stability checks.

Beyond that, we’re unfortunately pretty limited in the additional support we can provide since this appears to be isolated to your system.

[daring sonnet]

I did a deeper analysis using only Windows Event Viewer logs, and below are the exact system records that explain what’s happening.

In the Application log, there are two critical Application Hang events (Event ID 1002) occurring in direct sequence:

1. Wand.exe

Source: Application Hang
Event ID: 1002
Application: Wand.exe
Version: 12.8.0.0
Path:
C:\Users\kayke\AppData\Local\Wand\app-12.8.0\Wand.exe
Failure reason reported by Windows:
“Top level window is idle”
Logged time (SystemTime): 2026-01-21T20:39:29Z

This indicates that Wand stopped responding to Windows, with its main UI thread entering an idle/deadlocked state.

2. Lethal Company.exe

Source: Application Hang
Event ID: 1002
Application: Lethal Company.exe
Version: 2022.3.62.28864 (Unity)
Path:
C:\Users\kayke\Desktop\Nova pasta (15)\Lethal Company\Lethal Company\Lethal Company.exe
Reported status: “Unknown”
Logged time (SystemTime): 2026-01-21T20:40:59Z

Shortly after Wand enters a hang state, the game itself also enters an Application Hang, completely stopping interaction with the OS.

It’s important to note what does NOT appear in the logs:

No GPU driver crashes
No WHEA-Logger hardware errors
No Kernel-Power events prior to the freeze
No explicit system crash
Windows only reports full application deadlocks.

This matches the real behavior exactly:

Freeze during loading screen
Mouse becomes unresponsive
Alt+Tab stops working
Audio may continue briefly
Forced reboot required

The key point is that this sequence only started after using Wand. Before that, both games worked normally. Now the issue persists even with Wand completely closed, including after reinstalling the games, which suggests a corrupted game/system state (for example, an injection or hook not unloading cleanly).

I’m not stating that Wand is definitively the cause, but based strictly on Windows logs and event order, this looks like a software deadlock, not random hardware instability.

Based on these logs, what would you recommend as the correct recovery procedure?
Is there any specific Wand-related cleanup, reset, or full removal process to ensure no leftover state remains that could cause this behavior?

[daring sonnet]

?