Windows XP BSOD when playing Left 4 Dead 2

Status
Not open for further replies.

Swampwater

TS Rookie
I've recently been getting BSOD during gameplay whenever the next map tries to load. The game will play and then crash at random seemingly. I used WIndbg to get this information but don't know what it means:
I have also included some minidump files. Any more info would be great, I don't know what to do at this point.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: b6ce43b8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: b6ce43b8, address which referenced memory

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


READ_ADDRESS: b6ce43b8

CURRENT_IRQL: 2

FAULTING_IP:
viahduaa+a13b8
b6ce43b8 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: b54bebfc -- (.trap 0xffffffffb54bebfc)
ErrCode = 87219ad0
eax=87219ad0 ebx=8958b000 ecx=89857020 edx=804ef163 esi=87219ad0 edi=8958b000
eip=87219ad0 esp=b54bec70 ebp=b6b7a4d2 iopl=0 nv up di pl nz na po nc
cs=b000 ss=0010 ds=7790 es=b000 fs=0002 gs=0000 efl=00000000
b000:87219ad0 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from b6c5b3ba to b6ce43b8

FAILED_INSTRUCTION_ADDRESS:
viahduaa+a13b8
b6ce43b8 ?? ???

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b54be31c b6c5b3ba b54be3d4 b54be434 894378a4 viahduaa+0xa13b8
b54be3f4 b6c5d0be b0fa5c00 0000003f 00001e00 viahduaa+0x183ba
b54be9c4 b6c26676 897be408 b0fa5c00 b1dcf000 viahduaa+0x1a0be
b54be9ec b6c26945 b54bea01 0003c000 b54bea1c portcls!CPortPinWaveCyclic::Copy+0x56
b54bea2c b6c2611b 0000ec00 89b91548 890c7798 portcls!CPortPinWaveCyclic::RequestService+0x298
b54bea44 b6c3551f 855ad404 87219ad0 00000000 portcls!CPortPinWaveCyclic::IrpSubmitted+0x32
b54bea7c b6c3c61a 00000000 87219ad0 00000000 portcls!CIrpStream::TransferKsIrp+0x315
b54beab0 b6c2f74d 00000000 897f6030 87219ad0 portcls!CPortPinWaveCyclic::DeviceIoControl+0xf1
b54beacc b9114f0f 897f6030 87219ad0 b54beaf4 portcls!DispatchDeviceIoControl+0x49
b54beadc b6c2f8c0 897f6030 87219ad0 87219bac ks!KsDispatchIrp+0x126
b54beaf4 b6c2f881 897f6030 87219ad0 b54beb34 portcls!KsoDispatchIrp+0x43
b54beb04 b6d0b649 897f6030 87219ad0 8974d000 portcls!PcDispatchIrp+0x5f
b54beb34 804ef163 897f6030 87219ad0 c0000120 viahduaa+0xc8649
b54beb90 8051f740 e47ca000 e4e55862 b54beccc nt!IopfCallDriver+0x31
b54bebe4 80543938 00000000 e47ca000 00000000 nt!MmAccessFault+0x934
b54bebe4 87219ad0 00000000 e47ca000 00000000 nt!KiTrap0E+0xd0
b54bec6c 8958b000 00000078 ffffe16d 00000040 0x87219ad0
b54becb0 b3ec1012 88d8e000 804fead1 00000000 0x8958b000
b54beccc b54bedf0 b54bed50 b3eb2559 00000000 kmixer!MmxFinalPeg32to16+0x22
b54bed34 804ef163 897f9020 87219ad0 8725eed8 0xb54bedf0
b54bed44 b3eb262c 8722b7f8 00000001 b54bed84 nt!IopfCallDriver+0x31
b54bed54 b3ea0f07 8725eed8 8722b8b0 00000000 kmixer!WriteBuffer+0xbc
b54bed84 b3ea12a7 0022b7f8 00000000 00000000 kmixer!MxWorker+0x227
b54bedac 805ce9c2 8722b7f8 00000000 00000000 kmixer!MxPrivateWorkerThread+0xb7
b54beddc 8054549e b3ea11f0 8722b7f8 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
viahduaa+a13b8
b6ce43b8 ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: viahduaa+a13b8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: viahduaa

IMAGE_NAME: viahduaa.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4889c273

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_viahduaa+a13b8

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_viahduaa+a13b8

Followup: MachineOwner
 

Attachments

Route44

TechSpot Ambassador
All five minidumps are the same 0xD1 errors and these are usually caused by faulty drivers.

All five dumps cite the same driver as the cause of your crashes: viahduaa.sys. This is a VIA High Definition Audio Driver and belongs to your onboard sound.

* Go to your motherboard's website, find your exact motherboard model and download the latest updated drivers.
 

Swampwater

TS Rookie
Thanks for your reply route44. It hasn't crashed yet but sometimes it will run for a while without crashing.

may i suggest buying a better sound card if the new drivers fail? :D
What's wrong with the sound card I have? Other than the fact that I'm not entirely sure I downloaded the right sound card driver update for my computer, (ASUS P5KPL-CM) why would it not work?
 
Status
Not open for further replies.