1 of 1 people found this helpful
I appreciate your feedback on this matter. I will make sure your comment reaches the proper department for future consideration.
Thank you for taking the time to communicate this issue to us.
Thank you Allan, I am looking forward to the next driver updates, will test and provide my experience here.
Just want to say I'm having the exact same issue as well. It really sucks because the new drivers make the game run a lot better but not being able to access the menu makes it unplayable. Luckily I had an old restore point that should let me play the game again, but I'm praying a new update will fix this problem.
Hello my loved company intel I have a problem games Mass Efect 1games periodically takes off after 10-15 minutes after the game abozh when you go in the game menu it freezes and we throw out in Windows
I know that this is a problem in the drivers graphics adapter game on the system unit with processor Core I3 2105 HD3000 hope to address in the next version of driver
It seems that driver version 2622 has solved the issue, at least on Windows 7 64 bit, on a MacBook Air. I've tried ME 1 and so far no crashes :-) Thanks!
Update: I've had a few interesting crashes from Mass Effect 1 running under the HD 2622 drivers: a message is shown that I should clear up hard drive space as the system has run out of virtual memory. I'll try to write down the exact error code(s) next time this happens. Meanwhile, I've reduced the anisotropic filter level on the game from 8 to 4, this might possibly help (fingers xed).
I keep having crashes. The higher the anisotropy, the more often the crashes. Hm. Win 7 64, 4 Gigs of Ram, around 20 Gigs free on an SSD disk, i7.
This is the crash error message:
Ran out of virtual memory. To prevent this condition, you must free up more space on your primary hard disk. MallocLarge(size = 27709440, type = 4096, protect = 4, VM = 1986908160/2147352576)
... when this message is shown, I usually have to use alt-ctrl-delete to invoke the task manager where I can then quit Mass Effect.
It'd be great if you could have a look and possibly fix. Thanks!
... this might be something to do with Windows 7 64 bit. The MallocSize error in Mass Effect (and other applications) turns up quite often on Google. After some digging this might be an explanation:
I'm going to try this on the console:
> bcdedit /set IncreaseUserVA 3072
Funny thing is, this did not happen with the old drivers I used (2361 if I recall correctly).
... and another update: Applying the "Large Address Aware" flag to the Mass Effect executable as per
using the tool
actually helped. I have had no more MallocSize errors in Mass Effect 1. Now I'm a very happy camper with the 2622 drivers :-)
Have you guys tried the new driver version with Mass Effect 2 yet? Pretty curious if you can pause the game with that or it's still same old issues.
I've started playing ME 2 with the 2622 driver today. No crashes when hitting the esc key. No crashes from running out of virtual memory, either. In fact, the experience is quite pleasant :-)
Oh that is great news, thanks! And thanks to Intel as well for fixing this problem. Can't wait to try it out.
... oh, and for all those who find Mass Effect 2 a bit too dark -
The Bioware forum has an entry on one of the shaders used by Mass Effect 2:
---I have suffered with the heavy black shadows and tried changing the gamma settings and found posts suggesting to change Depth of Field to false in the gamersettings.ini.
which defines post processing, including the DoF effect. Changing that with a text editor can fix the shadow issue, but keep the effect over all.
float3 x = max(0,InLinearColour-0.004);It works for me so I hope others find this useful too.---Another post suggested copying the UberPostProcessBlendPixelShader.usf from Mass Effect (1) to the relevant Mass Effect 2 directory. I did that (not forgetting to back up the original Mass Effect 2 UberPostPr...whatever.usf) and it works very well.By the way - I used to play Mass Effect 2 on the "old" 2010 MBAir with Nvidia 320 integrated graphics. The game actually displays less graphics artefacts on the HD 3000 than on the Nvidia 320. The only thing I miss about the Nvidia card is its ability to set system wide anti-aliasing.