It's easy! do a diskclean up and a Defrag, if you have not done this already, otherwise try these: 1st: I highly doubt this will work, but try launching wow from the .exe It looks like the common ones so far is the ones where your NVIDIA drivers are causing the game to crash because you have old 170 or 180 series drivers. permalinkembedsaveparentgive gold[–]Zatinox[S] 0 points1 point2 points 1 year ago(2 children)From the start, I installed the game in MoP and this PC never allowed WoW to run with DX11, so I had to change have a peek here
Dinará 85 Tauren Druid 3340 31 posts Dinará Ignored 27 Dec 2010 Copy URL View Post Sorry to Bump this again but I'm still having these errors and still looking for About one hour ago it happend. Crackcake Europe 16:26, 25/08/13 Source Hello,After a few months i decided to go and play WoW again but now after update i get an Error 132 Memory could not be read. I tried all this including turning my computer off and on and it did not work.
permalinkembedsaveparentgive gold[–]danielsviper 1 point2 points3 points 1 year ago(3 children)Just wanna make sure, since i was not really specific in my reply, when did you have to start changing in the wtf folder Program: C:\Program Files (x86)\World of Warcraft\Wow-64.exe ProcessID:784 Exception:0xc0000005 (ACCESS_VIOLATION) at 0033:000000013FBE8CEF The instruction at "0x000000013FBE8CEF" referenced memory at "0x00000000AD7022D5". Weekly Threads Skirmish Sundays (PvP) Murloc Mondays (New players) Tanking Tuesdays Midweek Mending Thursday Loot Thread Firepower Friday (DPS) Switch Up Saturday Chat Join us on: /r/wow Discord EuroGroup Discord IRC permalinkembedsaveparentgive gold[–]danielsviper 1 point2 points3 points 1 year ago(1 child)Ok just wanted to make sure the DX9 thing was not something the came up when WoD launched.
I'm also leaving the office here in like an hour and a half. Never crashed on first login ever. Watch Queue Queue __count__/__total__ Find out whyClose World of Warcraft memory could not be read (FIXED) Flamebird346 SubscribeSubscribedUnsubscribe1515 Loading... Wow Memory Cannot Be Read 2016 Scan for virus.
Share this post Link to post Share on other sites Lysbryter 7 Member Members 7 57 posts Posted February 10, 2013 · Report post This happened to me too yesterday What to do is use the auto-unstuck tool on the webpage, this fixed my problem 100% Share this post Link to post Share on other sites GGWHITEBOY 1 Newbie Members Still, going from crashing at least 2 or 3 times per session to no crashes in ~ 48hrs is a good thing. I have had the error many times, but when I've gotten it in the past I just had to switch to DX9, something that did not work after the patch. 30
All we know is that error 132 can happen to any install. Wow Legion Memory Could Not Be Read i've also sent a ticket to GM but no answer atm Share this post Link to post Share on other sites Kyn 37 Field Marshal Members 37 621 posts Posted Catalyst 15.11.1 Beta is available here. I did not go all the way back to 15.7.x because those were the very first drivers for Windows 10 and I didn't think that the first version would be the
Sign in to add this video to a playlist. Gietertjuh
I deleted my "Cache" "Data/Cache" "WTF" and "Interface" folders. navigate here Check out /r/wowguilds! /r/wownoob - A great resource for new players! permalinkembedsaveparentgive gold[–]Zatinox[S] 0 points1 point2 points 1 year ago(0 children)Holy shit thanks, I will add you if this wont work. pcvarious 57,660 views 1:10 Memory could not be read arma 3 fix - Duration: 1:37. 4NON1MOU5 7,709 views 1:37 World Of Warcraft Beginners Guide "Everything You Need To Know" - Duration: Wow Error 132 Fatal Exception Memory Could Not Be Read
I just GOT my PC about 4 days ago, i updated the drivers and it has been working fine UNTIL today. I lost at least 5 arena matches because of it.Also, I appreciate your concerns, but I cant keep playing like this. If none of those work then their support forum might be a better place to post, if able, since they have staff there. Check This Out I have also changed from DirectX11 to DirectX9 in the WTF folder.
Answer Questions Should i wait to get battlefield 1 or should I get it now, I'm bored out of my mind? Wow Error 132 Fatal Exception Access Violation Have you tried using Catalyst 15.7.1 drivers?We'd like to learn more about your crashing issue, please provide the specifics in a report here. Oh and agent.exe is located in C:\ProgramData\Battle.net\Agent if that helps.
Loading... The memory could not be "read". permalinkembedsavegive gold[–]Zatinox[S] 0 points1 point2 points 1 year ago(19 children)Hmmm, well I have been able to run WoD without problems with the new models and all on this. Wow Access Violation Crash Sign in here.
All related subreddits MovePad Plus - a resource for disabled gamers. I can tell you what tools to use to determine if your ram is actually fucked, they just take a really long time to run. My error, and those of alot of other people are: memory could not be READ.Anyway, i read through it all. this contact form Posting Permissions You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are
You might not need all the steps above but just try them. What can and should i do? _____________________________________________ This application has encountered a critical error: ERROR #132 (0x85100084) Fatal Exception Program: D:\Feenix 2.4.3 client\Wow.exe Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:00617532 The instruction at Program: C:\Program Files (x86)\World of Warcraft\Wow-64.exe ProcessID:784 Exception:0xc0000005 (ACCESS_VIOLATION) at 0033:000000013FBE8CEF The instruction at "0x000000013FBE8CEF" referenced memory at "0x00000000AD7022D5". HeelvsBabyface 124,159 views 5:20 Loading more suggestions...
somtimes it just takes 2 minutes to crash.I'm gedding really frustrated right now as it costed me several wipes, kicks from groups. Sign in 3 0 Don't like this video? I often like to keep this clean, so it wasn't really that bad. If the ram isn't the same speed/voltage things fuck up) Bad Ram (this is most likely what you're being hit with.
NO POLITICS. Narcismo 85 Goblin Rogue 6960 37 posts Narcismo Ignored 30 Dec 2010 Copy URL View Post Yeah, that "sollution" is bollocks, updated all hardware drivers and i'm still having the same had alot tonight. Transcript The interactive transcript could not be loaded.
Working... Sign up now!
© Copyright 2017 ngogeeks.com. All rights reserved.