BSOD when playing Unreal Tornament 2004

BSOD when playing Unreal Tornament 2004

I'm not sure It will crash on other games. Havn't played any others since the new system has been built. I build this system about a week ago.
I was having serious problems with video cards crashing the system when I first built it. Then I disabled all the Powersaving features in the Bio's settings and that solved that problem. I would appreciate any help for the newbie to the forums.
I Put my system Information in my profile let me know if I need to post it.
Thanks you very much.... Ross

Fully Updated Drivers on

BIOs
Video Card
Sound Card

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88002CEEDA9
BCP3: FFFFF88009933A20
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\063011-18969-01.dmp
C:\Users\Ross\AppData\Local\Temp\WER-35037-0.sysdata.xml

System Manufacturer/Model Number Self Build DIY OS Windows 7 Pro 64bit OEM CPU Intel i3 Motherboard Intel DQ67SW Memory 4 Gig DDR3 Graphics Card(s) GeForce GT 430 Sound Card Sound Blaster Audigy2 zs Monitor(s) Displays SyncMaster 213t Screen Resolution N/A Hard Drives 500 gb 7200 rpm PSU Cooler Master GX 750W Case Cooler Master Cooling Fan Keyboard Microsoft Sidewinder x6 Mouse Logitec MX518 Internet Speed Cable Other Info IGesture touch pad
USB wirless network adapter
Nostromo Speedpad N52

I just installed this and UT3 on my nephews machine a few days ago. I forgot how fun those games were.
He played for a few hours and I played for a few hours and had no issues. The game doesn't support 16:9 screen resolutions though.
I can't help you with the dump file at the moment, but did you update the game with the latest patch, 3369?
Unreal Tournament

Yes i did update the game.. Yes it is fun. I play a modified invasion game thats lots of fun. Its Joe's Monster Madness wop. Oh here is a snapshot of my power monitor.



These readings are virtually the same on 2 different power supplies

Hello Vonross, welcome...

Your dumpfile blames your creative audio driver. Actually the hardware behind it. Chances that the Hw itself is messed up are slim... so first thing to try is the driver.. renew it and see what happens.

The driver: ctaud2k.sys
Should be (only!!) in \SystemRoot\system32\drivers\ctaud2k.sys
If it is somewhere else you've got malware and need an updated antivirus an anti malware check... Loads of tut's on that here.

Start by going to you MOBO supplier and update your drivers.
If you need help, post back... we'll show you how and where...

HTML Code:

FOLLOWUP_IP: 
ctaud2k+39da9
fffff880`02ceeda9 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ctaud2k+39da9

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88009933a20 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_ctaud2k.sys

BUCKET_ID:  X64_IP_MISALIGNED_ctaud2k.sys

2nd dumpfile is even more explicit:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88403e31b98, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880040416ec, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b4100
fffff88403e31b98

FAULTING_IP:
ctaud2k+3e6ec
fffff880`040416ec 8b16 mov edx,dword ptr [rsi]

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: UT2004.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88009756270 -- (.trap 0xfffff88009756270)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880040552e0 rbx=0000000000000000 rcx=fffffa8007b3d010
rdx=000000000000000e rsi=0000000000000000 rdi=0000000000000000
rip=fffff880040416ec rsp=fffff88009756400 rbp=fffff88009756440
r8=fffff88009756441 r9=000000000000003f r10=fffff880040552e0
r11=fffff88004051380 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ctaud2k+0x3e6ec:
fffff880`040416ec 8b16 mov edx,dword ptr [rsi] ds:65f0:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000322f3cf to fffff80003284d00

STACK_TEXT:
fffff880`09756108 fffff800`0322f3cf : 00000000`00000050 fffff884`03e31b98 00000000`00000000 fffff880`09756270 : nt!KeBugCheckEx
fffff880`09756110 fffff800`03282e2e : 00000000`00000000 fffff884`03e31b98 fffffa80`0770a100 fffffa80`03d86008 : nt! ?? ::FNODOBFM::`string'+0x44891
fffff880`09756270 fffff880`040416ec : 00000101`80000001 fffff880`09756460 00000000`0000000e fffff880`04042425 : nt!KiPageFault+0x16e
fffff880`09756400 00000101`80000001 : fffff880`09756460 00000000`0000000e fffff880`04042425 fffffa80`07b3d010 : ctaud2k+0x3e6ec
fffff880`09756408 fffff880`09756460 : 00000000`0000000e fffff880`04042425 fffffa80`07b3d010 fffff880`0403b1b0 : 0x101`80000001
fffff880`09756410 00000000`0000000e : fffff880`04042425 fffffa80`07b3d010 fffff880`0403b1b0 00000000`00000000 : 0xfffff880`09756460
fffff880`09756418 fffff880`04042425 : fffffa80`07b3d010 fffff880`0403b1b0 00000000`00000000 00000000`00800000 : 0xe
fffff880`09756420 fffffa80`07b3d010 : fffff880`0403b1b0 00000000`00000000 00000000`00800000 fffffa80`00000100 : ctaud2k+0x3f425
fffff880`09756428 fffff880`0403b1b0 : 00000000`00000000 00000000`00800000 fffffa80`00000100 fffffa80`03d86110 : 0xfffffa80`07b3d010
fffff880`09756430 00000000`00000000 : 00000000`00800000 fffffa80`00000100 fffffa80`03d86110 3ff00000`00000010 : ctaud2k+0x381b0


STACK_COMMAND: kb

FOLLOWUP_IP:
ctaud2k+3e6ec
fffff880`040416ec 8b16 mov edx,dword ptr [rsi]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ctaud2k+3e6ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ctaud2k

IMAGE_NAME: ctaud2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ba21a22

FAILURE_BUCKET_ID: X64_0x50_ctaud2k+3e6ec

BUCKET_ID: X64_0x50_ctaud2k+3e6ec

Followup: MachineOwner
---------

0: kd> lmvm ctaud2k
start end module name
fffff880`04003000 fffff880`040d4d80 ctaud2k T (no symbols)
Loaded symbol image file: ctaud2k.sys
Image path: \SystemRoot\system32\drivers\ctaud2k.sys
Image name: ctaud2k.sys
Timestamp: Thu Mar 18 13:18:42 2010 (4BA21A22)
CheckSum: 000D3E03
ImageSize: 000D1D80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

vonross2012 said:

TYVM Looks like its now semi stable..... I havn't crashed in a while... It's the only part it the pc thats older.... I love the "record what U hear" option this card gives me. I can't afford another creative card till later. Thank you. Ill post more if it happends again... I think what i did was change the sound settings on the pc and game and it doesn't seem to crash anymore. Lets cross our fingers. I wish I could have figured out excactly where the problem was.

Thanks, Ross

You did... it's the driver.. did n't you update it?