hasemtogo.blogg.se

1. #Firestorm wow error 132 install#
2. #Firestorm wow error 132 driver#
3. #Firestorm wow error 132 windows 7#

If you use xp then i can't help i don't remeber xp much now lol If none of the above helps then i realy have no idea why some people get the 132 error. Remove and addons you may use and dont even put them in the interface folder. I would also uninstall wow and remove all traces of it, Even if installed to programfiles like me it will leave stuff in the public documents folder.

#Firestorm wow error 132 install#

I install wow to Programfiles(x86), Not that you did but i don't touch the virtual memory settings i leave that to windows.įrom what i have seem on the wow forums most people who get that error seem to install wow to there backup drives rather than there main drive and it makes me wounder if this is part of the problem. I turn of user account control as i don't find it usefull and it pisses me off.

#Firestorm wow error 132 windows 7#

Not that it will help but if your running Windows 7 this is what i do. Never had a problem with wow and like others have said people with the same hardware might not have problems but some people do. Intel core 2 duo E6550 overclocked to 2800mhz.Ĥgig corseair XMS2 1066mhz 800mhz (Don't ask) I have payed for a 3 month subscription and have yet to play over 15 minutes. If you have any information pertaining to this error, please enlighten me. These are the factors I consider to be worth highlighting at this time. #5 I am not sure if this is of consequence but this rig is relatively new. There are many more similarities between or systems but this is the only likeness present in all three of our rigs. #4 It seems as though myself and two other individuals who are experiencing this error all have on board realtek audio. #3 The error says clearly I have extensively tested my RAM and know for a fact that it is not the culprit. The exact same event happens whenever I exit or quit a game. When the system starts, I have to open CCC and click "Ok." It is at this point that the overscan feature enables itself again. I am having a rather strange issue which has reportedly been plaguing many ATI users: my overscan setting in CCC will not save upon system reboot or during the exit of a game.

#Firestorm wow error 132 driver#

I have not found a driver that has been to my liking so I settled on the latest available. As you can see in my system specs, I own and utilize a diamond 5850. #1 It seems as though this error may be prominent among ATI 58xx series users. Seeing as how Blizzard is even having a tough time with this one, I thought that I would turn to the extremely knowledgeable and helpful users of the techpowerup forums. Someone actually post in the same thread nearly minutes after I did expressing their similar situation. Apparently, this is happening to quite a few people with rigs of my like.

I recently got in contact with one of Blizzard's staff members through their forums and he also has yet to find a solution. I have done what most of them offered as possible solutions and have made absolutely no progress. There are threads all over the net about this. I have searched through the net over the last few days for a solution to this seemingly notorious error# 132.