51 réponses à ce sujet

[Doofus42]

Samreay



Are you running the 196.34 nVidia drivers?



Have you updated your DirectX?



Feb 2010 at: http://www.microsoft...57-5ab8109cb4f5



What Visual C++ versions are you running?



July 2009 update at: http://www.microsoft...72-9112bab119c2



I have installed both the x86 and x64 versions on my Win7 x64 Pro system.



What type of audio are you using? Is the driver updated?

[Samreay]

@Herethos - Haha yes, Ive tried uninstalling the phys-x and letting the game install its version itself, but no luck. Ive also tried disabling Phys-x acceleration in the nVidia control panel but to no avail. And the game config utility and windows 7 both detect all four cores, but Ill give that exe fix a try anyway. Cheers.

@NebonRevurg - The problem is 90% of people playing this game will have SATA hard drives, they are the most common, and Ive already tried every single core fix out there just in case, but still doesnt work. Seems like Im doomed to watch the game crash forever.

@Doofus42 - Thanks for all the ideas. I think I'm going to try basically every fix at once today and see where that goes.

But so you know, Im running the 196.21 nVidia drivers, which is the latest driver for the 9 series cards. Im downloading that DirectX update now, thanks for the link, and Im also downloading the updae for Visual C++ just in case. And the audio is onboard, the mobo is the Penryn 1600sli-110dB. Its running the Realtek High Definition Audio Driver v6.0.1.5983, which is up to date.

But Ill install the other updates and let you know where its at.

Thanks mate.

Modifié par Samreay, 15 février 2010 - 09:57 .

[Samreay]

Damnit. Still crashing, updated everything Doofus42, tried the single core fix Herethos, even though both windows 7 and the game config picked up all 4 of my core (thought may as well try it, cant do no harm). Sigh. Im getting more resign to waiting 2 months and coming back when all the patches are release, but I dont want to do that...I want to play now!



Any luck on your part NebonRevurg?

[Herethos]

If you got OpenAL installed from some other game try uninstalling that. Run the game and see if theres any difference.
Try everything as default in ME2config, and set the game resolution to something like 1280x1084 , if it didn't work disable sound in config program and see if that did anything different.

New OpenAl.
http://connect.creat...al/default.aspx

Perhaps narrow down problem with process monitor.
http://technet.micro...s/bb896645.aspx

Download and run it, then right click the process names choose exclude process name to hide all the ones you don't want to monitor, run Mass Effect 2 by starting the executable \\mass effect 2\\binaries\\masseffect2.exe so you don't start the launcher.

Modifié par Herethos, 15 février 2010 - 10:37 .

[steve0070]

Samreay



It sounds that the problem your experiancing might be part (lack of avaible HHD) to run.Yet you've said your using a 1tb hhd.



This might or might not work but you could try the defrag program. To double check that the files are in order and to check to see if any clusters are corrupted.

[D4zed_Confused]

I know this might not help, but worth checking anyway as it solved 95% of my problems: Heat?



I went through a patch of crashing games, and eventually traced the source to the heat in the case.

My gfx card was idling at 65C and the cpu had all 4 cores at 55C, this all went through the roof when I started a game, and it would just freeze up. Gfx card is a GTX8800, which now has an aftermarket heatsink on it - in-gmae temps have dropped 20C. My cpu is also idling at 38 to 42C & usually stays below 60C in-game now thanks to better case (antec300) housing the same components.



Good luck.

[NebonRevurg]

Well I got the game working using the "Green Screen" fixes here http://social.biowar...905917/1#906648

[Samreay]

Wow, thanks for all the responses guys...however I may be straining you to your wits end with this.

@Herethos - Uninstalled OpenAl, reinstalled the new version, no luck. Went into config and changed to windowed at that resultion, everything on default at first, no luck, changed everything to low or off, no luck, turned audio off with still no luck. I did download and install Process Monitor though, and at the end of the post Ill put some of the last lines from masseffect2.exe before it crashed.

@steve0070 - Yeah, I doubt its the hard drive for me, Ive defraged before to try and fix it, and reinstalled it after creating large 20gb data files to make sure everything got written to new sectors, just in case (though never had a problem with bad sectors before, its run flawlessly).

@D4zed_Confused - My computer runs without one side of the case for extra ventilation normally to keep heat down. That said, I've monitored the temps for the CPU and GPU through what I can get of the game, they all run stable (I should hope so for the CPU, seeing I have a massive Thermalright Ultra 120 eXtreme installed on it).

@NebonRevurg - Ah well, that was one of the first fixes I tried, with no luck. Haha probably should have known it wouldn't help as I'm not a single core.


But thank you to all you guys offering your help, time and ideas, it is really appreciated.

And back @Herethos, I'm not sure if these will be much of a help, but here are some of the lines from the end of masseffect2.exe until the error program kicks in. Sorry, just tried copying and pasting it, but some of the symbols arent allowed in a text box, so please tell me if this link doesnt work. Also, would if the information is beneficial to discovering the root of the error, should we draw it to the attention of a BioWare employee?

img684.imageshack.us/img684/93/me2crash.png


Cheers


Modifié par Samreay, 16 février 2010 - 09:12 .

[Herethos]

Thanks the link worked, I think the error happens before those lines though, those looks like symbol libraries, perhaps when the game is creating dump file in \\My Documents\\BioWare\\Mass Effect 2\\BIOGame\\Logs\\ look in there and see if you have any files named unreal something .dmp. I don't know if the game automaticly sends those back to Bioware (via the ingame send feedback option in options) or are left there for the devs to take a closer look at.



I guess you've tried this already, reinstall .net framework perhaps it got corrupted. Also run windows update, install service packs/hotfixes etc if you haven't done so yet after the fresh install of windows 7.



.net framework

http://www.microsoft...en/default.aspx

[Samreay]

Haha yeah, updated .NET framework was the first thing I did



However, you sir, are a genius, I have a million different unreal....dmp files, is there a program I can use to view them.



And if you wanted, I've put the latest one in MegaUploads, heres the link:



http://www.megaupload.com/?d=ZNLQ4W94



I dont know what I'd do without you Herethos

[Herethos]

http://www.microsoft...ng/default.mspx
Seems to open it just fine. You'll want symbol package and debugging tools for windows x64 I guess since its your OS. Go to start then Debugging tools for Windows... run WinDbg go to file then symbol file path and point to the folder you installed the symbols to. Then select Open Crash Dump.

If you have problems with the symbols try pointing to this link: http://msdl.microsof...ownload/symbols
It will take alot longer to load then however. Or have both your folder and the link but seperate them with a ;

Once in try typing !analyze -v in the small command box at the bottom.

Check your ram:
Try pressing windowskey+R or go to start>run then type in mdsched.exe and run the test to see if your ram is ok.

[Samreay]

Okay, I've run the Memory diagnostic over several passes, and it says all my RAM is fine. Ive also run Memtest+ and it comes up good as well.



So that brokers the question, how on earth am I getting the game to crash from an INVALID_POINTER_WRITE (as I quote).



Every singly crash appears to be caused by this error, here are some of the details (I know this may not help you much Herethos, Im just not sure what else to do, Im going to try and google up some solutions but even google may fail me I fear).



FAULTING_IP:

MassEffect2!GColor::GetHSI+c66e

00c6c64e 8b11 mov edx,dword ptr [ecx]



EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)

ExceptionAddress: 00c6c64e (MassEffect2!GColor::GetHSI+0x0000c66e)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 00000000

Parameter[1]: 2a2946e0

Attempt to read from address 2a2946e0



DEFAULT_BUCKET_ID: INVALID_POINTER_WRITE



PROCESS_NAME: MassEffect2.exe



ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.



EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.



EXCEPTION_PARAMETER1: 00000000



EXCEPTION_PARAMETER2: 2a2946e0



READ_ADDRESS: 2a2946e0



FOLLOWUP_IP:

MassEffect2!GColor::GetHSI+c66e

00c6c64e 8b11 mov edx,dword ptr [ecx]



FAULTING_THREAD: 00000a74



PRIMARY_PROBLEM_class: INVALID_POINTER_WRITE



BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_WRITE_INVALID_POINTER_READ



LAST_CONTROL_TRANSFER: from 0196d1d6 to 00c6c64e



STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

29c5fe4c 0196d1d6 29c5febc 0196d1ec 0196d218 MassEffect2!GColor::GetHSI+0xc66e

00000000 00000000 00000000 00000000 00000000 umbra!Umbra::OBBModel::create+0xb6





SYMBOL_STACK_INDEX: 0



SYMBOL_NAME: MassEffect2!GColor::GetHSI+c66e



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: MassEffect2



IMAGE_NAME: MassEffect2.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 4b2845cd



STACK_COMMAND: ~17s; .ecxr ; kb



FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_MassEffect2.exe!GColor::GetHSI



BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_WRITE_INVALID_POINTER_READ_MassEffect2!GColor::GetHSI+c66e



WATSON_IBUCKET: 1674557841



WATSON_IBUCKETTABLE: 1



WATSON_STAGEONE_URL: http://watson.micros....htm?Retriage=1



Followup: MachineOwner

[Samreay]

Bumping again, though I dont know if anyone can really help at this point, when the error seems so weird.

[NebonRevurg]

I'm not sure if this will help or not. If you're using a disk version of the game, try registering it on the EA downloader and download the game with that version of the game and reinstall it (you'll need to uninstall Mass Effect). You may consider reinstalling the game in a different directory, and doing a full surface scan of your hard drive.



Based on the error dump, it looks like you're getting system memory related errors, which could be caused by any number of things, ranging from a bad memory stick (easy enough to test, just try pulling the memory sticks out one at a time and replacing them), to system errors with software, to video memory issues. You may want to start checking your hardware for general errors, but there are others more educated than I who can direct you on how this might work for you. I do know that many types of errors are difficult to locate using software diagnostics, so I wish you luck.



Sadly I'm not familiar with the way windows 7 allocates memory as I haven't had a chance to install it myself and learn its functions.

[Samreay]

Haha no worries. Firstly, I cant download from EA manager, as (seeing Im in australia where internet sucks) I dont have the amount of download that Mass Effect 2 would require, so I have to rely on the physicals.



And Ive run memtest repeatedly and it says no errors, Ill scan the hard drives with seagate in a tick, and Ill try running some video card memory checkers when possible (have already done a stress test with no artifacts).



Thanks for the tips.

[Samreay]

Update: RAM has tested 100% fine again. VRAM testing has returned 100% fine again, hard drive has returned fine... what on earth could be causing this error. So frustrating! Running an artifact scanner overnight to hope and force something out. But I have to ask, if this is hardware related, how can Mass Effect 2 be the only thing that is giving me problems?

[Rageaholic]

I take it you're using Seagate's SeaTools to run tests. Have you tried the old CHKDSK /r?

[Samreay]

Yes, SeaTools, but no I havent tried CHKDSK /r, ill do that now.

Cheers

EDIT: CHKDSK ran without detecting any problems, game still doesnt work. HDD checks fine, GPU stress testing came back fine, CPU and RAM testing came back fine. Sigh.

Modifié par Samreay, 19 février 2010 - 12:05 .

[OneBadAssMother]

Get the "green screen fix"



http://social.biowar.../index/905917/1

3rd post down



It should fix it, the game seems to be developed primarily for dual-core, not single or quad-core.

[Samreay]

Ive already tried various green screen fixes, and I tried this one again, but still the game crashes. I get the green square and about 2 seconds later the "Mass Effect has stopped working" dialogue box would open. Wish I could figure out what's going on.

[Samreay]

Okay, I randomly decided to try a saved game, so I browsed the forums and downloaded a soldier save game, level 26. Put it in the right folder and open up mass effect. It loaded. No problems what so ever. I could play it. So for some reason I just cant make a new character, so it much be something wrong in the game files. Maybe I got a dud.

[OneBadAssMother]

Back in Dragon Age, a few people had problems with their quad-cores, and started changing CPU-affinity settings to switch to dual or single core operation.



Try it, cause either then that... I'm sorry but seems I cant help you. Have you tried imported an ME1 savegame? You might also want to try the "iff fix" - in other words, during the 'press any key' screen, wait for the trailer to load up, play and finish, then press any key, and load the game.

[Samreay]

Yeah, have tried switch CPU affinity, still crashes. Importing ME1 save game - still crashes. Waiting for the trailer to play - still crashes.



I think Im about to give up anyway. Hopefully in a few weeks a patch will come out that somehow fixes it. Hopefully.



But thanks to everyone who has offered suggestions and ideas, it is really appreciated.



All the best



-Sam

[Jykoo01]

have you tried re-installing the game? it worked for someone i know, after he had a fresh install, everything was fine....he had a similar error to you, or maybe the exact same one im not sure, but as soon as he re-installed, it was fine.

[Samreay]

Haha Ive lost track of how many times I've installed it. Managed to get it working by manually creating a new game using Gibbed Save editor and loading that, as I can load games but not start new ones, its painful, but i can play (some of it, it still crashes a lot).



cheers