Crashing to desktop when selecting everon

[-ASS-Ebola 0]

My OFP is crashing to desktop either when I play a map on Everon or on Kolgujev. The only maps that work are Malden and Desert Island.

Does anyone have a solution for this problem?

Ebola

[theavonlady 2]

What version of OFP are you running?

[theavonlady 2]

Another question:

In OFP's directory, there's a text file named Flashpoint.rpt, which may contain a report documenting the crash(es). Does it?

[-ASS-Ebola 0]

Im running Version 1.46 and I have a Flashpoint.rpt

This is from the last crash:

=====================================================================

== D:\OperationFlashpoint\OperationFlashpoint.TMP0

=====================================================================

Exe version: Sat Feb 23 03: 00:50 2002

file:    

world:    eden

campaign:

battle:  

mission:  

=======================================================

Date: 02/23/02  Time: 03: 01:39

-------------------------------------------------------

file:    

world:    eden

campaign:

battle:  

mission:  

Exception code: C0000005 ACCESS_VIOLATION

Version 1.42

Fault address:  0052E641 01: 0012D641 D:\OperationFlashpoint\OperationFlashpoint.TMP0

Prev. code bytes: 85 C9 5E 74 05 E9 28 F6 F7 FF C3 8B 44 24 04 56

Fault code bytes: 8B 30 85 F6 57 8B F9 74 02 FF 06 8B 0F 85 C9 74

Registers:

EAX:281F9900 EBX: 00723280

ECX: 0013F36C EDX: 00000004

ESI: 0013F374 EDI:10848D00

CS:EIP:001B:0052E641

SS:ESP:0023: 0013F2F4  EBP: 0013F364

DS: 0023  ES: 0023  FS:003B  GS: 0000

Flags: 00010246

=======================================================

[theavonlady 2]

What is your detailed system configuration?

[UKPUSHER 0]

i had same problem BUT i was getting an in game error message which i had to simply press enter to skip it and reach the breifing screen ...........this only happened with everon and kolgujev and i had to complete reinstall as it was due to a user made addon  

[-ASS-Ebola 0]

I don't use unofficial AddOns cause I thought that would cause the crash

My Configuration is:

AMD Athlon 1,4Ghz

392MB Ram

GF2 GTS 64MB

on Windows XP

[UKPUSHER 0]

So this still happens after u do a full clean reinstall of OFP?

[-ASS-Ebola 0]

Yup, it's really annoying:(

[theavonlady 2]

Shooting in the dark:

- Delete all temporary files in Windows/temp

- Manually set Window's virtual swap file's max size to 1000 (must reboot)

- How many CD drives do you have and which are burners? What birn software do you have installed?

[ALDEGA 0]

== D:\OperationFlashpoint\OperationFlashpoint.TMP0

This is indeed pretty "fishy".

[-ASS-Ebola 0]

I have 2 CD-Drives. 1 DVD-Drive and 1 Burner and I'm using Nero Burning Rom 5.5

Oh and I do not have a OperationFlashpoint.TMP0-File

[theavonlady 2]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote ([ASS]Ebola @ Mar. 18 2002,20:37)</td></tr><tr><td id="QUOTE">I have 2 CD-Drives. 1 DVD-Drive and 1 Burner and I'm using Nero Burning Rom 5.5

Oh and I do not have a OperationFlashpoint.TMP0-File<span id='postcolor'>

I'm wondering if this is Nero messing up your PC's ASPI layer that is causing the problem during somepoint in gameplay but I doubt it.

About the TMP0 file,who knows! Most probably something temporary that OFP creates and then deletes at certain points.

[Mister Frag 0]

Since the problem is consistent and tied to specific islands, my guess would be that the .PBO file(s) for the island(s) are corrupted.

Could this be a system based on the VIA 686B chipset?

[theavonlady 2]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (Mister Frag @ Mar. 18 2002,21:35)</td></tr><tr><td id="QUOTE">Could this be a system based on the VIA 686B chipset?<span id='postcolor'>

Bite yer tongue!

[Mister Frag 0]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (theavonlady @ Mar. 19 2002,03:58)</td></tr><tr><td id="QUOTE"></span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (Mister Frag @ Mar. 18 2002,21:35)</td></tr><tr><td id="QUOTE">Could this be a system based on the VIA 686B chipset?<span id='postcolor'>

Bite yer tongue!    <span id='postcolor'>

They really should have called it the 666 chipset.

I'm surprised there hasn't been a class action lawsuit yet.

[ExtracTioN 0]

[ASS]Ebola m8 you said you was using version 1.46 but in the error message of your stays version 1.42 in the rpt file how can that be you say version 1.46 but the error was in 1.42

[-ASS-Ebola 0]

Oh yes sorry it was not the report of the last crash. This is the last one:

=======================================================

Date: 03/18/02  Time: 14:12: 08

-------------------------------------------------------

file:    

world:    eden

campaign:

battle:  

mission:  

Exception code: C0000005 ACCESS_VIOLATION

Version 1.46

Fault address:  004B20B6 01: 000B10B6 D:\OperationFlashpoint\OperationFlashpoint.exe

Prev. code bytes: 85 C9 5E 74 05 E9 BB 14 00 00 C3 8B 44 24 04 56

Fault code bytes: 8B 30 85 F6 57 8B F9 74 02 FF 06 8B 0F 85 C9 74

Registers:

EAX:27BB1400 EBX: 0073A8A0

ECX: 0013F358 EDX: 00000004

ESI: 0013F360 EDI:10596B00

CS: EIP: 001B: 004B20B6

SS:ESP: 0023: 0013F2DC  EBP: 0013F34C

DS: 0023  ES: 0023  FS:003B  GS: 0000

Flags: 00010246

=======================================================

[medvidek 0]

[ASS]Ebola: Send me flashpoint.rpt and context.bin files to support@bistudio.com with brief description of you problem. We will take a look on it.

[-ASS-Ebola 0]

Hi again,

thanks for your all help!!!

I solved the problem. It must be a conflict with any other of my games. I formated my game harddisk and reinstalled OFP again. And it works

I'll install my Games one by one and I'll tell you what game caused the crash.

Bye bye

Ebola

[Mister Frag 0]

Unless another game installed a component that runs while you play OFP, it can't be responsible for the problem.

More likely, something was messed up in your Windows installation or configuration, which you fixed by reformatting and reinstalling Windows.