1454 réponses à ce sujet

[Phonzo]

ok I just took some time with thitche and did some trouble shooting. His multicore is actually showing as a single core.



Please check to see the same thing...hit ctrl+alt+delete and in the taskmanager select processors. You should see either two or four graphs under cpu usage history. If you have a multicore and only see one then we need to continue troubleshooting. This implies that the operating system only sees one core and not four.



The configuration utility is basically polling windows system info i believe and the results it returns is the same as windows sees.



So you check and have a multicore and only see one core? Do the following:



Go to start

control panel

device manager



When device manager opens hit the little plus sign beside the word computer. Please write down what it says beside it and post it along with your cpu.

[blorbie]

I agree with Avarix Greenleaf. Not only is his icon of one who would espouse wisdom, but he has an excellent point that there are quite a few single core processors better than the 1.8 ghz Intel duo shown above. Thank you for looking to address the issue in the second patch, Bioware, but this should really be sussed out ahead of time for a potential issue on a mega-release that can affect so many users. As one who was a proponent of this game, getting three friends to purchase ME1 so that they would get into the story and buy ME2, I am disappointed that the product launch has not met expectations for so many users, especially after ME1 and DA:O were reversing the notion that the cost of upkeep required for PC gaming made consoles a better gaming platform.

[ohfarkyou]

Won't run either. I get a black screen on startup, followed by a Windows error saying "Mass Effect 2 has stopped working."

And this is in the Windows clipboard:

General protection fault!
History: GImage::GImage() Address = 0x894505   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0x9db826   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
AK::MusicEngine::Init() Address = 0xea3682   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
AK::MusicEngine::Init() Address = 0xe80e4b   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0x48e1eb   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0xba51dc   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0x573caa   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0x571649   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0x9d9abc   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0x9d6c41   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GImage::GImage() Address = 0x9d6e27   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
GColor::GetHSI() Address = 0xd6253b   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
BaseThreadInitThunk() Address = 0x758a3677 (filename not found) [in C:\\Windows\\syswow64\\kernel32.dll]
RtlInitializeExceptionChain() Address = 0x77cf9d45 (filename not found) [in C:\\Windows\\SysWOW64\\ntdll.dll]
GColor::GetHSI() Address = 0xd626b8   (filename not found) [in K:\\Mass Effect 2\\Binaries\\MassEffect2.exe]
Address = 0xfffde000 (filename not found)
Address = 0xfffde000 (filename not found)

(If that helps...)


Windows 7 x64
i7920
6 GB Ram
GeForce 8800 GTS
SoundBlaster XFi Platinum

[mignar08]

I have solved the issue. I have an AMd Dual core processor with 4 gig of ram and a 512 gig 8800gt vid card.
      MY bios was from 2004. I had an update for 2008 that i updated to.
            by the way save a restore point folks. I dont recomend it for those not skilled in messing with there bios updates. I dont think my 2004 bios was reading dual core.
           I now can play the game.

[Doug4130]

Michael Gamble wrote...

We're aware of the issue, and will be working on providing a fix in the *second* patch. The first patch is going to be released very shortly, and thus it is too late for this fix.

