NeophyteHC
Member
- Joined
- Aug 30, 2013
- Messages
- 119
- Reaction score
- 0
Yesterday evening. I was botting my Hunter. I used the premium plugin from Brodieman. My character was doing all fine and well.
However, when my character reached Swamp of Sorrows. And picked up the quests. Wow closed down with an error. ACCESS_VIOLATION. I re-opened wow a couple of times. It didn't work. I restarted PC and did a fresh install. None work.
Posting a log would be futile, consdering Honorbuddy didn't give any errors.
On a side note. Bots like Enyo still work. I don't usually run any other bots. I can try. But the problem I have here runs Questing. By chance I came across a post saying that Questing would no longer work for German people. Luckily I am not German, but I live close. The Netherlands. I can dig up the logs if you really want them.
PS: questing bot now crashes wow no matter what profiles no matter the level.
PPS: Tried again now. It's a different error. I should probably put some additional explaining down.
First the access_violation error came, three? Maybe four times. It was given in the standard wow error message. I sadly did not copy it. However now the error is a standard windows error with the following text. I hope it might be useful.
Problem signature:
Problem Event Name: BEX
Application Name: Wow.exe
Application Version: 6.0.3.19342
Application Timestamp: 548f8e55
Fault Module Name: StackHash_a37e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00000000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: a37e
Additional Information 2: a37eaa4c6fff3d2c63dfb3576470da41
Additional Information 3: 5d2f
Additional Information 4: 5d2ff650848cbb363aa4a9fd2a6e6700
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Edit two: Added all log files since the error, just in case.
View attachment 94816 2014-12-30 21.55.txtView attachment 97136 2014-12-30 22.23.txtView attachment 95400 2014-12-30 22.27.txtView attachment 97384 2014-12-30 22.34.txtView attachment 95536 2014-12-30 21.51.txtView attachment 99552 2014-12-31 12.35.txtView attachment 96180 2014-12-30 22.29.txt
However, when my character reached Swamp of Sorrows. And picked up the quests. Wow closed down with an error. ACCESS_VIOLATION. I re-opened wow a couple of times. It didn't work. I restarted PC and did a fresh install. None work.
Posting a log would be futile, consdering Honorbuddy didn't give any errors.
On a side note. Bots like Enyo still work. I don't usually run any other bots. I can try. But the problem I have here runs Questing. By chance I came across a post saying that Questing would no longer work for German people. Luckily I am not German, but I live close. The Netherlands. I can dig up the logs if you really want them.
PS: questing bot now crashes wow no matter what profiles no matter the level.
PPS: Tried again now. It's a different error. I should probably put some additional explaining down.
First the access_violation error came, three? Maybe four times. It was given in the standard wow error message. I sadly did not copy it. However now the error is a standard windows error with the following text. I hope it might be useful.
Problem signature:
Problem Event Name: BEX
Application Name: Wow.exe
Application Version: 6.0.3.19342
Application Timestamp: 548f8e55
Fault Module Name: StackHash_a37e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00000000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: a37e
Additional Information 2: a37eaa4c6fff3d2c63dfb3576470da41
Additional Information 3: 5d2f
Additional Information 4: 5d2ff650848cbb363aa4a9fd2a6e6700
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Edit two: Added all log files since the error, just in case.
View attachment 94816 2014-12-30 21.55.txtView attachment 97136 2014-12-30 22.23.txtView attachment 95400 2014-12-30 22.27.txtView attachment 97384 2014-12-30 22.34.txtView attachment 95536 2014-12-30 21.51.txtView attachment 99552 2014-12-31 12.35.txtView attachment 96180 2014-12-30 22.29.txt
Last edited: