Just so the Devs may have another area to look into, this problem arose after the Season 7 update. How about you guys look into what you put in that update and compare it to what was before the update.
That way you can see whats wrong. And it shouldnt really be too hard, get a simple laptop, download STO, see the problem for yourself, and then dissect it with your developer stuff from there. I don't see why this is taking so long to figure out when Season 7 clearly seems to be the causing issue.
I understand Intel may be an issue too, but you guys have seemed to not even regard Season 7 as the reason for the issue. All I have heard is that Intel is the problem and it looks like a blame game to many of us. From our perspective, you guys are ignoring us and pointing fingers for your own sake just to keep your hands clean. We wont freak out and hate you guys for some faulty programming, just fix the issue so we can get back to playing! Thats all we want! Just to play STO without issues and have fun.
I am not entirely sure what version of my video driver I had before...I might be able to find it..not sure. However I can tell you that I only updated my driver after I found Season 7 to have this bug. But Intel updated more then just the device driver...something about the chipset? Not sure.
What intel graphics is the patch/fix for? I run STO on my laptop which has HD graphics 4000 running on win 7 pro and i have never had the game crash because of a graphics issue. Are there people with HD 4000 who had their computer crash?
Probably a dumb question. But you can't debug this remotely? I mean if you could I would gladly give my time and computer to the cause. (well not permanently, I need my computer)
We've tried internally reproducing the problem on two different pieces of Intel hardware (HD3000 & 4000, IIRC), on two drivers, with no luck. I've made some speculative changes to disable new GPU profiling code that might be causing problems with the new drivers. We've asked Intel for help, but until we can repro the problem we're kind of stuck, especially since it's resetting the display driver, instead of giving us a crash report. Reading through the threads, I noticed some posters discussing an October driver, and when I checked Intel's download driver site, it looked like a different version than what I tested. We're going to give that a shot, but all of our programmers are fully booked. We've been giving CS updates to communicate to the customers, but when there's pages and pages of posts in multiple threads, it can be hard to get the message out. I'll be posting in the thread I've linked above.
Until we can get an idea of what is wrong, and work with Intel to get a fix, rolling back the driver might help, as indicated in this thread. I noticed there is also a December driver update, and you could try that, but I haven't tested it.
Dave
Using windows 7, how can I get you exact hardware specs that will make it easier for you to find a compatible test system on your end, and which specs do you need? If that will help.
The problem definitely still persists, and is way worse in some areas that others. Mainly, I find the Deferra Adventure Zone bad personally, or ground worse than space in general. But also last night I was doing the mission Operation Gamma, where you have to fly inside an asteroid (so many more on screen textures probably), and even with my emergency stabalizing settings I had to get out of there before my system needed a hard reset. Sometimes Starfleet Academy can cause problems too, I think it is mainly when drawing the "main building" if you get far away from it and then close again. Sometimes on Explore Strange New Worlds it seems certain generated Asteroid Fields are a problem.
Basic theme there is when the game has to draw a lot of large textures quickly, it is far far far more likely to see this. I play a lot of Elite STF, daily space missions etc and most of them are fine.
That makes a lot of sense. Ground maps are worse for me as well and when I tried the Azure Nebular Rescue I crashed. When most space maps I am fine on. I have noticed that if I am too close to something it will cause a driver crash. It would also explain why it happens more when people are around me. But it is a bit contradicotry, since space should have more texture in it. So it must be partly the distance one is away from it. I did not post this earlier because it is only people with Nvidia cards that have posted this error code. They are both experiencing the location based crashing as well.
fatal error: direct3d driver returned error code
(DXGI_ERROR_Device_Removed) while creating index buffer
technical detail: 4.79 gb ram, 746.28mb virtaul space available
Fatal Error: Direct3D driver returned error code (DXGI_ERROR_DEVICE_REMOVED) while creating a texture.
Technical Details: DXGI_ERROR_DEVICE_REMOVED while creating 2D texture size 512x512 (10 mips, RTEX_DXT1), 13.21 GB RAM, 1.09 GB virtual space available
Since the people who posted these error codes are not using Intel GPUs I am not sure how helpful those are if at all. But who knows maybe they will help. I don't get these error codes at all. And as far as I know anyone with a Intel GPU has not either.
Just occurred to me. That the easiest way to test and maybe reproduce this bug is to go to the fleet starbase system. That is a guaranteed system freeze for me.
OK! whatever is on Tribble is a fix! I ran around ESD!!!! And went to the fleet starbase system and Starbase 234!!! YAY!!!! Let hope it works on Holodeck!!
We've tried internally reproducing the problem on two different pieces of Intel hardware (HD3000 & 4000, IIRC), on two drivers, with no luck.
There doesn't seem to be a driver issue with HD3000 as I've used two different computers with the latest drivers and have had no issues with the game crashing the driver. However, the HD2000 seems to be the one causing the issue as I had issues with it until I downgraded my driver to 8.15.10.2253 11/28/2010. That version of the driver fixed the crashing on my laptop with HD2000 but obviously I would like to use the latest drivers as those are 2 years out of date now.
It would be interesting to see if its people with the original Intel HD and HD2000's that are causing the driver crash, as I haven't seen anyone specifically report issues with HD3000/4000's.
I am really tired of STO crashing and crashing my machine (not counting the thousands of time's it crashed just the video driver.) I have lost hundreds of millions of EC, hundreds of thousands of dilithium and thousands of omega & fleet marks.
I tried to get help from PWE's "Customer Service" and they just close the case. I'd even be willing to run debug code on the machines having problems (one laptop with Intel GPU (integrated in the P6100 CPU) and another machine with dedicated ATI (dual) GPU with 2GB VRAM.....) but of course, no response.
I am really tired of STO crashing and crashing my machine (not counting the thousands of time's it crashed just the video driver.) I have lost hundreds of millions of EC, hundreds of thousands of dilithium and thousands of omega & fleet marks.
I tried to get help from PWE's "Customer Service" and they just close the case. I'd even be willing to run debug code on the machines having problems (one laptop with Intel GPU (integrated in the P6100 CPU) and another machine with dedicated ATI (dual) GPU with 2GB VRAM.....) but of course, no response.
Well your issue seems to be much more pronounced them mine. It looks like we share almost the same system. Not sure if we do in fact though. However..Have you been on Tribble? Holodeck still has the bug on it, but I tried out Tribble and they seem to have fixed the problem. That fix should go live this week. I hope it does! Not having detailed specs of your machine it is hard to know if your system is compatible or not. It should be. http://techsupport.perfectworld.com/showthread.php?p=42631&posted=1#post42631
It is specifically about Intel machines that are not running the game properly. DarthPanda16 has his head on straight and should be able to advise you better then I. However I did post earlier in this thread a link to the model of the laptop I am using to play this game with. You can check that out as well. That should show whether or not it is a compatibility issue or not. Which I doubt it is.
Well your issue seems to be much more pronounced them mine. It looks like we share almost the same system. Not sure if we do in fact though. However..Have you been on Tribble? Holodeck still has the bug on it, but I tried out Tribble and they seem to have fixed the problem. That fix should go live this week. I hope it does! Not having detailed specs of your machine it is hard to know if your system is compatible or not. It should be. http://techsupport.perfectworld.com/showthread.php?p=42631&posted=1#post42631
It is specifically about Intel machines that are not running the game properly. DarthPanda16 has his head on straight and should be able to advise you better then I. However I did post earlier in this thread a link to the model of the laptop I am using to play this game with. You can check that out as well. That should show whether or not it is a compatibility issue or not. Which I doubt it is.
I haven't tried Tribble in a couple of weeks, but maybe I will.
I looked at my event logs and I've found that STO has crashed my display driver (Event ID 4101) 2929 times so far.
The one place I've noticed that I've never had a problem is when mining for dilithium on the asteroid.
I have never had a problem mining Dilthium. However I do get problems when traveling to the Asteroid. When I pass the great cloud of people around DS9 and Bajor, however I do get black screens of death. Though never enough to freeze my system.
Yeah the flight *to* the asteroid can be a real adventure (worst spot I've actually seen just flying around the map actually), but the asteroid itself seems totally stable and always has been.
I really have my fingers crossed for when the Tribble fix goes live.
"We are smart." - Grebnedlog
Member of Alliance Central Command/boq botlhra'ghom
In case anyone missed it, a possible solution to the problem is part of tomorrow's patch notes.
I've been experiencing some nasty video hangups on a regular basis since Season 7 arrived, using a Radeon 5770, which has basically rendered the game unplayable and driven me off to GW2 (which is fantastic).
Hopefully this will help those of us experiencing issues. *crossing fingers*
Ok well I am not sure my game completely patched right. I did force it to manually, but it still has the blanking screen problem at higher graphics quality settings. Which means I am stuck at the lowest settings for the while. I am going to update my drivers again and see what that does. It appeared to happen when I was near other people in game. And since there was no on in Tirbble when I tested the fix, there was no way of knowing how other players would effect this bug.
For anyone who is having trouble patching the game today. Turn of "OnDemand Patching" in the launcher options. That seems to fix the problem. Game should patch after that.
So far, so good. I went to my fleet's starbase as well as played "The Big Dig" - both of these always crashed my machine. So far, not a single flicker. I'm keeping my fingers crossed that this has resolved it.
Got on this morning, put my settings back to the defaults instead of what I've been using to keep the game stable. Ran asteroid mining, an elite STF (Infected: The Conduit), an Investigate Officer Report, and the Tau Dewa Sector Patrol Daily. So far? Not a hiccup using normal settings again.
Fingers crossed, but this looks like things are at the very least on the right track. Good job guys.
"We are smart." - Grebnedlog
Member of Alliance Central Command/boq botlhra'ghom
After getting the patch today. (After spending yesterday freaking out about a patch that had not happened yet. Derp.) It looks like everything is back to normal. I did the Azure Nebular Rescue and finished it for the first time. And I was able to do some other missions in the new sector. So far so good.
Dear Devs, Never, ever ,ever, ever, ever do anything like that again. You almost lost me to D&D online.
On an i3 M350 with GMA HD, the patch seems to have resolved the crashing. I haven't been able to run in ground without the "driver has stopped" message since s7.
I've been holding off any purchases until at least the pre-s7 content worked reliably again. Looks like it does now. I just ordered two 60-day game cards, so I can finally get some of the vet rewards, and show a little support for the devs.
After the test last week on Tribble, and the release to Holodeck last night/early today, it seems to be fixed according to the wave of players who are saying it has been fixed.
Please note this does not mean ALL Intel video chipset users will be able to play the game. If you have an ancient Intel video chipset, you may be out of luck.
For those of you with this specific issue mentioned at the beginning of this thread, it should be fixed. Cryptic and PWE understand everyone's frustrations who were able to play during Season 6 with Intel GPUs, and who weren't able to play after the Season 7 launch. We are very glad to be hearing back from relieved and happy players.
Thank you all so much for your patience and dedication to your game!
Well... On my Intel GPU, it's still working so far....
But.....
On my dual ATI system, I'm still getting a Fatal Error when changing maps:
Fatal Error: There is not enough available video memory (D3DERR_OUTOFVIDEOMEMORY) while while [sic] creating a render target texture. Please choose lower resolution settings, or close other graphics applications.
Technical Details: D3DERR_OUTOFVIDEOMEMORY while creating 2D render target texture size 3072 x 2048 (RTEX_NVIDIA_INTZ)
Comments
That way you can see whats wrong. And it shouldnt really be too hard, get a simple laptop, download STO, see the problem for yourself, and then dissect it with your developer stuff from there. I don't see why this is taking so long to figure out when Season 7 clearly seems to be the causing issue.
I understand Intel may be an issue too, but you guys have seemed to not even regard Season 7 as the reason for the issue. All I have heard is that Intel is the problem and it looks like a blame game to many of us. From our perspective, you guys are ignoring us and pointing fingers for your own sake just to keep your hands clean. We wont freak out and hate you guys for some faulty programming, just fix the issue so we can get back to playing! Thats all we want! Just to play STO without issues and have fun.
Is that too much to ask?
Elite Defense Stovokor
Using windows 7, how can I get you exact hardware specs that will make it easier for you to find a compatible test system on your end, and which specs do you need? If that will help.
The problem definitely still persists, and is way worse in some areas that others. Mainly, I find the Deferra Adventure Zone bad personally, or ground worse than space in general. But also last night I was doing the mission Operation Gamma, where you have to fly inside an asteroid (so many more on screen textures probably), and even with my emergency stabalizing settings I had to get out of there before my system needed a hard reset. Sometimes Starfleet Academy can cause problems too, I think it is mainly when drawing the "main building" if you get far away from it and then close again. Sometimes on Explore Strange New Worlds it seems certain generated Asteroid Fields are a problem.
Basic theme there is when the game has to draw a lot of large textures quickly, it is far far far more likely to see this. I play a lot of Elite STF, daily space missions etc and most of them are fine.
EDIT: http://sto-forum.perfectworld.com/showthread.php?t=431901&page=5 These are the in game settings I am using. Without them, the game is pretty much totally unplayable. With them I'm like 90% ok.
"We are smart." - Grebnedlog
Member of Alliance Central Command/boq botlhra'ghom
Since the people who posted these error codes are not using Intel GPUs I am not sure how helpful those are if at all. But who knows maybe they will help. I don't get these error codes at all. And as far as I know anyone with a Intel GPU has not either.
Fatal Error: Direct3D driver returning error code (UNKNOWN: 0x88760870) while Locking vertex buffer.
Technical Details: 1.39 GB RAM, 1.22 GB virtual space available.
There doesn't seem to be a driver issue with HD3000 as I've used two different computers with the latest drivers and have had no issues with the game crashing the driver. However, the HD2000 seems to be the one causing the issue as I had issues with it until I downgraded my driver to 8.15.10.2253 11/28/2010. That version of the driver fixed the crashing on my laptop with HD2000 but obviously I would like to use the latest drivers as those are 2 years out of date now.
It would be interesting to see if its people with the original Intel HD and HD2000's that are causing the driver crash, as I haven't seen anyone specifically report issues with HD3000/4000's.
I tried to get help from PWE's "Customer Service" and they just close the case. I'd even be willing to run debug code on the machines having problems (one laptop with Intel GPU (integrated in the P6100 CPU) and another machine with dedicated ATI (dual) GPU with 2GB VRAM.....) but of course, no response.
Well your issue seems to be much more pronounced them mine. It looks like we share almost the same system. Not sure if we do in fact though. However..Have you been on Tribble? Holodeck still has the bug on it, but I tried out Tribble and they seem to have fixed the problem. That fix should go live this week. I hope it does! Not having detailed specs of your machine it is hard to know if your system is compatible or not. It should be. http://techsupport.perfectworld.com/showthread.php?p=42631&posted=1#post42631
It is specifically about Intel machines that are not running the game properly. DarthPanda16 has his head on straight and should be able to advise you better then I. However I did post earlier in this thread a link to the model of the laptop I am using to play this game with. You can check that out as well. That should show whether or not it is a compatibility issue or not. Which I doubt it is.
I haven't tried Tribble in a couple of weeks, but maybe I will.
I looked at my event logs and I've found that STO has crashed my display driver (Event ID 4101) 2929 times so far.
The one place I've noticed that I've never had a problem is when mining for dilithium on the asteroid.
I really have my fingers crossed for when the Tribble fix goes live.
"We are smart." - Grebnedlog
Member of Alliance Central Command/boq botlhra'ghom
I've been experiencing some nasty video hangups on a regular basis since Season 7 arrived, using a Radeon 5770, which has basically rendered the game unplayable and driven me off to GW2 (which is fantastic).
Hopefully this will help those of us experiencing issues. *crossing fingers*
I also had to force the game to patch because it did not do it automatically. Also I am playing with a Intel integrated HDgraphics card
"We are smart." - Grebnedlog
Member of Alliance Central Command/boq botlhra'ghom
Got on this morning, put my settings back to the defaults instead of what I've been using to keep the game stable. Ran asteroid mining, an elite STF (Infected: The Conduit), an Investigate Officer Report, and the Tau Dewa Sector Patrol Daily. So far? Not a hiccup using normal settings again.
Fingers crossed, but this looks like things are at the very least on the right track. Good job guys.
"We are smart." - Grebnedlog
Member of Alliance Central Command/boq botlhra'ghom
Dear Devs, Never, ever ,ever, ever, ever do anything like that again. You almost lost me to D&D online.
Unfortunately, it appears to have made things worse on my end.
Oh well, back to GW2.
I've been holding off any purchases until at least the pre-s7 content worked reliably again. Looks like it does now. I just ordered two 60-day game cards, so I can finally get some of the vet rewards, and show a little support for the devs.
Thanks Devs, this is what we wanted all along.
Now time to get back to blasting the Borg in STFs.:D
But.....
On my dual ATI system, I'm still getting a Fatal Error when changing maps:
Fatal Error: There is not enough available video memory (D3DERR_OUTOFVIDEOMEMORY) while while [sic] creating a render target texture. Please choose lower resolution settings, or close other graphics applications.
Technical Details: D3DERR_OUTOFVIDEOMEMORY while creating 2D render target texture size 3072 x 2048 (RTEX_NVIDIA_INTZ)
Note: This only started happening with Season 7.