New
#11
The crash was blamed on audiodg.exe the Windows interface where 3rd party audio extensions hook in (DSPs etc.)
Which means something Audio-related was responsible for the crash. Did you happen to install anything audio-related before the crash (after the soundtap update)? Ask yourself What was I doing (or better what audio related programs were running) and look for culprits there.
Update all your Audio drivers ( conexant drivers (like cAudioFilterAgent/caudiofilteragent64.exe and SmartAudio/saiicpl.exe) via Toshiba) etc.
and monitor what audio related programs crash your rig.
Report back if anything new comes up.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\David\Desktop\TheZman\053011-33867-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16792.amd64fre.win7_gdr.110408-1633 Machine Name: Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50 Debug session time: Mon May 30 02:43:51.781 2011 (GMT-4) System Uptime: 2 days 9:30:50.482 Loading Kernel Symbols ............................................................... ................................................................ .............................................. Loading User Symbols Loading unloaded module list ................................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 76, {0, fffffa8004521060, 2, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+17d46 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PROCESS_HAS_LOCKED_PAGES (76) Caused by a driver not cleaning up correctly after an I/O. Arguments: Arg1: 0000000000000000, Locked memory pages found in process being terminated. Arg2: fffffa8004521060, Process address. Arg3: 0000000000000002, Humber of locked pages. Arg4: 0000000000000000, Pointer to driver stacks (if enabled) or 0 if not. Issue a !search over all of physical memory for the current process pointer. This will yield at least one MDL which points to it. Then do another !search for each MDL found, this will yield the IRP(s) that point to it, revealing which driver is leaking the pages. Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackLockedPages to a DWORD 1 value and reboot. Then the system will save stack traces so the guilty driver can be easily identified. When you enable this flag, if the driver commits the error again you will see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) - which can identify the offending driver(s). Debugging Details: ------------------ PROCESS_NAME: audiodg.exe DEFAULT_BUCKET_ID: DRIVER_FAULT_0x76 CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x76 CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002f28bf5 to fffff80002c87700 STACK_TEXT: fffff880`0a23ea38 fffff800`02f28bf5 : 00000000`00000076 00000000`00000000 fffffa80`04521060 00000000`00000002 : nt!KeBugCheckEx fffff880`0a23ea40 fffff800`02f44c8b : fffffa80`04521060 00000000`00000008 fffffa80`00000000 fffffa80`00000000 : nt! ?? ::NNGAKEGL::`string'+0x17d46 fffff880`0a23ea80 fffff800`02c8c8b4 : 00000000`00000000 fffffa80`04521060 fffffa80`04521030 fffff800`030154d5 : nt!PspProcessDelete+0x177 fffff880`0a23eae0 fffff800`02d8d3b9 : fffffa80`04521060 fffffa80`044ed000 fffffa80`044ede98 fffffa80`044ede90 : nt!ObfDereferenceObject+0xd4 fffff880`0a23eb40 fffff800`030d8cee : fffffa80`00000005 fffffa80`03814000 fffffa80`04521060 fffffa80`044ede98 : nt!MmFreeAccessPfnBuffer+0x29 fffff880`0a23eb70 fffff800`030fa310 : fffffa80`069e9701 00000000`00000080 fffffa80`033c99e0 fffff800`02e15568 : nt!PfpFlushBuffers+0x23e fffff880`0a23ec10 fffff800`02f2abc6 : ffffffff`ff676980 fffffa80`069e9780 00000000`00000080 fffffa80`033c99e0 : nt!PfTLoggingWorker+0xe0 fffff880`0a23ed40 fffff800`02c65bc6 : fffff880`009e8180 fffffa80`069e9780 fffffa80`067e6b60 fffff880`01233534 : nt!PspSystemThreadStartup+0x5a fffff880`0a23ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::NNGAKEGL::`string'+17d46 fffff800`02f28bf5 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+17d46 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34 FAILURE_BUCKET_ID: X64_0x76_audiodg.exe_nt!_??_::NNGAKEGL::_string_+17d46 BUCKET_ID: X64_0x76_audiodg.exe_nt!_??_::NNGAKEGL::_string_+17d46 Followup: MachineOwner