AW: Bluescreens und Abstürze im neuen pc
hey simpel!
hab grad wieder einen gehabt:
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121710-19624-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032a3e50
Debug session time: Fri Dec 17 16:54:18.682 2010 (GMT+1)
System Uptime: 0 days 2:28:07.430
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6f9d003b678, 0, fffff800030f24be, 5}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+de )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6f9d003b678, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030f24be, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330e0e0
fffff6f9d003b678
FAULTING_IP:
nt!MiDispatchFault+de
fffff800`030f24be 488b1c29 mov rbx,qword ptr [rcx+rbp]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: pes2011.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88007a1f5e0 -- (.trap 0xfffff88007a1f5e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800503c060 rbx=0000000000000059 rcx=fffff88007a1f930
rdx=000007806aac0710 rsi=0000000000000001 rdi=fffff880009e6180
rip=fffff800030cd680 rsp=fffff88007a1f778 rbp=fffff88007a1fca0
r8=0000000000000040 r9=0000000000000002 r10=0000000000000001
r11=fffff88007a1f8f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!memmove+0x250:
fffff800`030cd680 488b440af8 mov rax,qword ptr [rdx+rcx-8] ds:c600:00000000`724e0038=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800031558c1 to fffff800030d6740
STACK_TEXT:
fffff880`07a1f078 fffff800`031558c1 : 00000000`00000050 fffff6f9`d003b678 00000000`00000000 fffff880`07a1f1e0 : nt!KeBugCheckEx
fffff880`07a1f080 fffff800`030d482e : 00000000`00000000 00000000`724e0038 fffff8a0`0214cd00 fffffa80`04aec868 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`07a1f1e0 fffff800`030f24be : 00000000`00000000 00000000`733a0038 fffff680`00399d00 fffffa80`04aec868 : nt!KiPageFault+0x16e
fffff880`07a1f370 fffff800`030f0743 : 00000000`00060000 00000000`724e0038 fffff8a0`001dcd50 fffff800`00000000 : nt!MiDispatchFault+0xde
fffff880`07a1f480 fffff800`030d482e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x343
fffff880`07a1f5e0 fffff800`030cd680 : fffff800`0337f41b fffff880`07a1fca0 00000000`00000120 ffffffff`00000118 : nt!KiPageFault+0x16e
fffff880`07a1f778 fffff800`0337f41b : fffff880`07a1fca0 00000000`00000120 ffffffff`00000118 00000000`00000000 : nt!memmove+0x250
fffff880`07a1f780 fffff800`0337f80b : fffffa80`04aec4d0 00000000`724e0000 fffffa80`04f4c2d0 00000000`0029dff0 : nt!MmCopyVirtualMemory+0x17b
fffff880`07a1fb30 fffff800`030d5993 : fffffa80`0503c060 00000000`0008dc98 fffff880`07a1fbc8 00000000`00000130 : nt!NtReadVirtualMemory+0xff
fffff880`07a1fbb0 00000000`7724014a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008dc78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7724014a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDispatchFault+de
fffff800`030f24be 488b1c29 mov rbx,qword ptr [rcx+rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiDispatchFault+de
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiDispatchFault+de
BUCKET_ID: X64_0x50_nt!MiDispatchFault+de
Followup: MachineOwner
---------
Habe jetzt nach dem Bluescreen deine Ram-Konfiguration eingestellt, mit der frequenz auf 1066mhz.
Ist der Bluescreen denn einer der gleichen Art wie die vorher?
