Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\081610-26192-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) 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: Mon Aug 16 00:31:29.314 2010 (UTC + 2:00)
System Uptime: 0 days 0:00:10.594
Loading Kernel Symbols
...............................................................
........................
Loading User Symbols
Loading unloaded module list
.
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002abeb80, fffff8800316ed48, fffff8800316e5b0}
Probably caused by : atikmpag.sys ( atikmpag+9eaf )
Followup: MachineOwner
---------
0: kd> !analyze –v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002abeb80, fffff8800316ed48, fffff8800316e5b0}
Probably caused by : atikmpag.sys ( atikmpag+9eaf )
Followup: MachineOwner
---------
0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002abeb80, The address that the exception occurred at
Arg3: fffff8800316ed48, Exception Record Address
Arg4: fffff8800316e5b0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!IoGetAttachedDevice+0
fffff800`02abeb80 488b4118 mov rax,qword ptr [rcx+18h]
EXCEPTION_RECORD: fffff8800316ed48 -- (.exr 0xfffff8800316ed48)
ExceptionAddress: fffff80002abeb80 (nt!IoGetAttachedDevice)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000018
Attempt to read from address 0000000000000018
CONTEXT: fffff8800316e5b0 -- (.cxr 0xfffff8800316e5b0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff880040ecd10 rsi=fffffa8008749740 rdi=0000000000000000
rip=fffff80002abeb80 rsp=fffff8800316ef88 rbp=0000000000000000
r8=fffff8800316efb0 r9=0000000000000180 r10=fffff80002a0a000
r11=fffff8800316eda0 r12=0000000000000000 r13=fffff88004107838
r14=fffff8800316f4f8 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!IoGetAttachedDevice:
fffff800`02abeb80 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:00000000`00000018=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000018
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb20e0
0000000000000018
FOLLOWUP_IP:
atikmpag+9eaf
fffff880`040d3eaf ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff880040d3eaf to fffff80002abeb80
STACK_TEXT:
fffff880`0316ef88 fffff880`040d3eaf : fffffa80`08131060 fffff800`02c09800 fffff880`00000000 00000000`00000000 : nt!IoGetAttachedDevice
fffff880`0316ef90 fffffa80`08131060 : fffff800`02c09800 fffff880`00000000 00000000`00000000 fffff880`001a0018 : atikmpag+0x9eaf
fffff880`0316ef98 fffff800`02c09800 : fffff880`00000000 00000000`00000000 fffff880`001a0018 fffff880`040ecd10 : 0xfffffa80`08131060
fffff880`0316efa0 fffff880`00000000 : 00000000`00000000 fffff880`001a0018 fffff880`040ecd10 fffff800`02c09a70 : nt!ExpWorkerFactoryThreadCreationList+0x1a0
fffff880`0316efa8 00000000`00000000 : fffff880`001a0018 fffff880`040ecd10 fffff800`02c09a70 fffff800`02bf4e80 : 0xfffff880`00000000
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: atikmpag+9eaf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e
STACK_COMMAND: .cxr 0xfffff8800316e5b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmpag+9eaf
BUCKET_ID: X64_0x7E_atikmpag+9eaf
Followup: MachineOwner
---------
0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002abeb80, The address that the exception occurred at
Arg3: fffff8800316ed48, Exception Record Address
Arg4: fffff8800316e5b0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!IoGetAttachedDevice+0
fffff800`02abeb80 488b4118 mov rax,qword ptr [rcx+18h]
EXCEPTION_RECORD: fffff8800316ed48 -- (.exr 0xfffff8800316ed48)
ExceptionAddress: fffff80002abeb80 (nt!IoGetAttachedDevice)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000018
Attempt to read from address 0000000000000018
CONTEXT: fffff8800316e5b0 -- (.cxr 0xfffff8800316e5b0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff880040ecd10 rsi=fffffa8008749740 rdi=0000000000000000
rip=fffff80002abeb80 rsp=fffff8800316ef88 rbp=0000000000000000
r8=fffff8800316efb0 r9=0000000000000180 r10=fffff80002a0a000
r11=fffff8800316eda0 r12=0000000000000000 r13=fffff88004107838
r14=fffff8800316f4f8 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!IoGetAttachedDevice:
fffff800`02abeb80 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:00000000`00000018=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000018
READ_ADDRESS: 0000000000000018
FOLLOWUP_IP:
atikmpag+9eaf
fffff880`040d3eaf ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff880040d3eaf to fffff80002abeb80
STACK_TEXT:
fffff880`0316ef88 fffff880`040d3eaf : fffffa80`08131060 fffff800`02c09800 fffff880`00000000 00000000`00000000 : nt!IoGetAttachedDevice
fffff880`0316ef90 fffffa80`08131060 : fffff800`02c09800 fffff880`00000000 00000000`00000000 fffff880`001a0018 : atikmpag+0x9eaf
fffff880`0316ef98 fffff800`02c09800 : fffff880`00000000 00000000`00000000 fffff880`001a0018 fffff880`040ecd10 : 0xfffffa80`08131060
fffff880`0316efa0 fffff880`00000000 : 00000000`00000000 fffff880`001a0018 fffff880`040ecd10 fffff800`02c09a70 : nt!ExpWorkerFactoryThreadCreationList+0x1a0
fffff880`0316efa8 00000000`00000000 : fffff880`001a0018 fffff880`040ecd10 fffff800`02c09a70 fffff800`02bf4e80 : 0xfffff880`00000000
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: atikmpag+9eaf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e
STACK_COMMAND: .cxr 0xfffff8800316e5b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmpag+9eaf
BUCKET_ID: X64_0x7E_atikmpag+9eaf
Followup: MachineOwner
---------
0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002abeb80, The address that the exception occurred at
Arg3: fffff8800316ed48, Exception Record Address
Arg4: fffff8800316e5b0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!IoGetAttachedDevice+0
fffff800`02abeb80 488b4118 mov rax,qword ptr [rcx+18h]
EXCEPTION_RECORD: fffff8800316ed48 -- (.exr 0xfffff8800316ed48)
ExceptionAddress: fffff80002abeb80 (nt!IoGetAttachedDevice)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000018
Attempt to read from address 0000000000000018
CONTEXT: fffff8800316e5b0 -- (.cxr 0xfffff8800316e5b0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff880040ecd10 rsi=fffffa8008749740 rdi=0000000000000000
rip=fffff80002abeb80 rsp=fffff8800316ef88 rbp=0000000000000000
r8=fffff8800316efb0 r9=0000000000000180 r10=fffff80002a0a000
r11=fffff8800316eda0 r12=0000000000000000 r13=fffff88004107838
r14=fffff8800316f4f8 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!IoGetAttachedDevice:
fffff800`02abeb80 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:00000000`00000018=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000018
READ_ADDRESS: 0000000000000018
FOLLOWUP_IP:
atikmpag+9eaf
fffff880`040d3eaf ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff880040d3eaf to fffff80002abeb80
STACK_TEXT:
fffff880`0316ef88 fffff880`040d3eaf : fffffa80`08131060 fffff800`02c09800 fffff880`00000000 00000000`00000000 : nt!IoGetAttachedDevice
fffff880`0316ef90 fffffa80`08131060 : fffff800`02c09800 fffff880`00000000 00000000`00000000 fffff880`001a0018 : atikmpag+0x9eaf
fffff880`0316ef98 fffff800`02c09800 : fffff880`00000000 00000000`00000000 fffff880`001a0018 fffff880`040ecd10 : 0xfffffa80`08131060
fffff880`0316efa0 fffff880`00000000 : 00000000`00000000 fffff880`001a0018 fffff880`040ecd10 fffff800`02c09a70 : nt!ExpWorkerFactoryThreadCreationList+0x1a0
fffff880`0316efa8 00000000`00000000 : fffff880`001a0018 fffff880`040ecd10 fffff800`02c09a70 fffff800`02bf4e80 : 0xfffff880`00000000
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: atikmpag+9eaf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e
STACK_COMMAND: .cxr 0xfffff8800316e5b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmpag+9eaf
BUCKET_ID: X64_0x7E_atikmpag+9eaf
Followup: MachineOwner
---------