New
#1
Windows 7 dmp
Plz check my dmp.
+ i have one more dmp file named MEMORY.dmp but file is 147Mb and locked in Windows folder.
Plz check my dmp.
+ i have one more dmp file named MEMORY.dmp but file is 147Mb and locked in Windows folder.
Hi and welcome
This dmp was probably caused by nvlddmkm.sys, and of course should be apdated
I would also update this driver which is 6 years old
ASACPI.sys 0x8c937000 0x8c938420 0x00001420 0x411c2d04 8/12/2004 9:52:52 PM
Additonally
I would dl and run memtestx86 for several hours
run a system file check to verify and repair system files
type cmd in search>right click and run as admin>sfc /scannow
Ken J+
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\121809-20061-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82841000 PsLoadedModuleList = 0x82989810 Debug session time: Fri Dec 18 06:14:06.044 2009 (GMT-5) System Uptime: 0 days 0:00:13.074 Loading Kernel Symbols ............................................................... ........................................................ Loading User Symbols Loading unloaded module list .. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {1b85cc6, 2, 1, 8d093efd} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+7aefd ) Followup: MachineOwner --------- 1: 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: 01b85cc6, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 8d093efd, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829a9718 Unable to read MiSystemVaType memory at 82989160 01b85cc6 CURRENT_IRQL: 2 FAULTING_IP: nvlddmkm+7aefd 8d093efd a3c65cb801 mov dword ptr ds:[01B85CC6h],eax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: csrss.exe TRAP_FRAME: 8a9fc800 -- (.trap 0xffffffff8a9fc800) ErrCode = 00000002 eax=86327d6c ebx=00000000 ecx=8567222c edx=8567222c esi=856721d8 edi=00000008 eip=8d093efd esp=8a9fc874 ebp=8a9fc884 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 nvlddmkm+0x7aefd: 8d093efd a3c65cb801 mov dword ptr ds:[01B85CC6h],eax ds:0023:01b85cc6=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 8d093efd to 828877eb STACK_TEXT: 8a9fc800 8d093efd badb0d00 8567222c 00000008 nt!KiTrap0E+0x2cf WARNING: Stack unwind information not available. Following frames may be wrong. 8a9fc884 8d050ddd 86327c28 85672000 86327c28 nvlddmkm+0x7aefd 8a9fc89c 8d052935 8a9fc97c 862e7af0 862e7af0 nvlddmkm+0x37ddd 8a9fc8b0 8d0529ec 8a9fc97c 862e7af0 8a9fc97c nvlddmkm+0x39935 8a9fc8c8 8d052c9b 8a9fc97c 862e7af0 85672000 nvlddmkm+0x399ec 8a9fc8e8 8d518f82 c000009a 86211000 8280f6ee nvlddmkm+0x39c9b 8a9fc900 8d51c1af 8d518f4f 8a9fc97c 8a9fc93c nvlddmkm+0x4fff82 8a9fc910 8d95a8a9 862e7af0 8a9fc97c 86316788 nvlddmkm+0x5031af 8a9fc93c 8d9373e1 862e7af0 8a9fc97c 8a9fc960 dxgkrnl+0x2e8a9 8a9fc94c 8c81f086 86211000 862e7af0 8a9fc97c dxgkrnl+0xb3e1 8a9fc960 8c84c5c9 862e7af0 8a9fc97c 8a9fc9f4 dxgmms1!DXGADAPTER::DdiCreateContext+0x14 8a9fc9b0 8c84d08b 862e16a0 8a9fc9e8 00000000 dxgmms1!VidSchiCreateContextInternal+0x207 8a9fc9fc 8d93733e 00000000 862e70a8 8a9fcadc dxgmms1!VidSchInitializeAdapter+0x4f3 8a9fca0c 8d97b110 84fe6a30 86211000 85597648 dxgkrnl+0xb33e 8a9fcadc 8d97b894 ffffea76 00000000 8d98248d dxgkrnl+0x4f110 8a9fcaf8 8d97b812 85597648 8a9fcb0c 90a55988 dxgkrnl+0x4f894 8a9fcb10 8d982969 85597648 85597c8c 855a61b8 dxgkrnl+0x4f812 8a9fcc70 8d9823d0 85597648 00000001 00000000 dxgkrnl+0x56969 8a9fcc98 8d96d213 00000000 86fc99c8 00000040 dxgkrnl+0x563d0 8a9fccb8 86fc9e09 8a9fccd0 91e44322 00000001 dxgkrnl+0x41213 8a9fccc0 91e44322 00000001 ffffbc97 8a9fcd18 watchdog!SMgrNotifySessionChange+0x19 8a9fccd0 91e45e98 00000001 00000000 92033870 win32k!DrvNotifySessionStateChange+0x42 8a9fcd18 91e45992 0027f6dc 8a9fcd34 8288442a win32k!InitializeGreCSRSS+0x16 8a9fcd24 8288442a 00000040 00000044 0027f6f8 win32k!NtUserInitialize+0x81 8a9fcd24 776064f4 00000040 00000044 0027f6f8 nt!KiFastCallEntry+0x12a 0027f6f8 00000000 00000000 00000000 00000000 0x776064f4 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+7aefd 8d093efd a3c65cb801 mov dword ptr ds:[01B85CC6h],eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nvlddmkm+7aefd FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff9d FAILURE_BUCKET_ID: 0xD1_nvlddmkm+7aefd BUCKET_ID: 0xD1_nvlddmkm+7aefd Followup: MachineOwner ---------
THX ZigZag, plz give me link for downloading ASACPI.sys
File was replaced month ago... how can be there old ASACPI again. Hmm
In this time i was just installed new nVidia drivers. This is part of nVidia?