Kalim! Hulp!

[Skaara]

http://img.photobucket.com/albums/v187/Skaara/Error.jpg

[Berae]

memtest.org

[Kalim]

Yup, give memtest a try.

http://www.memtest.org/download/1.65/memtest86+-1.65.iso.zip

Unzip that file, and then use program like Nero to burn the .iso image to the cd. Make sure to burn it as an image and not as a file. If this doesn't make itself clear, then just tell me what burning program you use and I can step you through it.

Then restart the computer, and figure out what button you have to press to get into your BIOS in order to configure the computer to boot cd before the hard drive (this is necessary for the memtest cd to do what it's suppose to do).

Once you set it to boot from cd, restart the computer again, and then have memtest run it's diagnostic at least once to see if it errors. If it doesn't error, have it run another 5 or 6 more tests (it'll take a while.. maybe have it go while you're not doing anything or overnight) just to confirm.

If it errors, then it might be your ram that is causing the wow error. To really conclude if this is the case, take out the ram stick and put in a different ram stick and then run either memtest again or wow, and see if it explodes yet again. If it doesn't, be in the market for a new ram stick =P. If it does.. you're still in the market for a new ram stick!

Good luck, and if the ram does pass the memtest and yet still causes errors with wow, keep me updated and I'll see if there are any other reason it might be happening.

P.S. It can still be a ram problem even if it's only one program that is critical erroring. This is because depending on the program, it has a different way of utilizing the ram, or sends different type of bytes to the ram that other programs may not be doing. That is why memtest is pretty good for diagnostics, because it generates code and feeds it to the ram and then attempts to reclaim the code. Somewhere in the process it does random feeding and the more time you run it, the more times you can be sure that the ram is faulty or not.

[Trevlen]

Dude.. i have been plagued by this for 8 months. I have 544MB of error files. Have run memtest, changed vid cards, updated all drivers, changed power supplies, turned off all mods, ran in wondowed mode, turned off sound, chaged memory, reseated processor, reinstalled wow many times, reformatted. Done really everything but replace my MB. Still get em, Sometimes twice a night, sometimes 15 a night.


When you see:

Trevlen has gone offline.


That is the EXACT picture i get to look at that makes me beat my head on my desk.

So uhhh Good Luck, i can't find the fix.

[Kalim]

Replace the MB if the problem keeps happening. It might be the bay that you put the ram in on the MB that is malfunctioning in the transport of data.

Hate it when it's something essential as a MB that might be the culprit >.<.

I hate my MB cause I can't put two ram sticks in it or it will error... >.> it doesn't if I put the same stick(s) in the other slots, but as soon as I put the two of them in at the same time, it fails memtest... >.> It still makes me boggle and I gave up trying to figure it out.

Also, some Motherboard hates certain manufactured RAM. I've had that happen to me once when I bought ASUS motherboard and PNY memory stick. They just didn't work out well together... =/ It might just end up being the northbridge chip not made to coexist with the certain sorts of RAM.

[Vinen]

When I used to get memory errors in WoW my system would outright reboot.

[Skaara]

When I used to get memory errors in WoW my system would outright reboot.

Sometimes mine does this too.

[Kirynos]

Your computers have ghosts in them. Have you fed the ghosts lately?

:confuse:

[Kalim]

Who you gonna call?!

GHOSTBUSTERS!!~

[Skaara]

Your computers have ghosts in them. Have you fed the ghosts lately?

:confuse:

That reminds me... I don't think I've fed the little hampster that runs the wheel in my power supply in about 3 weeks...

[Kirynos]

omg you slave driver! I'm f**king calling PETA!

:confuse:

[Vinen]

Sometimes mine does this too.

I replaced my memory and that issue went away :/