[WOW CRASH] Only part of a ReadProcessMemory or WriteProcessMemory request was comple

[Thunfisch]

Hi there,

WoW is crashing after couple of minutes with BGBuddy active. Logfile is attached.

I have a brand new Windows 7 Ultimate 64 Bit installation, HonorbuddyDE_Installer_v2.5.8877.711 (not the zip archive version). I removed all the subfolders within the WoW Cache directory, set the game client to 32 Bit, DirectX 9 and windowed mode at 1280x1024 resolution. I started WoW and HB as admin, Addons disabled.

The attached log contains the crash using several plugins and combat routines (Ultimate_PvP_Suite_v1.21, MrGearBuyer_Version_3.2, Combat Routines for Mages: Portal.rev2, ForstDoeninge_lvl90). But the same crash occurs also without any plugins and custom routines (Singular only).

 

[Tony]

use Singular instead and let me know

 

[Thunfisch]

Running for a while now with Singular. No crash so far. Looks like it's one of the plugins or routines. Interesting.
Also, I notice some lags within the WoW client every 2 to 3 seconds. Could this be related to disabled Framelocks? Should I enable Framelocks?

 

[Tony]

you can enable it and also set wow process to a higher priority than normal

 

[Thunfisch]

Crashed again.

This time, it ran for a couple Battlegrounds. Log attached.
I had Framelock enabled. WoW client and HB process priority set to [one above normal]. No WoW addons, no custom HB plugins or routines.

Hardware should be sufficient. Core i5, 8 GB RAM, AMD Radeon 7600M, latest Catalyst driver.

 

[Tony]

use dx11 instead and let me know

 

[Thunfisch]

Switched to DX11, crashed again. Even faster this time.

I've attached two logs this time. One where Framelock was enabled, the other one without it.
Cleared game and HB caches before each session. Did not change process priorities this time.

 

[Thunfisch]

I went back to DX9/Singular/No Addons/No Plugins, which was working before but it crashed again.

Is there anything else I can do or try?

 

[Tony]

hm,


not many thing to try but make a new Hb installation from scratch and clear your wow cache as well

 

[Thunfisch]

Alright then. I'm gonna remove HB using the installer's Uninstall function, get rid of the whole installation directory of HB (e.g. C:\Users\Username\Documents\Honorbuddy) and also delete %WOW_DIR%\Cache\*
I tried searching for similar problems and found something related to my error messages. Someone in that thread suggested typing the mount names in the settings menu instead of letting the bot randomly choose one. Tried that, too. Didn't help.

Oh, and btw: I did a WoW game client repair through Blizzard's Launcher right before I opened this thread. Didn't help neither.

I'll get back to you as soon as I've tried a couple more things.

Thanks so far.

 

[Tony]

alright,you're welcome

 

[Thunfisch]

Unfortunately, nothing's changed. Here's what I did:

- WoW Client:
* Removed Cache Directory
* Removed WTF Directory
* Used Launcher Repair Tool

- HB:
* Uninstalled via installer's Uninstall function
* Removed C:\Users\MyUser\Documents\Honorbuddy completely
* Removed C:\Users\MyUser\AppData\Local\HonorbuddyMeshes
* Reinstalled via HonorbuddyDE_Installer_v2.5.8877.711

Afterwards:
* Restarted WoW Launcher as admin
* Changed Preferences to: DX9, 32-Bit Client
* Closed the WoW Launcher again
* Started Game and HB via Honorbuddy.Launcher as admin
* Logged into WoW, changed display settings to Windowed Mode, 800x600, Click-To-Move, also set the lowest graphical settings possible (for more FPS ...)
* Logged into HB, chose BGBuddy
* Changed Settings:
+ Uchecked all checkboxes in the advanced settings menu (loot mobs, resurrect at spirit healers, etc.)
+ No Framelock
+ Tped in Swift Red Wind Rider in both mount input fields
+ Set Bot settings to Random Battleground in the first dropdown menu

* Started the bot!

The Bot queued up for a random Battleground, accepted the invite, entered the Battleground, Conjured a Refreshment Table (Mage spell) and crashed several seconds later.

Logfile attached.

Unless anyone can point me to something I just have missed during initial game and HB setup, I really don't know what else to do.

 

[Tony]

the last thing i can suggest


remove:
- microsoft .net framework 4 client profile
- microsoft .net framework 4 extended
- microsoft visual c++ 2010 x86 redistributable
- microsoft visual c++ 2012 x86 redistributable


restart your pc,
download the installationwizard from here
run it as administrator.
after the wizard is done, run windows update. And install all updates for .net & c++
restart

 

[Thunfisch]

It is still crashing.

Removed visual c++ 2012 x86 redistributable, visual c++ 2010 x86 redistributable and microsoft .net framework 4 completely. Then I used the InstallationWizard you've linked which installed .NET 4.0 (I had 4.5.x before). Tested a while and had several crashes.
I updated every optional update Microsoft had to offer, including several .NET updates (updated to 4.5.x), rebooted, removed HB, reinstalled it, removed all WoW caches.

No luck.

I'm out of options. Final log attached.

It sometimes crashes even when the bot is waiting for a BG invite and is doing (visibly) nothing at all.
I've searched these forums for related threads. Is there really nothing left to do? What are my options now? Can I dig deeper somehow? Is there a way to provide more verbose debugging information to the developers?

Let me know if I can help.

Thanks again so far.

 

[Thunfisch]

After couple more tries I kinda gave up on this, uninstalled HB and was planning on doing some "manual" gaming. Then I noticed that WoW does also crash without HB. Quiet often, actually. I remembered that I switched from WoW 64 to WoW 32 for HB, switched back to WoW 64 and the crashing stopped.

So, this seems to be some other issue not even related to HB.

I'm very sorry that I've wasted your time, Tony.

Not sure about the further purpose of this thread. I guess it can be closed. But it would be nice if people got reminded of that a crashing WoW client could be related to this issue.

 

[CodenameG]

when it crashes take a look at the report that wow gives, and see i you can find out why, im willing to bet that it might be a driver issue. also doing windows updates and making sure everything is fine would also help.