January 29, 201610 yr Droidz, Here are a couple of crash logs during the night when I sleep and wake up to find that wow has crashed with an error message. Thanks for an awesome bot. 29 Jan 2016 04H54.log.html 29 Jan 2016 13H24.log.html
January 30, 201610 yr Author Tried that too this is the lastest crash with no dx. 30 Jan 2016 05H14.log.html
January 30, 201610 yr Author Nope have not disable all addons yet. Will do that next. Here is another crash after I just got back home. 30 Jan 2016 13H10.log.html
January 30, 201610 yr same issue as i have but for me it happens mostly on automation and sometimes on Party too :/ edit: post #100
January 30, 201610 yr Author Yes had crashes with automation too but that occurs faster than battlegrounder.
January 31, 201610 yr Author More crashes but instead of causing wow to crash with error message now it just freezes the program. This is without any addons enabled with all blizzard ui. 31 Jan 2016 05H35.log.html 31 Jan 2016 06H29.log.html
January 31, 201610 yr Strange thing is that it freezes for 6 hours and then throws the error (on the 2nd log)
January 31, 201610 yr Author Just tried with no addons enable and used regular wrobot battlegrounder and not with "no dx" crashed with error. 31 Jan 2016 13H48.log.html
January 31, 201610 yr what RAMs your PC has? I'm starting think about faulty memory Reasons for it is the crash dump tells that WoW tried to write something to memory and crashed because of it... But in other hand the crashes happen (for me atleast with same error) only if bot is active
January 31, 201610 yr So it isn't custom... i have custom PC with 2 sticks of 1 model ram and 1 stick of other model ram so it wouldn't be any surprise if it would cause problems for me but before we get your problem fixed i can't really count on RAM fault
January 31, 201610 yr Oh and while we're at it please remove your username from the crash files because it can potentionally get you banned if warmane staff checks the website. I've been banned for 3 days and i already regret getting busted (was own fault tho... stupid head hurts the whole body)
January 31, 201610 yr BINGO! i just remembered that back in moltens low population days if my game crashed i got the exact same error every now and then but it was because of some graphics settings example "reduce input lag" fixed it for me. Ever since i used it but for some reason i don't have it enabled now! gotta try it out
January 31, 201610 yr Hello, if "reduce input lag" option don't resolve your problem, can you try to launch wrobot with NoFakeCallStack.bat (download and move this file in wrobot folder, double click on it to launch WRobot) (if wow crash again, if you can send me wow crash files by private message).
January 31, 201610 yr What antivirus and firewall and windows do you have @tomei My game just crashed even with "reduce input lag". I started thinking if it's because of Avast...
January 31, 201610 yr 5 minutes ago, tomei said: Only malwarebytes and windows defender windows defender can cause same issue by denying something that it doesn't like causing a crash
February 1, 201610 yr 11 hours ago, Droidz said: Hello, if "reduce input lag" option don't resolve your problem, can you try to launch wrobot with NoFakeCallStack.bat (download and move this file in wrobot folder, double click on it to launch WRobot) (if wow crash again, if you can send me wow crash files by private message). i let the bot run for the night and it didn't crash!
February 2, 201610 yr You can try to run WRobot with this plugin activated: http://wrobot.eu/files/file/622-memory-clean/
Create an account or sign in to comment