unregelmäßige Abstürze - C:\Windows\Minidump\092012-49280-01.dmp
Hallo Foren-Gemeinde,
ich habe seit gestern das Problem, dass der Rechner in unregelmäßigen Abständen einen Bluescreen hat und runterfährt.
Hab gegooglet und die minidump Datei debugged. Jedoch kann ich damit nicht viel anfangen, da meine Kenntnisse nicht so weitreichend sind. Wäre freundlich wenn mal jemand einen Blick drauf werfen kann und mir sagt woarn es hakt ;)
Mfg, razore Code:
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: fffff88004377ff3, The address that the exception occurred at
Arg3: fffff880020a7698, Exception Record Address
Arg4: fffff880020a6f00, 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:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`04377ff3 48894108 mov qword ptr [rcx+8],rax
EXCEPTION_RECORD: fffff880020a7698 -- (.exr 0xfffff880020a7698)
ExceptionAddress: fffff88004377ff3 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000000a3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880020a6f00 -- (.cxr 0xfffff880020a6f00)
rax=fffffa8005562a70 rbx=fffff8a00bcf6a40 rcx=ffff4c8007116cb0
rdx=fffff8a007bccdf0 rsi=fffffa8006aeb200 rdi=fffffa8005442000
rip=fffff88004377ff3 rsp=fffff880020a78d0 rbp=0000000000000000
r8=fffffa8006aeb250 r9=fffff880020a7901 r10=0000000000000000
r11=fffffa8004ddb410 r12=0000000000000027 r13=0000000000000000
r14=fffffa80050898a0 r15=00000000000000ec
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3:
fffff880`04377ff3 48894108 mov qword ptr [rcx+8],rax ds:002b:ffff4c80`07116cb8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aba0e0
GetUlongFromAddress: unable to read from fffff80002aba198
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`04377ff3 48894108 mov qword ptr [rcx+8],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880043758af to fffff88004377ff3
STACK_TEXT:
fffff880`020a78d0 fffff880`043758af : 00000000`00000000 fffffa80`04fd1138 00000000`0000005a fffffa80`051bd3b0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3
fffff880`020a7910 fffff880`0438f65d : 00000000`00000000 fffff8a0`085c0910 fffffa80`00000000 fffffa80`050898a0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`020a7ae0 fffff880`0438f398 : fffff800`00b96080 fffff880`0438ed00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`020a7cd0 fffff880`0438ee96 : 00000000`00000000 fffffa80`0512d430 00000000`00000080 fffffa80`04ddb410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`020a7d00 fffff800`02b226e6 : fffff880`023dcd70 fffffa80`04e047d0 fffffa80`048f3040 fffff800`0287aec7 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`020a7d40 fffff800`02861566 : fffff800`029fce80 fffffa80`04e047d0 fffff800`02a0ac40 fffff880`0121ca90 : nt!PspSystemThreadStartup+0x5a
fffff880`020a7d80 00000000`00000000 : fffff880`020a8000 fffff880`020a2000 fffff880`020a7690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174
STACK_COMMAND: .cxr 0xfffff880020a6f00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
Followup: MachineOwner
---------
| 