Windows crashing - random BSOD on Windows 7 64-bit

Question

Hello
I tried reading this forum and tried IMO everything but computer still gets BSOD. I'm including Dump File. I don't know how to read it. Any advice?
http://sdrv.ms/1gwJEKq
What I did:
memtest86 - passed
ccleaner
regcleaner
antivirus scan
reinstalled drivers
chkdsk
I have mirrored drives on windows. It shows 'resynching'. Could it be failing and causing the problem?

Answer 1

Mindau
This one crash was Related to the
nvvad64v.sys NVIDIA Virtual Audio Driver from NVIDIA Corporation  I would install the newest driver available.
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\013114-22495-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`03467000 PsLoadedModuleList = 0xfffff800`036a3e70
Debug session time: Fri Jan 31 05:39:43.583 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:28.095
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck D1, {10, 2, 0, fffff880044f8689}
*** WARNING: Unable to verify timestamp for nvvad64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
Probably caused by : nvvad64v.sys ( nvvad64v+1689 )
Followup: MachineOwner
8: 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: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880044f8689, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370e0e0
GetUlongFromAddress: unable to read from fffff8000370e198
0000000000000010 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nvvad64v+1689
fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: audiodg.exe
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME: fffff8800eb894c0 -- (.trap 0xfffff8800eb894c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80179a6fd0
rdx=0000000000003fdc rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044f8689 rsp=fffff8800eb89650 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa80179a6fd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvvad64v+0x1689:
fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h] ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034d5de9 to fffff800034d6880
STACK_TEXT:
fffff880`0eb89378 fffff800`034d5de9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0eb89380 fffff800`034d4a60 : 00000000`00000000 00000000`0000100c fffffa80`1611a260 fffff880`035e61c0 : nt!KiBugCheckDispatch+0x69
fffff880`0eb894c0 fffff880`044f8689 : 00000000`0031c8d3 fffffa80`179a4000 00000000`00000000 fffff800`03665888 : nt!KiPageFault+0x260
fffff880`0eb89650 00000000`0031c8d3 : fffffa80`179a4000 00000000`00000000 fffff800`03665888 00000000`00000028 : nvvad64v+0x1689
fffff880`0eb89658 fffffa80`179a4000 : 00000000`00000000 fffff800`03665888 00000000`00000028 00000000`00524fbc : 0x31c8d3
fffff880`0eb89660 00000000`00000000 : fffff800`03665888 00000000`00000028 00000000`00524fbc 00000000`00002fbc : 0xfffffa80`179a4000
STACK_COMMAND: kb
FOLLOWUP_IP:
nvvad64v+1689
fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvvad64v+1689
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvvad64v
IMAGE_NAME: nvvad64v.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 529fb649
FAILURE_BUCKET_ID: X64_0xD1_nvvad64v+1689
BUCKET_ID: X64_0xD1_nvvad64v+1689
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xd1_nvvad64v+1689
FAILURE_ID_HASH: {58ea0214-7b27-7dc6-5a00-c215a7e166cc}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag