"Display Driver stopped responding and has recovered" [Archive]

View Full Version : "Display Driver stopped responding and has recovered"

Feyero

11-16-2010, 03:25 PM

Over the past few weeks (maybe months) my computer would suddenly lock up and the screen would go black for a few seconds, then it would recover and my computer would say "Display driver nvlddmkm stopped responding and has successfully recovered". It would only happen maybe once or twice a night so I just ignored it, but now its happening more frequently...to the point where I've had to close the game because it happens over and over and over again. Here is my system:ConRoeXFire-eSATA2 motherboard2.13ghz Core 2 Duo3GB RAMDirectx 11NVIDIA GeForce 7950GT (I have installed the newest drivers...didn't fix the problem...perhaps made it worse)Windows Vista 32bitIs my video card dying on me? Is this just a sign I need to buy a new one? Or is this an internal problem that can be fixed?

TSR-DennisG

11-16-2010, 06:58 PM

If you haven't done so already try using the custom install option when running the more recent NVidia video driver. You will get an option to perform a clean install before installing the newer driver. You may also want to try reinstalling this version of <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=04ac064b-00d1-474e-b7b1-442d8712d553&displaylang=en" target="_blank">Direct X 9.0c</a>.

Amphibia

11-20-2010, 01:22 PM

I keep getting this problem as well, and only when I enter Nektulos Forest. For some reason my display driver hates that zone and stops working every time I enter it.Specifications:Geforce GTX 260/Windows 7I found the page to download the drivers, but I am terribly clueless when it comes to these things. Am I supposed to download Geforce GTX 260 then? Will I then get a newer version of the one I have, or should I download something else? Sorry if this sounds like a ridiculously stupid question, but I honestly don't know.

Wingrider01

11-21-2010, 10:23 AM

<cite>Amphibia wrote:</cite><blockquote>I keep getting this problem as well, and only when I enter Nektulos Forest. For some reason my display driver hates that zone and stops working every time I enter it.Specifications:Geforce GTX 260/Windows 7I found the page to download the drivers, but I am terribly clueless when it comes to these things. Am I supposed to download Geforce GTX 260 then? Will I then get a newer version of the one I have, or should I download something else? Sorry if this sounds like a ridiculously stupid question, but I honestly don't know.</blockquote>If you are running the 32bit version of windows 7<a href="http://www.nvidia.com/object/win7-winvista-32bit-260.99-whql-driver.html">http://www.nvidia.com/object/win7-w...hql-driver.html</a>If you ar running the 64 bit version of windows 7<a href="http://www.nvidia.com/object/win7-winvista-64bit-260.99-whql-driver.html">http://www.nvidia.com/object/win7-w...hql-driver.html</a>Set a restore point, then install the new version. Might also want to look in the evernt viewer to see if any additional informatin is given on why the driver stopped responding.

Svetty

11-22-2010, 05:06 AM

My husband and I, as well as several members of our guild, are experiencing this same issue. We have all installed the latest Nvidia drivers and are using the correct version of Directx. The graphics will flicker, have random odd things happen like being able to see through the world, and then the screen will go black for a few seconds to a minute. We then receive a message from Windows that our graphics driver stopped responding and has recovered. The game will then work properly until you move through that same area again.This randomly happens in many different zones but it consistently happens in Enchanted Lands and in Nektulos Forest. *Editted because I apparently forget words in the middle of the night.

Wingrider01

11-22-2010, 06:57 PM

<cite>Svetlanavera@Antonia Bayle wrote:</cite><blockquote>My husband and I, as well as several members of our guild, are experiencing this same issue. We have all installed the latest Nvidia drivers and are using the correct version of Directx. The graphics will flicker, have random odd things happen like being able to see through the world, and then the screen will go black for a few seconds to a minute. We then receive a message from Windows that our graphics driver stopped responding and has recovered. The game will then work properly until you move through that same area again.This randomly happens in many different zones but it consistently happens in Enchanted Lands and in Nektulos Forest. *Editted because I apparently forget words in the middle of the night.</blockquote>Primarily what you describe is a card starting to fritz out due to heat. Verify that the fans on the card are running properly and not clogged with killer dust bunnies.What you can try doing it uninstalling the current display driver, run a driver cleaner and try reinstalling the driver again. As far as which driver goes - if you have a older vidoe card sometimes the latest driver is not a good choice for the card.

Peogia

11-22-2010, 07:42 PM

<cite>Wingrider01 wrote:</cite><blockquote><cite>Svetlanavera@Antonia Bayle wrote:</cite><blockquote>My husband and I, as well as several members of our guild, are experiencing this same issue. We have all installed the latest Nvidia drivers and are using the correct version of Directx. The graphics will flicker, have random odd things happen like being able to see through the world, and then the screen will go black for a few seconds to a minute. We then receive a message from Windows that our graphics driver stopped responding and has recovered. The game will then work properly until you move through that same area again.This randomly happens in many different zones but it consistently happens in Enchanted Lands and in Nektulos Forest. *Editted because I apparently forget words in the middle of the night.</blockquote>Primarily what you describe is a card starting to fritz out due to heat. Verify that the fans on the card are running properly and not clogged with killer dust bunnies.What you can try doing it uninstalling the current display driver, run a driver cleaner and try reinstalling the driver again. As far as which driver goes - if you have a older vidoe card sometimes the latest driver is not a good choice for the card.</blockquote>I have noticed running Everquest II with any NVIDIA SLI enabled with driver/bios can cause these types of crashes if run with Everquest II<a href="http://www.nvidia.com/object/hybrid_sli.html" target="_blank" rel="nofollow">http://www.nvidia.com/object/hybrid_sli.html</a><a href="http://www.slizone.com/page/home.html" target="_blank" rel="nofollow">http://www.slizone.com/page/home.html</a>

Svetty

11-22-2010, 10:42 PM

<cite>Wingrider01 wrote:</cite><blockquote>Primarily what you describe is a card starting to fritz out due to heat. Verify that the fans on the card are running properly and not clogged with killer dust bunnies.What you can try doing it uninstalling the current display driver, run a driver cleaner and try reinstalling the driver again. As far as which driver goes - if you have a older vidoe card sometimes the latest driver is not a good choice for the card.</blockquote>This is deifnitely not an issue of our cards overheating. I monitor my temps and have never seen my card over 124 degrees farenheit and it generally runs around 116. We have done clean installs of the driver and the issue persists. We both have 9800 GTX's, so, while not the newest cards out there, they are not crappy old cards either.If this was an issue with our hardware and not being caused by the game we would see issues outside of EQ2, which, we do not. Multiple people would not have the exact same issue in the exact same places in game. I have verified with my guild members that are having this issue that they all have Nvidia cards but not the same as the card my husband and I have. They get the same graphics glitches and video driver crashes that we get in the exact same spots in EL and Nek.

Wingrider01

11-23-2010, 10:18 AM

<cite>Svetlanavera@Antonia Bayle wrote:</cite><blockquote><cite>Wingrider01 wrote:</cite><blockquote>Primarily what you describe is a card starting to fritz out due to heat. Verify that the fans on the card are running properly and not clogged with killer dust bunnies.What you can try doing it uninstalling the current display driver, run a driver cleaner and try reinstalling the driver again. As far as which driver goes - if you have a older vidoe card sometimes the latest driver is not a good choice for the card.</blockquote>This is deifnitely not an issue of our cards overheating. I monitor my temps and have never seen my card over 124 degrees farenheit and it generally runs around 116. We have done clean installs of the driver and the issue persists. We both have 9800 GTX's, so, while not the newest cards out there, they are not crappy old cards either.If this was an issue with our hardware and not being caused by the game we would see issues outside of EQ2, which, we do not. Multiple people would not have the exact same issue in the exact same places in game. I have verified with my guild members that are having this issue that they all have Nvidia cards but not the same as the card my husband and I have. They get the same graphics glitches and video driver crashes that we get in the exact same spots in EL and Nek. </blockquote>still a little warm for my preference, run 3 480's on a EVGA E758-TR and they stay at around 95F, but I use liquid cooling on the system.what cards are you running and what video driver?Also, not always true that you will see issue outside of a specific application, it just depends on how hard the other applications hit the system. Using word or something like that no where near stresses the systrem out like eq2, even wow or lotro come near the strees on the system. If you feel like experimenting, try downloading and running 3dmark, there is a free version available and it will really give the system a work out, would be interesting to see if the issues show there.

rocker10

11-25-2010, 04:04 AM

This is not a hardware issue or overheating in my opinion. I am running a 3 month old Alienware laptop with a GTX 260M with 1GB vid memory. This rig also runs 6GB of system memory. This crashing started after GU58. I have done a clean install of drivers and am running most recent NVidia driver 260.99. I also verified and reinstalled the recommended Direct X version. To no avail. The areas I get crashes are Nektulos Forest, Enchanted Lands and the area of Toxxulia's Mound just going up the path where the Wurms are. SoE bugged something with that update.

Percussion

11-25-2010, 04:56 AM

had the same problem with displaydriver cuttingchanged my graphics card from a gts250 to gtx460problem disapeared so my conclusion .. Hardware failure or just the stinking card

Peogia

11-25-2010, 11:16 AM

<cite>Percussion wrote:</cite><blockquote>had the same problem with displaydriver cuttingchanged my graphics card from a gts250 to gtx460problem disapeared so my conclusion .. Hardware failure or just the stinking card</blockquote>Seen this issue with a branew GT 240 and a branew GTX 460 its a SOE Programing issue not hardware issue it only ever happens with Everquest II

Wingrider01

11-25-2010, 01:04 PM

<cite>Peogia wrote:</cite><blockquote><cite>Percussion wrote:</cite><blockquote>had the same problem with displaydriver cuttingchanged my graphics card from a gts250 to gtx460problem disapeared so my conclusion .. Hardware failure or just the stinking card</blockquote>Seen this issue with a branew GT 240 and a branew GTX 460 its a SOE Programing issue not hardware issue it only ever happens with Everquest II</blockquote>As stated before you are incorrect in your assumption that it is code issues, explain the simple fact that there are thousand of players utilizing Nvidia cards and they are not reporting issues. A large number of guildies utilze everything from a 8800 to the new the new 580 and they have no problems. Have one system running three 480's with no issues, have other systems running a 460's, and GT 250 with 0 issues. Can run 4 accounts on the system with the three 480's. have seen the exact same error reported for ATI cards in this game and in numerous other games.If you would take the time to do a little investigation you will find that this error occurs and have been reported in numerous games forums regarding numerous game - Call of Duty, WOW, LOTRO, Counter Strike to name a minor list of the games his is reported on, both nvidia and ATI. The nvidia and ato specific forums have numerous threads on this exact same error. Or are you claiming that all those games have coding errors also?

11-25-2010, 03:06 PM

I have same errors. If I can quick get down window with game before crush, after bringing widow back everything goes well without recovering.

Phaso

11-29-2010, 02:26 PM

Having the same problem in Nektulos Forest. As someone previously said, quickly minimizing the game stops the driver reset from Windows happening, or it works fine after the driver resets. Seems limited to this zone and apparently a few others. This was on a GTS 250. Since it isn't affecting everyone, I assume it's something that's turned on which isn't exactly standard. I have the game running in High Quality with Shader 3 on (which I would suspect based purely on how under-supported it is), and also have driver forced AA enabled. This seems to happen as the game is rendering flora, though, for what it's worth. As for heat issue, maybe, but I doubt it. Especially with so many people experiencing the same issues in the same places (with the same results). None of the temperatures I've seen in this thread are what I would consider abnormal for a GPU -- they're probably relatively low for one that's in use.

ccarro

11-29-2010, 03:10 PM

I've had this issue as well. Has only happened a few times but I have noticed it in Nek Forest and also during raid in The Underfoot Depths and one time while in a guild hall also.It seemed that something in the zone itself was causing it since it kind of happened when I turned and almost went away when I tried to turn back. The turned again and game crashed. It seem to happend enough to really narrow down the cause. But it does seem to be happening more often now then before.

Peogia

11-29-2010, 05:37 PM

<img src="http://i800.photobucket.com/albums/yy289/Icexstorm69/everquest2killingmydriver.png" width="1024" height="578" />Is this the Error message you guys are receiving <img src="/eq2/images/smilies/0a4d7238daa496a758252d0a2b1a1384.gif" border="0" />

Skiy

11-30-2010, 12:11 AM

Same exact issue here, and it ONLY happens to me and a few other guildies, all running almost brand new nVidia GTX cards in Underfoot Depths.

Dreyco

12-01-2010, 04:37 AM

Happening to a friend of mine as well. However, Windows XP doesn't have a nice recovery like that.. it just blue-screens, which is aggravating for him.He's running on my old PC. GeForce 7950 GTX.Edit to add: It happens in places with high item count, especially like our house or a really crowded dungeon.

Peogia

12-01-2010, 08:51 AM

I think you guys should make petitions with NVIDIAas stated on there web siteNVIDIA Graphics Driver was created by NVIDIA® Corporation. Please contact NVIDIA® Corporation for assistance and troubleshooting information or, to find out if a solution is available. For more information, see the NVIDIA® Corporation Web site<a href="http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=22&p_created=1096486168&p_sid=XzpoMpgk&p_accessibility=0&p_redirect=&p_srch=1&p_lva=22&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX 3Jvd19jbnQ9ODUsODUmcF9wcm9kcz0wJnBfY2F0cz0wJnBfcHY 9JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfb mwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1EaXNwbGF5IERyaXZ lcg!!&p_li=&p_topview=1" target="_blank" rel="nofollow">http://nvidia.custhelp.com/cgi-bin/...amp;p_topview=1</a><a href="http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=34&p_created=1096908236&p_sid=XzpoMpgk&p_accessibility=0&p_redirect=&p_srch=1&p_lva=22&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX 3Jvd19jbnQ9ODUsODUmcF9wcm9kcz0wJnBfY2F0cz0wJnBfcHY 9JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfb mwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1EaXNwbGF5IERyaXZ lcg!!&p_li=&p_topview=1" target="_blank" rel="nofollow">http://nvidia.custhelp.com/cgi-bin/...amp;p_topview=1</a>When I contacted Sony about this issue alls they would say is use streaming client

Peogia

12-06-2010, 12:05 AM

<a href="http://forums.nvidia.com/index.php?showtopic=65161" target="_blank" rel="nofollow">http://forums.nvidia.com/index.php?showtopic=65161</a>

Svetty

12-06-2010, 05:47 AM

<cite>Peogia wrote:</cite><blockquote><a rel="nofollow" href="http://forums.nvidia.com/index.php?showtopic=65161" target="_blank">http://forums.nvidia.com/index.php?showtopic=65161</a></blockquote>Peogia,While the links you are giving for Nvidia forums are informative they do not address the root cause of the issues we are having. The issues we are having are caused by something in EQ2 causing the graphics driver to have an exception. This is why it crashes and then recovers. It happens only in certain zones and only in specific areas of those zones. I have tested this running in every performance option available in EQ2 from extreme graphics to extreme performance and the issue occurs for all of them. The issue has only started since GU58. I would appreciate it if a TSR would actually step up and look into the issue at this point because it is obvious many people are having the problem.

Abraxsis

12-06-2010, 02:48 PM

My personal system's display driver resets anytime I face the Ulteran Spire in the Enchanted Lands. It has done this for several weeks now. I use a NVidia 250 with current drivers.I have been able to reproduce the crash on five separate computer systems using NVidia cards (all have current drivers installed).This issue started after one of the Tuesday morning patches several weeks back now.

Horgana

12-06-2010, 03:44 PM

I have a nearly 7 year old Sony Vaio Desktop PC 3.4 ghz pentium 4 with a Nvidia GeForce 7950GT AGP - yes I know this is a very old config. My point is that I have Windows XP and Windows 7 installed on different partitions of the same hard disk. I get the problem people are describing often when running under Windows 7 and NEVER under Windows XP (which unsuprisingly I therefore run it on for any serious grouping / raiding etc).I'm assuming most of the people posting on this thread with their bang up to date PC's with mega graphics cards are also probably running Windows 7?

Wingrider01

12-06-2010, 07:02 PM

<cite>Horgana@Butcherblock wrote:</cite><blockquote>I have a nearly 7 year old Sony Vaio Desktop PC 3.4 ghz pentium 4 with a Nvidia GeForce 7950GT AGP - yes I know this is a very old config. My point is that I have Windows XP and Windows 7 installed on different partitions of the same hard disk. I get the problem people are describing often when running under Windows 7 and NEVER under Windows XP (which unsuprisingly I therefore run it on for any serious grouping / raiding etc).I'm assuming most of the people posting on this thread with their bang up to date PC's with mega graphics cards are also probably running Windows 7?</blockquote>Windows 7 Ultimate 64 Bit, 3 Nvidia 480'sWindows 7 Ultimate 32 but, 2 Nvidia 480'sWindiws 7 Ultimate 32 Bit, 1 Nvidia 460have not seen the error since I installed Windows 7, and I multibox and raid a lot.

Esuna

12-14-2010, 05:29 PM

Post Deleted by User

Ghouti

12-27-2010, 06:23 AM

I've had the same problems as described. Also only noticed this happening the last few weeks. First few times were near toxulia's mound in Sundered Frontier, screen would go black every now and then while walking / rotating camera angle. But never so far that i'd actually get the windows 7 error showing.However two days ago i went to solusek's eye (needed to talk to nagafen) and that pretty much nearly fried the video card lol, first time pc went black, restart wouldn't even work. So i completely cleaned the pc on the interior and let it cool down a bit, that fixed it. But the crashes kept coming in solusek eye after that, several times windows 7 managed to recover but twice it failed and i had to reset the pc. It happened to be at the bottom near the glass walkways.Got a GTX260 it did have outdated drivers, but installing the latest didn't help either.

Ghouti

12-28-2010, 03:58 AM

Potential Fix ?I may have found a potential fix, a guild m8 of mine came with the suggestion to delete your "Everquest2.exe", your "ms322.dll" (can't recall exact name should check at home but something like that one) and your complete "miles" directory. Then use station launcher and redownload these files.I did this yesterday and when i went into solusek eye bottom level i didn't get any graphic failure whatsoever, might have been a fluke but worth giving a shot. So let us know if this worked for you too !!

Arianah

01-06-2011, 01:41 PM

The thing is, everyone I know and have read to be experiencing this problem, has only been experiencing it since GU58. That makes me think they changed something that's causing this to happen, not something on our end, which would be way too coincidental considering the variation of cards being used, the computer builds, the graphics settings, and the zones in which this happens.I am still having this issue. For me and my husband, it happens in our Tier 1 Guild Hall in the first room to the left. I've also had the display driver crash while in Mistmyr Manor at the hallway right before the Primogen room.For one of my guildees, it happens in the second room to the right.For another of my guildees, it happens in Vestigial Cella.The guildee experiencing the crash in VC swears it was the water, so I tried taking the fountain out of the room to the left, and we still experienced the crash. I've tried to find common pieces of furniture or achitecture in the rooms in our guild hall that we're crashing in, and found nothing. If it was the glass windows that allow you to see the sky, then the first room to the right should also reproduce the crash. If it was the chandeliers, every other room should also reproduce the crash. There are no other common pieces of furniture between the two rooms.My husband tried updating the graphic drivers. Didn't fix it.The first guildee tried re-installing the game fresh. Didn't fix it.The second guildee played around with her graphics and I think also driver settings. Didn't fix it.I've reported this as a bug. There are at least 3 posts about this now.<a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=493094" target="_blank">"Good bye"</a><a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=488098" target="_blank">"Recurring graphics problem in Guild Hall - Confirmed BUG"</a>Edit: Forgot there were two Tier 1 Guild Hall versions. Ours is a Qeynos styled one.Edit: Added that I've also had the display driver crash in Mistmyr Manor right before the Primogen room.

Dogtag

01-06-2011, 01:51 PM

Been having frequent problems since GU58 as well with driver failuresGF9800 GTX6 GB ramathlon 5000+ dualcore cpuvista pro corp editionBoth old and new launcher installed, only seem to have the problem with the new one thou..Drivers and dir x updated and tested various versions as well.So I wonder where the problem is located, since this is the only game I have this problem with.. *coughs*

Huggo

01-06-2011, 02:54 PM

Seems to be some update with the latest GU that mess up the Nvidia cards, as we dont see any with ATI voicing that they have problems. I get the very same problem, doesnt matter graphic resolution raid, group, solo etc it just seem to happen on random. And I also have a Nvidia card, 260GTX.And i didnt have any issues before the latest GU

TalisX1

01-06-2011, 03:17 PM

<cite>Huggo wrote:</cite><blockquote>Seems to be some update with the latest GU that mess up the Nvidia cards, as we dont see any with ATI voicing that they have problems. I get the very same problem, doesnt matter graphic resolution raid, group, solo etc it just seem to happen on random. And I also have a Nvidia card, 260GTX.And i didnt have any issues before the latest GU</blockquote>It's not from the last update. There are mulitple threads on this topic, though no actual solutions. It is a conflict between nVidia cards and eq2. That is all that has been determined. I have experienced the driver crashing issue in solusek's eye and cella for months. Happens every time I get out on the glassy bridges. My wife's system uses an ati card but is very similiar to mine otherwise and she has no issues.Silat

Cica

01-06-2011, 03:40 PM

Arianah

01-06-2011, 04:39 PM

<cite>TalisX1 wrote:</cite><blockquote><cite>Huggo wrote:</cite><blockquote>Seems to be some update with the latest GU that mess up the Nvidia cards, as we dont see any with ATI voicing that they have problems. I get the very same problem, doesnt matter graphic resolution raid, group, solo etc it just seem to happen on random. And I also have a Nvidia card, 260GTX.And i didnt have any issues before the latest GU</blockquote>It's not from the last update. There are mulitple threads on this topic, though no actual solutions. It is a conflict between nVidia cards and eq2. That is all that has been determined. I have experienced the driver crashing issue in solusek's eye and cella for months. Happens every time I get out on the glassy bridges. My wife's system uses an ati card but is very similiar to mine otherwise and she has no issues.Silat</blockquote>Yes it is. Why else would we not have seen this problem before the GU? I have changed nothing about my graphics settings, or any part of my computer. This just started happening to me after GU58, as well as my guildees. Kind of odd that this would just spontaneously start happening to multiple people after GU58 went live and it has nothing to do with the GU.I'm not saying that something similar hasn't been happening to others who experienced this before GU58. But all the complaints I've read and heard have been since GU58 went live, so I'm just saying I think this is a seperate issue.

isest

01-12-2011, 06:24 PM

I was just wondering if anybody had come up with a soloution to this. Before gu 58 I never had any issues. Now it happens all the time on my gtx295.Oh my tem is sitting at 75 on the card via the monitoring program, well below it. I had 3 crashes today and one of them so bad it gave me the blue screen of death in windows 7 64 bit.I got a direct x frame error 00B05F3B this time, all attemps to captuer that stupid message with a screen shot have failed.Any sugestions would be welcome. I have tried old driver, and new drivers.

TSR-JoshuaM

01-19-2011, 06:22 PM

The errors you are experiencing, particularly the direct x frame error, does elude to either DX9, your drivers, or the video card itself having failed somewhere in the rendering process. If you have updated DX9 and your video card drivers and still encounter the same issue, you may want to look in to running through stability tests and determining whether or not this behavior persists in other 3D environments. That would point towards a failing video card being the culprit.The GTX295 @ 75C shouldn't cause problems in and of itself, but it is not uncommon. We would consider 75C near the beginning of the 'red zone' as far as critical temperatures are concerned.

Te'ana

01-21-2011, 01:13 PM

The last two days this has gotten to be a really big issue instead of part-time issue for me and my husband. He tried to reload DX9 and Windows 7 Ultimate (64 bit) said "Nope, you have the latest version." He reinstalled his Nvidia drivers and that didn't help.Since you mentioned 3D, we tried another approach that has helped. We checked to make sure that Steroscopic 3D was disabled in the Nvidia Control Panel then went into EQ2 and disabled all 3D tools. This one is a real pain to fix because even though there wasn't a checkmark in the Stereoscopic 3D box there were 3D applications checked underneath when viewed in Advanced mode. To uncheck the Software Cursor and World Depth User Interface we had to briefly enable the Stereo Driver box to make these options availble for editing. Once we had unchecked those boxes we unchecked the Enable Stereo Driver box. So far, our computers seem stable. We hope this will be a permanent fix and not a fluke.

TSR-JoshuaM

01-21-2011, 06:17 PM

@Te'anaWould you mind sending me the contents of your eq2_recent.ini? You can PM this to me.

ATLDawgy

02-01-2011, 03:35 PM

My understanding of this error is that it only appears in Windows Vista and Windows 7 in DirectX applications. The nature of the error is that a new WDDM feature called TDR (Timeout Detection and Recovery). What is supposed to happen is when a task sent to the GPU does not complete within the expected time (i.e. graphics hang or crash) a delay value is considered (default is 2 seconds) then Windows resets the display adapter on the fly. This is a feature to prevent PC users experiencing a graphics related crash or hang from having to reboot to resume PC use. Many people seem to be having the problem with both Nvidia and ATI adapters across many games (all using DirectX). This quite possibly is a problem with the DirectX calls not always sending proper status updates to the graphics drivers or vice versa. I have seen this problem first hand with my wife's new Windows 7 system (using a new GT 240 with an AMD Athlon x4 640) but not on my new Windows 7 install (using a GTX 260 I've had for over a year with an AMD Phenom II x4 965). EQ2 appears to be running fine when all of a sudden the screen flickers, the error message is displayed, and the game either continues running normally until the next occurance or the screen redraw doesn't go so smoothly and provides blotchy colors or the "snow" effect. Google "Windows 4101" and you'll start seeing many threads on the issue. A potential fix I found on the web that I'll try when I get home today is to decrease the hardware acceleration of the display adapter. Perhaps this is a sync issue where her slower GPU isn't updating her relatively faster CPU in a timely manner, triggering the error. Who knows but it would be nice if Microsoft, Nvidia, ATI/AMD, and all current game developers this problem affects could use their debugging skills to at least pin down the cause for the issue rather than defaulting to the now generic "install the latest drivers and reinstall any number of programs" as a fix. That has replaced "reboot" as the canned IT solution to any problem. Perhaps GU 58 included some code that exposes the real problem to a larger audience rather than being the cause.

TSR-JoshuaM

02-01-2011, 07:25 PM

There are so many contributing factors for such an issue that it is difficult to narrow it down to a specific cause.

Reginald

02-02-2011, 12:51 AM

Windows 7 64 bitIntel i7 CPU6 gb ramNvidia GeForce GTX 280I am having this same error. I have followed all of the suggestions with the direct X9 link and updating my card drivers. After that did not work I contacted dell since my PC was still under warranty. When I explained that the error could be the card over heating. After much persistence they replaced the card. Then I noticed it again called back and again gave them a firm talking to explaining that they must have given me a bad card so they sent a guy out to make sure I was not an idiot and installed the card wrong. He did and ran a number of tests on the card. I then played a number of other 3D games with no problems and low and behold a number of weeks later this same error reappeared. I was furious so I called back and this time out of warranty Dell agreed to not only replace the video card but the motherboard and the power supply in case it was a power issue or something was defective on the board. He checked everything and again with the error. I have a hard time now believing that 3 video cards and a motherboard later that this can be a hardware issue. Last summer and early fall I was able to run 2 instances of EQ2 on duel monitors easily and now I'm getting these driver errors. If there is anything other advice besides: Getting new drivers (Video card/Bios) Direct X 9c or replacing all the hardware in my PC please let me know.Thanks!

Te'ana

02-02-2011, 04:07 AM

Although I still occasionaly have the problem, it is much less of an issue since I disabled 3D functions wherever I could.

Mark

02-02-2011, 07:34 PM

This happened over and over to me today when I was going into the Oratorium of Thyr. It didn't happen in sol A at all until I zoned in there. This has been happening in my guild hall for about a month now also.

TSR-JoshuaM

02-02-2011, 09:06 PM

You can start by posting your DXDIAG information and perhaps I'll be able to point out something that can get you going in the right direction. These issues are very hard to track down to a cause.

Reginald

02-02-2011, 10:21 PM

Joshua the following is my DXDIAG: for my Display if you need the rest I can post that as well------------DxDiag Notes------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Sound Tab 3: No problems found. Sound Tab 4: No problems found. Sound Tab 5: No problems found. Input Tab: No problems found.--------------------DirectX Debug Levels--------------------Direct3D: 0/4 (retail)DirectDraw: 0/4 (retail)DirectInput: 0/5 (retail)DirectMusic: 0/5 (retail)DirectPlay: 0/9 (retail)DirectSound: 0/5 (retail)DirectShow: 0/6 (retail)---------------Display Devices--------------- Card name: NVIDIA GeForce GTX 280 Manufacturer: NVIDIA Chip type: GeForce GTX 280 DAC type: Integrated RAMDAC Device Key: EnumPCIVEN_10DE&DEV_05E1&SUBSYS_055710DE&REV_A1 Display Memory: 3813 MB Dedicated Memory: 1001 MB Shared Memory: 2811 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) Monitor Name: Generic PnP Monitor Monitor Model: Acer H233H Monitor Id: ACR00A0 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: DVI Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,n vwgf2um,nvwgf2umDriver File Version: 8.17.0012.5896 (English) Driver Version: 8.17.12.5896 DDI Version: 10 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 7/9/2010 17:38:00, 12471400 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a Device Identifier: {D7B71E3E-46A1-11CF-6664-5B251FC2C535} Vendor ID: 0x10DE Device ID: 0x05E1 SubSys ID: 0x055710DE Revision ID: 0x00A1 Driver Strong Name: oem88.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section0 03:8.17.12.5896:pciven_10de&dev_05e1 Rank Of Driver: 00E62001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C To be continued

Reginald

02-02-2011, 10:22 PM

Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled Card name: NVIDIA GeForce GTX 280 Manufacturer: NVIDIA Chip type: GeForce GTX 280 DAC type: Integrated RAMDAC Device Key: EnumPCIVEN_10DE&DEV_05E1&SUBSYS_055710DE&REV_A1 Display Memory: 3813 MB Dedicated Memory: 1001 MB Shared Memory: 2811 MB Current Mode: 1280 x 1024 (32 bit) (60Hz) Monitor Name: Generic PnP Monitor Monitor Model: SDM-HX73 Monitor Id: SNY2870 Native Mode: 1280 x 1024(p) (60.020Hz) Output Type: HD15 Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,n vwgf2um,nvwgf2umDriver File Version: 8.17.0012.5896 (English) Driver Version: 8.17.12.5896 DDI Version: 10 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 7/9/2010 17:38:00, 12471400 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a Device Identifier: {D7B71E3E-46A1-11CF-6664-5B251FC2C535} Vendor ID: 0x10DE Device ID: 0x05E1 SubSys ID: 0x055710DE Revision ID: 0x00A1 Driver Strong Name: oem88.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section0 03:8.17.12.5896:pciven_10de&dev_05e1 Rank Of Driver: 00E62001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled

TSR-JoshuaM

02-02-2011, 10:22 PM

Give me the system and sound device sections too please.Copy the first handful of lines out of your wa_error.log as well.

Reginald

02-02-2011, 10:32 PM

------------------System Information------------------Time of this report: 2/2/2011, 20:15:56 Machine name: BILLY-PC Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621) Language: English (Regional Setting: English)System Manufacturer: DELL Inc. System Model: XPS 730X BIOS: Default System BIOS Processor: Intel(R) Core(TM) i7 CPU 940 @ 2.93GHz (8 CPUs), ~2.9GHz Memory: 6144MB RAMAvailable OS Memory: 6134MB RAM Page File: 4831MB used, 7436MB available Windows Dir: C:Windows DirectX Version: DirectX 11DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled DxDiag Version: 6.01.7600.16385 32bit Unicode--------------System Devices-------------- Name: Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4ADevice ID: PCIVEN_8086&DEV_3A4A&SUBSYS_02AF1028&REV_003&11583659&0&E5 Driver: n/a Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A39Device ID: PCIVEN_8086&DEV_3A39&SUBSYS_02AF1028&REV_003&11583659&0&D2 Driver: n/a Name: Intel(R) ICH10R LPC Interface Controller - 3A16Device ID: PCIVEN_8086&DEV_3A16&SUBSYS_02AF1028&REV_003&11583659&0&F8 Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 7 - 340EDevice ID: PCIVEN_8086&DEV_340E&SUBSYS_02AF1028&REV_123&11583659&0&38 Driver: n/a Name: Creative SB X-FiDevice ID: PCIVEN_1102&DEV_000B&SUBSYS_00441102&REV_034&20B92282&0&0008 Driver: n/a Name: Intel(R) ICH10 Family PCI Express Root Port 4 - 3A46Device ID: PCIVEN_8086&DEV_3A46&SUBSYS_02AF1028&REV_003&11583659&0&E3 Driver: n/a Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A38Device ID: PCIVEN_8086&DEV_3A38&SUBSYS_02AF1028&REV_003&11583659&0&D1 Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub Throttle Registers - 3438Device ID: PCIVEN_8086&DEV_3438&SUBSYS_00000000&REV_123&11583659&0&A3 Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340ADevice ID: PCIVEN_8086&DEV_340A&SUBSYS_02AF1028&REV_123&11583659&0&18 Driver: n/a Name: NVIDIA GeForce GTX 280Device ID: PCIVEN_10DE&DEV_05E1&SUBSYS_055710DE&REV_A14&295F40C7&0&0018 Driver: n/a Name: Intel(R) ICH10 Family PCI Express Root Port 3 - 3A44Device ID: PCIVEN_8086&DEV_3A44&SUBSYS_02AF1028&REV_003&11583659&0&E2 Driver: n/a Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A37Device ID: PCIVEN_8086&DEV_3A37&SUBSYS_02AF1028&REV_003&11583659&0&D0 Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub System Management Registers - 342EDevice ID: PCIVEN_8086&DEV_342E&SUBSYS_00000000&REV_123&11583659&0&A0 Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 1 - 3408Device ID: PCIVEN_8086&DEV_3408&SUBSYS_02AF1028&REV_123&11583659&0&08 Driver: n/a Name: Silicon Image SiI 3132 SATALink ControllerDevice ID: PCIVEN_1095&DEV_3132&SUBSYS_02AF1028&REV_014&1AB59225&0&00E5 Driver: n/a Name: Intel(R) ICH10 Family PCI Express Root Port 2 - 3A42Device ID: PCIVEN_8086&DEV_3A42&SUBSYS_02AF1028&REV_003&11583659&0&E1 Driver: n/a Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A36Device ID: PCIVEN_8086&DEV_3A36&SUBSYS_02AF1028&REV_003&11583659&0&EA Driver: n/a Name: Intel(R) 5520/5500/X58 Routing and Protocol Layer Registers Port 0 - 3426Device ID: PCIVEN_8086&DEV_3426&SUBSYS_00000000&REV_123&11583659&0&81 Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub to ESI Port - 3405Device ID: PCIVEN_8086&DEV_3405&SUBSYS_02AF1028&REV_123&11583659&0&00 Driver: n/a Name: Texas Instruments 1394 OHCI Compliant Host ControllerDevice ID: PCIVEN_104C&DEV_8023&SUBSYS_02AF1028&REV_004&2C8D84C9&0&10F0 Driver: n/a Name: Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40Device ID: PCIVEN_8086&DEV_3A40&SUBSYS_02AF1028&REV_003&11583659&0&E0 Driver: n/a Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A35Device ID: PCIVEN_8086&DEV_3A35&SUBSYS_02AF1028&REV_003&11583659&0&E9 Driver: n/a Name: Intel(R) 5520/5500/X58 Physical and Link Layer Registers Port 0 - 3425Device ID: PCIVEN_8086&DEV_3425&SUBSYS_00000000&REV_123&11583659&0&80 Driver: n/a Name: Intel(R) 82801 PCI Bridge - 244EDevice ID: PCIVEN_8086&DEV_244E&SUBSYS_02AF1028&REV_903&11583659&0&F0 Driver: n/a Name: High Definition Audio ControllerDevice ID: PCIVEN_8086&DEV_3A3E&SUBSYS_02AF1028&REV_003&11583659&0&D8 Driver: n/a Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A34Device ID: PCIVEN_8086&DEV_3A34&SUBSYS_02AF1028&REV_003&11583659&0&E8 Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub Control Status and RAS Registers - 3423Device ID: PCIVEN_8086&DEV_3423&SUBSYS_00000000&REV_123&11583659&0&A2 Driver: n/a Name: JMicron JMB36X ControllerDevice ID: PCIVEN_197B&DEV_2363&SUBSYS_02AF1028&REV_034&325A5B21&0&00E3 Driver: n/a Name: Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3CDevice ID: PCIVEN_8086&DEV_3A3C&SUBSYS_02AF1028&REV_003&11583659&0&D7 Driver: n/a Name: Intel(R) ICH10 Family SMBus Controller - 3A30Device ID: PCIVEN_8086&DEV_3A30&SUBSYS_02AF1028&REV_003&11583659&0&FB Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers - 3422Device ID: PCIVEN_8086&DEV_3422&SUBSYS_00000000&REV_123&11583659&0&A1 Driver: n/a Name: Broadcom NetLink (TM) Gigabit Ethernet #2Device ID: PCIVEN_14E4&DEV_1698&SUBSYS_02AF1028&REV_104&656F17A&0&00E2 Driver: n/a Name: Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3ADevice ID: PCIVEN_8086&DEV_3A3A&SUBSYS_02AF1028&REV_003&11583659&0&EF Driver: n/a Name: Intel(R) ICH10R SATA AHCI ControllerDevice ID: PCIVEN_8086&DEV_3A22&SUBSYS_02AF1028&REV_003&11583659&0&FA Driver: n/a Name: Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 9 - 3410Device ID: PCIVEN_8086&DEV_3410&SUBSYS_02AF1028&REV_123&11583659&0&48 Driver: n/a Name: Broadcom NetLink (TM) Gigabit EthernetDevice ID: PCIVEN_14E4&DEV_1698&SUBSYS_02AF1028&REV_104&37415011&0&00E1 Driver: n/a<div></div>

Reginald

02-02-2011, 10:33 PM

