Twitty

7 minutes ago, Krazzee said:

I've researched the error as it seems it can be common to WoW but the reasoning is unknown even by Blizzard. The main steps I'd like to see one of you try is what they and many who have experienced it on the forums recommend. The steps are:

1.) Rename the Cache, Interface and WTF folders to .old - Cache.old - Interface.old - WTF.old to keep them backed up but out of the way, they are ok to remove and will regenerate themselves when you log back in to your characters

2.) Seeing as it's memory related, I recommend downloading a quick memtest and running it, just to ensure it's not somehow memory that is actually causing the "Memory can not be read error", there's always the rare chance the computer is right when it tells you the error :P

3.) Update your drivers, GPU drivers, audio drivers, it never hurts to have up to date drivers and a lot of the error #132's i'm reading online were driver related

4.) Disable any Curse/Twitch addons, TeamViewer, basically anything extra as a test step. Running WoW without addons as a test step would also be very useful

If you two can do preferably all of those steps in order to see if any of them help, starting in order, it will help to either resolve your issue or give me a lot of information on how to possibly fix it for you and other users. Regardless of if it is caused by WoW or WRobot, something is causing an error and impacting your play, so I'm happy to help fix what I can when I can

Edit: Are either of you running any overclocking on your systems? Overclocked GPU, CPU, and/or RAM by chance?

I changed my direct x11 to 9 and disabled addons seems to be working just fine now will update if otherwise

6 minutes ago, Krazzee said:

I've researched the error as it seems it can be common to WoW but the reasoning is unknown even by Blizzard. The main steps I'd like to see one of you try is what they and many who have experienced it on the forums recommend. The steps are:

1.) Rename the Cache, Interface and WTF folders to .old - Cache.old - Interface.old - WTF.old to keep them backed up but out of the way, they are ok to remove and will regenerate themselves when you log back in to your characters

2.) Seeing as it's memory related, I recommend downloading a quick memtest and running it, just to ensure it's not somehow memory that is actually causing the "Memory can not be read error", there's always the rare chance the computer is right when it tells you the error :P

3.) Update your drivers, GPU drivers, audio drivers, it never hurts to have up to date drivers and a lot of the error #132's i'm reading online were driver related

4.) Disable any Curse/Twitch addons, TeamViewer, basically anything extra as a test step. Running WoW without addons as a test step would also be very useful

If you two can do preferably all of those steps in order to see if any of them help, starting in order, it will help to either resolve your issue or give me a lot of information on how to possibly fix it for you and other users. Regardless of if it is caused by WoW or WRobot, something is causing an error and impacting your play, so I'm happy to help fix what I can when I can

Edit: Are either of you running any overclocking on your systems? Overclocked GPU, CPU, and/or RAM by chance?

so far changed direct x11 to 9 and it seems to be working

and disabled dbms

13 hours ago, Krazzee said:

What type of processor are you using? Is it an AMD processor by chance? If you are unsure you can run a dxdiag via the start menu and post a log here, it has lots of useful information we can use. Also, is this crash replicatable in WoW without the bot, or does it ONLY happen when running WRobot? Error #132 - Access Violation, Memory cannot be read seems to be a common error for people in the latest expansion of Legion. Also, was this on the Windows Server NT computer, or Windows 7? The text logs indicate 7, but the .html logs and everything else shows Windows Server NT. According to the logs the main exception it is throwing is:

The instruction at "0x00438c72" referenced memory at "0x00000bb8".
The memory could not be "read".

So i'm thinking either it's not running properly as administrator, either WoW or WRobot, not enough RAM, or it could be something else like located too close to the C:/ drive and it is unable to write anything it needs to memory.. The more details you can provide that I asked for in this post, the better. As far as I can tell, this Access Violation happens more often than I'd like here on the WRobot forums, but it has provided some useful insight as well.

Seems like the bot is causing it because everytime i use the bot it crashes but i have windows 7 and i have 16gb of ram my processor is a 6700k skylake

2018-02-01 20.32.16 Crash - 19192.txt

2018-02-01 20.32.16 Crash - 19192.dmp

1 Feb 2018 18H55.log.html

Just crashes randomly wow says something about access violation idk

31 Jan 2018 22H00.log.html