UT 3 crashes with XP or Vista 64bit

[FikusErectus]

Anyone running UT 3 in Vista or XP 64bit? I keep getting crashes after about 30 minutes of play.

A typical crash is something like.

"Faulting application UT3.exe faulting module kernel32.dll version 5.3.3790.4062, fault address 0x00022366".

I'm thinking of switching to Vista 32 bit.

 

[Raynor.Z]

I'm successfully running Vista x64 and UT3. Kernel32.dll is a system file and looks like crash isn't directly caused by UT3 itself.
Maybe your system is running too hot. Do other games run fine?

 

[Alhanalem]

There's little reason to switch back to 32 bit from 64, ever anymore.

like raynor said, this crash doesnt sound like its specifically being caused by UT3; and I'm running vista ultimate x64, and have no trouble (with crashes, anyway)

 

[Bersy]

UT3 in vista 64 ult works beautifully for me. First I've been able to actually play it stable, but that could be the q9550 and 8 gb ram...

 

[oldkawman]

I have been running UT3 in XP_64 since day 1, including the demo. No issues since the initial demo exe file problem.

My not so obsolete specs;
Opty 180 @ 2.6GHz (socket 939)
DFI Infinity NF4 SLI (nforce 6.85 driver)
2GB GSkill DDR400
2 X 7900GTX 650MHz with DDR3 512MB in SLI (AFR2)
BFG Ageia PhysX (1.1.1.14 driver)
Koolance EXOS2 LIQUID cooling System
Cooler Master Real Power Pro 750 watt
Lian Li aluminum "oldschool" PC7 plus case
XP64 pro SP2 (only until Linux port arrives)
21" Sony Trinitron G520, 100Hz refresh
1600x1200, 2-2 quality, 40-85 FPS (I set an 85 FPS cap)
1600x1200, 2-2 quality, 35-85 FPS PhysX maps(capped at 85)
UT3 ver. 1.3
http://www.oldkawman.com/liquid_cooling.html

 

[Poker]

lol support: "Well I'm running it fine, and my system is awesome. You're welcome."

Do you have the latest video drivers installed? Error-prone RAM or a faulty or overheated hard drive might be the next things to check after that.

 

[FikusErectus]

Everything runs fine excepts UT3. I'll test the ram next. I have a ATI 4850 video card. This is like trying to find a needle in a haystack.

 

[Hunter]

A quick google it seems like a RAM problem, note the memory address at the end of the line you posted:

"fault address 0x00022366"

 

[FikusErectus]

I'll test it tonight when I get how. My ram voltage might need adjustment.