Could you help me make sense of this please?
this is what i got when i ran the mini dump on WINDBG.
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini032911-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbolfiles*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.17021.x86fre.vista_gdr.100218-0019
Machine Name:
Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
Debug session time: Tue Mar 29 16:46:29.721 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:28.516
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 825aaa2e, 82fc0ba0, 82fc089c}
Probably caused by : ntkrpamp.exe ( nt!PnpProcessQueryRemoveAndEject+860 )
Followup: MachineOwner
---------
1: 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: 825aaa2e, The address that the exception occurred at
Arg3: 82fc0ba0, Exception Record Address
Arg4: 82fc089c, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!PnpProcessQueryRemoveAndEject+860
825aaa2e 399e24010000 cmp dword ptr [esi+124h],ebx
EXCEPTION_RECORD: 82fc0ba0 -- (.exr 0xffffffff82fc0ba0)
ExceptionAddress: 825aaa2e (nt!PnpProcessQueryRemoveAndEject+0x00000860)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000124
Attempt to read from address 00000124
CONTEXT: 82fc089c -- (.cxr 0xffffffff82fc089c)
eax=00000000 ebx=00000000 ecx=0000bb40 edx=84244ed8 esi=00000000 edi=824a4c50
eip=825aaa2e esp=82fc0c68 ebp=82fc0d04 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!PnpProcessQueryRemoveAndEject+0x860:
825aaa2e 399e24010000 cmp dword ptr [esi+124h],ebx ds:0023:00000124=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
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: 00000000
EXCEPTION_PARAMETER2: 00000124
READ_ADDRESS: GetPointerFromAddress: unable to read from 825315ac
Unable to read MiSystemVaType memory at 825117e0
00000124
FOLLOWUP_IP:
nt!PnpProcessQueryRemoveAndEject+860
825aaa2e 399e24010000 cmp dword ptr [esi+124h],ebx
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 825aadcd to 825aaa2e
STACK_TEXT:
82fc0d04 825aadcd 82fc0d34 00000000 aa708cc8 nt!PnpProcessQueryRemoveAndEject+0x860
82fc0d1c 825a992f 00000000 824fde7c 8427a020 nt!PnpProcessTargetDeviceEvent+0x38
82fc0d44 82478fc0 8481f258 00000000 8427a020 nt!PnpDeviceEventWorker+0x201
82fc0d7c 82625704 8481f258 82fcb680 00000000 nt!ExpWorkerThread+0xfd
82fc0dc0 8249162e 82478ec3 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!PnpProcessQueryRemoveAndEject+860
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b7d25c9
STACK_COMMAND: .cxr 0xffffffff82fc089c ; kb
FAILURE_BUCKET_ID: 0x7E_nt!PnpProcessQueryRemoveAndEject+860
BUCKET_ID: 0x7E_nt!PnpProcessQueryRemoveAndEject+860
Followup: MachineOwner
---------
1: kd> lmvm nt
start end module name
82400000 827a1000 nt (pdb symbols) c:\symbolfiles\ntkrpamp.pdb\D928687D16FB4389BA783A36567621302\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: c:\symbolfiles\ntkrnlpa.exe\4B7D25C93a1000\ntkrnlpa.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Thu Feb 18 06:34:33 2010 (4B7D25C9)
CheckSum: 00361FBC
ImageSize: 003A1000
File version: 6.0.6000.17021
Product version: 6.0.6000.17021
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 6.0.6000.17021
FileVersion: 6.0.6000.17021 (vista_gdr.100218-0019)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
