Ayahime | Error #132 after upgrading PCThu, 26. Jan. 2012 19:01 GMT Hi, I have recently(2weeks ago) replaced my old CPU/mobo/Memory with: I7 2600K,gigabyte GA-Z68AP-D3, 8GB Corsair Vengeance Black LP (2x4GB) DDR3. I have a decent 800W PSU so that is not a problem. Ever since then, I have random crashes from WOW which has never happened before. Other games such as Starwars the old republic, BF3 crashes much more often, sometime with display artifact, random flickering even blue screen. I was using a 830MHZ 560ti from Asus for the past 6month, and I kept getting the TDR error "Nvidia driver has stopped responding ..." even when I was using only firefox. After countless tries with different drivers 275.xx/280.xx/290.xx, the crashing stays. Therefore, I thought since my 560ti was crashing at destop before I upgraded my PC, I replaced the graphic card with a MSI 570GTX today, installed 285.62 driver with the clean install option ticked, at a intensive 25HM Ultraxion last phase(full effect 8x multisample), my game crashed again. Now, I have stress tested CPU prime95/ full Win7 mem test/ stress test GPU MSI Kombustor/graphic mem test, All tests returns no error. So I went back to the error log, I found the WOW only started crashing after I have changed my CPU/mobo/mem, and all the error are with the similar heading: 1: Today's crash with 570 GTX graphic card. ERROR #132 (0x85100084) Fatal exception! Program: C:\World of Warcraft\WoW.exe ProcessID: 4232 Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:0184523C The instruction at "0x0184523C" referenced memory at "0x577C4488". The memory could not be "read". 2: 12-01-2012's crash with 560ti GTX This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! Program: C:\World of Warcraft\WoW.exe ProcessID: 2140 Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:6DE826E3 The instruction at "0x6DE826E3" referenced memory at "0x00000004". The memory could not be "read". I checked all other error logs this part "0xC0000005 (ACCESS_VIOLATION) at 0023:xxxxxx" is always the same. Since I have replaced the graphic card and I am still getting the same error, and this error only appeared after I upgraded my CPU/mobo/mem, it is hard to determine what is wrong. It would be very helpful to me if you can tell me which part of the function is this related to (like graphic driver?memory dump?) so I can figure out exactly where is wrong with my newly upgraded PC, so I can replace/return or reinstall accordingly. |
![]() Lurdlespor | Error #132 after upgrading PCFri, 27. Jan. 2012 09:01 GMT Hi there, Can you please switch to Directx 9 mode, and then if you get a crash in that mode please post the new error you receive? I ask because it's harder to see what's causing the issue when the game is running under the Directx 11 API |



