Jump to content

  •  

  • iBotModz CBox


    Photo

    error 132


    • Please log in to reply
    5 replies to this topic

    #1 jordandipaolo

    jordandipaolo

      Private Grade 2

    • Members+

    • 84 posts
    • Joined: 17-April 08

    Posted 26 June 2008 - 03:37 PM

    when i go to play wow i get an error 132 any help???

    #2 subs_55

    subs_55

      Defender Of Whatever Needs It Most

    • VIP

    • 505 posts
    • Joined: 26-February 08
    • Location:at home, maybe

    Posted 26 June 2008 - 03:44 PM

    i would google it. i doubt very many ppl on this site play wow.

    #3 jordandipaolo

    jordandipaolo

      Private Grade 2

    • Members+

    • 84 posts
    • Joined: 17-April 08

    Posted 26 June 2008 - 03:54 PM

    i tried that and yea thats true

    #4 SmokiestGrunl

    SmokiestGrunl

      Australian Retired Staff

    • Retired Staff

    • 3,888 posts
    • Joined: 02-September 07
    • Gender:Male
    • Location:Australia

    Posted 27 June 2008 - 12:49 AM

    MOVED FFS!

    I play wow but I think it sucks.

    The 132 problem is 99% unique to WoW. The exception being 1 or 2 people who simply had bad sticks of RAM that caused the same error in one of the new top of the line offline games.

    It isnt a software problem. Reinstalling WoW wont fix it, removing mods or having clean savedvariables wont fix it (thats Blizzards default cop out first answer for most problems), etc.

    I have read page after page on the WoW boards and argued with the official tech board representatives over it. The occurance of the error is really pretty random. There doesnt seem to be an identifyable set of game circumstances that cause it reliably. I ran the game for nearly a year without ever having an error. Then 3 months after playing on a new machine, I started getting them. Well that machine went to hell and I had to gut it. New HD, PSU, & MB. Same CPU&RAM. After all the clean installs, new hardware, etc... I got one the very first day I booted it up. I still get them occasionally, but with no real frequency.

    Also sadly the std memory testors will not identify any problems in the RAM unless the RAM is just simply bad. WoW techs admit that unless the RAM is just bad the std testors most likely will not reveal any problems with RAM getting the 132 erros.

    OK. So what exactly is my point? After about 3 months of arguing over this, I think it really is 1 of 2 problems.

    1) overheating of ram, cpu, or mb chipsets
    2) the RAM that people are using is not of the *quality* that will run WoW as it was ment to be.

    This is my opinions on the matter of RAM: All RAM is not created equal. A stick of RAM may not be *bad* in that it can preform all or 99% of the normal functions required by general computing with few enough errors that the system can ignore or compensate for them.

    But the fact is that all RAM contains some degree of *badness*. Its just part of the manufacturing process. I call them deficiencies. In normal computing, there doesnt seem to be much of a difference in using *performance RAM* vs *budget* RAM.

    BUT, WoW and similar MMOs are not normal computing. If you dig through all the WoW tech forum discussions, their stance boils down to a statement that WoW is a very demanding cutting edge piece of software that tends to bring out deficiencies in normal hardware. Sounds like a big cop out right? *shrugs* I gave up arguing with them over it.

    So, make sure your RAM, CPU, MB chipsets are not overheating. If the error happens enough to make game play intolerable, and you have the cash... invest in some performance RAM. This is not the answer I want to hear either, but its the ones I have come to conclude.

    If you have a cheap motherboard that is known to have some performance problems that could definitely affect things especially if you overclock. There are several threads where people fixed thier 132 problem by underclocking the FSB by 1 mghz or changed RAM CAS slightly and fixed thier problems. Even though they did not mention overclocking, I think they probably were which made thier system a bit unstable.

    If I had the money, I would buy a pair of Kingston performance RAM myself. But right now my 132 are infrequent enough to not worry about it.



    #5 jordandipaolo

    jordandipaolo

      Private Grade 2

    • Members+

    • 84 posts
    • Joined: 17-April 08

    Posted 27 June 2008 - 07:02 AM

    trust me i used to hate wow and then when i was at my friends house when he was sleeping i had nothing to do so i started to play

    #6 us marines 479

    us marines 479

      Corporal Grade 1

    • Members+

    • 117 posts
    • Joined: 19-June 08

    Posted 27 June 2008 - 05:19 PM

    Dosent matter if you play wow or not i belive it takes quit a bit of ram and a little more detail My best guse is you don't have enopugh ram or it may be somethgin else but please send a reply on the following

    Everythign the mesage says
    how much memory you have
    how much Ram you have

    And I'l be able to help you out more