icrosoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_SF_09-12-2013.zip\SF_09-12-2013\Mini120913-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 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 = 0x82800000 PsLoadedModuleList = 0x82911e10
Debug session time: Sun Dec 8 11:40:22.442 2013 (UTC - 5:00)
System Uptime: 0 days 0:56:19.381
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, c, af0ffcf0, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 0000000c, The address that the exception occurred at
Arg3: af0ffcf0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+0
0000000c ?? ???
TRAP_FRAME: af0ffcf0 -- (.trap 0xffffffffaf0ffcf0)
ErrCode = 00000010
eax=00000102 ebx=804270e0 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=0000000c esp=af0ffd64 ebp=af0ffd64 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
0000000c ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0031e954 to 0000000c
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
af0ffd60 0031e954 77ce0f34 badb0d00 0031e8e8 0xc
af0ffd64 77ce0f34 badb0d00 0031e8e8 00000000 0x31e954
af0ffd68 badb0d00 0031e8e8 00000000 00000000 0x77ce0f34
af0ffd6c 0031e8e8 00000000 00000000 00000000 0xbadb0d00
af0ffd70 00000000 00000000 00000000 00000000 0x31e8e8
STACK_COMMAND: .trap 0xffffffffaf0ffcf0 ; kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: BAD_STACK
Followup: MachineOwner
The above is what I can see from the file that you posted. I have bolded where the report indicates that the results are inconclusive, which is unusual