-------------Sound Devices------------- Description: Speakers (4- Logitech USB Headset) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: USBVID_046D&PID_0A0C&REV_1013&MI_00 Manufacturer ID: 65535 Product ID: 65535 Type: WDM Driver Name: USBAUDIO.sys Driver Version: 6.01.7600.16385 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 7/13/2009 19:06:32, 109568 bytes Other Files: Driver Provider: Microsoft HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: Realtek Digital Output (Realtek High Definition Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0888&SUBSYS_102802AF&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.5700 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 10/20/2008 23:57:00, 1493784 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: SPDIF Out (Creative SB X-Fi) Default Sound Playback: No Default Voice Playback: No Hardware ID: PCIVEN_1102&DEV_000B&SUBSYS_00441102&REV_03 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1348 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 7/7/2010 13:16:24, 697816 bytes Other Files: Driver Provider: Creative HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: Speakers (Creative SB X-Fi) Default Sound Playback: No Default Voice Playback: No Hardware ID: PCIVEN_1102&DEV_000B&SUBSYS_00441102&REV_03 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1348 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 7/7/2010 13:16:24, 697816 bytes Other Files: Driver Provider: Creative HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: Digital Audio (HDMI) (Creative SB X-Fi) Default Sound Playback: No Default Voice Playback: No Hardware ID: PCIVEN_1102&DEV_000B&SUBSYS_00441102&REV_03 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1348 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 7/7/2010 13:16:24, 697816 bytes Other Files: Driver Provider: Creative HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No---------------------Sound Capture Devices--------------------- Description: Microphone (4- Logitech USB Headset) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: USBAUDIO.sys Driver Version: 6.01.7600.16385 (English) Driver Attributes: Final Retail Date and Size: 7/13/2009 19:06:32, 109568 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF Description: Digital-In (Creative SB X-Fi) Default Sound Capture: No Default Voice Capture: No Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1348 (English) Driver Attributes: Final Retail Date and Size: 7/7/2010 13:16:24, 697816 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF Description: "What U Hear" (Creative SB X-Fi) Default Sound Capture: No Default Voice Capture: No Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1348 (English) Driver Attributes: Final Retail Date and Size: 7/7/2010 13:16:24, 697816 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF

Reginald

02-02-2011, 10:35 PM

I am not seeing a wa_error.log file on my machine could it be called something else?

isest

02-02-2011, 11:09 PM

<cite>Reginald@Crushbone wrote:</cite><blockquote>I am not seeing a wa_error.log file on my machine could it be called something else?</blockquote>EnabledI also dont see the wa file, my dx diag almost looked the same as your except mine says its a gtx295---------------Display Devices--------------- Card name: NVIDIA GeForce GTX 295 Manufacturer: NVIDIA Chip type: NVxx DAC type: Integrated RAMDAC Device Key: EnumPCIVEN_10DE&DEV_05E0&SUBSYS_12913842&REV_A1 Display Memory: 4069 MB Dedicated Memory: 869 MB Shared Memory: 3199 MB Current Mode: 1680 x 1050 (32 bit) (60Hz) Monitor Name: ACER X223W (Analog) Monitor Model: Acer X223W Monitor Id: ACR0050 Native Mode: 1680 x 1050(p) (59.883Hz) Output Type: DVI Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,n vwgf2um,nvwgf2umDriver File Version: 8.17.0012.6099 (English) Driver Version: 8.17.12.6099 DDI Version: 10 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 10/16/2010 12:55:00, 12788840 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a Device Identifier: {D7B71E3E-46A0-11CF-214C-9D321FC2C535} Vendor ID: 0x10DE Device ID: 0x05E0 SubSys ID: 0x12913842 Revision ID: 0x00A1 Driver Strong Name: oem46.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section0 04:8.17.12.6099:pciven_10de&dev_05e0 Rank Of Driver: 00E62001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status:

isest

02-02-2011, 11:15 PM

here is the rest of my dxdiag------------------System Information------------------Time of this report: 2/2/2011, 19:58:15 Machine name: Wargames-PC Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621) Language: English (Regional Setting: English)System Manufacturer: XFX79U System Model: XFX nForce 790i Ultra 3-Way SLI BIOS: Phoenix - AwardBIOS v6.00PG Processor: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (4 CPUs), ~2.8GHz Memory: 8192MB RAMAvailable OS Memory: 8190MB RAM Page File: 3008MB used, 13371MB available Windows Dir: C:Windows DirectX Version: DirectX 11DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled DxDiag Version: 6.01.7600.16385 32bit Unicode------------DxDiag Notes------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Sound Tab 3: No problems found. Sound Tab 4: No problems found. Input Tab: No problems found.-------------Sound Devices------------- Description: Speakers (Realtek High Definition Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0888&SUBSYS_10DE0175&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.5767 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 12/26/2008 03:25:00, 1590048 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: Speakers (USB Audio Device) Default Sound Playback: No Default Voice Playback: No Hardware ID: USBVID_0D8C&PID_000C&REV_0100&MI_00 Manufacturer ID: 65535 Product ID: 65535 Type: WDM Driver Name: USBAUDIO.sys Driver Version: 6.01.7600.16385 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 7/13/2009 18:06:32, 109568 bytes Other Files: Driver Provider: Microsoft HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: Realtek HDMI Output (Realtek High Definition Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0888&SUBSYS_10DE0175&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.5767 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 12/26/2008 03:25:00, 1590048 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: Realtek Digital Output (Realtek High Definition Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0888&SUBSYS_10DE0175&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.5767 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 12/26/2008 03:25:00, 1590048 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No

TSR-JoshuaM

02-03-2011, 12:08 AM

Sorry wa_error.log is for a different game of ours... I support multiple games and got my wires tangled!

twanderso

02-03-2011, 04:54 PM

I had the same error and have come to the conclusion that my Radeon HD 4850 just bought the farm and, as I think about its replacement, I can't help but wonder about the NVIDIA flash on the startup screen. Is NVIDIA better than ATI for EQ2 or does it matter? Anyone have any recommendations in the $150-200 range? I was thinking Radeon Hawk HD 5770. Also, any recommendations of manufacturers within the selected model (e.g. MSI over ASUS, etc.).Any help is appreciated...going through withdrawal!!<img src="http://forums.station.sony.com/eq2/images/smilies/c30b4198e0907b23b8246bdd52aa1c3c.gif" border="0" />

Zin`Car

02-03-2011, 05:06 PM

<cite>twanderso wrote:</cite><blockquote>I had the same error and have come to the conclusion that my Radeon HD 4850 just bought the farm and, as I think about its replacement, I can't help but wonder about the NVIDIA flash on the startup screen. Is NVIDIA better than ATI for EQ2 or does it matter? Anyone have any recommendations in the $150-200 range? I was thinking Radeon Hawk HD 5770. Also, any recommendations of manufacturers within the selected model (e.g. MSI over ASUS, etc.).Any help is appreciated...going through withdrawal!!<img src="http://forums.station.sony.com/eq2/images/smilies/c30b4198e0907b23b8246bdd52aa1c3c.gif" border="0" /></blockquote>just do a quick search on teh support forums and you will get your answer about ATi and EQ2. The long and short of it: Yes, stick with nVidia.

Bacci

02-08-2011, 07:11 PM

I am experiencing the same problem since end of last year.It happens also in the places that the other people reported already.-----------------------------------Here is my dxdiag:------------------System Information------------------Time of this report: 2/8/2011, 23:03:24 Operating System: Windows 7 Professional 32-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: GA-MA78GM-UD2H BIOS: Award Modular BIOS v6.00PG Processor: AMD Phenom(tm) II X4 955 Processor (4 CPUs), ~1.6GHz Memory: 8192MB RAMAvailable OS Memory: 3326MB RAM Page File: 2197MB used, 4453MB available Windows Dir: C:Windows DirectX Version: DirectX 11DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled DxDiag Version: 6.01.7600.16385 32bit Unicode------------DxDiag Notes------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Input Tab: No problems found.--------------------DirectX Debug Levels--------------------Direct3D: 0/4 (retail)DirectDraw: 0/4 (retail)DirectInput: 0/5 (retail)DirectMusic: 0/5 (retail)DirectPlay: 0/9 (retail)DirectSound: 0/5 (retail)DirectShow: 0/6 (retail)---------------Display Devices--------------- Card name: NVIDIA GeForce GTX 285 Manufacturer: NVIDIA Chip type: GeForce GTX 285 DAC type: Integrated RAMDAC Device Key: EnumPCIVEN_10DE&DEV_05E3&SUBSYS_040110B0&REV_A1 Display Memory: 2414 MB Dedicated Memory: 1007 MB Shared Memory: 1407 MB Current Mode: 1680 x 1050 (32 bit) (59Hz) Monitor Name: PnP-Monitor (Standard) Monitor Model: VW225 Monitor Id: ACI22A0 Native Mode: 1680 x 1050(p) (59.954Hz) Output Type: HD15 Driver Name: nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dllDriver File Version: 8.17.0012.6099 (English) Driver Version: 8.17.12.6099 DDI Version: 10 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 10/22/2010 07:23:05, 10023528 bytes WHQL Logo'd: Yes WHQL Date Stamp: Device Identifier: {D7B71E3E-46A3-11CF-D364-0D241FC2C535} Vendor ID: 0x10DE Device ID: 0x05E3 SubSys ID: 0x040110B0 Revision ID: 0x00A1 Driver Strong Name: oem60.inf:NVIDIA_SetA_Devices.NTx86.6.1:Section004 :8.17.12.6099:pciven_10de&dev_05e3 Rank Of Driver: 00E62001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled-------------Sound Devices------------- Description: Lautsprecher (Realtek High Definition Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0885&SUBSYS_1458A002&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHDA.sys Driver Version: 6.00.0001.5694 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 8/27/2008 10:15:32, 2163032 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No Description: Realtek Digital Output (Realtek High Definition Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0885&SUBSYS_1458A002&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHDA.sys Driver Version: 6.00.0001.5694 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 8/27/2008 10:15:32, 2163032 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, NoSensaura(tm) ZoomFX(tm): No----------------EVR Power Information---------------Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0

Mesmer01

02-14-2011, 09:17 AM

Hope this gets fixed. Is happening to me and a friend of mine as well.

Skandragon

02-14-2011, 01:23 PM

I can confirm GU58 is when this started.I get a recovery message in many zones, but they seem to be the same zones/locations within the zones. I can reproduce this at will.Given that this a a well-reported issue, can Sony please look in to this? Please don't suggest insulting solutions such as "reinstall windows" to fix an EQ2 issue.

Reginald

02-14-2011, 07:26 PM

Any word on what the DXDIAG files may show? It has been a month since the last TSR response.

isest

02-14-2011, 08:11 PM

<cite>Skandragon wrote:</cite><blockquote>I can confirm GU58 is when this started.I get a recovery message in many zones, but they seem to be the same zones/locations within the zones. I can reproduce this at will.Given that this a a well-reported issue, can Sony please look in to this? Please don't suggest insulting solutions such as "reinstall windows" to fix an EQ2 issue.</blockquote>This is very true. I never had an issue until they started messing with the shader options. I can say that I have issues near the spires in el. There are other areas that the shaders have caused issues.

TSR-JoshuaM

02-14-2011, 08:33 PM

This is a very difficult error to track down. There are three main reasons that this error occurs. Driver issues, hardware failure, or heat issues. With the information posted, we can rule out drivers. We cannot yet rule out hardware failure or heat issues. As previously stated, I use, and have tested, a majority of the video cards posted here and that exist but not every possible configuration or failure can be planned for. With the introduction of Shader 3, we may have emphasized the issues in your configuration but enabling a supported feature would not be the cause of such an issue.

Zirel

02-16-2011, 06:56 AM

I posted my work-around in different thread <a href="http://forums.station.sony.com/eq2/posts/list.m?start=15&topic_id=489688#5501919" target="_blank">"Solusek's Eye crashing my computer"</a>, but it looks like it happens in different locations too...So i'm posting it here, as well.Setting Complex Shader Distance to -1 in Options (Advanced) / Performance section, stopped those display driver resets for me.

Arianah

02-19-2011, 03:43 AM

I can tell you exactly what I think is causing the problem. It's the glass textures and I'm guessing something you guys changed in Game Update 58 tweaked something causing this error to happen to more people.Since GU58 I have only been getting this error in the first room to the left in our Tier 1 Qeynos guild hall (with the glass windows).Now that I'm working on Deathtoll access quests I had to go down into Solusek's Eye to meet with Naggy, well... I had this error but even WORSE this time while running on the glass walkways.Every time I've read someone posting about having this problem it was near a glass texture or something similar (water etc)My driver didn't even recover this time, my screen flickered, had scrambled colored pixels on my screen and then my computer restarted with a blue screen of death <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" />Please please PLEASE fix this! <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" />

Erevis

02-23-2011, 03:31 PM

Ok so before Velious... I could get by ignoring these little glitches that everyone has been talking about because well.... they were usually in one specific area in a certain zone so I figured "Eh... this zone takes 20 minutes to do so I'll be out of here soon.' But now? With the expansion? I can’t even zone into it without these issues occurring (these being just about every one everyone else has had in this thread). Earlier today (as of this post) I was attempting to quest in the Great Divide and not only did my driver crash but I got a blue screen. The Othimir illusion even causes my driver to crash, and I know this because before, my house never made my driver crash, but earlier today (as of this post as well) I turned the illusion on and presto! driver crashed. It is very hard to enjoy an expansion when you can't even zone into it =( Stuff about my computer… OS Name Microsoft® Windows Vista™ Home Premium Version 6.0.6002 Service Pack 2 Build 6002 OS Manufacturer Microsoft Corporation System Manufacturer ASUSTeK Computer Inc. System Model F50Sf System Type X86-based PC Processor Intel(R) Core(TM)2 Duo CPU T6500 @ 2.10GHz, 2100 Mhz, 2 Core(s), 2 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 202, 6/9/2009 SMBIOS Version 2.5 Windows Directory C:Windows System Directory C:Windowssystem32 Boot Device DeviceHarddiskVolume2 Locale United States Hardware Abstraction Layer Version = "6.0.6002.18005" Installed Physical Memory (RAM) 4.00 GB Total Physical Memory 3.00 GB Available Physical Memory 889 MB Total Virtual Memory 6.19 GB Available Virtual Memory 3.86 GB Page File Space 3.29 GB Page File C:pagefile.sys Stuff about video card… Name NVIDIA GeForce GT 220M PNP Device ID PCIVEN_10DE&DEV_0654&SUBSYS_20391043&REV_A14&107F648&0&0008 Adapter Type GeForce GT 220M, NVIDIA compatible Adapter Description NVIDIA GeForce GT 220M Adapter RAM 1.00 GB (1,073,741,824 bytes) Installed Drivers nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll Driver Version 8.17.12.6099 INF File oem16.inf (Section029 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1366 x 768 x 59 hertz Bits/Pixel 32 Memory Address 0xFC000000-0xFCFFFFFF Memory Address 0xD0000000-0xDFFFFFFF Memory Address 0xFA000000-0xFDEFFFFF I/O Port 0x0000DC00-0x0000DC7F IRQ Channel IRQ 16 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:windowssystem32driversnvlddmkm.sys (8.17.12.6099, 9.62 MB (10,084,360 bytes), 11/29/2010 6:17 PM) (Every time this happens the nvlddmkm driver crashes btw! After downloading and installing the new driver it actually got worse…) Some zones and locations I know where this was happening before Velious (but after GU 58 ) Instances: The Vestigial Cella: by Kraitenae and the Queen (water seemed to cause this) Conservatory by the last named (again, water) Outer Vault near Crag (water yet again!) My guilds t1 Qeynos guild hall, the only place I have gotten this to happen is coming up our stairs from the basement (could be the windows that caused it, glass) Overland zones or dungeons: Great Divide on the Ice by the zone in Greater Faydark in the north-western corner by all the treants (the treants caused this... which is strange but okay) In Butcherblock by Irontoe Outpost East. I was jumping over a rock and the treants or the little pool there made my computer freak out. I do have some lovely screen shots of this one <3 Solusek's Eye I got this on the sixth level by (-117, 509, 200). The only thing I can think of that caused this was the glass. (There are more zones, just there are so many that I cannot remember them all right now) Illusions: Othimir illusion (the one from marketplace that you got for logging in on Feb 22nd) If I need to post anything else please let me know... =(

TSR-JoshuaM

02-23-2011, 06:16 PM

Erevis. There are a few things that can be done.First, open Power Options from your Control Panel.Select a high performance profile.Next, obtain a diagnostic utility from your video card manufacturer (Nvidia). The Nvidia Control Panel should have the necessary tools but you can use any official application to monitor video card temperatures. What you want to keep an eye on are the temperatures of your GPU at the time of a 'crash'. Record these readings and post them here.

Breiya

02-23-2011, 09:42 PM

hmmm, I really hope this gets fixed soon. It started happening to me tonight, too <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" /> and just fyi, I have a Geforce GTX 260, it says DirectX version 11, and I have Windows 7. I've only had this happen randomly a couple times in the past few months but since the xpack dl'd yesterday, it has been happening all the time. I don't know how to tell the temperature of my computer but I live in Florida and it's kinda warm today, so I have the AC on <img src="/smilies/69934afc394145350659cd7add244ca9.gif" border="0" alt="SMILEY" />

TSR-JoshuaM

02-23-2011, 10:19 PM

The expansion may demand more from your video card emphasizing any existing issues it may have. While that may not be your specific cause we should rule it out.Nvidia System tool, available on their website, has a temperature monitoring utility. You can use it to keep an eye on the GPU temperatures around the time of the error. Record them and post them here.

noluuk

02-23-2011, 11:48 PM

Add mine to the list. Just started doing it about a week ago. Never even a hickup over the past year and I play other games as well. Now all of a sudden this mess. How very disappointing.

Erevis

02-23-2011, 11:52 PM

Alrighty. So I finally got that program installed after 2 hours of trying (I'm so not computer savvy :) and watched my GPU temp like you said to. Just standing around without the crash happening it was between 165 and 170 F (which is probably hot? I don't know) and when I got the crash it didn't change. It stayed in the same range.Edit: If you need I can test it a lot... Not like I can do much until something gets fixed somewhere <img src="/eq2/images/smilies/1cfd6e2a9a2c0cf8e74b49b35e2e46c7.gif" border="0" />

gistane

02-24-2011, 04:35 AM

I had this issue as well but i appear to have found a fixUnder the options and performance down the bottom there is an option somewhere about turning on Anti Aliasing once i turned this on the issue vanished

noluuk

02-24-2011, 02:47 PM

No luck with the AA for me. Still does it either way. Talked with some of my guild mates last night and a few of them are having the same problem in the T-3 GH looking out over the water. Any new information on this issue or is this getting swept under the rug?

Foepaw

02-24-2011, 03:08 PM

There are certain places that cause my Nvidia to do the same thing, black screen, driver crash and reset. It's a relatively new card, and I dont have problems except in certain specific places so I don't buy the overheating thing. The most frustrating one for me is in the crafting instance off of Commonlands. It makes that one unplayable for me as it causes the black screen/reset over and over if I move. I had to call out. If you have ever been there, not a lot of fancy stuff going on. I have shadows off, all water effects to minimal and it still does it.I have 8gb of ram and a 1gb Nvidia card. I play a lot of other games on high detail settings with no issues at all. In fact, EQ2 is the ONLY game that causes these driver crashes, and it causes them consistantly in specific areas.I, like many others have updated all my drivers, have the most up to date DirectX and have decent hardware. I don't believe this is a case of mass graphics card failures. This is programming issue that has been recently introduced in a GU. All of this "your card is overheating" misdirection is not useful. If it were a handful of people having the problem, I would certainly think the problem is on their end. But there are a considerable amount of people experiencing this problem now, who have not had this trouble in the past.

Zirel

02-24-2011, 05:59 PM

I tried gistane's hint on turning on Driver Forced Anti-Aliasing, but it didn't help (well, I have anti-aliasing turned off in NVidia Control Panel anyway).Still, only solution for me, with my current settings is to have Complex Shader Distance set to -1.I use custom settings as I prefer better FPS and quiet GPU fans before shiny picture <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" />But.. at least he gave me an idea of testing something else.I switched Performance Profile to Very High Quality and then changed only Shadow Type to GPU Shadow Maps.With these new settings, I wasn't able to reproduce any driver reset issues and I spent more than an hour in Solusek's Eye (in area with transparent bridges, sublevel 6 and 7) and Bathezid's Watch Post's crafting room.So my results lead to conclusion, that those issues happens only to those, who are trying to gain some FPS and doesn't play with very high graphics settings.Summary of my system:OS: Windows Vista Ultimate 64-bit (fully updated with Windows Update)CPU: Intel Q6600Memory: 4GBGraphics card: MSI N285GTX, 1GB DDR3Drivers: 266.58_desktop_win7_winvista_64bit_english_whql.ex eDirectX: 9.0c (fully updated with DirectX End-User Runtime Web Installer)GPU stats during issue: GPU Usage 23%, GPU Temp 54°C (using NVIDIA System Monitor)Location: 1195.04, 203.42, 1437.68 (crating room in Bathezid's Watch Post - Fens of Nathsar)Orientation: 24.13, 0.00, 0.00At above location I can stand still, and move slowly Complex Shader Distance to value around 20, and i'll get screen garbled followed by display driver reset.Now I have at least choice of playing with lousy FPS and great picture, or with even worse graphics than I've got already used to <img src="../images/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" />

noluuk

02-24-2011, 07:24 PM

I get mid to hi 50's FPS and have my custom settings on good to better quality. I've tried to lower settings hoping that would releive the problem but no go. Hope somebody stumbles across a solution to this. Would be nice to be able to play without worrying about lock ups.

TSR-JoshuaM

02-24-2011, 10:40 PM

<cite>Erevis@Guk wrote:</cite><blockquote>Alrighty. So I finally got that program installed after 2 hours of trying (I'm so not computer savvy :) and watched my GPU temp like you said to. Just standing around without the crash happening it was between 165 and 170 F (which is probably hot? I don't know) and when I got the crash it didn't change. It stayed in the same range.Edit: If you need I can test it a lot... Not like I can do much until something gets fixed somewhere <img src="/eq2/images/smilies/1cfd6e2a9a2c0cf8e74b49b35e2e46c7.gif" border="0" /></blockquote>170F, or roughly 77C, is a high temperature to have just standing around. While in and of itself at 77C shouldn't cause any issues but at the time of the crash there is likely more action going on pushing your video card much harder, forcing that 77C forcer in to the 'red'. Give your video card fans a good cleaning and see if you can get that temperature in to the 60's or less while no action is occuring.

noluuk

02-25-2011, 12:21 AM

So let me get this straight. You are saying that its a heat problem even for those of us that are not having abnormal heating of our gear? I use a meter to test my temps not a program just in case you were wondering how I check it.

Te'ana

02-25-2011, 01:21 AM

My temperture monitoring system (via my Alienware monitor) has consistently shown a temp of 30c to 32C. My problems stopped after I disabled all 3D functions.

Erevis

02-25-2011, 11:09 AM

Alright... I cleaned my laptop then decided to do another test for giggles<img src="/eq2/images/smilies/2786c5c8e1a8be796fb2f726cca5a0fe.gif" border="0" />.Yesterday (before I cleaned it) my laptop had been on for about 30 minutes and I got the video driver to crash for 10 seconds. The temp. ranged anywhere from 69c to 72c for this duration. (don't remember what it normally sat at temp wise)Today after I cleaned it it normally sits at 50c or so when I dont have EQ2 up, then around 57-62c with it up. During this crash (which I also did 30 mins after my computer had been on, and also lasted for 10 seconds) the temperature just stayed at 62c....Now what? <img src="/eq2/images/smilies/136dd33cba83140c7ce38db096d05aed.gif" border="0" />

noluuk

02-26-2011, 12:44 PM

Is it still happening to you guys ?

isest

02-26-2011, 12:53 PM

yes it is, I still crash around the spires in el, and now there are a few areas in the great divide in and around the water that i crash. Twice near that turtle yesterday and once near the sea urchins and in the watter getting seeweed stuff.

Erevis

02-26-2011, 02:45 PM

Yea it's still happening but *shrug*. Found out that just about everywhere in Thurgadin has a chance to cause this as well. I've started playing the game in the new zones just looking at the ground because it's basically the safest way to not crash that I've found <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

Aljernon

02-26-2011, 04:32 PM

Thurgidan whenever entering the round rooms off to the sides will cause me to crach if I look in a certain direction. The only time in the great divide was leaving the otter area and that just started today. Last night I was all over that area with not one problem.My GPU temp is solid at 56C which has been the same value for the last year.I am running windows 7 64bit with Direct x 11.I do not believe the problem is on our side but a programming issue on Sony's side.

OwlHaven

02-26-2011, 05:40 PM

I have never had this Error until the expansion was released. Now it mainly happenes to me in Thurgadin on the western half of the city. Mostly near the far western round room off the main circular hallway. My screen goes black, and then I get a crazy plethora of pixelated colors, streaks and lines, until finally it will shut the game down. I can hear sounds, footsteps going by, anticipating it happening the last time i had my port to guildhall loaded where I could easily hit a hotkey for it and once the graphic error happened I was able to port to guildhall where the graphic bug continued for about 1min and then the game returned to normal without crashing. I play many games and i have no issues in any other game. My system and GPU card temps are within normal parameters and I think pawning this off on a heat issue, when so many people are having the same exact problem in some cases in the exact same spots in the game, is just plain irresponsible. I run: Win7 Home Prem 64bit - i7 CPU 930 2.8GHz 6GB RAM GeForce 260 DX11 Nvidia Driver 266.58

Amarisa

02-26-2011, 06:37 PM

Just to add my 2cents, I am haveing the exact problems in the exact places for months now. When doing the grottos and going from EL to Nek, happens every time..

isest

02-26-2011, 07:46 PM

<cite>Amarisa@Everfrost wrote:</cite><blockquote>Just to add my 2cents, I am haveing the exact problems in the exact places for months now. When doing the grottos and going from EL to Nek, happens every time..</blockquote>And that is why wheren I hear you and other folks say this is were I crash, my wife crashes. Something is really strange. If it were my vid card why does everybdoy else crash right by the spires in el headed to mushroom quests.Oh well now that I got my income tax in I might get a new card, if I could really say it was the card.

Kitaria

02-26-2011, 08:43 PM

Myself im also experiancing this issue, on both PC's and laptops, all use Nvidia cards, none are overheating!l(lol as if all these people suddenly have overheating GPU's)exactly the same symptoms as everyone else.Got one vista PC, one win7 PC, one Win7 laptop and one Vista laptop.When it started i updated drivers, did'nt solve it,switched to streaming client,did'nt solve it..reinstalled eq2, did'nt solve it, reinstalled windows, did'nt solve it...Its ironic that Nvidia is recommended tbh.

Bleuty

02-26-2011, 09:11 PM

Done the same to me in thurgadin

Thundy

02-26-2011, 09:15 PM

Lothlo

02-26-2011, 09:22 PM

I have just experienced the same problem, my video drivers stopped responding and recovered, it happened while I was doing a quest in the great divide, I clicked one item and then when i clicked the second item that's when it stopped responding. At the time my vid card was running at 52C. I have also noticed that when this happens it is around glassy / icy looking textures, especially ones that change from a solid texture to an glass / icy one.any further word on this, as it seems to be happening to more and more people?

Spritelady

02-27-2011, 07:42 PM

<cite>Aljernon wrote:</cite><blockquote>Thurgidan whenever entering the round rooms off to the sides will cause me to crach if I look in a certain direction. The only time in the great divide was leaving the otter area and that just started today. Last night I was all over that area with not one problem.My GPU temp is solid at 56C which has been the same value for the last year.I am running windows 7 64bit with Direct x 11.I do not believe the problem is on our side but a programming issue on Sony's side. </blockquote>I have this problem EVERY time in Thurga. I have to get someone on auto follow to drag me through those areas and minimize my window which makes it very difficult to complete quests or collect red shinies.I tried to take a screenshot but it appeared totally black every time I try and take one while this is happening. But it is like a psychadelic drug trip on my screen with the graphics wigging out all over and the colors being all wacked. This ONLY happens in Thurga and one place near the othmir so far. It is NOT a heat issue, it is a texture issue with those areas.

Feather

02-27-2011, 08:48 PM

I was getting Win 7 BSOD in Thudadin too but the following seems to have helped a lot. It is now playable for me with only slight flickering when in 3rd person (scrolled back view).Update to latest nvidia driversTurn off AERO in Win7 (selected Win7 Basic Theme).Stay mostly in 1st person viewI hope this helps some people that are getting crashes in that zone.Am running GTS250, i7-920, 6GB, Asus P6T

Spritelady

02-28-2011, 09:38 AM

<cite>Feather wrote:</cite><blockquote>I was getting Win 7 BSOD in Thudadin too but the following seems to have helped a lot. It is now playable for me with only slight flickering when in 3rd person (scrolled back view).Update to latest nvidia driversDoneTurn off AERO in Win7 (selected Win7 Basic Theme).Done, the day I installed Win7Stay mostly in 1st person viewTried, didn't make a diddly bit o' DifferenceI hope this helps some people that are getting crashes in that zone.Am running GTS250, i7-920, 6GB, Asus P6T</blockquote>Still getting video psychodelica in Thurga /sigh getting unplayable when your video card freaks every time you run through the area with the broker/banker, etc. and the areas with glass/icey ramps.

Lyranny

02-28-2011, 09:49 AM

I am getting the exact same thing... It is in the same area - in Thurgadin. I cannot go through there without this happening. It has gotten to the point that it will cause my entire computer to have an unrecoverable error if it doesn't recover. It even causes my husband's computer to lag when it is happening to mine due to the amount of drain it has on the internet connection at the time. (Though his computer doesn't have the error) 2 others in my guild have the same problem - same place - in Thurgadin.I updated the drivers. Didn't fix it.I'm using windows vista - Nvidia GeForce 9400 GTPlease find a true fix for this!

Lyranny

02-28-2011, 01:32 PM

<cite>Zirel@Runnyeye wrote:</cite><blockquote>I posted my work-around in different thread <a href="http://forums.station.sony.com/eq2/posts/list.m?start=15&topic_id=489688#5501919" target="_blank">"Solusek's Eye crashing my computer"</a>, but it looks like it happens in different locations too...So i'm posting it here, as well.Setting Complex Shader Distance to -1 in Options (Advanced) / Performance section, stopped those display driver resets for me.</blockquote>Thank you so much! This actually worked for me! I had tried everything else but nothing worked til I tried this. Now I can go to Thurgadin!

Zirel

02-28-2011, 02:20 PM

Glad it helped you as well, Lyranny <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" />Now i played a bit more with the options, as i really don't want to play with completely disabled complex shaders.And i think i found even better solution, though i'm still testing it, but no problems so far.So, if you want to play with Complex Shader Distance turned on (value higher than -1), then turn on also Water Reflections in Water section of advanced mode.It doesn't only affects rendering of water, but also glass objects like flasks, windows, mirrors, etc.So deadly combination is Complex Shader Distance at anything else than -1 and Water Reflections turned off.

OwlHaven

02-28-2011, 03:39 PM

Thanks alot Zirel this is working for me so far. I turned Water Reflections ON and i was able to set my Complex Shaders back up to my normal setting and I can now move through Thurgadin without any graphic errors.

schizmark

02-28-2011, 06:10 PM

Yep, worked for me too! I can even play in balanced mode again. Thanks!

Finneli

03-01-2011, 12:26 AM

I have the same problem, started around the time the expansion realeased. Only happenes in certain areas. I have a geforce 8800GT my GPU temp runs around 145 with EQ2 running on high quality. EQ2 is the only game where I have this problem. The graphics drivers will stop working just like every else here. I updated the drivers and it did not fix.This seems to only happen around areas with ice or glassy spots. I was in the estate of unrest today and the EQ2 client kept crashing. It gets really annoying.

Galldora

03-01-2011, 01:11 AM

I was getting this error. Since my machine was new and the temperature looked OK, I figured it wasn't a hardware problem. I tried a variety of fixes that I read about, but the problem continued until I returned the video card to the manufacturer and got a replacement. It hasn't happened once since then.

Xanvarin

03-01-2011, 05:13 AM

<cite>Zirel@Runnyeye wrote:</cite><blockquote>Glad it helped you as well, Lyranny <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" />Now i played a bit more with the options, as i really don't want to play with completely disabled complex shaders.And i think i found even better solution, though i'm still testing it, but no problems so far.So, if you want to play with Complex Shader Distance turned on (value higher than -1), then turn on also Water Reflections in Water section of advanced mode.It doesn't only affects rendering of water, but also glass objects like flasks, windows, mirrors, etc.So deadly combination is Complex Shader Distance at anything else than -1 and Water Reflections turned off.</blockquote>Thanks!This worked for me as well (so far at least).Reference data...Vista, Geforce 9800 GT (most recent drivers)I had previously started experiencing the problem around the previous update as tohers here mentioend as well. The problem occured for me in Nek, EL, Fens and Paineel. While I had experienced GPU overheating with a previous card and the error itself was the same, I would say with a fair amount of confidence that this specific error is not heat releated on my system (GPU temp of 61c after most recent occurance)Changing complex shader to -1 also worked, but that was not an ideal solution. While I'm not not sure what performance hit I'll see from turnign on reflections, this is a much better solution.FWIW, switching ot Shader 3 also fixed the issue for me, but gah!!!, that has some hideous texture rendering still, and I'd rather play with complex shader set to neg 1 than use shader 3, but I mention it in case its helpful in diagnosing the core problem to get it fixed.

Breiya

03-01-2011, 10:09 PM

Thanks Zirel! Turning on water reflections worked for me too...I'm not even sure how mine were set to off but turning them back on seems to have fixed the problem <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

kdmorse

03-01-2011, 11:34 PM

<cite>Breiya wrote:</cite><blockquote>Thanks Zirel! Turning on water reflections worked for me too...I'm not even sure how mine were set to off but turning them back on seems to have fixed the problem <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></blockquote>Son of a .....Worked here too...

noluuk

03-02-2011, 12:42 AM

I have'nt had time to test so we'll see what happens. So does this mean that dude gets paid for finding a fix??

Rotate

03-02-2011, 08:43 AM

I got this on my desktop on my old vid card. 9800 gtx. about a year ago. It did it for about a month until it died. Now my 280 gtx started doing this recently too. Along with my laptops 9600 gtm. Laptop is unplayable atm chain bod's. I didnt want my desktop to crash so i started messing with settings.. i did notce turnng the complex shader distance down to -1 stoped the display driver stop working but it still stutter in those spots. I then messing with the differnt presets.. blanace and so on but nothing helped. I noticed i had an old custom settings saved from months ago settings i had tweaked and ajudsted for pvpn so i loaded those settings. And no more stutters or display driver stop responding.. So did some update turn on some dispaly setting that is hidden or soemthing? and when i reverted back to my old save it got rid of it? Dunno what the differnce is.. but its been 3 days and my 280 gtx hasnt acted up again.ps. before my 9800gtx died i played alot of fps on it too.. and top end games.. it played flawless up until the time it died while playing eq2.

noluuk

03-02-2011, 08:29 PM

Tested the water reflections and no dice. Running the complex shader at any range had no effect either. So..we going to get any help here or just deal with it as is ?????

Minorious

03-03-2011, 01:26 AM

I'll post this here because it "may" be somewhat related, although different, to this issue.My wife and I play daily, and have been for over 6 years. We both have Windows 7 64 bit with high end AMD cpu's and 8gb of ram each. Virtually the same system except for our video cards. I have an old 8800gtx, and she has a 9800gt.My system is running fine. However, since we installed DoV, she has been experiencing strange video issues every few hours while in game. It's like she is shelling out to the desktop with the windows key after a brief blackout of the screen. Her screen will just go black for about 2 seconds, then show the desktop for about another 10 seconds, then she's back in the game. There is no error displayed when this happens.I have installed the most recent drivers for her and it's not overheating. I've been tweeking multiple graphic settings both on the card and in the game with no effect.There is no particular area that this happens in, it seems to be completely random. It's even happened while standing in the Guild hall.Any help or suggestions would be appreciated.Bones

noluuk

03-03-2011, 12:55 PM

Turning on the water reflections and dropping the complex shader to -1 seem to have helped some. Hasnt worked for me and it seems we are having to figure it out on our own now. So good luck and check back in if that works or not.

Zirel

03-03-2011, 01:03 PM

@noluukSo, you still have display driver resets with Water Reflections turned on?

noluuk

03-03-2011, 03:42 PM

yep. I've gone through everything I know plus all the stuff thats been posted here trying to fix it but as the name says it all..Noluk

noluuk

03-06-2011, 01:03 PM

I dont know if this is related but I lost my hard drive Saturday morning. We'll see what happens after I reinstall. Anyone else having this problem still?

Narsikus

03-07-2011, 11:32 AM

Yes, I am still having this problem. Yes, I have tried everything suggested on this forum, including water reflections on.Details:I bought a top of the line system about a year ago and played EQ2 almost every day for months. I was playing on Extreme Quality (with shadows turned off) and never had a problem. I quit playing last year around end-August/early-September time frame.I started back playing about mid-January of this year to get ready for expansion. And almost immediately I started having these problems. I thought it was random at first, but the place that gets me almost every time is my tier 1 guild hall in North Qeynos. Just about every other time zoning into guild hall would net me that error. Sometimes I could keep playing, other times I'd have to reboot system completely. Other places I experienced it were in Sol's eye and EL, but it could happen anywhere.I did a lot of research and tried everything and more listed on this forum and elsewhere. I updated all drivers with clean installs - video, sound, even chipset. I reinstalled directx. Updated all other Win 7 updates and anything else I could think of. Also reloaded EQ2 from the DoV disks as a fresh install and reconfigured my entire UI. After ALL that I was very disappointed to have the same thing happen again after a few hours of playing.So it got me thinking - [Removed for Content] happened? It was working perfectly last year. And I've played a ton of graphics-intensive 1st person shooters and games other than EQ2 on my system as well without any problems. That's when I stumbled onto GU58, which was released Oct 12th, 2010 - right after I quit playing last year. Everything was fine before that, and now I'm getting this error all the time as a lot of other people pointed out that started having the same problem. Anyway, I've read all the posts on here and elsewhere that claim this is a hardware problem with the card. And I just don't think so. Between diagnostics, benchmarking, monitoring temps and all the other games I play, my card (and other hardware) is fine. My system is still under warranty, so I'd love to say my card is bad and get a new one. But I just can't in good faith say this as I don't have ANY problems in any other game/application. I'm convinced this is something related to GU58 which is why there's a lot of people getting this error all the sudden. There's obviously something just mis-firing between a select number of vid cards, win 7, EQ2 and GU58.I did turn complex shader down to -1 or whatever and that seemed to work. But honestly I didn't play that way long as the game looks like crap at -1. I didn't pay what I did for my system to play this game looking that badly. I believe I have it set to something low like 2 or 5 now and I don't get the crash nearly as often. But I'd still like to crank it back up to the "very beautiful" setting at some point when (or IF) this gets fixed.So yeah, bottom line, I'm still having the problem.

Narsikus

03-07-2011, 11:47 AM

Oh yeah, one other thing.I can't remember if this was posted earlier in this forum or another, but this helps.For me, when I'm about to get this error, my screen will suddenly start flickering. It will do that for about 5 seconds or so before going totally black, and then getting the "recovered" error. As SOON as you see it start flickering, immediately press "windows key + D". This minimizes everything to the "D"esktop. Leave everything minimized for about 5-10 seconds before bringing it back up and you can usually avoid the error. Just make sure you're not auto-running when you do, or you might come back to a respawn screen.Just a tip in case anyone missed it.

Loxus

03-07-2011, 05:51 PM

I'm running a completely water-cooled system on a Nvidia GTX295 and it's happening to me about every 7 to 10 mins in Thuradin depending which way I face (sometimes back to back)- it's not a heat issue.Here's my guess.Setting the complex shaders to -1 fixed it, therefore I believe the error has to lie somewhere in the coding for ice/water walls and the way it tries to render reflection-transperncies at the same time combined with the new dynamic shading that causes the fuzzy appearances at distance and close up which is conflicting and causing the graphic cards to have a stroke.

Neiloch

03-07-2011, 09:39 PM

Also having this problem.Tried newest driver and even older ones.Tried complex shader distance and water reflections in various combination's including the one suggested here with no change.Makes the game nearly unplayable. Happens a lot when leaving the first othmir camp and heading towards the second one, and in and around the Goahmari Village. Happened around a lot in the gnoll camp as well. Some times it gets so bad it will happen repeatedly several times in a row, basically stopping me from playing and I have to close the game and restart.

TSR-JoshuaM

03-08-2011, 11:07 PM

Neiloch, do you have a way to look in to a stability test, or temperature monitoring? I would rule that out as a cause first.

noluuk

03-09-2011, 12:26 AM

Why do you keep going back to temps when so many of us have the same issue but our temps are fine?

TSR-JoshuaM

03-09-2011, 12:30 AM

<cite>noluuk wrote:</cite><blockquote>Why do you keep going back to temps when so many of us have the same issue but our temps are fine?</blockquote>Mainly because everyones causes are different and temperature related issues have been the majority of all reports of this issue since it was reported the very first time with us. Ruling it out does not harm anything here <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

Svetty

03-09-2011, 02:16 AM

<cite>TSR-JoshuaM wrote:</cite><blockquote><cite>noluuk wrote:</cite><blockquote>Why do you keep going back to temps when so many of us have the same issue but our temps are fine?</blockquote>Mainly because everyones causes are different and temperature related issues have been the majority of all reports of this issue since it was reported the very first time with us. Ruling it out does not harm anything here <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></blockquote>I can assure you that the issue is not temperature related for me. If you look back at my earlier posts in this thread you will see where and when this is happening to me. I monitor my system temps and have done a full reinstall of Win7 since I first posted about having this issue. I was sure to install directX 9c and have the latest drivers for my Nvidia Geforce 9800 GTX.I have this happen in specific zones and in very specific places within those zones. I have not tried going into any of the new Velious zones to see if I have the issues there or not.

Arianah

03-09-2011, 12:53 PM

<cite>TSR-JoshuaM wrote:</cite><blockquote><cite>noluuk wrote:</cite><blockquote>Why do you keep going back to temps when so many of us have the same issue but our temps are fine?</blockquote>Mainly because everyones causes are different and temperature related issues have been the majority of all reports of this issue since it was reported the very first time with us. Ruling it out does not harm anything here <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></blockquote>So I was just staring at the room my guildmates and I have been having the display driver crash in one day, when I noticed the glass sculptures I had placed in the room. Remembering that I figured transparent textures (glass, ice, water, etc...) were causing this issue, I took them out of the room.None of us have been experiencing this display driver crash in that room of the guild hall since.For the record, the items were the Azurite Entwined Sculpture and Azurite Tall Entwined Sculpture (I had completely forgot they were a glass texture since they're golden and not quite as transparent).Kind of feels futile to keep trying to share my findings to get this problem fixed to be honest though...................................

noluuk

03-10-2011, 12:12 PM

yeah

Minorious

03-11-2011, 04:32 AM

<cite>noluuk wrote:</cite><blockquote>I dont know if this is related but I lost my hard drive Saturday morning. We'll see what happens after I reinstall. Anyone else having this problem still?</blockquote>What does this have to do with Video issues?

noluuk

03-11-2011, 12:58 PM

Just seeing if the temeratures changed any

zaknafene

03-11-2011, 01:15 PM

If it was a heat issue the symptoms would occur and not stop when the card overheats. Heat kills it does not recover, symptoms would persist. In my case and what appears to be happening to most is that the driver recovers and then game play is resumed. My experience of this has been limited to certain areas. For the last week I have not had this happen. I hope it never returns. I did switch to a SSD drive with a fresh re-install of windows 7, the latest graphics driver and directx. With the exception of the hard drive all components remained the same.

Egeis

03-11-2011, 05:39 PM

Been having this issue since DoV and I suspect since i returned back in septermber.According to the frys "techs" my computer is fine however this issue is no longer just Eq2 problem. Occurs in windows while in Dreamweaver of all places. Make that photoshop...

TSR-JoshuaM

03-11-2011, 06:21 PM

<cite>Myoria@Butcherblock wrote:</cite><blockquote>If it was a heat issue the symptoms would occur and not stop when the card overheats. Heat kills it does not recover, symptoms would persist. In my case and what appears to be happening to most is that the driver recovers and then game play is resumed. My experience of this has been limited to certain areas. For the last week I have not had this happen. I hope it never returns. I did switch to a SSD drive with a fresh re-install of windows 7, the latest graphics driver and directx. With the exception of the hard drive all components remained the same. </blockquote>Not necessarily true at all. Windows Vista/7 implemented that feature by design. When your video card locks up, Windows attempts to continue operations without having to restart the PC (due to a hard lockup). If heat caused the issue, nothing would be processing while the video card stopped responding, thus the heat would subside and operations would continue until the thresholds are hit again.Again, heat is just one of many causes of such an issue and due to how easy it is to identify or rule out, it has to be asked.

TSR-JoshuaM

03-11-2011, 06:24 PM

<cite>Arianah wrote:</cite><blockquote><cite>TSR-JoshuaM wrote:</cite><blockquote><cite>noluuk wrote:</cite><blockquote>Why do you keep going back to temps when so many of us have the same issue but our temps are fine?</blockquote>Mainly because everyones causes are different and temperature related issues have been the majority of all reports of this issue since it was reported the very first time with us. Ruling it out does not harm anything here <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></blockquote>So I was just staring at the room my guildmates and I have been having the display driver crash in one day, when I noticed the glass sculptures I had placed in the room. Remembering that I figured transparent textures (glass, ice, water, etc...) were causing this issue, I took them out of the room.None of us have been experiencing this display driver crash in that room of the guild hall since.For the record, the items were the Azurite Entwined Sculpture and Azurite Tall Entwined Sculpture (I had completely forgot they were a glass texture since they're golden and not quite as transparent).Kind of feels futile to keep trying to share my findings to get this problem fixed to be honest though...................................</blockquote>For you specifically, could you send me your DXDIAG information (if you have already posted it, just let me know where)? I had the same issue with a GTX260, driver stopped responding when near glass/reflective textures, but I did manage to work out of the problem through a few needed updates at the time.

TSR-JoshuaM

03-11-2011, 06:25 PM

<cite>Baedian@Antonia Bayle wrote:</cite><blockquote>Been having this issue since DoV and I suspect since i returned back in septermber.According to the frys "techs" my computer is fine however this issue is no longer just Eq2 problem. Occurs in windows while in Dreamweaver of all places. Make that photoshop...</blockquote>In your specific situation, as it occurs out of game, I believe that the stress that EQ2 and Photoshop put on a video card may be emphasizing an existing issue. Can you PM me your DXDIAG information as well?

Bacci

03-11-2011, 07:05 PM

Windows Vista and Windows 7 have a feature called Timeout Detection and Recovery (TDR).TDR attempts to detect problematic situations and recover to a functional desktop dynamically. In prior operating systems these situations would have resulted in a system freeze and forced customers to reboot their PC. More information about this Vista feature can be found here: <a class="bbc_url" title="External link" rel="nofollow" href="http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx">http://www.microsoft...dm_timeout.mspx</a>.Therefore, when you see the TDR error message "Display driver stopped responding and has recovered", you know that the display driver is being reset without requiring a reboot. Why does it happen?TDRs can occur for a variety of reasons, many of which are unrelated to the graphics card or graphics driver.Checklist:- Run memtest (memtest.org). This should complete with NO errors. - Check your PSU ratings. Is it providing enough power, and most importantly enough Amps on the 12V rail. - Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online. - Test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue. - If you are using SLI, try each card separately to see if the fault lies with one. - Try graphics card/cards in another computer if you can. - Check for newer driver version. - Check for patches to the specific game with issues.Since Vista launched, NVIDIA has been working hard to address TDRs issues that are specific to the graphics driver.There is the NVIDIA Vista/win 7 Quality Assurance Site to record and address user issues: <a class="bbc_url" title="External link" rel="nofollow" href="http://www.nvidia.com/object/vistaqualityassurance.html">http://www.nvidia.co...yassurance.html</a>.Also, if your game falls below a certain FPS and something graphically complex occurs, it could trigger a TDR too.So it might be wise if we check our FPS in those areas.

Finneli

03-11-2011, 07:26 PM

I got the driver stop error message as well as the screen flickering and turning black just now in the enchanted lands at the docks. Monitoring my temp at the time, it was at 145F. I use an 8800GT with windows 7 ult 64bit.

Narsikus

03-12-2011, 02:06 AM

<cite>Arianah wrote:</cite><blockquote>So I was just staring at the room my guildmates and I have been having the display driver crash in one day, when I noticed the glass sculptures I had placed in the room. Remembering that I figured transparent textures (glass, ice, water, etc...) were causing this issue, I took them out of the room.None of us have been experiencing this display driver crash in that room of the guild hall since.For the record, the items were the Azurite Entwined Sculpture and Azurite Tall Entwined Sculpture (I had completely forgot they were a glass texture since they're golden and not quite as transparent).Kind of feels futile to keep trying to share my findings to get this problem fixed to be honest though...................................</blockquote>Wow, I have the exact 2 items in the zone in room of my guild hall. Like the exact 2 items, tall one on left and regular one on right. And when you zone in, they are right there in view. And as I stated in an earlier post, I was getting the "DDSRAHR" error msg about every other time zoning into guild hall.This error is something to do with those particular textures and complex shader distance, IMO.

Fa1cor

03-12-2011, 10:04 PM

ive had this problem too. is it a coincidence ive had 2 video cards die within the past 2 weeks?

Arek

03-21-2011, 02:37 PM

I'll have to post the directx info when I am home later, but I have been having this problem since DoV also.I run an 8800GTX on Win7 64. It has been an annoyance to say the least with it seemingly getting worse. Yesterday I got the error 3 times and it reset just fine. 2 times yesterday I got all of these little red specs all over my screen, it kinda of reminded me of the green Matrix thing except it wasnt moving. It seemed as though the whole PC froze, but then I could hear people in vent but it was very very slow and drawn out. Almost like something satanic and robotic.I play Black-Ops, Crysis, GTA4, Fallout3/Vegas and tons of other games with no issues at all.MY GPU is running at 59-65 celsius while playing games, so I don't think it is a heat issue.

Miun

03-21-2011, 06:18 PM

I didn't bother reading every page.I had posted about issues in Thurgadin weeks ago: <a href="http://forums.station.sony.com/eq2/posts/list.m?start=0&topic_id=495775�" target="_blank" rel="nofollow">http://forums.station.sony.com/eq2/...75�</a>and to make a long story short someone came up with going to Advanced water settings and check the box for reflections. I have been fixed from the driver crash for several weeks now once I did that. It was in no way a heat issue someone tested on a water rig had same problem. But fixed for most hope this is helpful.Edit: People with ATI cards may still have the issue even after reflections get turned on.And make sure to restart game from desktop once you change options, even if not prompted to.

Arek

03-22-2011, 11:59 AM

Well...can't post the DX info as of yesterday my card died. Sucks, I was able to play everything and only EQ2 was having issues, went to log on after work yesterday and it crashes at character select. Tried some other games and I get crazy anime seizure artifacting going on.No DKP for at least 3 weeks now...sigh

Elizadeth

03-26-2011, 09:56 AM

Look, I haven't pored over every post in this thread, but after 9+ pages it's clear we're still hung up on the idea that this is a heat issue.Let me make this perfectly clear, coming from another graphics dev: for 99% of the people experiencing this issue, it is absolutely, in no way, a heat issue or a power issue. Do yourself a favor and stop getting hung up on that.I don't know exactly what's going on under the hood in EQ2's engine but this looks like a case of a buffer overrun (the app is writing to shared memory, likely owned by the driver, outside the bounds it was allocated, corrupting the state of the driver). Either that or the game just surfaced a nasty driver bug. But to reiterate, 99% of the time neither overheating nor inconsistent power makes sense given the behaviors we're seeing, so look elsewhere.The heat idea actually makes less sense for EQ2 than it might for other games... EQ2 is still very CPU-bound compared to modern games, so a decent GPU will spend a lot of time just sitting around idle, and will not generate a huge amount of heat. If you can play CoD, Battlefield, DA2, or just about any other graphically intensive, modern game without heat issues, EQ2 isn't going to magically create them.

Liavy

03-26-2011, 03:09 PM

With Complex Shader Distance set to any value above -1, my graphics drivers will crash with the "stopped responding and recovered" error. I set it to -1 and I don't get any errors. I was originally rolling with 266.58 drivers, 64-bit. I reverted to the EQ2 recommended drivers 196.21, 64-bit, and this was true for both.

Neiloch

04-08-2011, 07:33 PM

I sat down today and tried every fix and work around suggested in this very thread. I am trying these on my Windows 7 Notebook computer with a GeForce 280M. For clarification here is what I tried:<ul><li> obtain a diagnostic utility from your video card manufacturer (Nvidia). The Nvidia Control Panel should have the necessary tools but you can use any official application to monitor video card temperatures. What you want to keep an eye on are the temperatures of your GPU at the time of a 'crash'. <ul><li>Result: No overheating at the times of the error. Matter of fact no overheating at all. I even went as far as using the tool to monitor gameplay of other games, and watch the temperature exceed that of what EQ2 was putting out. I had no errors during the other games.</li></ul></li></ul><ul><li>I may have found a potential fix, a guild m8 of mine came with the suggestion to delete your "Everquest2.exe", your "ms322.dll" (can't recall exact name should check at home but something like that one) and your complete "miles" directory. Then use station launcher and redownload these files. I did this yesterday and when i went into solusek eye bottom level i didn't get any graphic failure whatsoever, might have been a fluke but worth giving a shot. So let us know if this worked for you too !! <ul><li>Result: No improvement.</li></ul></li></ul><ul><li> We checked to make sure that Steroscopic 3D was disabled in the Nvidia Control Panel then went into EQ2 and disabled all 3D tools. ......So far, our computers seem stable. We hope this will be a permanent fix and not a fluke.<ul><li>Result: No Improvement.</li></ul></li></ul><ul><li> Setting Complex Shader Distance to -1 in Options (Advanced) / Performance section, stopped those display driver resets for me. So deadly combination is Complex Shader Distance at anything else than -1 and Water Reflections turned off.<ul><li>Result: No Imporvement</li></ul></li></ul><ul><li>I reverted to the EQ2 recommended drivers 196.21, 64-bit, and this was true for both. <ul><li>Result: Not applicable. I'm trying to run EQ2 from a 'gaming' laptop. It has a GeForce 280M, the desktop drivers are different from the notebook ones.</li></ul></li></ul><ul><li>My own 'why not since nothing else worked' attempt was to actually increase my graphical settings. <ul><li>Result: Inconclusive. This seemed to result in a slightly lower rate of error, but still existent. So any lower rate could have simply been my imagination.</li></ul></li></ul>So. Now what?

Te'ana

04-09-2011, 02:09 AM

During this past week my computer started having issues with EQ2 again. I went into Options and found that 3dD functions had been turned on again, probably by some update. I disabled everything in the 3D list of options again via the Advanced mode and everything is back to normal.

ccarro

04-09-2011, 12:03 PM

This is stupid.There are many places in many zones where this error only happends while facing a certain direction. Even with graphics all messed up or a black screen you can still turn your character away from the direction of the error and everything starts working fine (before the driver error). But, if you turn your toon back to face the direction where the error occured it gets all messy again and will continue to do so until the driver resets. After that everything will work great for hours.No high temps (ever) so please stop asking. There is more to this then such a noob tech support question about system temps (it would not be NEARLY as wide spread).Most people with this issue seem to be running NVIDIA cards with up to date drivers.The question here...is it a driver issue with certain aspects of the new shader or particle effects or is it an issue with the game?

Neiloch

04-09-2011, 03:28 PM

I'm pretty convinced this has something to do with shaders, water or even lighting. These errors only occur in outpost type areas for me. Such as 'Thurgadin Harbor', 'Goahmari Village' and the Othmir camp in Icy Fingers.When i'm out in the wilds of [Removed for Content] killing mobs and away from these areas, I get no problems.EDIT: can still occur when fighting ice golems.

Rainkng

04-09-2011, 05:21 PM

Dear SOE,My video card fried and I'm sad.Signed,A Sad EQ2 Player

Neiloch

04-10-2011, 03:15 PM

<cite>Neiloch@Kithicor wrote:</cite><blockquote>My own 'why not since nothing else worked' attempt was to actually increase my graphical settings. <ul><li><ul><li>Result: Inconclusive. This seemed to result in a slightly lower rate of error, but still existent. So any lower rate could have simply been my imagination.</li></ul></li></ul></blockquote>This actually seems to be working quite well, I'm really not sure why. I'm trying to isolate settings to see which one being high is making the driver not crash as much.

Te'ana

04-11-2011, 12:25 AM

There must be several different things happening to cause this error. I get the driver error in nearly any zone with no obvious connection between events. The only thing that works for me is to get rid of Stereoscopic 3D effects, which keep popping up with new updates. I wish whatever is causing it would just go away for good <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" />

ccarro

04-11-2011, 09:06 AM

One place it happends a lot is in Sanctum of the Scaleborn at the bottom of the zone in the area where the x2 drakkota's are at. Many times as I would pull the golems in this area, I would get graphical problems if facing the wrong direction. Turn my character away to face a different direction and the problem would go away (but would come back if turned in the same direction again until driver reset).

Neiloch

04-16-2011, 08:59 PM

So no new updates on this?I hope it gets fixed by next billing cycle because if I can't play I see no reason to keep the subscription going.

TSR-JoshuaM

04-18-2011, 05:31 PM

<cite>Neiloch@Kithicor wrote:</cite><blockquote>So no new updates on this?I hope it gets fixed by next billing cycle because if I can't play I see no reason to keep the subscription going.</blockquote>I do too. Unfortunately with the hundreds of completely different causes for your drivers or hardware to stop responding, it may not be a fix SOE can provide as requesting your hardware to do standard calls and it failing isn't really something that is easily worked around, especially with hundreds of entirely seperate causes, nor does it address the issue to begin with, which is why does your drivers or hardware fail when asked to do something a majority of the hardware being utilized right now, even the same exact model, had no issues doing.I've had this issue myself many times. Each time, overheating video card or old drivers. Failed PCI-E slots have caused it, bad ram has caused it, corrupt game files have caused it, corrupt DirectX or improper driver installations have caused it.The only update that I can provide at this time is that every case seems to be unique and different solutions have been reached for every incident or are still being looked in to. What I suggest from anyone that has not already done so, please contact support directly and open a support ticket so that we can better track and trend this issue. The more information the better due to the amount of contributing factors involved. PM me your incident numbers as well.

Arianah

04-19-2011, 07:55 PM

After PM'ing you the information you requested, I haven't had the issue since. I didn't change anything about my computer or my in-game settings, so I don't know how the problem was fixed for me, but I haven't had a display driver crash in a while now /knocks on wood.

Leinna

04-23-2011, 10:18 AM

I also see this issue on a regular basis doing Public Quests. I am using 270.61 from nvidia on dual GTX 260 cards.

TSR-JoshuaM

04-25-2011, 03:49 PM

<cite>Leinna wrote:</cite><blockquote>I also see this issue on a regular basis doing Public Quests. I am using 270.61 from nvidia on dual GTX 260 cards.</blockquote>I do not believe EQ2 takes advantage of your dual video cards and in our testing it has caused a few issues. Just test cases, nothing official. Try it with one of the two disabled, let me know if it occurs again and how quickly. If you can check your temps throughout that would also help identify or eliminate a potential cause.

troodon311

07-12-2011, 06:06 PM

I have started getting this problem frequently as well. Didn't exist 2 years ago when I took a break from the game.

TSR-JoshuaM

07-14-2011, 01:26 PM

<cite>troodon311 wrote:</cite><blockquote>I have started getting this problem frequently as well. Didn't exist 2 years ago when I took a break from the game.</blockquote>Oh it existed since it's an error in your video card, not the game, but what may be emphasizing the issue now may be new or a progressive issue. Make sure you are using the latest drivers, DX9 revision, and that there isn't any conflicts or hardware issues like overheating. Those are the most common causes for your drivers to stop responding.ATI users have a lot of success with drivers prior to 10.12 or drivers later than 11.6. The drivers that fell inbetween had many reported issues with our games unfortunately.Nvidia users have reported a lot of success with the new 275.33 drivers but anything dated 2011 has been received well.

Sphiriah

07-22-2011, 11:49 PM

<cite>TSR-JoshuaM wrote:</cite><blockquote>Oh it existed since it's an error in your video card, not the game</blockquote>I fail to understand this response. In fact, the response in itself seems somewhat unprofessional.I have been experiencing this issue since I came back to the game about a week ago. It only happens in specific places. The screen will flicker black, and then I will get the crash and recovery.EQ2 is the ONLY game this happens in. How can it be the hardware if it's only this game that brings it out?

deadcrickets2

07-23-2011, 02:43 AM

<cite>Sphiriah@Permafrost wrote:</cite><blockquote><cite>TSR-JoshuaM wrote:</cite><blockquote>Oh it existed since it's an error in your video card, not the game</blockquote>I fail to understand this response. In fact, the response in itself seems somewhat unprofessional.I have been experiencing this issue since I came back to the game about a week ago. It only happens in specific places. The screen will flicker black, and then I will get the crash and recovery.EQ2 is the ONLY game this happens in. How can it be the hardware if it's only this game that brings it out?</blockquote>Only unprofessional if not true. Do a search on that error string and you'll find it's quite common since the introduction of Vista and then 7.

Loranthala

08-05-2011, 05:24 PM

This has gotten infinitely worse since I updated to 275.33 like you recommended. I am not sure what I can turn down in my settings to reduce the occurance, i'm not kidding when i'm talking 5-6 times an hour, every hour that I play. Its worse in some places (Sol Eye is HORRIBLE) and seems to happen even in gumbi mode.

TSR-JoshuaM

08-05-2011, 06:03 PM

<cite>Simonx@Unrest wrote:</cite><blockquote>This has gotten infinitely worse since I updated to 275.33 like you recommended. I am not sure what I can turn down in my settings to reduce the occurance, i'm not kidding when i'm talking 5-6 times an hour, every hour that I play. Its worse in some places (Sol Eye is HORRIBLE) and seems to happen even in gumbi mode.</blockquote>Please open a support ticket with your MSINFO file. Also, taking a temperature reading of your GPU leading up to the error occurring can identify, or rule out, a potential overheating failure. I use 275.33 myself and play EQII quite a bit, I haven't had these issues, personally, since the launch release of Windows Vista when the drivers werent up to par yet.

Narsikus

08-08-2011, 11:49 AM

<cite>Simonx@Unrest wrote:</cite><blockquote>I am not sure what I can turn down in my settings to reduce the occurance,</blockquote>You need to set Complex Shader Distance to the lowest possible setting, which I believe is -1.I can set my display options to "extreme quality", then go turn that one setting down to -1 and I don't ever get the DDSRAHS error.It's a shame too, since that setting makes the game look really bad. For instance, in the new halas housing, you don't get the pretty view out the windows. You just see a "white" screen and you have to actually walk outside to see the view. Like I've said before on this thread, I have a really nice and expensive gaming machine, yet I can't run a game from 2004 on max settings. I've done all the troubleshooting listed here as well. And nothing in my machine is "overheating" which seems to be the most common excuse this keeps getting blamed on. This is a problem with the graphics settings of the game which they need to fix. In the meantime, you got a choice of having it stable yet homely, or beautiful but volatile - which is not unlike the choice we have of women. But when it comes to video games, I want my cake and I want to eat it too.

TSR-JoshuaM

08-08-2011, 11:53 AM

<cite>Narsikus@Kithicor wrote:</cite><blockquote><cite>Simonx@Unrest wrote:</cite><blockquote>I am not sure what I can turn down in my settings to reduce the occurance,</blockquote>You need to set Complex Shader Distance to the lowest possible setting, which I believe is -1.I can set my display options to "extreme quality", then go turn that one setting down to -1 and I don't ever get the DDSRAHS error.It's a shame too, since that setting makes the game look really bad. For instance, in the new halas housing, you don't get the pretty view out the windows. You just see a "white" screen and you have to actually walk outside to see the view. Like I've said before on this thread, I have a really nice and expensive gaming machine, yet I can't run a game from 2004 on max settings. I've done all the troubleshooting listed here as well. And nothing in my machine is "overheating" which seems to be the most common excuse this keeps getting blamed on. This is a problem with the graphics settings of the game which they need to fix. In the meantime, you got a choice of having it stable yet homely, or beautiful but volatile - which is not unlike the choice we have of women. But when it comes to video games, I want my cake and I want to eat it too.</blockquote>It is not a graphic setting in the game causing the issue in and of itself. Please contact our support staff directly for any further assistance on these types of errors, I am locking up this thread permenantly.