Null reference trying to host local server

(Dawg) #1

I tried creating a local server to test out a map that a friend is working on. However, when I attempted to ‘Host Game’ I get an immediate crash of the game. The error message clearly indicates that someone is trying to deref null. Is anyone else having this problem?

I have used the Host Game facility before patching to 1.02 without problem. This is the first time I have attempted it since patching. The error is consistent.

I attempted entering the ‘Play Online’ section and then backing out to ‘Host Game’ but it still occurs.

Here is a screenshot of the error message for the curious.

Dawg

(skinner) #2

i got loadsa memory errors a while before my memory died… are you using cheap memory?

(Dawg) #3

Nope. I have a full gig of Corsair.

I have no other memory errors and the game plays fine online.

Dawg

(SylverDragon) #4

May or may not be related, but a while back anytime I attepmted to host a game ET would crash out to windows everytime I hit the host game button. I don’t recall what the error said at this point, unfortunatly. The fix for it was to remove all of the custom map files from my ET directory. Once I did that, hosting started working again. (I don’t remember who posted that fix, but I found it on this forum somewhere. Just don’t want to take credit for someone else’s fix here.)

(=TAC=Chron) #5

i would still recommend troubleshooting the RAM, just because it’s corsair, it could still be squirrelly. just pull it out and test each stick individually, and see if the game still crashes. if it does, then it has to be in the custom map scripting somewhere.

(SCDS_reyalP) #6

I would guess that it is a problem caused by having too many .pk3s in your et main folder. Try moving or deleting some of them. This is an old bug from RTCW which apperently wasn’t fixed in ET, and is made worse by the fact that every custom campaign comes with it’s own .pk3.

Be sure to keep
mp_bin.pk3
mp_pak0.pk3
mp_pak1.pk3

(Dawg) #7

Given the error message, I do not have any reason to suspect that my memory cards are the root problem. It is related to software. I imagine that one of the custom pk3 files is the problem so I will go through and remove some and see if it clears things up.

I wish I could say, “I just added BLAH map.” but no such luck. I’ve added a few since patching and haven’t tried to Host Game until now. If I can isolate a particular map as problematic I will post it.

Dawg

(=TAC=Chron) #8

To an extent, yes, but the error states that “memory could not be read”.

So, imo, troubleshooting the RAM first will guarentee that the error has to be software related.

(Lekdevil.NL) #9

Run Memtest-86 first and let it complete at least one full cycle. If your memory passes, it’s time to look for other causes… but not before that, I’d say.

(Rippin Kitten) #10

Maybe it just be, but I would think moving all custom pk3s out of the et directory and seeing if that resolves the issue to be a much easier and therefore far more practical first course of action. Be kinda pointless to crack open the case, single test each stick of RAM, only to find that a simple miscoded pk3 was the problem. =)

RK

(twiFight) #11

I would try this:

remove all custom maps/server configs out of your etmain.
does this solve the problem?
yes: try putting back the custom files one by one will you find out which file gave you the problem. then post that files name on this board.
no: test your ram. I suggest using windows memory checker, even though all other people here will recommend you use memtest86. the problem is, memtest said my ram was fine, windows memory checker returned 48 errors. And yes, win mem tester was right. If win mem tester says your ram is ok and you still have problems then try some other software.

if all fails, then ask us again.

(Dawg) #12

To an extent, yes, but the error states that “memory could not be read”.

So, imo, troubleshooting the RAM first will guarentee that the error has to be software related.[/quote]
If you read the error message closely it specifically says that the memory address that the attempted read is on is 0x00000000. This is the null addresss and cannot be dereferenced. It is intended for special purposes. Some software code is attempting to dereference the null address, which it cannot do. Ergo, the resulting error. It does not indicate bad memory.

I removed all the suspect pk3 files and the problem resolved. I wish I could say which pk3 was the problem but I just don’t think its that big a deal. It could be some server script pk3 or could be some unfinished map pk3. Probably the former…

You know… all I was trying to do was sound out if there was a known bug in 1.02. If not, I was planning on doing the pk3 shuffle with the expectation that it was a buggy file. But, thanks to all anyway!

Dawg

p.s. If you hear hoofbeats - think horses, not zebras. Unless you’re in Africa…

(IPvD) #13

reyalP rescues another noob (me)! Cheers :beer:

buy vaporgenie