Fix for those "Blue" light Crashes: ship, colony, core (UPDATED)
#26
Posté 09 mars 2010 - 08:59
#27
Posté 10 mars 2010 - 05:49
LeoInterVir wrote...
DirectX is mainly used by the game ...
Yes, all games for windows nowadays use DirectX. They wouldn't even work if you didn't have it installed.
What I meant was that Vista and Windows 7 are the only OSes that natively support DirectX10 (W7 is DX11). And since everyone I see in this post is either using Vista or W7, I assume that it might be somewhat related to the way these two OSes handle DirectX, even if the game has DirectX10 turned off (for graphics cards that aren't DX10 or for some other odd reason).
My laptop, on the other hand, which is also running W7 Ultimate x64 and has a 8600M-GT has the same issues as everybody here.
Modifié par Terminus Pi, 10 mars 2010 - 06:34 .
#28
Posté 10 mars 2010 - 05:54
LeoInterVir wrote...
In one of the ini files I remember seeing something about nVidai optimization and I don't think the game was using it... maybe thats an issue?
Dunno... depends on the optimizations. If they are optimizations for newer models of Nvidia cards with newer pixel shaders and CUDA processors and so on, then they are supposed to be turned off on your system with the 8500GT.
Do you think you can find those lines again and post them here?
#29
Posté 10 mars 2010 - 06:44
Anyhow, I am running windows 7 and the 8500GT supports CUDA and DX10. I tried turning on DirectX 10 and it crashes the game on start-up. This game runs on windows xp, vista, and 7 so I doubt they really put the effort in to truely making the game DX10 capable, not to mention the game is on the 360. By the way, CUDA was supported by my old 6600GT.
The fact that your new graphics card works without any problems has nothing to do with DX and more to do with the drivers and architecture being different. It seems that either BioWare broke compatibility or nVidia's drivers aren't up to par. This actually helps narrow down the issue since it shows that newer nVidia cards are not affected.
#30
Posté 10 mars 2010 - 06:57
I have no idea if this works or not but if someone put it in theirs and would test it out it would be nice.
I put it in mine but that was after I beat the game and right now I'm still on the first mission in this play through. First time on insanity...
[Engine.ISVHacks]
bInitializeShadersOnDemand=True <---- didn't change this
DisableATITextureFilterOptimizationChecks=True <----- this came that way
UseMinimalNVIDIADriverShaderOptimization=False <----- was set to true
PumpWindowMessagesWhenRenderThreadStalled=True <----- was set to false
#31
Posté 10 mars 2010 - 10:57
Doh! Don't start flaming just because you forgot to put a "9" after DirectX. If you read your post again, it really sounds like: "it looks like the game uses DirectX". I wasn't mocking you and if you read all my posts you'll see that I try to be as polite as possible with people. This is a forum where people are supposed to help each other after all, so keep it civil.LeoInterVir wrote...
I meant to say DirectX9 is mainly used by the game, which I been hinting at in my posts. I thought you could have picked up on it. Thankyou for stating the obvious about Windows Vista (DX 10) and Windows 7 (DX 10/11).
I wasn't stating the obvious with Vista and W7 and their support of DirectX. I merely pointed out that these are the OSes where people are having problems. People with XP and with similar graphics cards as ours don't have this problem, so the first thing that I thought of game-wise was DirectX, so let me rephrase my previous posts:
"People with XP don't have this problem, but people with Vista and W7 do. Could the native DirectX support of the OS have any influence?"
Back to the cards - the 250GTS is merely a re-branded 9800GTX+ and doesn't differ that much from the architecture of, say, your card. The main difference being brute force, I recall someone here saying that the blue light/lightning effects may be overwhelming the graphics card for some reason (maybe bad coding?), making it unstable or even crash. This might be why the 250 doesn't crash and the 8600 does.
BTW, I have a save on the reaper core, to try out different things and tried on my laptop these changes you suggested in coalesced.ini. The game crashed immediately after the save loaded.
Modifié par Terminus Pi, 10 mars 2010 - 11:00 .
#32
Posté 11 mars 2010 - 04:37
The game gets touchy for some things.
I think they do more than just rebrand, they probably improve coding and design slightly, to a point where it makes some sort of difference. Then again it could just be something wrong with how the nVidia drivers communicate with Windows Vista/7. I remember that Windows now pokes its fingers in to driver management and the such more than what it did in XP. Anything is possible, after all one of nVidia's drivers that got removed from their site was killing fans and thus boards.
#33
Posté 11 mars 2010 - 06:05
Modifié par LeoInterVir, 11 mars 2010 - 06:12 .
#34
Posté 11 mars 2010 - 03:17
Sorry, Ididn't write that very well. What I meant to say was that I tried those lines from coalesced.ini in gamersettings.iniTerminus Pi wrote...
BTW, I have a save on the reaper core, to try out different things and tried on my laptop these changes you suggested in coalesced.ini. The game crashed immediately after the save loaded.
Meanwhile, while poking on other threads about crashes, I found some people were able to significantly reduce crashing problems (but not completely eliminate them) by simply opening the Nvidia control panel and pulling the slider all the way back to "performance" instead of "quality".
This looked like too easy to be true, but I gave it a try. Oddly enough, I was able to pass the reaper core like this. It started to stutter for a fraction of a second and the sound made that odd crackling sound it makes when it's about to crash, but it didn't.
I'll try to import to my laptop a few more saves of other troublesome areas to see if it really works or if I just was lucky this time.
Anyway, what works for me, might not work for everybody, so here are the specs of the laptop I tried it on:
Compal IFL90
Core 2 Duo T7700 2.4GHz
4GB DDR2
8600M-GT
Windows 7 Ultimate x64
Latest version of DirectX
WHQL 196.21 Nvidia drivers
No overclocks, tweaks or editing of ini files was done here
#35
Posté 11 mars 2010 - 06:18
I wish I had the 8600
Terminus can you email me the save you have: (my username) at live.com
Modifié par LeoInterVir, 11 mars 2010 - 06:19 .
#36
Posté 11 mars 2010 - 10:14
If that is your case, I could still try and send you the save on the Normandy, just before starting the Reaper IFF mission. You'll just have to play your way to the core.
#37
Posté 11 mars 2010 - 10:20
#38
Posté 11 mars 2010 - 10:38
Modifié par Terminus Pi, 11 mars 2010 - 11:14 .
#39
Posté 12 mars 2010 - 04:04
Terminus Pi wrote...
lol, we now have a new DLC heavy gun: a blue lightning gun called the Arc Projector. I imagine it will work like a charm for us, eh? XD
Yeah no kidding...can't wait to download, install, get out there and face some husks, whip out this and....crash to desktop
#40
Posté 12 mars 2010 - 08:11
#41
Posté 13 mars 2010 - 12:52
Aside from the grunt crash my crashes are exceedingly rare, but look like when my regular nintendo use to crash, and I have to hard restart my computer, is this the crash type most people are facing?
P.S. Warp combos seem to be crashing it more often.
#42
Posté 17 mars 2010 - 05:52
.:THERE MAY BE SPOILERS:.
I'm on some destroyed ship. There is a part where I have to reposition the laser beam (blue laser) so that it hits some target (I'm not sure what; I haven't gotten that far). When I do, it crashes. T_T.
Modifié par Varonine, 17 mars 2010 - 05:55 .
#43
Posté 18 mars 2010 - 01:59
#44
Posté 19 mars 2010 - 11:22
Varonine wrote...
I'm on some destroyed ship. There is a part where I have to reposition the laser beam (blue laser) so that it hits some target (I'm not sure what; I haven't gotten that far). When I do, it crashes. T_T.
Yep, mine crashes there also
I've tried looking away, updating, changing to fullscreen and back to windowed, but it still does it.
It sounds like alot of people are having the blue light problem, you would think they would fix it =.=
Not a happy customer....
Im running
Windows Vista Home Premium
Intel Core 2 Duo CPU T8100 2.10GHz
2GB ram
NVIDIA GeForce 8400M GS
Modifié par Lemondrop, 19 mars 2010 - 10:42 .
#45
Posté 30 mars 2010 - 07:19
Modifié par DontBannMe, 30 mars 2010 - 07:21 .
#46
Posté 31 mars 2010 - 07:22
#47
Posté 06 avril 2010 - 09:44
compared to ME1 pc, ME2 pc is really buggy, i've encountered many glitches, but i dont care as long as i enjoy the story. But now, i think this is just really testing my patience.
I brought the game for $99.98 (NZD) when it first came out, so im sure i deserve to expect a much better qualitied work than this. Love the story and characters, but hate the technical probs.
i hope they can fix this problem soon, im not making anymore excuses, or to try some other way to not look at the blue light, because this time it's literaly impossible. ;/
Bioware i hope you can come up with a solution some time soon.
Your loyal fan
Lisa
#48
Guest_Soverain_*
Posté 06 avril 2010 - 05:40
Guest_Soverain_*
AMD Phenom 2 quad core 940 processor
4 Gigs DDR2
NVIDIA Ge Force 9600GT
500 GBs Hard Drive
Windows 7 64bit professional.
my gamne and pc crashes at anytime and anywhere in the game, at any particular location, restarting the computer gives it a temperory fix, i have the latest Nvidia Drivers. would you solution work for quad core processors ?
Modifié par Soverain, 06 avril 2010 - 05:41 .
#49
Posté 06 avril 2010 - 05:58
Good luck I found away to get pass the problem, by putting an exteral fan on my video card during the blue light problems. The rest of the ame ran fine without the fan as does DAO and ME1. I tried posting a new post to see if I could get BW to respond, as there have been countless post about this problem. They locked the post, they didn't like what was being said. It was Woo who did this, so I believe they don't care.Paperdollies wrote...
same with others, game crashes at all 3 spots mentioned. i learnt to come out to shoot when the preatorian stop laser beaming, so i've over comed the 1st and 2nd crash spots, i had to re-do the preatorian boss many many times as my game crashes on me, before i finally got the hang of ducking away from the sight of the blue light, run around and around and shoot at the same time. this made the mission harder than it should be, took me twice as long as this method was really inpracticle. However since i managed to figure out a way to avoid the crash i just baged my complains and carried on playing. But at the IFF core?...unless i can fire without looking at the direction im shooting at?...i dont think i can actually overcome this.
compared to ME1 pc, ME2 pc is really buggy, i've encountered many glitches, but i dont care as long as i enjoy the story. But now, i think this is just really testing my patience.
I brought the game for $99.98 (NZD) when it first came out, so im sure i deserve to expect a much better qualitied work than this. Love the story and characters, but hate the technical probs.
i hope they can fix this problem soon, im not making anymore excuses, or to try some other way to not look at the blue light, because this time it's literaly impossible. ;/
Bioware i hope you can come up with a solution some time soon.
Your loyal fan
Lisa
#50
Posté 06 avril 2010 - 11:03
William e wrote...
Good luck I found away to get pass the problem, by putting an exteral fan on my video card during the blue light problems. The rest of the ame ran fine without the fan as does DAO and ME1. I tried posting a new post to see if I could get BW to respond, as there have been countless post about this problem. They locked the post, they didn't like what was being said. It was Woo who did this, so I believe they don't care.Paperdollies wrote...
same with others, game crashes at all 3 spots mentioned. i learnt to come out to shoot when the preatorian stop laser beaming, so i've over comed the 1st and 2nd crash spots, i had to re-do the preatorian boss many many times as my game crashes on me, before i finally got the hang of ducking away from the sight of the blue light, run around and around and shoot at the same time. this made the mission harder than it should be, took me twice as long as this method was really inpracticle. However since i managed to figure out a way to avoid the crash i just baged my complains and carried on playing. But at the IFF core?...unless i can fire without looking at the direction im shooting at?...i dont think i can actually overcome this.
compared to ME1 pc, ME2 pc is really buggy, i've encountered many glitches, but i dont care as long as i enjoy the story. But now, i think this is just really testing my patience.
I brought the game for $99.98 (NZD) when it first came out, so im sure i deserve to expect a much better qualitied work than this. Love the story and characters, but hate the technical probs.
i hope they can fix this problem soon, im not making anymore excuses, or to try some other way to not look at the blue light, because this time it's literaly impossible. ;/
Bioware i hope you can come up with a solution some time soon.
Your loyal fan
Lisa





Retour en haut






