Curse Facebook Twitter Youtube Civ 6 Wiki Help Careers Privacy Policy Civ 6 Leaders About Curse Advertise Terms of Service Civ 6 Guide Copyright 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.

Wow Crash Memory Could Not Be Read

TheLazyPeon 480,302 views 19:54 The memory could not be written error - 7 Possible Causes and Fixes - Duration: 1:22. This doesn't work at all.Went all the way back to older catalyst drivers. Wow Access Violation Memory Could Not Be Read Sign in to make your opinion count. Wow Error 132 Fatal Exception Memory Could Not Be Written Sign in to add this to Watch Later Add to Loading playlists...

WoW's trying to run something that it wrote to your ram and it couldn't get to it.) So, you MIGHT have some bad ram and that's what is fucking you up. Here is the log file from my error folder... Prev 1 2 Next 1 / 2 Go to Page: Join the Conversation Ignored Have something to say? Need Help? Wow Error 132 Fatal Exception Memory Could Not Be Read

Loading... Still having these errors. 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 Check This Out More discussions in Drivers & Software Where is this place located?CommunityAll PlacesSupport ForumsDrivers & Software 16 Replies Latest reply on Mar 28, 2016 5:59 AM by stonelight "Access Violation" - Memory

if i pay u then u need to fix it plz This application has encountered a critical error:ERROR #132 (0x85100084) Fatal ExceptionProgram: C:\Program Files\World of Warcraft\WoW.exeException: 0xC0000005 (ACCESS_VIOLATION) at 001B:0049765A Dinará Wow Error 132 Fix permalinkembedsaveparentgive gold[–]lntrn 1 point2 points3 points 1 year ago(13 children)Okay so your config settings aren't the problem which is good, that means when the game is loading it's not fucking you up there. Connect With ZAM © 2016 ZAM Network LLC Remember Me?

permalinkembedsaveparentgive gold[–]lntrn 1 point2 points3 points 1 year ago(18 children)I don't remember if there's a file that stores your video settings, but it seems like it's something along those lines.

coulnt find anything that worked :(Thanks though.mate turn of your computer an take out all ram meroy you have and insert only one and boot up your system and then try memory could not be "read" *Solved* error 132. Trending Now Gleb Savchenko Call of Duty Anthony Rizzo Breeders Cup Luxury SUV Deals Rheumatoid Arthritis Symptoms Garth Brooks Hulk Hogan Serena Williams 2016 Cars Answers Best Answer: What have you Wow Access Violation Crash Like Show 1 Likes(1) Actions Re: "Access Violation" - Memory Cannot Be Read (World of Warcraft) bamboostick Jan 25, 2016 7:21 PM (in response to bamboostick) I spoke too soon..

Seeing a crash when walking / flying etc etc? The instruction at «0x000000013F99F55E» referenced memory at «0x000000042D5A6F6C».The memory could not be «read».0xC0000005 (ACCESS_VIOLATION) at 0033:000000013F99F55E<:Inspector.Summary>DBG–ADDR<000000013F99F55E>(«WoW–64.exe»)DBG–ADDR<000000013FC6D4A3>(«WoW–64.exe»)DBG–ADDR<000000013FCB040C>(«WoW–64.exe»)DBG–ADDR<000000013FC58D8B>(«WoW–64.exe»)DBG–ADDR<000000013FC5B9B1>(«WoW–64.exe»)DBG–ADDR<000000013FC5C40F>(«WoW–64.exe»)DBG–ADDR<000000013FC47BFF>(«WoW–64.exe»)DBG–ADDR<000000013FC315CC>(«WoW–64.exe»)DBG–ADDR<000000013FA451D7>(«WoW–64.exe»)DBG–ADDR<000000013FA458B6>(«WoW–64.exe»)DBG–ADDR<000000013F391E77>(«WoW–64.exe»)DBG–ADDR<000000013F3CBF6B>(«WoW–64.exe»)DBG–ADDR<000000013F3CD1B0>(«WoW–64.exe»)DBG–ADDR<000000013F4D08A6>(«WoW–64.exe»)DBG–ADDR<000000013F37783F>(«WoW–64.exe»)DBG–ADDR<000000013F377FC1>(«WoW–64.exe»)DBG–ADDR<000000013F375361>(«WoW–64.exe»)DBG–ADDR<000000013F375D6C>(«WoW–64.exe»)DBG–ADDR<000000013F2FCFA8>(«WoW–64.exe»)DBG–ADDR<000000013F303CD9>(«WoW–64.exe»)DBG–ADDR<000000013FD01198>(«WoW–64.exe»)<:Inspector.Assertion>DBG–OPTIONSDBG–ADDR<000000013F99F55E>(«WoW–64.exe»)DBG–ADDR<000000013FC6D4A3>(«WoW–64.exe»)DBG–ADDR<000000013FCB040C>(«WoW–64.exe»)DBG–ADDR<000000013FC58D8B>(«WoW–64.exe»)DBG–ADDR<000000013FC5B9B1>(«WoW–64.exe»)DBG–ADDR<000000013FC5C40F>(«WoW–64.exe»)DBG–OPTIONS<><:Inspector.HashBlock> x64 RegistersRAX=0000000000000070 RCX=000000042D5A6F64 RDX=0000000036B42C48 RBX=000000002C0C5A05RSP=000000000023ECE8 RBP=0000000000000001 RSI=000000002C0C59EC RDI=000000000DE30680R8 =0000000036B42CA8 R9 =000000002F1072D8 R10=000000002C0C5AA0 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 this contact form Trollbane Turalyon Twilight's Hammer Vashj Vek'nilash Xavius Zenedar Reply Prev 1 2 Next 1 / 2 Go to Page: Dinará 85 Tauren Druid 3340 31 posts Dinará Ignored 24 Dec 2010

Crossing fingers, it's only been 2 days. Back this file up before deleting it, I don't remember if there's a default one created on startup or if you have to have one in order for wow to launch. Thread: How To Fix "Fatal exception" (ERROR #???'s) Basic Guide. permalinkembedsavegive gold[–]Zatinox[S] 0 points1 point2 points 1 year ago(0 children)Will try, thanks!