
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080613-13587-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: C:\Windows\System32
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e61670
Debug session time: Tue Aug  6 12:27:16.368 2013 (UTC + 2:00)
System Uptime: 0 days 0:00:39.148
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {200, 2, 1, fffff8000320662a}

*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : hardware ( PCIIDEX!BmFlush+25 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000200, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000320662a, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecb100
GetUlongFromAddress: unable to read from fffff80002ecb1c0
 0000000000000200 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalpDmaFlushScatterTransfer+3e
fffff800`0320662a 010f            add     dword ptr [rdi],ecx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF88002F93FB0

TRAP_FRAME:  fffff88002f8c7b0 -- (.trap 0xfffff88002f8c7b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f8c988 rbx=0000000000000000 rcx=fffffa80070e5850
rdx=fffffa800884d0d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000320662a rsp=fffff88002f8c940 rbp=0000000000000000
 r8=fffffa800717fbe0  r9=0000000000000000 r10=fffffa8007225610
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
hal!HalpDmaFlushScatterTransfer+0x3e:
fffff800`0320662a 010f            add     dword ptr [rdi],ecx ds:00000000`00000000=????????
Resetting default scope

MISALIGNED_IP: 
hal!HalpDmaFlushScatterTransfer+3e
fffff800`0320662a 010f            add     dword ptr [rdi],ecx

LAST_CONTROL_TRANSFER:  from fffff80002c931a9 to fffff80002c93c00

STACK_TEXT:  
fffff880`02f8c668 fffff800`02c931a9 : 00000000`0000000a 00000000`00000200 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f8c670 fffff800`02c91e20 : 00000000`00000000 fffffa80`073bebb8 00000000`00000025 fffffa80`0717fbe0 : nt!KiBugCheckDispatch+0x69
fffff880`02f8c7b0 fffff800`0320662a : fffff880`01080764 fffffa80`07d57440 00000000`00000000 fffffa80`077bfc00 : nt!KiPageFault+0x260
fffff880`02f8c940 fffff800`0320983f : fffffa80`070e5850 00000000`00000000 fffffa80`0717fbe0 00000000`00000200 : hal!HalpDmaFlushScatterTransfer+0x3e
fffff880`02f8c990 fffff800`032087d5 : fffffa80`07d570b0 00000000`00000000 00000000`00000200 fffffa80`0884d0d0 : hal!IoFlushAdapterBuffers+0xaf
fffff880`02f8c9d0 fffff880`00fe6199 : fffffa80`07d57010 fffffa80`072381b0 fffffa80`07d57010 fffffa80`069cd000 : hal!HalPutScatterGatherList+0x85
fffff880`02f8ca30 fffff880`00dd7453 : fffffa80`077c2500 fffffa80`06af6e40 00000000`00000000 fffffa80`069ce6e3 : PCIIDEX!BmFlush+0x25
fffff880`02f8ca60 fffff880`00dd7104 : fffffa80`072241a0 00000000`00000000 fffffa80`072241a0 fffffa80`07d57010 : ataport!IdeProcessCompletedRequests+0x123
fffff880`02f8cb90 fffff880`010d55fc : fffffa80`069cd000 00000000`00000000 fffffa80`07224118 fffffa80`07224100 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f8cc50 fffffa80`069cd000 : 00000000`00000000 fffffa80`07224118 fffffa80`07224100 00000000`00000010 : sptd+0x4b5fc
fffff880`02f8cc58 00000000`00000000 : fffffa80`07224118 fffffa80`07224100 00000000`00000010 00000000`00000246 : 0xfffffa80`069cd000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
PCIIDEX!BmFlush+25
fffff880`00fe6199 4883a3e003000000 and     qword ptr [rbx+3E0h],0

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  PCIIDEX!BmFlush+25

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner
---------

