Cannot find the root of BSODs - 0xC4, 0x93, 0x19 - prompted by gaming

[Chowley]

This is really odd.
I have been having BSODs a lot over the last week. My PC will usually run fine for hours at a time. Then I load up Planetside 2, sometimes i go 20 minutes, sometimes 90. But, I will always crashed and get a BSOD. After that while doing less intensive tasks in windows I will get more BSODs and eventually they will stop again.
Any time i got BSODs before I sorted it out farily quickly it was AOD and Daemon Tools in the past.

I have run memtest86 on both sticks 6 - 12 passes over numerous attempts. I have checked my OS ssd numerous times with different tools (Smartmontools and Seatools).
I have run SFC /scannow multiple times along with chkdsk.
I have reseated cards.

Going through my logs driver verifier pointed at asacpi.sys as causing a crash, so i changed that to asacpi.old in the drivers folder.

I attempted to update my older drivers but having issues finding the correct versions. I updated either my Marvell or Realtek drivers (cannot remember which it was at this stage) and that caused constant BSODs no matter what I was doing so rolled back on that, went back to the usual frequency again.

When I ran driver verifier last night, I got stop codes that I have not seen regularly before, but the crash was not prompted by one of the monitored drivers, unlike in the past. So I am starting to think it may be an OS issue. But I am very reluctant to wipe my C drive, exams next week and dont want to have to set up VirtualBox and VMware software again.
I also have run numerous virus scans, and also scans with MBAM

Dumps and all of that are attached.

 

[Chowley]

I just got another BSOD (D1) while playing Planetside 2 that blames a Xonar driver (according to carrona), which is the first time i have seen that.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {408, 2, 0, fffff88004c31320}

Unable to load image cmudaxp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
Probably caused by : cmudaxp.sys ( cmudaxp+1cd320 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000408, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004c31320, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003712100
 0000000000000408 

CURRENT_IRQL:  2

FAULTING_IP: 
cmudaxp+1cd320
fffff880`04c31320 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c210 -- (.trap 0xfffff80000b9c210)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000400
rdx=0000000000000009 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004c31320 rsp=fffff80000b9c3a0 rbp=0000000000000080
 r8=0000000000000080  r9=0000000000000000 r10=fffff88004c3e6f0
r11=0000000000000042 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cmudaxp+0x1cd320:
fffff880`04c31320 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034da169 to fffff800034dabc0

STACK_TEXT:  
fffff800`00b9c0c8 fffff800`034da169 : 00000000`0000000a 00000000`00000408 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c0d0 fffff800`034d8de0 : fffff800`00b9c2b0 fffffa80`070090b0 fffffa80`06d4ae20 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c210 fffff880`04c31320 : fffffa80`0938f29c 002f0024`00000080 0016001a`00000000 0031002d`001b000f : nt!KiPageFault+0x260
fffff800`00b9c3a0 fffffa80`0938f29c : 002f0024`00000080 0016001a`00000000 0031002d`001b000f 00000000`00000016 : cmudaxp+0x1cd320
fffff800`00b9c3a8 002f0024`00000080 : 0016001a`00000000 0031002d`001b000f 00000000`00000016 fffff880`04c2addf : 0xfffffa80`0938f29c
fffff800`00b9c3b0 0016001a`00000000 : 0031002d`001b000f 00000000`00000016 fffff880`04c2addf 00000000`00000003 : 0x2f0024`00000080
fffff800`00b9c3b8 0031002d`001b000f : 00000000`00000016 fffff880`04c2addf 00000000`00000003 00000000`00000080 : 0x16001a`00000000
fffff800`00b9c3c0 00000000`00000016 : fffff880`04c2addf 00000000`00000003 00000000`00000080 fffffa80`088021b0 : 0x31002d`001b000f
fffff800`00b9c3c8 fffff880`04c2addf : 00000000`00000003 00000000`00000080 fffffa80`088021b0 fffff800`00b9c3fc : 0x16
fffff800`00b9c3d0 00000000`00000003 : 00000000`00000080 fffffa80`088021b0 fffff800`00b9c3fc 00000020`00000010 : cmudaxp+0x1c6ddf
fffff800`00b9c3d8 00000000`00000080 : fffffa80`088021b0 fffff800`00b9c3fc 00000020`00000010 00000080`00000040 : 0x3
fffff800`00b9c3e0 fffffa80`088021b0 : fffff800`00b9c3fc 00000020`00000010 00000080`00000040 00000200`00000100 : 0x80
fffff800`00b9c3e8 fffff800`00b9c3fc : 00000020`00000010 00000080`00000040 00000200`00000100 0031002d`001b000f : 0xfffffa80`088021b0
fffff800`00b9c3f0 00000020`00000010 : 00000080`00000040 00000200`00000100 0031002d`001b000f fffff800`03663cc0 : 0xfffff800`00b9c3fc
fffff800`00b9c3f8 00000080`00000040 : 00000200`00000100 0031002d`001b000f fffff800`03663cc0 fffff800`00b9cc58 : 0x20`00000010
fffff800`00b9c400 00000200`00000100 : 0031002d`001b000f fffff800`03663cc0 fffff800`00b9cc58 00000000`00000016 : 0x80`00000040
fffff800`00b9c408 0031002d`001b000f : fffff800`03663cc0 fffff800`00b9cc58 00000000`00000016 fffff880`04c2b09f : 0x200`00000100
fffff800`00b9c410 fffff800`03663cc0 : fffff800`00b9cc58 00000000`00000016 fffff880`04c2b09f fffffa80`099ce660 : 0x31002d`001b000f
fffff800`00b9c418 fffff800`00b9cc58 : 00000000`00000016 fffff880`04c2b09f fffffa80`099ce660 00000000`00000000 : nt!KiInitialThread
fffff800`00b9c420 00000000`00000016 : fffff880`04c2b09f fffffa80`099ce660 00000000`00000000 00000000`00000040 : 0xfffff800`00b9cc58
fffff800`00b9c428 fffff880`04c2b09f : fffffa80`099ce660 00000000`00000000 00000000`00000040 00000000`00000001 : 0x16
fffff800`00b9c430 fffffa80`099ce660 : 00000000`00000000 00000000`00000040 00000000`00000001 fffffa80`07ad55b0 : cmudaxp+0x1c709f
fffff800`00b9c438 00000000`00000000 : 00000000`00000040 00000000`00000001 fffffa80`07ad55b0 fffff880`04c1831f : 0xfffffa80`099ce660


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cmudaxp+1cd320
fffff880`04c31320 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cmudaxp+1cd320

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cmudaxp

IMAGE_NAME:  cmudaxp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d78814f

FAILURE_BUCKET_ID:  X64_0xD1_cmudaxp+1cd320

BUCKET_ID:  X64_0xD1_cmudaxp+1cd320

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