Hello,

After Wrobot update, the WoW client crashes here and there shortly after starting up Wrobot or during combat.

The error: Wow.exe 3.3.5a crashes (memory access violation in unknown module) since WRobot 2.8.2 (27439)

Whats used:

- WRobot 2.8.2 (27439), compiled 10/20/2026, for 3.3.5a_12340

- Log shows: "[Memory] D3D9 used", "HWBP hook", "[StealthProtection] Active", "[Memory] Hooking success"

What happens:

- About 3 seconds before the crash the game stops responding: Lua calls.

- Then the client dies. WRobot logs a flood of these errors as it goes down (I assume this is a symptom, not the cause):

GetReactionTowards(WoWFactionTemplate otherFaction): System.NullReferenceException at wManager.Wow.Helpers.WoWFactionTemplate.GetReactionTowards(WoWFactionTemplate otherFaction)

Windows Event Viewer (Application log)

Faulting application name: Wow.exe, version: 3.3.5.12340, time stamp: 0x4c2452fe

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x7ff44e73

Problem signature: APPCRASH, P4: StackHash_3850, P7: c0000005, P8: PCH_38_FROM_unknown+0x00000000

I have attached the Wrobot logs for the character this happened to, but its the same type of logs on my other characters as well.

I never experienced this issue before, and it only started happening after the recent Wrobot update.

22 Oct 2026 10H35 - crash 2.log.html 22 Oct 2026 10H31 - crash 1.log.html

Update:

I used the downgraded version of Wrobot I had from before, and the crashes are gone. This is a workaround, but is there any chance to see what caused these issues on the newest Wrobot version?

Thanks!

Hello,

I think it comes from a change in this update, the way keys are sent to the game on 3.3.5 (movement, and spells cast with the action bar keys).

Can you try the latest version again with these two options unchecked in the General Settings, and tell me if it still crashes?

- "Move with game input" in the "Class / Fights Class" tab

- "Cast spells with the action bar keys" in the "Human-like behavior" tab

The GetReactionTowards errors are only a side effect of the client going down, you can ignore them.

4 hours ago, Droidz said:

Hello,

I think it comes from a change in this update, the way keys are sent to the game on 3.3.5 (movement, and spells cast with the action bar keys).

Can you try the latest version again with these two options unchecked in the General Settings, and tell me if it still crashes?

- "Move with game input" in the "Class / Fights Class" tab

- "Cast spells with the action bar keys" in the "Human-like behavior" tab

The GetReactionTowards errors are only a side effect of the client going down, you can ignore them.

23 Oct 2026 07H10 - zCoGmoE.log.html

Hi. I turned it off and ran it again. As soon as it walked one or two waypoints it crashed. Checked the logs, same red colored errors appeared before crashing. I saw there was a update this morning, so I applied that also before testing.

Hello,

I pushed an update for WotLK, can you try with this version and tell me if it still crashes?

If it still crashes, try with this plugin. It turns off the new way keys are sent to the game. Your fight class (AIO) turns the "Move with game input" option back on when it loads, that's why unchecking it did nothing. Create a file DisableGameInput.cs in the Plugins folder with the code below, then enable it in the Plugins tab.

using wManager.Plugin;

public class Main : IPlugin
{
    public void Initialize()
    {
        wManager.Wow.Helpers.GameInput.UseGameInput = false;
    }

    public void Dispose()
    {
    }

    public void Settings()
    {
    }
}

If it's better with the plugin, let me know, it will help me find the exact cause.

And if the game crashes again, can you send me its crash report by private message? It's the .txt file with the time of the crash in the Errors folder of WoW (World of Warcraft\Errors).

Hello @Droidz ,

Thank you very much for the assistance. With the plugin, all crashes are gone and Wrobot works with the client without issues.

I hope that helps you further to track down the root of the cause. Do you need anything from me?

Hello,

Your test with the plugin helped a lot, I could reproduce the crash here and found the cause. It's fixed in the update I just pushed, for all WRobot versions.

Can you remove the plugin (DisableGameInput.cs) and try the new version? Tell me if you still get a crash.

Looks good. No more problems. That new human behavior looks cool, but I dont see it being applied on my run now, perhaps a work in progress?

Also, is there any changelog on these kind of updates? I have to dig through the settings to find out every time otherwise.

Thanks for everything!