8 réponses à ce sujet

[stlthx1]

Rig:
OS: Windows 7 64-bit Pro and Windows XP 32 Pro (Can boot to either)
MOBO:  ASUS Crosshair IV Formula
RAM: 8gig
Processor: AMD 1090t Phenom II X6 OC to 3.7ghz (Driver: 6.1.7600.16385)
Graphics: Dual (ASUS) AMD HD Radeon 6870 in Crossfire (Driver 8.861.0.0) (Catalyst versiion:11.6)
Sound: Integrated Creative SouldBlaster X-Fi in MOBO

If I forgot to list anything let me know and I'd be happy to list it.
I know its not an indicator but my rig runs DAO,DAII, and ME2 at the highest setting w/ no problems.

I have installed ME1 on both my operating systems (both patches and Bring Down the Sky).  In windows 7 I "press any key" then the world fades away for a second then crashes and completely closes out.  In XP it crashes at the same point but to a General Protection Fault. I have done the usual "run as admin" and compatebility stuff.  I have also tried using base clock for the processor and dissable the crossfire and other graphics features.  Im stumped and have no idea what to do next.  I would like to play ME1 because i havent played it before and really liked ME2.  I bought it as a value game off Amazon.com and had to Install both manually if that helps at all. 

If you have any ideas thanks in advance!
stlthx

[Bogsnot1]

Try setting your processing affinity to single core. ME wasnt designed with multi-core processors in mind, and thus can have issues with some, especially AMD's, as they often have cores runngin at slightly different clock speeds.

[stlthx1]

I start the .exe then go through the task manager and set it to only CPU0 and HIGH priority and it still crashes in the same spot.

[Bogsnot1]

Do you have any ASUS apps installed, such as GamerOSD, or SmartDoctor? They have been known to cause problems with ME2, and could also be causing problems with ME1.
Kapersky A/V is also a known culprit for causing crashes in games that run on the Unreal3 engine.

Also, if you have anything overclocked, try settnig it for its native speed.

[stlthx1]

The ASUS programs installed are AI suite, Probe II, ASUS updade, and TurboV EVO. I took off the two you mentioned because they did mess with ME2. The ones i have installed are only installed on my win7 partition and not on XP. I have tried the native speed on Win7 but not on XP. Ill post how it works.

[stlthx1]

Okay On win7 i set the clock to stock speed, i have the above mentioned programs installed, i have Mcafee total protection and Malware Bytes as my A/V. And still crashes

On XP There are no ASUS programs installed A/V is only Malware bytes and with stock clock i still get the GPF crash.

My XP partition Is as bare as i can get it ( malware bytes, ccleaner are pretty much it.) and the only game on it is ME1.

Still not working, I appretiate the help though.

[Bogsnot1]

The only other thing I can think of off the top of my head is possibly the display drivers. Probably best to try this out on the XP build as a basic test bed.
Download and install an older revision driver, such as 10.6. Nvidia drivers are more guilty of screwing up with older games than ATI, but it is possible the newer drivers have been tweaked too much to work properly with older games, such as ME.
Reinstall DX9.0c from the disk. It should have installed as part of the game install, but the manual install process may have skipped it, or done something to not allow it to install correctly.

Did you install BDtS before or after the 1.02 patch? BDtS has the 1.01 patch incorporated in it, and its possible it couldhave reverted the install back to 1.01 if you did it after the 1.02.

[mcsupersport]

You are either having one problem that is hardware effecting both operating systems, ie motherboard, harddrive, video card, ram, or you are fighting two separate issues. The last General protection fault on this board was fixed by replacing the Harddrive and reinstalling Windows.......but there are so many causes that may not even effect you.

To my mind since it is hitting both operating systems in the same location it is most likely a single issue. This assumption can get you into trouble but that is my feeling. Since it probably is(my assumption) one issue and thus hardware you may want to try all the standard fixes(software) and then see if you can sub out hardware. Look closely at cables, harddrives and the like and if you have spares you may want to install another hd and put windows on it to see if it makes a difference. How many spare parts do you have around???

[stlthx1]

I will try the DX9.0c and then the older drivers on the XP OS.. I installed 1.01 then BDTS then 1.02 patches