Here is a few of my bsod mini dumps but im not sure how to interpret them can anyone help?
Ps. the coloured |||||||||||| lines is what ive put it to seperate the mini dump files from each other there is a total of 3 mini dumps here.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\110310-33250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50
Debug session time: Wed Nov 3 12:54:33.818 2010 (UTC + 0:00)
System Uptime: 0 days 0:04:11.427
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002a79984, fffff88006c22250, 0}
Probably caused by : hardware ( nt!KiSystemServiceCopyEnd+4 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002a79984, Address of the instruction which caused the bugcheck
Arg3: fffff88006c22250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al
CONTEXT: fffff88006c22250 -- (.cxr 0xfffff88006c22250)
rax=0000000000000000 rbx=fffffa8005b71060 rcx=0000000000000000
rdx=00000000000007ff rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002a79984 rsp=fffff88006c22c20 rbp=fffff88006c22ca0
r8=fffffa80050ddbb8 r9=0000000000000000 r10=fffffffffffffffe
r11=00000000002f9d00 r12=000000001f24fcf0 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KiSystemServiceCopyEnd+0x4:
fffff800`02a79984 1800 sbb byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: vsserv.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al
LAST_CONTROL_TRANSFER: from 000000007738009a to fffff80002a79984
STACK_TEXT:
fffff880`06c22c20 00000000`7738009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x4
00000000`1f24fcc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7738009a
FOLLOWUP_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemServiceCopyEnd+4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff88006c22250 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Loading Dump File [C:\Windows\Minidump\110210-586265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
Debug session time: Tue Nov 2 16:17:31.796 2010 (UTC + 0:00)
System Uptime: 0 days 0:10:26.406
Loading Kernel Symbols
...............................................................
................................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck DA, {504, fffff6fc40077820, 2, ef04}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b43b )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_PTE_MISUSE (da)
The stack trace identifies the guilty driver.
Arguments:
Arg1: 0000000000000504, Type of error.
Arg2: fffff6fc40077820
Arg3: 0000000000000002
Arg4: 000000000000ef04
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xDA
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002b28e11 to fffff80002ad0740
STACK_TEXT:
fffff880`02f939d8 fffff800`02b28e11 : 00000000`000000da 00000000`00000504 fffff6fc`40077820 00000000`00000002 : nt!KeBugCheckEx
fffff880`02f939e0 fffff800`02ae05e4 : 00000000`00000004 fffff800`02c85720 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xb43b
fffff880`02f93af0 fffff800`02ae3df5 : fffffa80`018a8040 00000000`00000008 0000ef6c`000026ea 00000000`00000001 : nt!MiEmptyPteBins+0x10d
fffff880`02f93b40 fffff800`02ae4eb4 : 00000000`00000008 00000000`00000001 fffffa80`018a8040 fffff800`02ae40cb : nt!MiAdjustPteBins+0x29
fffff880`02f93b80 fffff800`02ae5173 : 00000000`00000008 fffff880`02f93c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x40
fffff880`02f93bd0 fffff800`02d74c06 : fffffa80`018c8040 00000000`00000080 fffffa80`018a8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`02f93d40 fffff800`02aaec26 : fffff800`02c4ae80 fffffa80`018c8040 fffffa80`018c7530 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f93d80 00000000`00000000 : fffff880`02f94000 fffff880`02f8e000 fffff880`02f93710 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+b43b
fffff800`02b28e11 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+b43b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b
BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b
Followup: MachineOwner
---------
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Loading Dump File [C:\Windows\Minidump\110110-34265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Mon Nov 1 15:35:38.527 2010 (UTC + 0:00)
System Uptime: 0 days 0:11:08.136
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002acb984, fffff880065ad1e0, 0}
Probably caused by : hardware ( nt!KiSystemServiceCopyEnd+4 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002acb984, Address of the instruction which caused the bugcheck
Arg3: fffff880065ad1e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al
CONTEXT: fffff880065ad1e0 -- (.cxr 0xfffff880065ad1e0)
rax=0000000000000002 rbx=fffffa8005bc5b60 rcx=fffffa80057de530
rdx=fffffa80057de4b8 rsi=00000000044ee4d8 rdi=fffff880065adbc8
rip=fffff80002acb984 rsp=fffff880065adbb0 rbp=fffff880065adca0
r8=0000000000000000 r9=0000000000000001 r10=0000000000000003
r11=fffff880065adba0 r12=0000000000000000 r13=00000000044ee560
r14=0000000000000000 r15=0000000000ca9f20
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!KiSystemServiceCopyEnd+0x4:
fffff800`02acb984 1800 sbb byte ptr [rax],al ds:002b:00000000`00000002=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: SearchIndexer.
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al
LAST_CONTROL_TRANSFER: from 000000007789030a to fffff80002acb984
STACK_TEXT:
fffff880`065adbb0 00000000`7789030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x4
00000000`044ee4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7789030a
FOLLOWUP_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemServiceCopyEnd+4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff880065ad1e0 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Here are 3 different mini dump files all fairly recently i just picked some at random hope this is enough
Ps. the coloured |||||||||||| lines is what ive put it to seperate the mini dump files from each other there is a total of 3 mini dumps here.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\110310-33250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50
Debug session time: Wed Nov 3 12:54:33.818 2010 (UTC + 0:00)
System Uptime: 0 days 0:04:11.427
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002a79984, fffff88006c22250, 0}
Probably caused by : hardware ( nt!KiSystemServiceCopyEnd+4 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002a79984, Address of the instruction which caused the bugcheck
Arg3: fffff88006c22250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al
CONTEXT: fffff88006c22250 -- (.cxr 0xfffff88006c22250)
rax=0000000000000000 rbx=fffffa8005b71060 rcx=0000000000000000
rdx=00000000000007ff rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002a79984 rsp=fffff88006c22c20 rbp=fffff88006c22ca0
r8=fffffa80050ddbb8 r9=0000000000000000 r10=fffffffffffffffe
r11=00000000002f9d00 r12=000000001f24fcf0 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KiSystemServiceCopyEnd+0x4:
fffff800`02a79984 1800 sbb byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: vsserv.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al
LAST_CONTROL_TRANSFER: from 000000007738009a to fffff80002a79984
STACK_TEXT:
fffff880`06c22c20 00000000`7738009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x4
00000000`1f24fcc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7738009a
FOLLOWUP_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemServiceCopyEnd+4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff88006c22250 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Loading Dump File [C:\Windows\Minidump\110210-586265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
Debug session time: Tue Nov 2 16:17:31.796 2010 (UTC + 0:00)
System Uptime: 0 days 0:10:26.406
Loading Kernel Symbols
...............................................................
................................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck DA, {504, fffff6fc40077820, 2, ef04}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b43b )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_PTE_MISUSE (da)
The stack trace identifies the guilty driver.
Arguments:
Arg1: 0000000000000504, Type of error.
Arg2: fffff6fc40077820
Arg3: 0000000000000002
Arg4: 000000000000ef04
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xDA
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002b28e11 to fffff80002ad0740
STACK_TEXT:
fffff880`02f939d8 fffff800`02b28e11 : 00000000`000000da 00000000`00000504 fffff6fc`40077820 00000000`00000002 : nt!KeBugCheckEx
fffff880`02f939e0 fffff800`02ae05e4 : 00000000`00000004 fffff800`02c85720 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xb43b
fffff880`02f93af0 fffff800`02ae3df5 : fffffa80`018a8040 00000000`00000008 0000ef6c`000026ea 00000000`00000001 : nt!MiEmptyPteBins+0x10d
fffff880`02f93b40 fffff800`02ae4eb4 : 00000000`00000008 00000000`00000001 fffffa80`018a8040 fffff800`02ae40cb : nt!MiAdjustPteBins+0x29
fffff880`02f93b80 fffff800`02ae5173 : 00000000`00000008 fffff880`02f93c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x40
fffff880`02f93bd0 fffff800`02d74c06 : fffffa80`018c8040 00000000`00000080 fffffa80`018a8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`02f93d40 fffff800`02aaec26 : fffff800`02c4ae80 fffffa80`018c8040 fffffa80`018c7530 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f93d80 00000000`00000000 : fffff880`02f94000 fffff880`02f8e000 fffff880`02f93710 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+b43b
fffff800`02b28e11 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+b43b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b
BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b
Followup: MachineOwner
---------
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Loading Dump File [C:\Windows\Minidump\110110-34265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Mon Nov 1 15:35:38.527 2010 (UTC + 0:00)
System Uptime: 0 days 0:11:08.136
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002acb984, fffff880065ad1e0, 0}
Probably caused by : hardware ( nt!KiSystemServiceCopyEnd+4 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002acb984, Address of the instruction which caused the bugcheck
Arg3: fffff880065ad1e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al
CONTEXT: fffff880065ad1e0 -- (.cxr 0xfffff880065ad1e0)
rax=0000000000000002 rbx=fffffa8005bc5b60 rcx=fffffa80057de530
rdx=fffffa80057de4b8 rsi=00000000044ee4d8 rdi=fffff880065adbc8
rip=fffff80002acb984 rsp=fffff880065adbb0 rbp=fffff880065adca0
r8=0000000000000000 r9=0000000000000001 r10=0000000000000003
r11=fffff880065adba0 r12=0000000000000000 r13=00000000044ee560
r14=0000000000000000 r15=0000000000ca9f20
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!KiSystemServiceCopyEnd+0x4:
fffff800`02acb984 1800 sbb byte ptr [rax],al ds:002b:00000000`00000002=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: SearchIndexer.
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al
LAST_CONTROL_TRANSFER: from 000000007789030a to fffff80002acb984
STACK_TEXT:
fffff880`065adbb0 00000000`7789030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x4
00000000`044ee4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7789030a
FOLLOWUP_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemServiceCopyEnd+4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff880065ad1e0 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Here are 3 different mini dump files all fairly recently i just picked some at random hope this is enough
Last edited: