UT2004 Build UT2004_Build_[2005-11-23_16.22]

OS: Windows NT 6.1 (Build: 7601)
CPU: AuthenticAMD Unknown processor @ 2900 MHz with 3838MB RAM
Video: ATI Radeon HD 4200 (1094)

General protection fault!

History: UObject::ProcessEvent <- (CYLOMk2PrimaryFire CTF-Face3.CYLOAssaultWeapon.CYLOMk2PrimaryFire8, Function BCoreV25.BallisticFire.ModeDoFire) <- UWeaponFire::ModeTick <- AActor::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=0) <- TickLevel <- UGameEngine::Tick <- Level Facing Worlds 3 <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 10910191 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

is this user error, OS error, or a bug in the mod? (reason i ask is i keep getting erors that look extremley similar no matter what mod map or models i use)

When do the errors happen, and what did you do right before it crashed?

Check here and see if the first one applies to your case.

none of those apply, it usually happens after 2 or 3 maps usually in the middle of a heavy fire fight

Hmm... Might be a system error. Do you have full graphics quality for things? Might want to try going through BW preferences and turning down effects quality and toning down blood effects. See if it still happens, or at least if it happens as often.

everything set to normal, (all but trilinear and shadows(these are off)) didn't even get through one map, at least it isn't the Ra ot of Virtual mamory(got that set to a 16gig)

Well I would recommend disabling options under the BW mutator menu (in Preferences and Bloody Hell tabs) and seeing if the crashes still happen as often. At least we can narrow down the problem list this way.

all the bells and whistles turned of, and still CRASH!, i hate Vista and win7, i had UT2K4 runnin sweet on a 9 year old PC runnin XP, but on this Win7 pc it crashes with regularity almost always that dang General protection fault

Ok, now have you ever had this crash with BW turned off? I recommend trying that. Also try running BW with less weapons available for Loadout/Swap/whatever you use. Its possible you are running out of memory as more and more of the guns get loaded.

okay reducing the loadout list seems to be fixing the problem, on a side note, BW makes UT2K4 a whole new game, when i played it w/out BW i got CREAMED on inhuman, using BW Loadout, i am on even footing with the bots

Hah, yeah. I can't play vanilla UT2004 any more.

But glad to know you got it working. I think that would be due to a lack of RAM, but I'm not 100% certain. Not a fun fix, but if reducing weapon count makes it work that's a good workaround.

i can't figure out why my 4gig ram dual core 2011 rig can't handle what my single core 512meg ram machine could though, other the my new rig is win7 and my old one(which i had to trash after the power pack blew and fried everything) was winXP

Well I'm not really sure. It might not actually be a ram thing, but I think it has something to do with the hardware rather than BW specifically. Or maybe it's UT2004. I dunno.

okay the error came back, took longer this time, i am thinking some stray leftovers from some other mod may be the clprit, so i am gonna just do a fresh install with only BW and Sergeant Kelly's pack and see if that helps any

P.S. do y'all got any live chat thingy-ma-bobs at all?

This is most certainly not a RAM issue unless one of your RAM modules or the OS memory management are acting funny, in which case there would be a system-wide instability regardless of what you are running and under what circumstances. The operating system takes care of moving data to/from memory from/to virtual pages, handling page faults and so on so neither you nor UT2004 need to worry about any form of on-the-fly memory management. In fact if you as a programmer worry about memory management you may just end up breaking the OS's flow of work and cause your software to crash unexpectedly at any random moment of use.

If you read the error you notice that the crash occurs in one of Sarge's classes, specifically the CYLO Mk2. Personally I would start by removing the CYLO Mk2 gun from the matches and go from there. It is also a good idea to remove all mutators except BW to minimize the possibility of interferences.

A fresh reinstall is a great idea though. Let us know if that fixes the problem.

okay managed to play for an hour with no crashes, so it was either the prototypes package or a stray mod, going to slowly add back a few select mods and pray they dont cause problems(starting with the biggie HaloUT)

This might be related to the bug where radius-damaging bullet weapons can cause game instability. I'll likely be replacing the code in V10 to fix the issue.

If you want to verify this, try making an Arena match with only the CYLO Firestorm.

this error wasnt just with the firestorm, it was happening with a variety of weapons, i just posted that particular example, it would appear also with the X83 on occasion, and a few others, and i just realized it only happened after i added in the prototypes package(a good nights sleep and you realize alot of things sometimes )

Hmm, it may happen with the Bulldog, GRSXX, X83, HMC, AH104, and CYLO IV Firestorm then. All of those use radius damage.

The railgun has radius damage and doesn't appear to have crashed anybody yet, so I'm going to switch the weapons over to its code.

i wouldn't know about the grsxx, i dont use it or the E-Vand the H-V, when the bots get ahold of those i get creamed even on the easiest difficulty level but the rest of those i remeber seeing errors with, but only if the prototypes package is also loaded