PDA

View Full Version : Nasty graphics issue



Themaxx
03-19-2009, 09:16 PM
I'm experiencing a graphics issue that appears to be really spastic flashing triangular shapes that are often "originated" from certain shapes on-screen, such as a character's cloak, and stretched way across the screen, blinking and just being very annoying in general. This didn't always happen. I'm not very tech-savvy and I'm not sure what the issue is, though it sounds like a video card, I have no idea how to check for that. Any ideas?

Here are some specs:

Intel Core 2 Duo CPU E6850 @ 3.00 GHz (2 CPUs)
2048 MB RAM

Card:
NVIDIA GeForce 8600 GT
DAC Type: Integrated RAMDAC
Approx total mem: 1024 MB

Drivers:
Main: nv4_disp.dll
version: 6.14.0011.7519 (English)
Mini VDD: nv4_mini.sys
DDI Version: 9 (or higher)

Sajuuk
03-19-2009, 10:29 PM
Do you have a spare graphics card you can throw in your computer?

Note to self: Get spare PCI-E card!

spannah
03-20-2009, 01:55 AM
Most likely a heating issue, or your card is toasted. Try another card like Sajuuk suggest,or even try that card in a diff computer an note what happens (or doesn't)

Themaxx
03-20-2009, 03:13 AM
Lol, I am currently more broke than I've ever been before and trying another card isn't an option right now. Do you foresee that as the only possible solution?

FunkStar
03-20-2009, 05:02 AM
for starters just try opening your case, and clean out the dust from your gpu ventilator. Might want to use 'Gpu-Z' to monitor the temperatures.

As sais, looks like a heathing issue or a broken card

Themaxx
03-20-2009, 01:46 PM
Man, that's strange/sucks. The computer is less than 6 months old :( I opened it up and inside there's very little dust anywhere - I cleaned anything that was there. I can't imagine this is a result of dual-boxing (especially since I have graphics settings on low), though it happened a few weeks after I started playing two characters. Is it possible to blow a card from the added stress of two instances and the occasional FRAPS?

Heenan
03-20-2009, 02:27 PM
Does this happen only when you have 2 or more instances of WoW open? In other words, only open 1 WoW window and see if you get the tearing/popping.

If that happens it's most likely your config.wtf file. Deleting it and letting the game recreate it has fixed many people's problems.

Video artifacts running 2 copies of WoW ('http://dual-boxing.com/forums/index.php?page=Thread&threadID=17161')

Themaxx
03-20-2009, 06:30 PM
Does this happen only when you have 2 or more instances of WoW open? In other words, only open 1 WoW window and see if you get the tearing/popping.

If that happens it's most likely your config.wtf file. Deleting it and letting the game recreate it has fixed many people's problems.

Video artifacts running 2 copies of WoW ('http://dual-boxing.com/forums/index.php?page=Thread&threadID=17161')Yeah, it only happens when two instances are up. I just tried deleting the config file, but it didn't work.

Also, here's some new information: if one of the windows is in windowed mode, and the other is not, I don't get the artifacts. However this is far from ideal for obvious reasons, at least while leveling.

Themaxx
03-20-2009, 06:55 PM
Also, I did something, I don't know what, and I am now unable to tab between certain windows when WoW is open, most notably WoW windows.. this is one thing after another.. :whistling:

Themaxx
03-20-2009, 07:14 PM
Even newer developments:

Fixed the tabbing issue by rebooting. I just tried having both instances run in windowed mode but with only ONE maximized; if I minimize the un-max'd instance onto the taskbar, the other window is artifact-free; however, if I pull up the non-maximized windowed-mode instance and have it running on top of the maximized instance, that instance will then have the artifacts if it is on top of the other window.

Gibberish-free version:

If a window is on top with a non-minimized (i.e.: NOT minimized onto the taskbar) instance running directly behind it, it get tearing and artifacts.

Themaxx
03-20-2009, 07:52 PM
Well, this isn't working out as well as I had hoped. On my master's screen, I'm getting excessive video lag of my slave; for example, if I move forward and stop, the slave will bounce oddly around as it makes the way to the master, even appearing to run through the master before coming to a halt behind it; this only happens if the slave instance is minimized to the taskbar. However, if it's maximized and directly behind the master's instance window, I get the artifacts and tearing. So I can either choose an extremely jerky and difficult to anticipate slave image, or the artifacts and tears. Computers are fucking peachy, really.

Starbuck_Jones
03-20-2009, 10:54 PM
The weird slave lag when minimized isn't strange. I got that exact same thing when tried to 5 box on one system and maximize my desktop space.

Themaxx
03-21-2009, 03:09 AM
The weird slave lag when minimized isn't strange. I got that exact same thing when tried to 5 box on one system and maximize my desktop space.Yeah, I'm just frustrated is all. I think I just have a lemon video card.

alcattle
03-22-2009, 04:37 AM
don't overlook only having 2 gigs of RAM. All together your rig is iffy to dual box.

Seldum
03-27-2009, 11:29 AM
I had a problem with my grafics blinking when I installed my Nvidia Geforce 7950 gx2 into my new rig. I fixed it by reducing the shadows in wow under the grafic settings.

My problem is the driver I use. Vista 64 bit dosen't support the latest driver for my grafic card, so I had to revert to an older version.

NEVER CONSIDER BUYING GEFORCE 7950 GX2 - it is the suxor!

Spudgun
04-08-2009, 05:42 PM
I got the same irratic 'triangles' problem on my system only when i took all my 5 chars to Dalaran. Seems to be linked to whenever a massive number of players are rendered on all the screens at once.

My solution was to not take all my chars to Dalaran ;o)

Ive got a Nvidia 280 by the way.

Ellusionist
04-09-2009, 02:50 AM
I also vote for heat being the issue. I just skimmed the posts, so if you've already fixed it, I'll accept being called an idiot.

confusedtx5
04-09-2009, 03:36 AM
another ditto for overheating. Or unstable processor core - mostly caused by/from overheating anyway