Aller au contenu

Photo

ME2 SAME AS ME1 CRASH CRASH CRASH CRASH


13 réponses à ce sujet

#1
Nogata321

Nogata321
  • Members
  • 2 messages
Bioware once agian you have failed your consumers one put out ME on pc and it fails its unstable crash's all day long people lose data due to the crash's as a consumer i dedicate my purchase's to Reliable products. I thought you would redeem your self after ME but of course you didint. I will not longer be purchasing biowares POS Games any longer and for the rest of you PC's out there i suggest you do the same they no longer care for the PC players we are an off-hand market second class your money is worth less to them then console players money.

#2
General Corrado

General Corrado
  • BioWare Employees
  • 19 messages
Hi Nogata,



Can you tell me more about the crashing? What is happening, any error message? What is your hardware specs?



Thanks Kindly



-Ryan

#3
PSUHammer

PSUHammer
  • Members
  • 3 302 messages
Nogata...just blindly blaming the game is nonsense in terms of PC gaming. Chances are, a driver update or a little bit of troubleshooting can help here. There are some volunteers on this forum that can assist as well as Bioware folks who are obviously helping.



Please post a DXDIAG printout here and we can look at your machine and drivers. Googel "DXDIAG" to learn how.

#4
karlen7

karlen7
  • Members
  • 8 messages
I'm having a lot crash issues my self. At fist it was crashing my pc (which at the time was over clocked) so i ran Core Temp with logging enabled to see if the core temperatures were being exceeded but it seems ME2 dose not like having Core Temp running in the back ground. the game began to crash to the desktop before i could load a save, so i killed Core Temp and de-overclocked my pc. unfortunately that still did not solve the problem it is still crashing, and often, some times blues screening, but not as often as just freezing. Side note when it is running it looks great not even the slightest frame rate drop and i have it set on max, guess i should back off the settings and see if it stabilizes.



any thoughts?



Windows XP Sp 3

2 GB Ram

AMD Athlon 64 X2 4800+

Dual SLI Nvidia Geforce 9800 gtx + running the latest drivers

creative SB Audigy 2zs running the latest drivers

500 GB raid 5 hard drive

#5
karlen7

karlen7
  • Members
  • 8 messages
No luck, on default settings the game still crashed back to the desktop... I'm out of ideas (other than buy it for Xbox and hope it dose not cause the TRoD)

#6
Verusman

Verusman
  • Members
  • 1 messages
played through the entire game. took about 30-31 hours and did not have a single crash. not even one. I did get stuck in a table once but a quick load of a saved file fixed that.



if the game crashes a lot you ned to fix your pc.

#7
Phonzo

Phonzo
  • Members
  • 137 messages
also if you are running vista or 7 the log from the event viewer can be useful. Especially if something crashes alongside the game.

#8
karlen7

karlen7
  • Members
  • 8 messages
well thank you, i'm so glad that you could inform me of that. i had not even thought that it could even be so simple. your help has been invaluable.



thanks verusman you have really enlightened me in the realm of my problem.

#9
PSUHammer

PSUHammer
  • Members
  • 3 302 messages
Blue Screens are almost entirely related to hardware failures or driver issues. Could be bad ram, underpowered PSU, overclocked anything (CPU or GPU), overheating, bad driver, etc.

#10
zacrobmer

zacrobmer
  • Members
  • 195 messages
Have you tried de-deactivating SLI? If you getting a blue screen odds are it is driver, memory or heat related.
 I'm sure you tried the following, but just in case.

1) Roll back you video driver to the last one that worked, making sure that you have used driver cleaner or some other program to scour the driver from your system.
2) Deactivate your Audigy and try the game, say what you will but the Audigy's were junk when they were new and Creative's driver history is mediocre at best. I'm sure it works fine for X game, just try it.
3)Do the normal "check for dusk critters" in your case, especially in your cpu heat sink, just because it looks clean does not mean the fins are packed full of dust. Remove the fan if possible and really get in there. If you are a smoker or live in a smoking household, get in there with a Q-tip dipped in alcohol and wipe the fins down, you will find a nice thick yellow layer of crap on all of your heat sinks. remove the side of your case and see what happens, if that works reevaluate your airflow.
4) Run Memtest 86, make sure that you do not have a stick of ram that suddenly went bad, just because it did not show in game X does mean that ME2 is not aggravating an already dormant issue.
5) Post your DXDiag and so we can look at it and check for errant programs/services that may be doing you in.

Also your AMD X2 +4800 is getting long in the teeth, especially if you have been overclocking it over the years. Are you still running a 939 chipset? The fact of the matter is that your CPU is the bottom end of the requirements, I'm sure someone will chime in that the requirements are overstated, whatever. If you are in the bottom tier you should assume you will need to make some tweaks/sacrifices to get the game to run well.

#11
karlen7

karlen7
  • Members
  • 8 messages
Thanks zacrobmer, those are all good thoughts, just ran Prime95 and got an error...F?#K

#12
karlen7

karlen7
  • Members
  • 8 messages

Modifié par karlen7, 26 janvier 2010 - 03:25 .


#13
xmenq3

xmenq3
  • Members
  • 1 messages
I'm having a lot crash issues.. Windows 7, ATI 4850 and AMD Athlon 64 x2 6400



Log Name: Application

Source: Application Error

Date: 26.01.2010 15:00:50

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: classic

User: N/A

Computer: NERO-PC

Description:

Faulting application name: MassEffect2.exe, version: 1.0.1593.2, time stamp: 0x4b2845cd

Faulting module name: MassEffect2.exe, version: 1.0.1593.2, time stamp: 0x4b2845cd

Exception code: 0xc0000005

Fault offset: 0x008dada6

Faulting process id: 0xe44

Faulting application start time: 0x01ca9e00fbbed08c

Faulting application path: C:\\Program Files\\Mass Effect 2\\Binaries\\MassEffect2.exe

Faulting module path: C:\\Program Files\\Mass Effect 2\\Binaries\\MassEffect2.exe

Report Id: b72ef1bc-09f4-11df-93c6-001e8c70913f

Event Xml:

<Event xmlns="http://schemas.micro.../events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2010-01-25T21:00:50.000000000Z" />

<EventRecordID>24279</EventRecordID>

<Channel>Application</Channel>

<Computer>NERO-PC</Computer>

<Security />

</System>

<EventData>

<Data>MassEffect2.exe</Data>

<Data>1.0.1593.2</Data>

<Data>4b2845cd</Data>

<Data>MassEffect2.exe</Data>

<Data>1.0.1593.2</Data>

<Data>4b2845cd</Data>

<Data>c0000005</Data>

<Data>008dada6</Data>

<Data>e44</Data>

<Data>01ca9e00fbbed08c</Data>

<Data>C:\\Program Files\\Mass Effect 2\\Binaries\\MassEffect2.exe</Data>

<Data>C:\\Program Files\\Mass Effect 2\\Binaries\\MassEffect2.exe</Data>

<Data>b72ef1bc-09f4-11df-93c6-001e8c70913f</Data>

</EventData>

</Event>


#14
Nogata321

Nogata321
  • Members
  • 2 messages
bump