How do I go about fixing these sort of WoWErrors?

Well, let me start from the beginning. I'm running Windows 7, 512mb 8500gt graphics card, fairly high settings, 2g DDR2 RAM; basically a decent computer (imo). Certain zones of Northrend - mainly Grizzly Hills and Howling Fjord, although certain places with a lot of terrain everywhere (large cliffs around parts of Borean Tundra) - cause my game to suddenly remove my entire UI and all objects from the screen besides the terrain and skybox until I turn the camera a different direction, away from most of the objects.

At first I thought it was the (ridiculous?) amount of trees in Grizzly Hills and Howling Fjord causing this if I pointed my camera at them while flying over them a decent height, but the same issue started happening while flying over certain mountain-like patches of Borean Tundra. My game slows to a grueling 3FPS, the UI and objects disappear, and if I don't turn my camera correctly or quick enough, I get an INT_DIVIDE_BY_ZERO #132 error.

I'm not sure if my graphic settings are just too high to be roaming Northrend with; on a different yet somewhat related note Dalaran almost always freezes my game by trying to load everything that's in the city anywhere from immediately teleporting into the city or spending a couple of minutes on the bank steps waiting for the player models to load - I don't know if that's related to how many addons I run and my rather small amount of RAM in comparison or if this is also a graphical issue but Northrend is just a terrible place for me to try to be in the majority of the time because of these issues I'm experiencing.

If you need me to provide you with certain specifications or more information about these issues I would be glad to, as long as you'll at least attempt to help me after it is provided. :D

Hi Georgecarlin,

Divide by zero errors are usually sound-related problems. Do you have a full error log available for us to look at?

You won't really like it if it's not a sound crash. A sound one is an easy driver update to get it fixed, but the affected sound drivers date back before Windows 7's time. For other cases, you're looking at really rare cases of an addon failing or the more rare one where a hardware failure somewhere makes the processor think that it's dividing a number by zero. That's not fun to try and detect. A program such as Prime95 being ran as a stress test overnight might uncover any potential basic issues you might have.