Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\022411-17940-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82a3e000 PsLoadedModuleList = 0x82b88850
Debug session time: Thu Feb 24 06:53:10.529 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:50.090
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 82adfcbd, 8ab2ba60, 8ab2b640}
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwppInjectTransportSendAsync+2e8 )
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: 82adfcbd, The address that the exception occurred at
Arg3: 8ab2ba60, Exception Record Address
Arg4: 8ab2b640, 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!RtlImageNtHeaderEx+4a
82adfcbd 663902 cmp word ptr [edx],ax
EXCEPTION_RECORD: 8ab2ba60 -- (.exr 0xffffffff8ab2ba60)
ExceptionAddress: 82adfcbd (nt!RtlImageNtHeaderEx+0x0000004a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 7ffa0000
Attempt to read from address 7ffa0000
CONTEXT: 8ab2b640 -- (.cxr 0xffffffff8ab2b640)
eax=00005a4d ebx=85212efc ecx=00000000 edx=7ffa0000 esi=00000000 edi=8ab2bb3c
eip=82adfcbd esp=8ab2bb28 ebp=8ab2bb28 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlImageNtHeaderEx+0x4a:
82adfcbd 663902 cmp word ptr [edx],ax ds:0023:7ffa0000=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
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: 7ffa0000
READ_ADDRESS: GetPointerFromAddress: unable to read from 82ba8718
Unable to read MiSystemVaType memory at 82b881a0
7ffa0000
FOLLOWUP_IP:
fwpkclnt!FwppInjectTransportSendAsync+2e8
88f6aa0c 5f pop edi
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 82ae6a54 to 82adfcbd
STACK_TEXT:
8ab2bb28 82ae6a54 00000000 00000000 85212cc0 nt!RtlImageNtHeaderEx+0x4a
8ab2bbe8 82abc86f 00000000 82b69d20 82b6b63c nt!RtlImageNtHeader+0x1a
8ab2bc08 88f6aa0c 84cbe020 00000000 8ab2bc28 nt!KiSearchForNewThread+0x2e
8ab2bcb8 8d91c661 00000000 00000000 8d92cdf0 fwpkclnt!FwppInjectTransportSendAsync+0x2e8
8ab2bd00 82abbaab 80000b20 00000000 84cbe020 tunnel!LwUnlockQueue+0x21
8ab2bd50 82c47f5e 00000001 a203e27c 00000000 nt!ExpWorkerThread+0x10d
8ab2bd90 82aef219 82abb99e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: fwpkclnt!FwppInjectTransportSendAsync+2e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fwpkclnt
IMAGE_NAME: fwpkclnt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7892c
STACK_COMMAND: .cxr 0xffffffff8ab2b640 ; kb
FAILURE_BUCKET_ID: 0x7E_fwpkclnt!FwppInjectTransportSendAsync+2e8
BUCKET_ID: 0x7E_fwpkclnt!FwppInjectTransportSendAsync+2e8
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\022011-12776-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a43000 PsLoadedModuleList = 0x82b8b810
Debug session time: Sun Feb 20 12:52:36.102 2011 (UTC - 5:00)
System Uptime: 0 days 6:27:02.215
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {a10e7a00, 2, 0, 833c8fb6}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+94 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: a10e7a00, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 833c8fb6, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bab718
Unable to read MiSystemVaType memory at 82b8b160
a10e7a00
CURRENT_IRQL: 2
FAULTING_IP:
ataport!IdeLogCrbActive+94
833c8fb6 a5 movs dword ptr es:[edi],dword ptr [esi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 82b69a38 -- (.trap 0xffffffff82b69a38)
ErrCode = 00000000
eax=87267d10 ebx=85577020 ecx=a10e79d0 edx=00000036 esi=a10e7a00 edi=85577020
eip=833c8fb6 esp=82b69aac ebp=82b69ab8 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
ataport!IdeLogCrbActive+0x94:
833c8fb6 a5 movs dword ptr es:[edi],dword ptr [esi] es:0023:85577020=???????? ds:0023:a10e7a00=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 833c8fb6 to 82a8982b
STACK_TEXT:
82b69a38 833c8fb6 badb0d00 00000036 01a1e459 nt!KiTrap0E+0x2cf
82b69ab8 833d10e8 87267d10 85b93200 00000000 ataport!IdeLogCrbActive+0x94
82b69adc 8339b074 87267d10 82b69b14 82a10a2e ataport!IdeStartIoCallBack+0x5c
82b69ae8 82a10a2e 8556fc00 00000000 87267d6c PCIIDEX!BmReceiveScatterGatherList+0x1e
82b69b14 8339b199 87267d6c 8556fc00 85b931e0 hal!HalBuildScatterGatherList+0x1ba
82b69b50 833d0b46 8556fcb8 87267d10 87267d00 PCIIDEX!BmSetup+0x3d
82b69b6c 833d1041 84ca80e0 87267d00 87267d10 ataport!IdePortSetupScatterGatherList+0x2a
82b69b84 833cfa12 84ca80e0 87267d10 868c5e2a ataport!IdeDispatchChannelRequest+0x59
82b69b9c 833cfc6a 84ca80e0 87267d10 868c5ba0 ataport!IdeStartChannelRequest+0x42
82b69bb0 833d12a0 84ca66c8 868c5ba0 84ca80e0 ataport!IdeStartNextDeviceRequest+0x22
82b69c24 833d166b 84ca80e0 868c5ba0 84ca809c ataport!IdeProcessCompletedRequests+0xd8
82b69c78 82aab3b5 84ca809c 84ca8028 00000000 ataport!IdePortCompletionDpc+0xab
82b69cd4 82aab218 82b6cd20 82b76280 00000000 nt!KiExecuteAllDpcs+0xf9
82b69d20 82aab038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82b69d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!IdeLogCrbActive+94
833c8fb6 a5 movs dword ptr es:[edi],dword ptr [esi]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ataport!IdeLogCrbActive+94
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf16
FAILURE_BUCKET_ID: 0xD1_ataport!IdeLogCrbActive+94
BUCKET_ID: 0xD1_ataport!IdeLogCrbActive+94
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\022011-12386-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a09000 PsLoadedModuleList = 0x82b51810
Debug session time: Sun Feb 20 15:56:58.063 2011 (UTC - 5:00)
System Uptime: 0 days 3:03:29.624
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {9e1b9810, 2, 0, 833dbfb6}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+94 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 9e1b9810, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 833dbfb6, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82b71718
Unable to read MiSystemVaType memory at 82b51160
9e1b9810
CURRENT_IRQL: 2
FAULTING_IP:
ataport!IdeLogCrbActive+94
833dbfb6 a5 movs dword ptr es:[edi],dword ptr [esi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 82b2fa38 -- (.trap 0xffffffff82b2fa38)
ErrCode = 00000000
eax=872a2008 ebx=855765a0 ecx=9e1b97e0 edx=00000019 esi=9e1b9810 edi=855765a0
eip=833dbfb6 esp=82b2faac ebp=82b2fab8 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
ataport!IdeLogCrbActive+0x94:
833dbfb6 a5 movs dword ptr es:[edi],dword ptr [esi] es:0023:855765a0=???????? ds:0023:9e1b9810=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 833dbfb6 to 82a4f82b
STACK_TEXT:
82b2fa38 833dbfb6 badb0d00 00000019 863ec0d0 nt!KiTrap0E+0x2cf
82b2fab8 833e40e8 872a2008 86855180 00000000 ataport!IdeLogCrbActive+0x94
82b2fadc 833ae074 872a2008 82b2fb14 82e1da2e ataport!IdeStartIoCallBack+0x5c
82b2fae8 82e1da2e 84c98c00 00000000 872a2064 PCIIDEX!BmReceiveScatterGatherList+0x1e
82b2fb14 833ae199 872a2064 84c98c00 86855160 hal!HalBuildScatterGatherList+0x1ba
82b2fb50 833e3b46 84c98cb8 872a2008 872a2000 PCIIDEX!BmSetup+0x3d
82b2fb6c 833e4041 84cc70e0 872a2000 872a2008 ataport!IdePortSetupScatterGatherList+0x2a
82b2fb84 833e2a12 84cc70e0 872a2008 86b01c52 ataport!IdeDispatchChannelRequest+0x59
82b2fb9c 833e2c6a 84cc70e0 872a2008 86b019c8 ataport!IdeStartChannelRequest+0x42
82b2fbb0 833e42a0 84cc56c8 86b019c8 84cc70e0 ataport!IdeStartNextDeviceRequest+0x22
82b2fc24 833e466b 84cc70e0 86b019c8 84cc709c ataport!IdeProcessCompletedRequests+0xd8
82b2fc78 82a713b5 84cc709c 84cc7028 00000000 ataport!IdePortCompletionDpc+0xab
82b2fcd4 82a71218 82b32d20 82b3c280 00000000 nt!KiExecuteAllDpcs+0xf9
82b2fd20 82a71038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82b2fd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!IdeLogCrbActive+94
833dbfb6 a5 movs dword ptr es:[edi],dword ptr [esi]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ataport!IdeLogCrbActive+94
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf16
FAILURE_BUCKET_ID: 0xD1_ataport!IdeLogCrbActive+94
BUCKET_ID: 0xD1_ataport!IdeLogCrbActive+94
Followup: MachineOwner
---------