WoW freezes whenever I go to far North

[kingslayer]

I don't lag, I don't freeze (except when I go past Razor Hill (North), and I don't have any other problems.

When I go past Razor Hill and start the trip to Ogrimmar I always freeze and it takes me like 5 minutes just to have the ctrl + alt + delete thing to work.

My realm = Gorgonnash... is it a glitch or something? My computer? Something else?

It's really annoying... specially since the trainer for skinning = there.

First time it happened I got to place with weird metal machines on ground... set WoW back up and tried to go up... didn't work. Third time I didn't even get as far... and the last time I barely got out of Razor Hill. It seems like it keeps shrinking... if I don't get this problem fixed the game won't be enjoyably at ALL. I'm stuck in low level places with lvl 8 creatures max basically.

Maybe this has happened before? I don't have time tonight to search the forum for other problems like mine... but I will tomorrow.

Just read this on WoW Support... under bugs... "how to tell if my problem is a bug"... I don't really understand it though... can any1 clarify it for me?


For example, if your client crashes while entering a certain area on one of your characters, but not for anyone else, chances are this is an issue with your WTF, Interface, and WDB folders, and can be resolved by simply going to your World of Warcraft folder and deleting them.

Example: What's WTF and WDB folders?

[Kalos]

The WTF and WDB folders are directories contained inside the main directory of the game to where you installed it upon your hard drive.

Let's get some knowledge on your computer, like how much ram and what processor you are running.

[theshard]

The WTF and WDB folders are directories contained inside the main directory of the game to where you installed it upon your hard drive.

Let's get some knowledge on your computer, like how much ram and what processor you are running.

If he has played fine up to this point, I can't think of anything (from a hardware issue) north of Razor Hill that would cause that problem. Except for maybe the brewfest thing. I would try deleting said folders and try again.

To find them search the hard drive for 'program files', 'world of warcraft', then the said folders, delete them and start game.

Good Luck.

[Kalos]

If he has played fine up to this point, I can't think of anything (from a hardware issue) north of Razor Hill that would cause that problem. Except for maybe the brewfest thing. I would try deleting said folders and try again.

To find them search the hard drive for 'program files', 'world of warcraft', then the said folders, delete them and start game.

Good Luck.
If I may, I can think of several hardware issues that could be cropping up in this region. Plus, it canot hurt to actually get these system specs down. We blundered through one problem without them, I think it is honestly time we got these facts nailed down. We might even spot something.

As for an example hardware cause for this problem: Ram. On the approach to Ogrimmar the ram is more heavily loaded than in the majority of Durotar, more sectors of the ram boards are used. If a bad sector happens to be in the ram, near the higher end, and it failed to write properly, that would crash it. The reason why the game wouldn't crash all the time is that said sector of ram is only called into duty in this perticularly busy section of the game. Hence all is fine until the approach of Ogrimmar, where the problem rears it's head. There is one, quick, simple hardware based scenario to which could be the root. Just because you don't know of them doesn't mean that there cannot be hardware related causes responsible.

I suspect the ram, either the sticks themselves or on the graphics card (worse), to be a possible cause. On the software side, drivers could be an issue too.

[kingslayer]

It's fine now... just had to delete the files I guess... or maybe my comp was just acting strange that day... who knows.