It is very nice to finally have some feedback from you guys. Now instead of players just being angry at each other maybe we can start looking for a fix.

I don't know enough about hardware...But how old were those systems that you used to try and reproduce this?? I do know system is about a year to two old. It is hard to know since I did not buy it. But my guess is that it is 2010. Here is the link to the product page. http://us.toshiba.com/computers/lapt...50/L655-S5101/


(and before you trolls even start! It played season 6 just fine).

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.

Is that too much to ask?

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)

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/sh...=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.

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.

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!!

If STO crashes and I get an error... it often is a Direct3D error. Here's the last one I got:

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.