I did the second step from you advice, because i have checked memory before with memtest.
my last mini dump looks like:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\101211-14976-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e52670
Debug session time: Wed Oct 12 12:11:00.879 2011 (UTC + 2:00)
System Uptime: 0 days 0:08:35.495
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E,
{ffffffffc0000005, fffff880049cf13b, fffff880056b14d8, fffff880056b0d30}
Probably caused by : igdkmd64.sys ( igdkmd64+1b313b )
Followup: MachineOwner
---------
2: 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: fffff880049cf13b, The address that the exception occurred at
Arg3: fffff880056b14d8, Exception Record Address
Arg4: fffff880056b0d30, Context Record Address
Debugging Details:
------------------
Code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]
EXCEPTION_RECORD: fffff880056b14d8 -- (.exr 0xfffff880056b14d8)
ExceptionAddress: fffff880049cf13b (igdkmd64+0x00000000001b313b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff880056b0d30 -- (.cxr 0xfffff880056b0d30)
rax=0000000000000000 rbx=0000000000000057 rcx=0000000000000000
rdx=000000000000000d rsi=fffff880056b1770 rdi=fffffa8008dea000
rip=fffff880049cf13b rsp=fffff880056b1710 rbp=fffffa8008380950
r8=000000000000040b r9=fffff880011b48dc r10=fffff880056b19e0
r11=fffff880056b15f0 r12=fffff8a00d804355 r13=0000000000000000
r14=fffffa8008e1cd01 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
igdkmd64+0x1b313b:
fffff880`049cf13b ff10 call qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
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: 0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebc100
0000000000000000
FOLLOWUP_IP:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa8008381bf0 to fffff880049cf13b
STACK_TEXT:
fffff880`056b1710 fffffa80`08381bf0 : 00000000`00000000 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 : igdkmd64+0x1b313b
fffff880`056b1718 00000000`00000000 : 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 fffff880`048459ec : 0xfffffa80`08381bf0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: igdkmd64+1b313b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e4152eb
STACK_COMMAND: .cxr 0xfffff880056b0d30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b
BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b
Followup: MachineOwner
---------
2: 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: fffff880049cf13b, The address that the exception occurred at
Arg3: fffff880056b14d8, Exception Record Address
Arg4: fffff880056b0d30, 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:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]
EXCEPTION_RECORD: fffff880056b14d8 -- (.exr 0xfffff880056b14d8)
ExceptionAddress: fffff880049cf13b (igdkmd64+0x00000000001b313b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff880056b0d30 -- (.cxr 0xfffff880056b0d30)
rax=0000000000000000 rbx=0000000000000057 rcx=0000000000000000
rdx=000000000000000d rsi=fffff880056b1770 rdi=fffffa8008dea000
rip=fffff880049cf13b rsp=fffff880056b1710 rbp=fffffa8008380950
r8=000000000000040b r9=fffff880011b48dc r10=fffff880056b19e0
r11=fffff880056b15f0 r12=fffff8a00d804355 r13=0000000000000000
r14=fffffa8008e1cd01 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
igdkmd64+0x1b313b:
fffff880`049cf13b ff10 call qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
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: 0000000000000000
READ_ADDRESS: 0000000000000000
FOLLOWUP_IP:
igdkmd64+1b313b
fffff880`049cf13b ff10 call qword ptr [rax]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa8008381bf0 to fffff880049cf13b
STACK_TEXT:
fffff880`056b1710 fffffa80`08381bf0 : 00000000`00000000 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 : igdkmd64+0x1b313b
fffff880`056b1718 00000000`00000000 : 00000000`000ffdfc fffffa80`083ec000 fffffa80`083ec000 fffff880`048459ec : 0xfffffa80`08381bf0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: igdkmd64+1b313b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e4152eb
STACK_COMMAND: .cxr 0xfffff880056b0d30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b
BUCKET_ID: X64_0x7E_VRF_igdkmd64+1b313b
Followup: MachineOwner
---------