To be clear, the fix does ONLY impact single core users (as well as dual core users who only have one core reported by their operating system (beyond our control). As a result, this is lower than our min-spec, so it's not a matter of "not testing the game". We're doing this so we can create the best game possible, and make sure that everyone is able to play.

Ill post more information as I get it. We will try to release this second patch in a timely manner, but we also want to make sure any patch does not create new issues.

In the meantime, I encourage users to try some of the 'home grown' solutions no this thread (which, by the way are very clever), and also encourage those with dual core machines which are being reported as single core to try and find a source of that (again, outside the scope and beyond the control of BioWare).

Thanks.

I know I'm just a single person and my monetary contribution doesn't really affect your income or the revenue this game will generate, but man that's awesome, thanks a ton

[Medhia Nox]

Bioware tried to build a house with cheap materials - their "architecture" cut corners.



This game runs beautifully on my "single core" now that Sylenced fixed it for Bioware.



There really wasn't any need for this.



Mr. Gambel - you claim this game was made so "everyone" could play - or are you saying that Bioware would like to make it that way "now"? From the get go - obviously A LOT of people still have single core systems. If you were really interested in maximizing your consumer base - you would have also answered their isses. ((I'm also aware you're just the messenger - and I'm grateful you're here. "You" is just a broad generalization.))

[dremhunk]

I would like to add I have never ever had problems with any pc games even news up until now.

I buy only pc games and I buy CE at that.  I have much powerful cpu than a intel 2 duo core

Modifié par dremhunk, 29 janvier 2010 - 12:57 .

[DashRunner92]

Medhia Nox wrote...

Bioware tried to build a house with cheap materials - their "architecture" cut corners.

This game runs beautifully on my "single core" now that Sylenced fixed it for Bioware.

There really wasn't any need for this.

Mr. Gambel - you claim this game was made so "everyone" could play - or are you saying that Bioware would like to make it that way "now"? From the get go - obviously A LOT of people still have single core systems. If you were really interested in maximizing your consumer base - you would have also answered their isses. ((I'm also aware you're just the messenger - and I'm grateful you're here. "You" is just a broad generalization.))

The game is not "fixed" since some are cut scenesout from fix. 

[samson987]

have the same problem. Initial load worked but was very slow so I shut it down. Now it freezes at loading screen. Tried reinstalling and updating video card even though old one was fine. Still same problem. Any help or fixes would be appreciated.

[Blackout62]

Thanks for being willing to fix this Bioware.

[iamaddj]

Ive tried the novideo fix and it did not work. Sucks to be me I guess.

[T1l]

So there are people saying that they have ME2 running just fine on a single core processor?



Interesting.

[Shufly]

I want to that Ive solved my problem, I realized that it was my system that was infact not recognizing my second core all this time. I reinstalled my motherboard drivers and then re-updated my CPU drivers. went into msconfig, and setup for 2 cpu's BOOM it works even better now!

[digsafe]

I am in the same boat with the loading screen freeze and a single core.
System specs;

AMD 3700+
2.5 GB RAM
Windows XP w/SP3
Nvidia 9600 GT

I see on the box that the requirement for CPU is 1.8 HHz Core 2 Duo or AMD equivalent.
Not at all clear that "equivalent" means having multicore.
Bioware should never have have released this game like this.

Am really pissed.

[Finn mac Cumhaill]

My problem is fixed and game is working perfectly.  My PC was freezing during start-up movies and in start of gameplay for last few days.

As noted previously, I edited Shortcut to include this in Target field replacing current entry (keep quotes)

"C:\\\\Program Files\\\\Mass Effect 2\\\\Binaries\\\\MassEffect2.exe" -nomoviestartup

My PC Spec using Mass Effect 2 Config Utility (note processor)
------------------------------------------------------------------------------------------------------------------
Processor: AMD Athlon 64 FX-57
Clock Speed: 2817 MHz                                                           Physical memory: 2.00 GB

Display Adaptor: NVIDIA GeForce 7800 GTX                       VRAM: 256 MB
Driver Version: 196.21

Sound Adaptor: Realtek AC97 Audio
Driver Version: 5.10.0.5750

Operating System: Windows XP Professional
DirectX Version: DirectX 9.0c (Mar2009) or later
------------------------------------------------------------------------------------------------------------------

Hope this helps

[Eyezek]

same wow!!!!

[TMWolf22]

I fixed my core problem and now game runs smooth. I posted my solution on forums

[jasonnov118]

Mine says "Standard PC" under computer.



I have an Intel E8400 Dual Core processor and an Nvidia 750i MOBO with the latest bios/drivers.



Went into BIOS and did not see any option for enabling multi cores. In fact, it says the CPU is a 2.0 GHZ when it is actually a 3.0 dual core. I have windows service pack 3 and am still getting one core.



I tried to google this problem but cant seem to find a solution. Can you guys help me?

[bjdbwea]

Yes, the -nomoviestartup works, but you lose all movies, not just the startup-movies. It's like cutting random pieces from a movie.



And indeed, with that "fix" in place, the real 3D scenes so far work PERFECTLY FINE on the highest settings on my single core CPU, so there was NO reason in the first place to neglect and obviously not even once test the game on that hardware. What were they thinking, I wonder? Those requirements on the box may even discourage people with older hardware from buying the game when in fact their system would be totally capable of running the game - were it not for that stupid and completely unnecessary bug with the bik files of course.



Shame on you, BioWare. You never fixed the sound stutter bug in ME 1, and now this. Oh well, that's what we get for being not only honest customers, but even buying a game on release day.

[greghis]

thank you MG at Bioware, for asking the right people the right questions are securing a second patch.

[spike54]

Every time i start the game my screen goes black and then i get this error message

Problem signature:

Problem Event Name: APPCRASH
Application Name: MassEffect2.exe
Application Version: 1.0.1593.2
Application Timestamp: 4b2845cd
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdb3b
Exception Code: c0000005
Exception Offset: 00022272
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789



computer specs:

Intel® Core™2 Duo CPU E7300 @ 2.66GHz

NVIDIA GeForce GTS 250

4 gigs of ram

windows 7


Any ideas??? ive updated all of my drivers and everything ive also tried reinstalling

Modifié par spike54, 29 janvier 2010 - 02:22 .

[Eyezek]

same here

[OrioTecc]

I have disregarded CPU requirements for games for a couple of years now, always seems overkill. Replacing the bik load videos with stripped ones work for me as well, though I still get the stutter after the others play as well. Interestingly I believe I had a similar issue with another game a while back but I can't remember the details now, will update if I can remember.

[Eyezek]

this sucks

[Eyezek]

how do i fix this, i tried the short cut way and i don't think i'm doing it right