Author Topic: BattlEye Errors (Read 60457 times)

-Major- · « **Reply #120 on:** November 13, 2009, 10:55:22 am »

Quote from: $able on November 13, 2009, 10:16:21 am

But you still get the above AVs?

From: November 13, 2009, 10:26:41 am
Please, could you all test v1.109 with "/beclient test" enabled (make sure to enable it AFTER BE updated to 1.109!)? This will probably bring back the fps problem, but as people started to report these problems after I fixed it, I need to know if this is the reason.

with 109 I get no crashes, but horrible fps unless I'm alone.

Fujifabric · « **Reply #121 on:** November 13, 2009, 12:20:32 pm »

no crashes indeed.

$able · « **Reply #122 on:** November 13, 2009, 12:21:18 pm »

On the other hand, does this version crash without "/beclient test"?

Fujifabric · « **Reply #123 on:** November 13, 2009, 01:43:55 pm »

Yes, stops working.

-Major- · « **Reply #124 on:** November 13, 2009, 02:56:55 pm »

here is an access violtion without beclient test on 109

ki0sk · « **Reply #125 on:** November 13, 2009, 04:59:53 pm »

got another "soldat not working" pop up, forgot to enable test.

*edit*
played for about 20 minutes, had test enabled and got really low fps. No crash

Z i p p y · « **Reply #126 on:** November 13, 2009, 05:15:20 pm »

The crashing still persists, what can I do to help?

-Major- · « **Reply #127 on:** November 13, 2009, 05:59:13 pm »

write /beclient test, you will suffer from lower fps but won't crash (as far as I know).

Hand of Pownage · « **Reply #128 on:** November 13, 2009, 06:37:08 pm »

I'm using Vista, but running the program as Windows 2000.

With /beclient test, it didn't crash for a LONG time, but it did eventually, and I didn't get message.

-Major- · « **Reply #129 on:** November 13, 2009, 06:55:41 pm »

Quote from: Hand of Pownage on November 13, 2009, 06:37:08 pm

I'm using Vista, but running the program as Windows 2000.

With /beclient test, it didn't crash for a LONG time, but it did eventually, and I didn't get message.

would you post your event log, type eventvwr.msc in run and then in windows logs > application, find the error there, match the time settings and post Faulting module name:, Exception code: and Fault offset: or I guess even better, take a screen shot.

Z i p p y · « **Reply #130 on:** November 13, 2009, 07:47:28 pm »

I did /beclient test, and soldat had fraps lag... then crashed.

Hand of Pownage · « **Reply #131 on:** November 13, 2009, 08:42:52 pm »

Quote from: -Major- on November 13, 2009, 06:55:41 pm

Quote from: Hand of Pownage on November 13, 2009, 06:37:08 pm
I'm using Vista, but running the program as Windows 2000.

With /beclient test, it didn't crash for a LONG time, but it did eventually, and I didn't get message.
would you post your event log, type eventvwr.msc in run and then in windows logs > application, find the error there, match the time settings and post Faulting module name:, Exception code: and Fault offset: or I guess even better, take a screen shot.

Here are a few

Faulting application Soldat.exe, version 1.5.0.0, time stamp 0x2a425e19, faulting module user32.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0xc0000409, fault offset 0x00078630, process id 0x1674, application start time 0x01ca64c20ad2c290.

Faulting application Soldat.exe, version 1.5.0.0, time stamp 0x2a425e19, faulting module user32.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0xc0000409, fault offset 0x00078630, process id 0x1274, application start time 0x01ca64b8308bc9a0.

Faulting application Soldat.exe, version 1.5.0.0, time stamp 0x2a425e19, faulting module user32.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0xc0000409, fault offset 0x00078630, process id 0xb1c, application start time 0x01ca64b3611f5780.

SpiltCoffee · « **Reply #132 on:** November 13, 2009, 10:07:51 pm »

Quote from: $able on November 13, 2009, 08:36:14 am

Quote from: SpiltCoffee on November 13, 2009, 07:04:20 am
Had a friend with a similar problem. Got him to do /beclient test

Here's the message that appeared when it crashed:

"Exception: 5 0EEDFADE 7C812AFB 1 00000000 7 0050290B 0196A324"

That one is normal on a mapchange. Does he get any other message before it crashes (when that one doesn't come up)?

Nup. That was the only message he received, and then the game crashed.

Fujifabric · « **Reply #133 on:** November 13, 2009, 11:22:23 pm »

latest version (1.111?) still crashes for me (stops working) $:-\$
(this without /beclient test)

Faulting application: Soldat.exe, version 1.5.0.0, time stamp: 0x2a425e19
Fault Module: user32.dll, version 6.1.7600.16385, time stamp: 0x4a5bdb3c
Exception code: 0xc0000409
Offset Error: 0x00030195
Failed process ID: 0x110c
Application start time: 0x01ca64df5d37db21

$able · « **Reply #134 on:** November 14, 2009, 08:45:41 am »

Does it still crash now in version 1.113? I changed something that doesn't require a client update.

biohazard · « **Reply #135 on:** November 14, 2009, 10:25:09 am »

1.5.1

not sure about the other dll errors

$able · « **Reply #136 on:** November 14, 2009, 12:14:17 pm »

Update your BE to the latest version. There was a problem with 1.5.1 that was fixed in v1.113. Your BE Client should have been updated by the 1.5.1 installer though, so obviously something went wrong.

Anyway, could I get reports on the current BE in 1.5.0 please? BE doesn't really do anything in 1.5.1 at the moment.

Z i p p y · « **Reply #137 on:** November 14, 2009, 02:07:40 pm »

Posting back saying Soldat stopped responding after 10-30 minutes, what can I do to help?

Fujifabric · « **Reply #138 on:** November 14, 2009, 02:09:37 pm »

Quote from: Z i p p y on November 14, 2009, 02:07:40 pm

Posting back saying Soldat stopped responding after 10-30 minutes, what can I do to help?

well... same.

$able · « **Reply #139 on:** November 14, 2009, 02:23:54 pm »

Can you check if it's still the same error in the event log?

Anyway, it would be cool if I could talk to you guys directly on IRC (/query BE|Sable). Would make things easier.

News:

Author Topic: BattlEye Errors (Read 60457 times)