Hi for all and thanks in advance for your help
Its the first time that I opened an dmp file and I used windbg.
I am using home vista premium.
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\oualidos80\Desktop\New Folder\Mini121608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
/symbols[/url]
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8280c000 PsLoadedModuleList = 0x82923c70
Debug session time: Tue Dec 16 11:12:20.796 2008 (GMT+0)
System Uptime: 1 days 0:13:41.595
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 829a290b, 89b5fa24, 89b5f720}
Probably caused by : ntkrpamp.exe ( nt!CmpFreeView+21 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 829a290b, The address that the exception occurred at
Arg3: 89b5fa24, Exception Record Address
Arg4: 89b5f720, Context Record Address
Debugging Details:
------------------
AUTOBUG_OS_SKU: 3
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!CmpFreeView+21
829a290b 897204 mov dword ptr [edx+4],esi
EXCEPTION_RECORD: 89b5fa24 -- (.exr 0xffffffff89b5fa24)
ExceptionAddress: 829a290b (nt!CmpFreeView+0x00000021)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000004
Attempt to write to address 00000004
CONTEXT: 89b5f720 -- (.cxr 0xffffffff89b5f720)
eax=ab9390a0 ebx=a9aae9a8 ecx=a9aae678 edx=00000000 esi=93f5e4e0 edi=00000000
eip=829a290b esp=89b5faec ebp=89b5fb04 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!CmpFreeView+0x21:
829a290b 897204 mov dword ptr [edx+4],esi ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 00000004
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82943868
Unable to read MiSystemVaType memory at 82923420
00000004
FOLLOWUP_IP:
nt!CmpFreeView+21
829a290b 897204 mov dword ptr [edx+4],esi
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 829a2897 to 829a290b
STACK_TEXT:
89b5faf0 829a2897 a9aaec3c 00000000 89b5fb60 nt!CmpFreeView+0x21
89b5fb04 82995626 00000000 89b5fc60 800042e8 nt!CmpDestroyHiveViewList+0x86
89b5fb60 82993224 89b5fbb4 00000005 00000000 nt!CmpInitializeHive+0x3de
89b5fbd8 8298c8c5 89b5fc60 00000000 89b5fc4c nt!CmpInitHiveFromFile+0x19e
89b5fc18 8298ad4c 89b5fc60 00000000 89b5fc7b nt!CmpCmdHiveOpen+0x36
89b5fd14 8298af81 00000005 8290459c 00000005 nt!CmpFlushBackupHive+0x2fd
89b5fd38 82a65f07 8290e13c 84a84d78 82844445 nt!CmpSyncBackupHives+0x90
89b5fd44 82844445 00000000 00000000 84a84d78 nt!CmpPeriodicBackupFlushWorker+0x32
89b5fd7c 829e1b18 00000000 ec4092b3 00000000 nt!ExpWorkerThread+0xfd
89b5fdc0 8283aa2e 82844348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpFreeView+21
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
STACK_COMMAND: .cxr 0xffffffff89b5f720 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!CmpFreeView+21
BUCKET_ID: 0x7E_nt!CmpFreeView+21
Followup: MachineOwner
---------
Its the first time that I opened an dmp file and I used windbg.
I am using home vista premium.
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\oualidos80\Desktop\New Folder\Mini121608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
/symbols[/url]
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8280c000 PsLoadedModuleList = 0x82923c70
Debug session time: Tue Dec 16 11:12:20.796 2008 (GMT+0)
System Uptime: 1 days 0:13:41.595
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 829a290b, 89b5fa24, 89b5f720}
Probably caused by : ntkrpamp.exe ( nt!CmpFreeView+21 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 829a290b, The address that the exception occurred at
Arg3: 89b5fa24, Exception Record Address
Arg4: 89b5f720, Context Record Address
Debugging Details:
------------------
AUTOBUG_OS_SKU: 3
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!CmpFreeView+21
829a290b 897204 mov dword ptr [edx+4],esi
EXCEPTION_RECORD: 89b5fa24 -- (.exr 0xffffffff89b5fa24)
ExceptionAddress: 829a290b (nt!CmpFreeView+0x00000021)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000004
Attempt to write to address 00000004
CONTEXT: 89b5f720 -- (.cxr 0xffffffff89b5f720)
eax=ab9390a0 ebx=a9aae9a8 ecx=a9aae678 edx=00000000 esi=93f5e4e0 edi=00000000
eip=829a290b esp=89b5faec ebp=89b5fb04 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!CmpFreeView+0x21:
829a290b 897204 mov dword ptr [edx+4],esi ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 00000004
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82943868
Unable to read MiSystemVaType memory at 82923420
00000004
FOLLOWUP_IP:
nt!CmpFreeView+21
829a290b 897204 mov dword ptr [edx+4],esi
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 829a2897 to 829a290b
STACK_TEXT:
89b5faf0 829a2897 a9aaec3c 00000000 89b5fb60 nt!CmpFreeView+0x21
89b5fb04 82995626 00000000 89b5fc60 800042e8 nt!CmpDestroyHiveViewList+0x86
89b5fb60 82993224 89b5fbb4 00000005 00000000 nt!CmpInitializeHive+0x3de
89b5fbd8 8298c8c5 89b5fc60 00000000 89b5fc4c nt!CmpInitHiveFromFile+0x19e
89b5fc18 8298ad4c 89b5fc60 00000000 89b5fc7b nt!CmpCmdHiveOpen+0x36
89b5fd14 8298af81 00000005 8290459c 00000005 nt!CmpFlushBackupHive+0x2fd
89b5fd38 82a65f07 8290e13c 84a84d78 82844445 nt!CmpSyncBackupHives+0x90
89b5fd44 82844445 00000000 00000000 84a84d78 nt!CmpPeriodicBackupFlushWorker+0x32
89b5fd7c 829e1b18 00000000 ec4092b3 00000000 nt!ExpWorkerThread+0xfd
89b5fdc0 8283aa2e 82844348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpFreeView+21
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
STACK_COMMAND: .cxr 0xffffffff89b5f720 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!CmpFreeView+21
BUCKET_ID: 0x7E_nt!CmpFreeView+21
Followup: MachineOwner
---------
