Until whatever result I get tomorrow, a fine day to you all.ĮDIT, due to not being allowed to post before someone else does: If I deem any of it worth sharing, I’ll add it later tomorrow after having tested for crashing, in case anyone else might come across Error #132 and find their way here during troubleshooting by Internet search. If it does pop up, I’ve received some additional advice from a support ticket that I’ll attempt. Tomorrow, I’ll likely attempt to enable all my AddOns and just do whatever to pass the time and await a crash from Error #132. So my RAM doesn’t seem to be the immediate problem and I return to the background applications from Startup. Luckily, I have no plans in the morning and will thusly continue with the final pass to make sure nothing pops up. Well, assuming the 4th pass of the MemTest86 doesn’t suddenly pull something crazy, it currently shows no errors after 3 passes and 4 hrs 42 mins. Corrupted data files could in theory (but very rarely) cause such issues, so scan/repair may sometimes help, but it is not specifically related or even likely. That rumor has been floating about for a while already, but #132 solely indicates a memory-related conflict. P.S.: Since it was mentioned in the thread - error #132 has nothing inherently to do with “corrupted maps”. Running a RAM diagnostic with a tool like memtest86 would definitely be worth a try, beyond that I’d actually recommend to get in touch with a local technician for a more thorough hardware review. In terms of troubleshooting that does leave only a few options - it is still possible for the memory areas to be just accidentally blocked by another application, but unfortunately a potential hardware defect cannot be ruled out anymore. This would also roughly fit with the described timeline of events: game/addon memory consumption steadily increases over time, so it’d make sense for the conflict to take a while to manifest. There seems to be an actual memory error, possibly a corrupted sector or similar, which becomes an issue soon as memory needs get high enough to eventually tap said problematic sector. Seeing the problem also occurred without any addons installed (as per the earlier crash report) I think the addons are just aggravating circumstances here, not ultimately cause them. The ultimate root cause for the crash was a memory conflict where address space that should be reserved for WoW was not usable - this is of course a common problem for addons (and there were roughly a 100 of them loaded during the last crash), but I am rather sure that is not the whole story here. I’ll name the proverbial elephant in the room right away: this is very likely a memory-induced problem that addons were involved in but did not trigger on their own. Thanks for the crashlog - it proved rather illuminating regarding the circumstances the crash occurred in!
0 kommentar(er)
