Love to help but the dump file was not uploaded.
Ken
Sorry
. It is now.
Hi kampa and welcome to sevenforums
This dump was probably caused by a memory problem. The file listed as probable is ntkernl.exe but I think that is erroneous.
I would
download and run a memory test like memtestx86 preferably overnight.
run a system file check to verify the system files. to run type cmd in search>right click and run as admin>sfc /scannow
let us know the results
If you are overclocking STOP
If you have any more bsod's upload the dumps so we can narrow the focus
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\103109-17971-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Fri Oct 30 18:44:07.820 2009 (GMT-4)
System Uptime: 0 days 6:10:16.819
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8001b89d90, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001b89d90
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002b4926e to fffff80002ad6f00
STACK_TEXT:
fffff880`06e24828 fffff800`02b4926e : 00000000`0000001a 00000000`00041790 fffffa80`01b89d90 00000000`0000ffff : nt!KeBugCheckEx
fffff880`06e24830 fffff800`02b0a5d9 : 00000000`00000000 000007fe`ff485fff fffffa80`00000000 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`06e249f0 fffff800`02dece50 : fffffa80`057be680 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`06e24b10 fffff800`02ded25b : fffff880`00000000 000007fe`fe700000 fffffa80`00000001 fffffa80`06d815f0 : nt!MiUnmapViewOfSection+0x1b0
fffff880`06e24bd0 fffff800`02ad6153 : fffffa80`05cbd060 fffff880`06e24ca0 fffffa80`05ea5620 00000000`00000001 : nt!NtUnmapViewOfSection+0x5f
fffff880`06e24c20 00000000`778a015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0021f2f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778a015a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02b4926e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+339d6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
Followup: MachineOwner
---------
I have been pulling my hairs away for the past four days, getting random Memory_Management BSOD on my new rig.
