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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8053ac11, The address that the exception occurred at
Arg3: b01dbbb4, Exception Record Address
Arg4: b01db8b0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!memset+41
8053ac11 f3ab            rep stos dword ptr es:[edi]

EXCEPTION_RECORD:  b01dbbb4 -- (.exr 0xffffffffb01dbbb4)
ExceptionAddress: 8053ac11 (nt!memset+0x00000041)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 02350000
Attempt to write to address 02350000

CONTEXT:  b01db8b0 -- (.cxr 0xffffffffb01db8b0)
eax=00000000 ebx=00000080 ecx=00000020 edx=00000000 esi=e3f2f768 edi=02350000
eip=8053ac11 esp=b01dbc7c ebp=b01dbd18 iopl=0         nv up ei pl nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010212
nt!memset+0x41:
8053ac11 f3ab            rep stos dword ptr es:[edi]
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  QCDPlayer.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  02350000

WRITE_ADDRESS:  02350000

FOLLOWUP_IP:
BazisVirtualCDBus+ffb5
b2e93fb5 ??              ???

BUGCHECK_STR:  0x7E

EXCEPTION_DOESNOT_MATCH_CODE:  This indicates a hardware error.
Instruction at 8053ac11 does not read/write to 02350000

LAST_CONTROL_TRANSFER:  from 806e6d43 to 8053ac11

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb01dbc84

STACK_COMMAND:  dds B01DBC84-0x20 ; kb

STACK_TEXT:
b01dbc64  00000080
b01dbc68  b01dbd18
b01dbc6c  00000002
b01dbc70  8053ac11 nt!memset+0x41
b01dbc74  00000008
b01dbc78  00010212
b01dbc7c  02350000
b01dbc80  b2e93fb5 BazisVirtualCDBus+0xffb5
b01dbc84  02350000
b01dbc88  00000000
b01dbc8c  00000080
b01dbc90  02350000
b01dbc94  89af1038
b01dbc98  89af1068
b01dbc9c  894e61a0
b01dbca0  8a3ab4f8
b01dbca4  00000000
b01dbca8  b01dbcc0
b01dbcac  804fc96c nt!KeReleaseMutex+0x14
b01dbcb0  00000000
b01dbcb4  00000001
b01dbcb8  00000000
b01dbcbc  00000000
b01dbcc0  806e6d43 hal!HalpDispatchInterrupt+0xbb
b01dbcc4  b01dbd68
b01dbcc8  806e6427 hal!KfLowerIrql+0x17
b01dbccc  badb0d00
b01dbcd0  00000000
b01dbcd4  8a3ab4f8
b01dbcd8  894e61e8
b01dbcdc  00000000
b01dbce0  00000000


SYMBOL_NAME:  BazisVirtualCDBus+ffb5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BazisVirtualCDBus

IMAGE_NAME:  BazisVirtualCDBus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc98469

FAILURE_BUCKET_ID:  0x7E_CODE_ADDRESS_MISMATCH_BazisVirtualCDBus+ffb5

BUCKET_ID:  0x7E_CODE_ADDRESS_MISMATCH_BazisVirtualCDBus+ffb5

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