!!Error!!

(p3iN) #1

hi all

after a few minutes playing,this error heapens

how i fix that?

thx

(Jaquboss) #2

Stock ET , mod , BOTS ?
Specify please!

(chr0nicles) #3

Disable VC++ debugging monitor, if you can’t then disable windows error reporting

In windows XP

Press windows key ( the key with the windows logo on it) + pause
click on the advanced tab, click on the “error reporting” button on the lower right.

Disable error reporting and uncheck all checkboxes.

Reboot.

cu soon :slight_smile:

(p3iN) #4

Disable VC++ debugging monitor, if you can’t then disable windows error reporting

In windows XP

Press windows key ( the key with the windows logo on it) + pause
click on the advanced tab, click on the “error reporting” button on the lower right.

Disable error reporting and uncheck all checkboxes.

Reboot.

I made this, and now the game crashes

help plz

:frowning:

(chr0nicles) #5

and now the game crashes

Like i said, see you soon :wink:

Post us your full system specs including driver versions.

(p3iN) #6

OS Windows XP Professional, Service Pack 1 (5.1 - 2600) UP Time 8m 37s -
Memory Usage: 246/1024 (24%)
Processor: 2-Intel Pentium 4, 3000MHz, 1024KB (0% Load) - Connection Miniporta WAN (PPPOE) @ 100Mb/s for 4m 22s (0.20MB up, 1.30MB down)] -
Video Card NVIDIA GeForce FX 5600 1152x864 32bit 60Hz -drivers 66.93
HDs: C:\ (2.19GB Free, 37.30GB Total)

(Cueeee!) #7

nice cfg though ;p

(Mr_Tickles) #8

You wouldn’t happen to be this “pain” would you?

(p3iN) #9

my guid 012204D04CE7D62C05D7D69C4691329E1E47D17B

u can check out here

(Mr_Tickles) #10

Then I guess that isn’t the problem :wink:

(p3iN) #11

help people :moo:

(chr0nicles) #12

Things you need to do:

#1 First we need to check if your memory is fine, download memtest and let it run for a couple of minutes ± 30min, if it doesn’t detect an error your memory is fine.

http://www.memtest.org/

#2 Update your motherboard BIOS.
Its essential you keep your motherboard bios up2date.

#3 If you are using SATA hdd’s make sure you use the latest SATA drivers and not the ones built in windows XP.

#4 Scan your system for virusses, install a good virus scanner and completely scan your system,
i prefer Kaspersky 5.0

Try these and then post again :wink:
let us know

(p3iN) #13

i have found how to fix the error :moo: its was runing at 125 fps,then i put 72 to see,then 43, with 43 no more crashes :clap:

(Ragnar_40k) #14

Maybe a problem with overheating and/or wrong mobo/graphic card/ram voltage then.

(p3iN) #15

the error come back,plz help :frowning:

(ouroboro) #16

lol. poor bastard

(chr0nicles) #17

Like we said do those tests, including checking cpu/system temperature. Open up your case and check the temperature while playing and right after it crashes.

(petameta) #18

Running a memory tester, or other test programs, won’t tell you that much. If it finds an error, you’ll know your memory (or maybe cpu/motherboard) is bad. If it finds nothing, your memory maybe is OK, but maybe not.

That’s because some errors only happen under very specific conditions. It’s possible that an error only occurs when you play ET.

I have a good example: I use a Slot 1-system as a DSL-Router. I had a P2-266 plugged in, somewhen the fan failed (what I noticed after it crashed often). So I changed the fan, the system bootet fine and worked without a problem. At least so far. Every time I started the Midnight Commander (a Norton Commander Clone), the system crashed. I plugged in another CPU and everything ran fine again (including MC). The point is that this special CPU for some reason only crashed when running MC, a CPU- or Memory-tester maybe hadn’t found anything (although I never checked).

(DG) #19

“(although I never checked).”
errr… :wink:

a decent memory checker should go through every single bit on the sticks.

(petameta) #20

That’s true. Anyway, it doesn’t mean it finds every error just because every bit is scanned. This may sound a bit stupid, but that’s the way it is. Some errors only occur for very specific access patterns. That means that a certain memory cell may only produces an error if some other cells (or the cell itself) were accessed before, and maybe only a specific access pattern produces this error. A RAM tester can’t test all possible access patterns, there are just too many.

In my experience, the only reliable way to test RAM is to take the RAM out of the PC and put another RAM module in. If it works, the RAM most likely is broken. Or maybe it’s not, just clocked too high.

I’d agree that if a lower FPS rate solves the problem, it most likely is a heat problem. So try to downclock, check fans, or maybe add some case fans. Try to run the PC with an open case, so the heat can get out easier.