BSOD in clean installed Windows 7 64 - HELP needed!

[StevenS]

Hi, my problem symptoms is..
98% loading memory - 4gb total. I try to find out who are eating all memories.. but didnt see anythink in task manager. I supposed it could be caused by antivirus? after I turn off antivirus bitdefender it didn't change anything. the loading of memory still where up to 98%. than about 20 second i catch BSOD!

here is my dump file. If sombody can find out what the problem is?
google didnt find out my error - ntoskrnl.exe (nt+78aec)

will be very appreciated for helping me!

 

[koolkat77]

Looks like the bsod was caused by C-Media Audio Interface Driver (WDM) by C-Media (2009) driver.
Update to the latest and see if tht stops the bsods.

• Driver Reference Table

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {d50, 2, 1, fffff80002a79aec}

*** 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+1076 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000d50, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a79aec, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca80e0
GetUlongFromAddress: unable to read from fffff80002ca8198
 0000000000000d50 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+13c
fffff800`02a79aec f00fba2e07      lock bts dword ptr [rsi],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  audiodg.exe

TRAP_FRAME:  fffff8800579a170 -- (.trap 0xfffff8800579a170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000001ce36d rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a79aec rsp=fffff8800579a300 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff80002beae80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x13c:
fffff800`02a79aec f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a6fde9 to fffff80002a70880

STACK_TEXT:  
fffff880`0579a028 fffff800`02a6fde9 : 00000000`0000000a 00000000`00000d50 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0579a030 fffff800`02a6ea60 : 00000000`00002280 00000000`00000000 00000000`00000004 fffff8a0`025bd6a0 : nt!KiBugCheckDispatch+0x69
fffff880`0579a170 fffff800`02a79aec : 00000000`00000001 fffff880`077d6007 fffffa80`056a3e20 fffffa80`05526390 : nt!KiPageFault+0x260
fffff880`0579a300 fffff880`0761e076 : fffffa80`08248800 fffffa80`00000000 fffff8a0`c0000000 00000100`00000000 : nt!KeWaitForSingleObject+0x13c
fffff880`0579a3a0 fffffa80`08248800 : fffffa80`00000000 fffff8a0`c0000000 00000100`00000000 00000000`00000000 : cmudaxp+0x1076
fffff880`0579a3a8 fffffa80`00000000 : fffff8a0`c0000000 00000100`00000000 00000000`00000000 0000ac44`0002fffe : 0xfffffa80`08248800
fffff880`0579a3b0 fffff8a0`c0000000 : 00000100`00000000 00000000`00000000 0000ac44`0002fffe fffffa80`0de5d060 : 0xfffffa80`00000000
fffff880`0579a3b8 00000100`00000000 : 00000000`00000000 0000ac44`0002fffe fffffa80`0de5d060 fffff880`07621729 : 0xfffff8a0`c0000000
fffff880`0579a3c0 00000000`00000000 : 0000ac44`0002fffe fffffa80`0de5d060 fffff880`07621729 00000000`00000000 : 0x00000100`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cmudaxp+1076
fffff880`0761e076 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  cmudaxp+1076

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cmudaxp

IMAGE_NAME:  cmudaxp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adc2d1d

FAILURE_BUCKET_ID:  X64_0xA_cmudaxp+1076

BUCKET_ID:  X64_0xA_cmudaxp+1076

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

0: kd> lmvm cmudaxp
start             end                 module name
fffff880`0761d000 fffff880`077df000   cmudaxp  T (no symbols)           
    Loaded symbol image file: cmudaxp.sys
    Image path: \SystemRoot\system32\drivers\cmudaxp.sys
    Image name: cmudaxp.sys
    Timestamp:        Mon Oct 19 15:10:53 2009 (4ADC2D1D)
    CheckSum:         0013510E
    ImageSize:        001C2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[StevenS]

i have switched off in bios. now I got Xonar dx audio card. how c-media could be cause? ok i will check again! thanx for respond.

I look again and found Nvidia HDMI sound interface.. maybe this is the problem? I will say if i got again bsod.