• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

"Read Errors" playing World of Warcraft.

.Lethal

.Lethal

.Lethal

Soldato
Joined
8 Jun 2005
Posts
8,435
Location
United Kingdom
Hi,

I have been getting random crashes while playing World of Warcraft where the game would just instantly close and give me an error report basically saying it is due to "read error" of various objects ie maps, characters not loading the err graphic (or whatever it may be it is trying to display).

I have an 8800 GTS 512mb card by BFG Tech and I am aware of there RMA process BUT this is a card I have received back from BFG a year or so ago as a refurb as my original GTS had problems where it was actually crashing my PC.

My problem is that I am don't know if this makes sense or if this is my graphics card at all. I don't want to send it in and have them tell me its fine and you now have to pay some fee for wasting our time.

I bought brand new hdds last wk from OcUK thinking read error was my HDD which was not the case. I have formatted and installed the latest drivers, I have installed WoW by various methods to ensure it was not a bad instalation. Memtest states there is no problem with my RAM. I have never overclocked anything on the PC or changed settings in the nVidia control panel.

So I'm at the point where I believe the next step is to return the card to BFG Tech as an RMA.

Anyone have any input? It would be MUCH appreciated.

Thank you.
 
mmj_uk said:
Is your system Prime stable?

It definitely sounds CPU/memory related to me.
Click to expand...

I'm not sure what you mean by "Prime stable"

I have an Intel Q4400 quad core and 4gb RAM (4x1GB sticks).

The only changes I have made in the BIOS was from an older thread where I set the timings to match exactly what my memory stated.

I also have Intel speedstep disabled in the BIOS. I think thats pretty much it to be honest.

While I am glad you don't think it is my GFX Card I am very curious on how to proceed in identifying this problem.

Thank you.
 
Damonic said:
I'm not sure what you mean by "Prime stable"

I have an Intel Q4400 quad core and 4gb RAM (4x1GB sticks).

The only changes I have made in the BIOS was from an older thread where I set the timings to match exactly what my memory stated.

I also have Intel speedstep disabled in the BIOS. I think thats pretty much it to be honest.

While I am glad you don't think it is my GFX Card I am very curious on how to proceed in identifying this problem.

Thank you.
Click to expand...

You need to run Prime95's torture test for a couple of hours, to see if its prime stable
Just google prime95, I'm sure you'll find where to get it.
 
I had similar problems all of a sudden in WoW.

It turned out that my RAM was on its way out and WoW is very sensitive to memory errors.

As suggested, run Prime or try memtest as that was what narrowed it down to the RAM for me.
 
antonusklesk said:
I had similar problems all of a sudden in WoW.

It turned out that my RAM was on its way out and WoW is very sensitive to memory errors.

As suggested, run Prime or try memtest as that was what narrowed it down to the RAM for me.
Click to expand...

Been thinking this all afternoon, ordered some brand new ram.
 
I get the occasional crashes also but it just a memory issue i just upped my voltage to my ram as it was set at 1.8v when it should have been 2.1v seem to of cured it now
 
stuartbat said:
I get the occasional crashes also but it just a memory issue i just upped my voltage to my ram as it was set at 1.8v when it should have been 2.1v seem to of cured it now
Click to expand...

Until my new RAM arrives tomorrow I reset the values in my BIOS for the RAM, I was given set values but clearly they don't work. Last night I had no crashes but the settings are "loose" now so I'm not happy with it.

I will set the proper timings when the new RAM is delivered tomorrow.
 
Dont quote me on this but wont your memory timings always differ slightly with each CPU, the speccs are a typical guide.

So forcing them to a specific value could be causing this? or there undervolted maybe?
 
If it's a ".adt" map error you repeatedly get, there have been numerous bugs since 3.1 involving map load crashes and instance load crashes.

If it isn't a RAM fail, it could well be this.
Relevant official wow threads with info on the .adt errors can be found here:
...or not.. the .adt help threads have vanished. Blue efficiency at it's finest -.-

Posting a copy pasta of the specific wow error would help, and tbh, try taking this to the official wow tech support forums as well (If you haven't already) - http://forums.wow-europe.com/board.html?forumId=11079&sid=1

My particular solution when I had .adt errors was a complete cache, WTF and variables nuke.
 
The tech support forums for WoW both in US and Europe are awash with people suffering Error 134s which usually relate to *.adt files being unreadable.

Unfortunately, all you get are stock requests from their guys to disable addons, post an error log and your machine specs. Usually once youve done that you get no actual help.

Ive personally run 6 hour prime95 and memtests with zero errors but running under directx will still generate these errors.

The new solution to the problem which is helping a lot of people, is to run the game in OpenGL mode - its a bit slower, and prone to mouse lag, but it appears to be solving a lot of peoples issues.

This, and the sheer number of people reporting these errors, leads me to believe theres a gremlin in WoWs use of Directx.

Also try turning down some of the graphics settings - in particular terrain distance. I can force my game to crash merely by setting this high and then attempting to fly out of Dalaran - crashes every time.

Hope this helps a bit
 
Just an update here.

I installed the new RAM last week on Friday and I can confirm I have had ZERO problems since. It definately was a problem with my RAM, even though about 2 months ago I had ran a stress test with Memtest which gave me a report of no problems.

FWIW I had cleared WTFolder, CacheFolder etc etc. I even formatted entirely, fully reinstalled (Various ways I tried installing, I even bought a new copy of WotlK thinking it was a dodgy instalation).

antonusklesk nailed it when he said WoW is very touchy with RAM.

Saying this I can't recall a problem when I reset the values of my previous RAM, however, they were not set at the correct settings and had reduced PC performance (Yes it did make a difference!).

It was various map/model errors. I can't remember if it was .adt error but the extention is "familiar" when I red that. To be honest I was getting crashes every evening I just stopped reading the error after a while because it had become the norm.

If your having errors like I did, I suggest new RAM.

Also (sorry to go on).
I would like to think I was clued up (at the time) regarding my previous RAM and the specific settings I had in the BIOS. I never ever had problems with my RAM until the crashes with WoW while into WotlK in the last 2 months. I think patches are part of the problem being so sensitive to memory errors forcing the game to crash.

unknownsock - not quite.
 
ooo this may be what's causing the missus's wow problems, time to swap out the ram. Thanks for the heads up :)
 
Run repair.exe in the wow folder, get it to check the files for error's. I did this and it told my installation was so corupt i needed to reinstall wow from scratch :( lol.

Been getting a lot of these read errors on it recently, so guessing the last patch messed up my install badly.
 
You must log in or register to reply here.
Back
Top Bottom