اطلاعات حاصل از تحلیل فایل مینی دامپ:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e62670
Debug session time: Wed Jul 31 10:45:37.211 2013 (UTC - 4:00)
System Uptime: 0 days 1:28:41.616
*******************************************************************************
* *
* 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: fffff8800647367a, The address that the exception occurred at
Arg3: fffff880031b57f8, Exception Record Address
Arg4: fffff880031b5050, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
igdpmd64+3867a
fffff880`0647367a ff5070 call qword ptr [rax+70h]
EXCEPTION_RECORD: fffff880031b57f8 -- (.exr 0xfffff880031b57f8)
ExceptionAddress: fffff8800647367a (igdpmd64+0x000000000003867a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031b5050 -- (.cxr 0xfffff880031b5050)
rax=00730077006f0064 rbx=fffffa80075d3440 rcx=fffffa8008b85ac0
rdx=0000000001f857f0 rsi=fffffa8008b85ac0 rdi=fffffa800800af88
rip=fffff8800647367a rsp=fffff880031b5a30 rbp=fffff880031b5ae0
r8=0000000000000000 r9=0000000000000000 r10=0000000000000018
r11=fffff880031b5ae8 r12=fffffa8007491ab0 r13=fffffa800486bd30
r14=fffffa80050cb190 r15=0000000000000038
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
igdpmd64+0x3867a:
fffff880`0647367a ff5070 call qword ptr [rax+70h] ds:002b:00730077`006f00d4=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
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: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecc100
GetUlongFromAddress: unable to read from fffff80002ecc1c0
ffffffffffffffff
FOLLOWUP_IP:
igdpmd64+3867a
fffff880`0647367a ff5070 call qword ptr [rax+70h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff8800647367a
STACK_TEXT:
fffff880`031b5a30 00000000`00000001 : fffff880`040315de 00000000`00000001 fffffa80`050cb190 fffffa80`08b85ac0 : igdpmd64+0x3867a
fffff880`031b5a38 fffff880`040315de : 00000000`00000001 fffffa80`050cb190 fffffa80`08b85ac0 fffffa80`c00000bb : 0x1
fffff880`031b5a40 fffff880`040316b9 : 00000000`00000000 fffffa80`052a5000 fffff880`031b5ab0 fffff880`048aa9e7 : dxgkrnl!DXGADAPTER::IsSchedulerFlushable+0x5e
fffff880`031b5a70 fffff880`04885b97 : fffffa80`08b85ac0 fffff880`031b5ac0 fffff880`031b5ae0 fffff880`048b2761 : dxgkrnl!DXGADAPTER::FlushScheduler+0xc9
fffff880`031b5aa0 fffffa80`08b85ac0 : fffff880`031b5ac0 fffff880`031b5ae0 fffff880`048b2761 fffff880`0487b6e0 : atikmpag+0xeb97
fffff880`031b5aa8 fffff880`031b5ac0 : fffff880`031b5ae0 fffff880`048b2761 fffff880`0487b6e0 00000000`00010038 : 0xfffffa80`08b85ac0
fffff880`031b5ab0 fffff880`031b5ae0 : fffff880`048b2761 fffff880`0487b6e0 00000000`00010038 fffffa80`075d3db0 : 0xfffff880`031b5ac0
fffff880`031b5ab8 fffff880`048b2761 : fffff880`0487b6e0 00000000`00010038 fffffa80`075d3db0 00000000`00000000 : 0xfffff880`031b5ae0
fffff880`031b5ac0 fffff880`0487b6e0 : 00000000`00010038 fffffa80`075d3db0 00000000`00000000 fffff880`031b5b10 : atikmpag+0x3b761
fffff880`031b5ac8 00000000`00010038 : fffffa80`075d3db0 00000000`00000000 fffff880`031b5b10 fffff880`04886c09 : atikmpag+0x46e0
fffff880`031b5ad0 fffffa80`075d3db0 : 00000000`00000000 fffff880`031b5b10 fffff880`04886c09 fffffa80`075d3440 : 0x10038
fffff880`031b5ad8 00000000`00000000 : fffff880`031b5b10 fffff880`04886c09 fffffa80`075d3440 00000000`00000000 : 0xfffffa80`075d3db0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: igdpmd64+3867a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdpmd64
IMAGE_NAME: igdpmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d0abf35
STACK_COMMAND: .cxr 0xfffff880031b5050 ; kb
FAILURE_BUCKET_ID: X64_0x7E_igdpmd64+3867a
BUCKET_ID: X64_0x7E_igdpmd64+3867a
Followup: MachineOwner
همانطور که مشاهده می کنید مشکل شما دقیقا مشابه دفعه قبل است.
موفق و موید باشید.