Video Card Freezes, crashes after Patch 2.4
by Ultimodragon | 25/03/2008 22:25:27![]() Blizzard, you changed something in WoW's interface for patch 2.4, and now it causes my video card to frequently and randomly Lock Up and crash windows. The first time this occured was about 45 minutes after logging into patch 2.4 for the first time. I was in Shattrath, and my curser reset to the middle of my screen and become stuck as it was not accepting any input from the mouse. As i shut down WoW there was some very funking flickering and resisizing by my videocard as it returned to the desktop. Upon restarting WoW the game Froze as i first appeared in Shattrath, and then my computer bluescreened. The message said that there was a video error and the driver for dxdiag was stuck in a continuous loop, and so Windows had been shut down. I've never seen this error before for Any of the many games I have played with this Videocard, an ATI Radeon 9200+. I was able to successfully restart my computer and log back into wow. However, upon returning to the game i saw that some sort of funky buff countdown timer had been added to every buff on my display, so I know some changes have been made to the graphical interface for patch 2.4. I then made my way to the new Throne of Kiljadean area in Hellfire Penninsula. Where I was able to participate in the madness for about 10 minutes, untill again my display froze, but this time my computer just simply restarted. I have had this happen before while running games that are unstable on older video cards such as Civilization 4. However, this has never happened to me before while running WoW. Not once, not even in highly populated, Ram or graphics intensive areas. My computer is running cool, and well, very well. It's simply that WoW's client now runs unstably on my videocard after patch 2.4. If this problem isn't resolved, I'll have to quit WoW, as i cannot have it crashing or restarting on me every 30 minutes. |
by Datth | 26/03/2008 15:27:13![]()
If you can make it inside the game, you can simply type these lines to make them active: /console pixelshaders 0 /console specular 0 /console m2useshaders 0 I'm not sure if M2UseShaders will override the other two settings but it's safer to throw that in. Tell me if it works or not and I'll forward the reports on to the devs. For ATI Radeon 8500-based GPU owners (includes 8500, 9000/9100/9200), make sure you're at Catalyst 6.11. |
by Datth | 26/03/2008 15:31:27![]() Welcome to partial torrents. If another torrent uses the same file that the previous torrent was downloading, it picks up from there. |
by Datth | 26/03/2008 15:34:27![]()
You have another issue. I'm not sure why you're in the thread, but try downloading the patch you need from http://us.blizzard.com/support/article.xml?articleId=21079 Please do not hijack threads with offtopic issues. |
by Datth | 26/03/2008 15:43:22![]()
1. You're not in the game. 2. You're not using your video card for anything except the Windows GDI 3. If you're blue-screening on a patch download, your network driver is the culprit. |
by Datth | 26/03/2008 15:55:53![]() The game crashing should not make it revert to an earlier version. Only a System Restore or a similar utility is capable of that. You really should make a new thread. Continuing to post on this thread will make it a lot harder to track down shader-specific crashes. The Radeon 9600 isn't even on the same class as the 8500/9000/9100/9200. It's quite a leap above them, using shader model 2. |
by Datth | 26/03/2008 16:45:45![]()
That would be a different crash. Please post in a new thread. The error log in the window would help. |
by Datth | 26/03/2008 16:50:59![]() Reava, Go to the last line (SET UnitNameCompanionName "0"), then hit Enter. Type in the commands. It would look something like... SET UnitNameCompanionName "0" SET Pixelshaders "0" SET Specular "0" SET M2UseShaders "0" Save the file |
by Datth | 26/03/2008 17:24:05![]()
You're in the wrong thread if you're missing ground textures. Update your motherboard chipset drivers. http://www.playtool.com/pages/chipsetdrivers/chipset.html If you have PC Cillin antivirus installed, it's known to cause symptoms like this. Add WoW.exe or the entire World of Warcraft folder to your exclusion list. Please post in another thread. |
by Datth | 26/03/2008 17:30:59![]()
You did not post anything about your system specs. http://forums.worldofwarcraft.com/search.html?forumId=11110&charac This thread is being reserved for Radeon 9200/9100/9000 and 8500 users. It may possibly extend out to other DirectX 8 family cards if there is an issue with the code to the old shader models. Please post more information about your system if it matches that. |
by Datth | 26/03/2008 17:35:49![]()
You did not post any information about your system, nor the message in the blue screen. Your issue may not be related to this thread. http://forums.worldofwarcraft.com/search.html?forumId=11110&charac |
by Datth | 26/03/2008 18:19:25![]()
You need to update your Mobility Radeon drivers to Catalyst 6.11. We will test desktop equivalent cards on that driver and nothing else. If your manufacturer does not provide you those drivers, look up DH Mod Tool or Omega and get the equivalent drivers. It's not supported but it's the only way to update an old Mobility card. |
by Datth | 26/03/2008 19:49:47![]() You have a different card and a different issue. Update to Catalyst 8.3 or higher. Make a new thread if you continue to have issues. |
by Datth | 26/03/2008 20:00:37![]()
We're not sure yet. We tested a general Windows XP SP2 system with a 9200 but did not get it to crash. What areas are you all in? If you can, copy and paste your config.wtf file along with the character's location. More information (like how long you can stay in the game before you crash) would be helpful. |
by Datth | 26/03/2008 22:01:46![]() |
by Datth | 26/03/2008 22:50:11![]()
You're on the PC forum. Try heading over to the Mac forum to see if there are any known issues for your setup. |
by Datth | 26/03/2008 22:57:08![]()
If possible, please post the blue screen message. If the system is restarting, stop it from doing that.
|
by Datth | 26/03/2008 23:13:28![]() Wulfdog, please post the entire error log. I cannot view it if it is only a portion of one. |
by Datth | 26/03/2008 23:28:08![]()
Why are you in a thread about video cards and crashing, when you just have a patching problem? Run the repair utility to have it check your current install. If all else fails, reinstall. |
by Datth | 26/03/2008 23:48:42![]() |
by Datth | 26/03/2008 23:57:34![]()
That's a video card communication issue. It can be caused by any of the following: mobo <--> video card communication died somewhere (bios update and chipset driver update should take care of this), PC Cillin antivirus is preventing some of the game data from being loaded, or your power supply is insufficient for that type of system. You'll want to post on another thread if you continue to have issues. |
by Datth | 26/03/2008 23:58:16![]()
Wrong issue. Post in another thread or make a new one. |
by Datth | 27/03/2008 15:39:47![]()
FYI, all memory operations are dealt with via the memory controller and the memory sticks themselves. A software cannot do something outside of that scope. If WoW does something invalid, you'd hit an Error 132, not a system freeze. |
by Datth | 27/03/2008 16:37:52![]()
That may not be surprising. World of Warcraft is making use of the shader hardware, which your 7000M lacks (both in quantity and horsepower). Thanks for the report. I'll keep this in mind for lower-end and integrated cards. |
by Datth | 27/03/2008 22:46:05![]()
Did you try a memory test with all 4 sticks in? Otherwise you describe my home system and I haven't had a single freeze yet. |


Recent Blizzard Announcements