- Joined
- Aug 26, 2008
- Messages
- 639 (0.10/day)
- Location
- Fresno, CA
| System Name | MFCJA |
|---|---|
| Processor | Intel 4770k |
| Motherboard | MSI Z87-G45 |
| Cooling | Intel Liquid Cooler |
| Memory | Corsair DDR3 4X4GB |
| Video Card(s) | MSI GTX 770 |
| Storage | 120GB SSD/1TB |
| Display(s) | 23" Acer H233H |
| Case | Corsair Mid Tower |
| Power Supply | Corsair TX850M |
| Software | Windows 7 64 bit |
Looking for some help here.
I have searched through the net over the last few days for a solution to this seemingly notorious error# 132. There are threads all over the net about this. I have done what most of them offered as possible solutions and have made absolutely no progress. I recently got in contact with one of Blizzard's staff members through their forums and he also has yet to find a solution. Apparently, this is happening to quite a few people with rigs of my like. Someone actually post in the same thread nearly minutes after I did expressing their similar situation. 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.
Please, help me figure this out.
Factors to consider:
#1 It seems as though this error may be prominent among ATI 58xx series users. As you can see in my system specs, I own and utilize a diamond 5850.
#2 I am currently running 10.9 drivers. I have not found a driver that has been to my liking so I settled on the latest available. 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. When the system starts, I have to open CCC and click "Ok." It is at this point that the overscan feature enables itself again. The exact same event happens whenever I exit or quit a game.
#3 The error says clearly [The memory could not be "read."] I have extensively tested my RAM and know for a fact that it is not the culprit.
#4 It seems as though myself and two other individuals who are experiencing this error all have on board realtek audio. There are many more similarities between or systems but this is the only likeness present in all three of our rigs.
#5 I am not sure if this is of consequence but this rig is relatively new.
These are the factors I consider to be worth highlighting at this time. I am certain that there are more. If you have any information pertaining to this error, please enlighten me. I have payed for a 3 month subscription and have yet to play over 15 minutes.
I have searched through the net over the last few days for a solution to this seemingly notorious error# 132. There are threads all over the net about this. I have done what most of them offered as possible solutions and have made absolutely no progress. I recently got in contact with one of Blizzard's staff members through their forums and he also has yet to find a solution. Apparently, this is happening to quite a few people with rigs of my like. Someone actually post in the same thread nearly minutes after I did expressing their similar situation. 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.
Please, help me figure this out.
Factors to consider:
#1 It seems as though this error may be prominent among ATI 58xx series users. As you can see in my system specs, I own and utilize a diamond 5850.
#2 I am currently running 10.9 drivers. I have not found a driver that has been to my liking so I settled on the latest available. 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. When the system starts, I have to open CCC and click "Ok." It is at this point that the overscan feature enables itself again. The exact same event happens whenever I exit or quit a game.
#3 The error says clearly [The memory could not be "read."] I have extensively tested my RAM and know for a fact that it is not the culprit.
#4 It seems as though myself and two other individuals who are experiencing this error all have on board realtek audio. There are many more similarities between or systems but this is the only likeness present in all three of our rigs.
#5 I am not sure if this is of consequence but this rig is relatively new.
These are the factors I consider to be worth highlighting at this time. I am certain that there are more. If you have any information pertaining to this error, please enlighten me. I have payed for a 3 month subscription and have yet to play over 15 minutes.
. It is very frustrating. Especially when I am running a better than average computer here that I spent quite a bit of time and money on. As I had said earlier in my thread, I believe that the culprit may be as simple as a hard disk issue. I stated that my wow folder is currently seated in my storage drive and not on my main OS. This seems to be a common trait among those who experience the dreaded error #132. I don't have the money to test this theory at the moment (by buying another SSD of larger size) but I am interested in hearing what you all might have to say about this. Does my conclusion make sense? Any more suggestions as to what I could do so that I can run wow at decent settings?