TalkingSoft.com Forums: RADEON 9800 SE 3D game crashing problem - TalkingSoft.com Forums

[attachment=136:attachment]I have a radeon 9800 se 128 mb and i exsperance system crashes while useing anything that uses grafix games ect eg when i start up world of warcraft and get to the loading screen wow error apears and says violation of blah blah and it says the problem was in the WOW.exe as of games such as quake 3 while i play error message apears cannot contine quake 3 and allso says it the quake3.exe i hav tryed down gradeing the drivers to a lower verson and reinstalling windows but it still apears? please help

It appears from the screenshot that you are using Windows XP.

My first choice here would be to visit
http://forums.worldofwarcraft.com/thread.a...mp=1#post308254
which is a sticky at the WorldofWarCraft forums site dealing with Error 132 information. (Your situation is not new or uncommon, at all.)

There are other postings to Error 132 problems on the first page of the forum you may want to check out as well. The forums link is http://forums.worldofwarcraft.com/board.as...ow-tech-support

After familiarizing yourself with the general description they have there, I think you should consider the conclusion that a user came to last fall, that the most common ultimate cause of the problem is overheating of system components. Blizzard points out both the excepional levels of system utilizaton that WOW demands, and the degree to which the software is dependent on the hardware maintaining system timing to standard specifications while using multiple hardware components.

Quoting from the WOW forums thread cited before:

"World of Warcraft is an enormous seemless (sic) world, with no level loads. The only time you see a loading screen is either when you log in, or when you change continents (on the ship or zeppelin). This means that we are constantly uploading textures to the graphics card and loading terrain and scenery from disk. WoW exercises the data bus heavily. All this activity falls to the northbridge chipset to process. The fault can lay in many places: mismatched RAM, overclocked or improperly timed RAM, RAM not supported by the MB's BIOS, older chipset drivers, older graphics drivers, older BIOS, defective RAM, overheating of the CPU, overheating of the GPU, even overheating of the northbridge chipset itself has been found to be at fault. Many, if not all, of these problems did not expose themselves in games that were more minimal with their bus traffic, such as games with level loads.

About the only thing that we could do to reduce the frequency of the crashes on systems that exhibit these problems would be to cripple our use of the data bus (only load a limited number of textures at a time, reduce the frequency of disk reads, etc). The net effect of this would be more frequent lag and drops in frame rate. We are considering this as an option, so that Tech Support could have it available as a debugging tool when assisting customers experiencing frequent crashes. "

. . .

"The game software has no knowledge of memory timing, it expects its reads and writes to be executed faithfully and without error.

I'd be really happy if someone could write a memory tester that exercises the machine in the way that WoW does, with simultaneous GPU, CPU, sound, network and disk traffic."

Soooo, it is known that WOW both pushes the limits of your hardware, and imposes tight timing demands which overheating of the system can cause to fail. Doing everything you can to cool your system, starting with a thorough inspection and cleaning, reseating of components, etc. would seem appropriate as first steps in attempting a repair.

If those measures do not do the job, you can follow up on some of the hardware component and software settings items mentioned in the forum discussion.

For a good discussion of system cleaning in this context, in addition to a couple of notes in the forum thread cited, you could look at Googles cache of postings by ""Horace" on the forum.

Google Cached WOW postings Error 132 - Horace

ty verry much that helped alot

Thanks for the thank you. It is an interesting problem, and I enjoyed the research. I hope you get WoW running.

If I had the resources and skill, it looks like WoW might make a good benchmarking tool itself - put a system under heavy WoW loading and see how long it takes to produce Error 132 due to overheating.