Problem with BF2142

I have a Dell Dimension 8400. 3.2 GHz proc, 2 GB RAM. XP Media Center Edition. Logged in as Local Adminstrator.

Periodically when playing BF2142, I get bounced back to desktop and the Application Event Log entry reads:

Event Type: Error
Event Source:
Event Category: None
Event ID: 0
Date: 12/29/2006
Time: 6:44:29 PM
User: N/A
Computer: OFF-D45T5R61
Description:
The description for Event ID ( 0 ) in Source ( ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 6.
Data:
0000: 3f 3f d1 2a af e6 92 2d ??Ñ*¯æ’-
0008: 52 32 d9 22 ee e9 9a e5 R2Ù"îéšå
0010: 2e 2f c1 3a f3 f1 82 3d ./Á:óñ‚=
0018: 72 e8 b9 32 f9 f9 8a 35 rè¹2ùùŠ5
0020: 1e 1f f1 0a 8b c1 b2 0d ..ñ.‹Á².
0028: aa ee eb 02 d7 c9 ba 05 ªîë.×ɺ.
0030: 6a 22 46 b8 0b 28 b0 1d j"F¸.(°.
0038: 06 07 e9 12 cb f4 0d b7 ..é.Ëô.·
0040: 41 7f 90 6a a3 a1 d2 6d A�j£¡Òm
0048: 76 77 99 62 ab a9 da 65 vw™b«©Úe
0050: 6e 6f 81 7a b3 b1 c2 7d no�z³±Â}
0058: 66 67 89 72 bb b9 ca 75 fg‰r»¹Êu


Nothing else that I find in the groups or my crash analyzers tell anything. Even EventID.Net shows nothing.

Any help would be welcome. I have all the latest drivers for my devices in my system.

On Sat, 30 Dec 2006 02:25:13 GMT, lernebo <none.DeleteThis@000.com> wrote something
that piqued my interest enough to reply with:

>I have a Dell Dimension 8400. 3.2 GHz proc, 2 GB RAM. XP Media Center
>Edition. Logged in as Local Adminstrator.
>
>Periodically when playing BF2142, I get bounced back to desktop and
>the Application Event Log entry reads:
>
>Event Type: Error
>Event Source:
>Event Category: None
>Event ID: 0

Without an event source that is going to be difficult to track down, ID
0 will mean different things depending upon the source, but is usually
the base error for a source.

I seem to recall some other BF2142 players saying that they had this
problem when one of the patches was applied (1.05/1.06 ?), particularly
if they had previously had the demo installed.

Answer for some seems to be uninstall, use a registry cleaner or
manually get rid of all BF references in the registry, then re-install
and only use the newer full patches (not 1.01->1.04->1.05->1.06, etc).

Others have suggested disabling EAX if you use it, and disable VoIP
(actually disable in-game VoIP comes up a lot as a fix that stops CTDs).
--
Alfie
<http://www.delphia.co.uk/>
Why doesn't DOS ever say 'EXCELLENT command or filename !'