New
#11
Good thing you enabled Driver Verifier, because it is now pointing to your Realtek Audio Drivers. See if you can find an update:It is recommended to download drivers from the computer manufacturer's website. However, if you can't find them, you can download some generic drivers directly from Realtek: RealtekCode:Timestamp: Wed Oct 21 10:27:48 2009 (4ADF1A64)
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Memdump3.zip\072710-21340-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50 Debug session time: Tue Jul 27 05:43:15.839 2010 (GMT-4) System Uptime: 0 days 0:00:23.524 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D5, {fffff9800bbc8d60, 0, fffff880064ba1ee, 0} Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for RTKVHD64.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys Could not read faulting driver name Probably caused by : RTKVHD64.sys ( RTKVHD64+b61ee ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5) Memory was referenced after it was freed. This cannot be protected by try-except. When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff9800bbc8d60, memory referenced Arg2: 0000000000000000, value 0 = read operation, 1 = write operation Arg3: fffff880064ba1ee, if non-zero, the address which referenced memory. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b50e0 fffff9800bbc8d60 FAULTING_IP: RTKVHD64+b61ee fffff880`064ba1ee 8b4630 mov eax,dword ptr [rsi+30h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD5 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88003721290 -- (.trap 0xfffff88003721290) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff880037214b8 rdx=fffff88003721420 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880064ba1ee rsp=fffff88003721420 rbp=0000000000000002 r8=0000000000000000 r9=fffff880064ba1ee r10=0000000000000000 r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc RTKVHD64+0xb61ee: fffff880`064ba1ee 8b4630 mov eax,dword ptr [rsi+30h] ds:8180:00000000`00000030=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002efde54 to fffff80002e7d600 STACK_TEXT: fffff880`03721128 fffff800`02efde54 : 00000000`00000050 fffff980`0bbc8d60 00000000`00000000 fffff880`03721290 : nt!KeBugCheckEx fffff880`03721130 fffff800`02e7b6ee : 00000000`00000000 fffff8a0`0172c110 fffffa80`06438500 fffff800`02eb020f : nt! ?? ::FNODOBFM::`string'+0x42877 fffff880`03721290 fffff880`064ba1ee : fffff880`037214b8 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 : nt!KiPageFault+0x16e fffff880`03721420 fffff880`037214b8 : 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 : RTKVHD64+0xb61ee fffff880`03721428 00000000`00000000 : fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 fffff800`00000000 : 0xfffff880`037214b8 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHD64+b61ee fffff880`064ba1ee 8b4630 mov eax,dword ptr [rsi+30h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: RTKVHD64+b61ee FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHD64 IMAGE_NAME: RTKVHD64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4adf1a64 FAILURE_BUCKET_ID: X64_0xD5_VRF_RTKVHD64+b61ee BUCKET_ID: X64_0xD5_VRF_RTKVHD64+b61ee Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5) Memory was referenced after it was freed. This cannot be protected by try-except. When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff9800bbc8d60, memory referenced Arg2: 0000000000000000, value 0 = read operation, 1 = write operation Arg3: fffff880064ba1ee, if non-zero, the address which referenced memory. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: fffff9800bbc8d60 FAULTING_IP: RTKVHD64+b61ee fffff880`064ba1ee 8b4630 mov eax,dword ptr [rsi+30h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD5 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88003721290 -- (.trap 0xfffff88003721290) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff880037214b8 rdx=fffff88003721420 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880064ba1ee rsp=fffff88003721420 rbp=0000000000000002 r8=0000000000000000 r9=fffff880064ba1ee r10=0000000000000000 r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc RTKVHD64+0xb61ee: fffff880`064ba1ee 8b4630 mov eax,dword ptr [rsi+30h] ds:8180:00000000`00000030=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002efde54 to fffff80002e7d600 STACK_TEXT: fffff880`03721128 fffff800`02efde54 : 00000000`00000050 fffff980`0bbc8d60 00000000`00000000 fffff880`03721290 : nt!KeBugCheckEx fffff880`03721130 fffff800`02e7b6ee : 00000000`00000000 fffff8a0`0172c110 fffffa80`06438500 fffff800`02eb020f : nt! ?? ::FNODOBFM::`string'+0x42877 fffff880`03721290 fffff880`064ba1ee : fffff880`037214b8 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 : nt!KiPageFault+0x16e fffff880`03721420 fffff880`037214b8 : 00000000`00000000 fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 : RTKVHD64+0xb61ee fffff880`03721428 00000000`00000000 : fffff8a0`0172c110 fffffa80`06ab1f40 00000000`00000000 fffff800`00000000 : 0xfffff880`037214b8 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHD64+b61ee fffff880`064ba1ee 8b4630 mov eax,dword ptr [rsi+30h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: RTKVHD64+b61ee FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHD64 IMAGE_NAME: RTKVHD64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4adf1a64 FAILURE_BUCKET_ID: X64_0xD5_VRF_RTKVHD64+b61ee BUCKET_ID: X64_0xD5_VRF_RTKVHD64+b61ee Followup: MachineOwner --------- 1: kd> lmvm RTKVHD64 start end module name fffff880`06404000 fffff880`065ee080 RTKVHD64 T (no symbols) Loaded symbol image file: RTKVHD64.sys Image path: \SystemRoot\system32\drivers\RTKVHD64.sys Image name: RTKVHD64.sys Timestamp: Wed Oct 21 10:27:48 2009 (4ADF1A64) CheckSum: 001FA0EE ImageSize: 001EA080 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4