Hallo ich habe in den letzten Wochen immer wieder Blue Screens. Ich vermute das es am Arbeitsspeicher liegt.
Es sind verschiedene Blue Screens ich habe mal 4 CrashDumps gemacht und werde sie posten.
Der MEMORY_MANAGEMENT Screen kommt am häufigsten.
zu meinem System:
I7-860 @ 3.3Ghz
8Gb G.Skill RipJaws RAM
2 x Samsung Spin Point F3 500/1000GB
MSI P55 GD65 Mainboard
Windows 8.1
Hier die CrashDumps:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff680000081f8
Arg3: 0400000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41792
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: WerFault.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff801c6fecbd3 to fffff801c6fcdca0
STACK_TEXT:
ffffd000`2cb4a238 fffff801`c6fecbd3 : 00000000`0000001a 00000000`00041792 fffff680`000081f8 04000000`00000000 : nt!KeBugCheckEx
ffffd000`2cb4a240 fffff801`c6ec54ad : ffffc000`04625380 ffffd000`2cb4a5f0 00000000`00000000 ffffd000`00000006 : nt! ?? ::FNODOBFM::`string'+0xea33
ffffd000`2cb4a4a0 fffff801`c7232e31 : ffffe000`030457a0 00000000`00000000 ffffe000`00000000 ffffe000`00000000 : nt!MiDeleteVad+0x22d
ffffd000`2cb4a590 fffff960`002237e6 : ffffc000`04625380 ffffc000`00024220 ffffe000`027e57c0 fffff801`c711f100 : nt!MiUnmapViewOfSection+0xf9
ffffd000`2cb4a660 fffff960`002236c7 : 00000000`00000049 ffffe000`001a29b0 ffffd000`2cb4a770 ffffe000`0022bdc0 : win32k!FreeView+0x96
ffffd000`2cb4a6e0 fffff801`c72a52d6 : 00000000`00000001 ffffd000`2cb4a770 00000000`0000000a ffffe000`034ee500 : win32k!UnmapDesktop+0x53
ffffd000`2cb4a710 fffff801`c72a3c7b : ffffe000`035df4b0 ffffe000`035df400 00000000`00000001 ffffe000`035df4e0 : nt!PsInvokeWin32Callout+0x42
ffffd000`2cb4a750 fffff801`c72af6e2 : ffffe000`00000000 ffffe000`0022bdc0 ffffe000`035df4c0 ffffe000`035df4b0 : nt!ExpWin32CloseProcedure+0x4f
ffffd000`2cb4a7a0 fffff801`c72af4db : 00000000`00000060 ffffc000`02448180 00000000`00000000 00000000`00000000 : nt!ObpDecrementHandleCount+0x1b6
ffffd000`2cb4a840 fffff801`c72afee6 : 00000000`00000060 fffff960`0022336d fffff901`40945cc0 00000000`00000000 : nt!ObCloseHandleTableEntry+0x313
ffffd000`2cb4a910 fffff960`00223739 : 00000000`00000060 00000000`00004000 00000000`00000000 fffff901`40945a01 : nt!ObpCloseHandle+0xae
ffffd000`2cb4a960 fffff960`00218bb5 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000030 : win32k!CloseProtectedHandle+0x2d
ffffd000`2cb4a990 fffff960`002264a5 : fffff901`40945a10 ffffd000`2cb4aa10 00000000`ffffffff ffffd000`2cb4ab00 : win32k!DestroyProcessInfo+0x2d5
ffffd000`2cb4a9c0 fffff960`00217d01 : 00000000`00000000 ffffe000`039f2080 ffffe000`02e947c0 00000000`00000000 : win32k!xxxUserProcessCallout+0x1d1
ffffd000`2cb4aa50 fffff801`c72a52d6 : ffffd000`2cb4ab60 ffffd000`2cb4ab00 00000000`00000000 00060030`00010002 : win32k!W32pProcessCallout+0x39
ffffd000`2cb4aa80 fffff801`c72a57c5 : ffffe000`0347da40 00000000`00000000 00000000`00000000 ffffe000`027e5a88 : nt!PsInvokeWin32Callout+0x42
ffffd000`2cb4aac0 fffff801`c727224d : 00000000`00000000 00000000`00000000 ffffe000`027e57c0 ffffe000`039f2080 : nt!PspExitThread+0x46d
ffffd000`2cb4abd0 fffff801`c6fd94b3 : ffffe000`027e57c0 ffffe000`039f2080 ffffd000`2cb4acc0 00000000`00000000 : nt!NtTerminateProcess+0xfd
ffffd000`2cb4ac40 00000000`77312772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e9ec48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77312772
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!FreeView+96
fffff960`002237e6 488d96a0020000 lea rdx,[rsi+2A0h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: win32k!FreeView+96
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52f9930a
BUCKET_ID_FUNC_OFFSET: 96
FAILURE_BUCKET_ID: 0x1a_41792_win32k!FreeView
BUCKET_ID: 0x1a_41792_win32k!FreeView
Followup: MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8027eee5d72, Address of the instruction which caused the bugcheck
Arg3: ffffd000204d3d40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!KiSwapThread+1a2
fffff802`7eee5d72 c3 ret
CONTEXT: ffffd000204d3d40 -- (.cxr 0xffffd000204d3d40)
rax=ffffe0017007be00 rbx=ffffe001716a8080 rcx=9c098c03f7550000
rdx=ffffe001716a81a0 rsi=ffffd001b12c0180 rdi=0000000000000002
rip=fffff8027eee5d72 rsp=ffffd000204d4778 rbp=0000000000000000
r8=0000000000001f80 r9=00000000000000ec r10=00000000000000ec
r11=ffffe0016e0cd128 r12=00000000000013ec r13=0000000000000000
r14=ffffe001716a8180 r15=0000000000000001
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!KiSwapThread+0x1a2:
fffff802`7eee5d72 c3 ret
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fbfff8027eee5779 to fffff8027eee5d72
STACK_TEXT:
ffffd000`204d4778 fbfff802`7eee5779 : ffffe001`716a8080 00000000`00080000 00000000`000013ec fffff802`7ef1d451 : nt!KiSwapThread+0x1a2
ffffd000`204d4780 ffffe001`716a8080 : 00000000`00080000 00000000`000013ec fffff802`7ef1d451 ffffe001`40ec0088 : 0xfbfff802`7eee5779
ffffd000`204d4788 00000000`00080000 : 00000000`000013ec fffff802`7ef1d451 ffffe001`40ec0088 00000000`00000001 : 0xffffe001`716a8080
ffffd000`204d4790 00000000`000013ec : fffff802`7ef1d451 ffffe001`40ec0088 00000000`00000001 00000000`00000100 : 0x80000
ffffd000`204d4798 fffff802`7ef1d451 : ffffe001`40ec0088 00000000`00000001 00000000`00000100 00000000`00000000 : 0x13ec
ffffd000`204d47a0 00000000`4fb153c8 : ffffe001`716a8080 fffff802`7eee4f0b ffffe001`716a8080 ffffe001`716a81c0 : nt!KiResumeThread+0x85
ffffd000`204d47f0 ffffe001`716a8080 : fffff802`7eee4f0b ffffe001`716a8080 ffffe001`716a81c0 00000000`000000ec : 0x4fb153c8
ffffd000`204d47f8 fffff802`7eee4f0b : ffffe001`716a8080 ffffe001`716a81c0 00000000`000000ec 00000000`00000000 : 0xffffe001`716a8080
ffffd000`204d4800 fffff802`7eee4a7a : 00000000`00000000 fffff802`7f248501 ffffe001`7169dd01 ffffe001`00000002 : nt!KeRemoveQueueEx+0x27b
ffffd000`204d4890 fffff802`7eee346a : 00000000`00000001 fffff802`7f28b930 00000000`00000000 ffffd000`204d4cc0 : nt!IoRemoveIoCompletion+0x8a
ffffd000`204d49b0 fffff802`7efee7b3 : 00000000`0000001c 000000f5`4e7d5350 00000000`00000010 000000f5`502bf6b8 : nt!NtWaitForWorkViaWorkerFactory+0x30a
ffffd000`204d4bd0 00007fff`83fec67a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000f5`502bf638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`83fec67a
FOLLOWUP_IP:
nt!KiSwapThread+1a2
fffff802`7eee5d72 c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSwapThread+1a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5318053f
STACK_COMMAND: .cxr 0xffffd000204d3d40 ; kb
BUCKET_ID_FUNC_OFFSET: 1a2
FAILURE_BUCKET_ID: 0x3B_nt!KiSwapThread
BUCKET_ID: 0x3B_nt!KiSwapThread
Followup: MachineOwner
---------
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0000265a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff801`29770a38 fffff801`27e37c9f : 00000000`00000124 00000000`00000000 ffffe000`0265a028 00000000`b2000000 : nt!KeBugCheckEx
fffff801`29770a40 fffff801`28028d41 : 00000000`00000001 ffffe000`0206b030 ffffe000`0206b030 ffffe000`0265a028 : hal!HalBugCheckSystem+0xcf
fffff801`29770a80 fffff801`27e3812c : 00000000`00000728 00000000`00000000 fffff801`29770e70 00000000`00000000 : nt!WheaReportHwError+0x22d
fffff801`29770ae0 fffff801`27e38499 : ffffe000`00000010 ffffe000`0206b030 fffff801`29770c88 ffffe000`0206b030 : hal!HalpMcaReportError+0x50
fffff801`29770c30 fffff801`27e38384 : ffffe000`0024fb00 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
fffff801`29770c80 fffff801`27e385ce : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
fffff801`29770cc0 fffff801`27e3874f : ffffe000`0024fb00 fffff801`29770ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff801`29770cf0 fffff801`27fc97bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`29770d20 fffff801`27fc9571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff801`29770e60 fffff801`27f1eb7d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
fffff801`2975c930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x39
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------
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: fffff80051b18d25, The address that the exception occurred at
Arg3: ffffd000fd82f8b8, Exception Record Address
Arg4: ffffd000fd82f0c0, 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!CcFlushCachePriv+b5
fffff800`51b18d25 488b7f08 mov rdi,qword ptr [rdi+8]
EXCEPTION_RECORD: ffffd000fd82f8b8 -- (.exr 0xffffd000fd82f8b8)
ExceptionAddress: fffff80051b18d25 (nt!CcFlushCachePriv+0x00000000000000b5)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffd000fd82f0c0 -- (.cxr 0xffffd000fd82f0c0)
rax=0000000000000000 rbx=ffffe0012366adf0 rcx=fffff80051dd4b40
rdx=0000000000000000 rsi=0000000000000001 rdi=fbffe0012341c308
rip=fffff80051b18d25 rsp=ffffd000fd82faf0 rbp=ffffd000fd82fba1
r8=ffffd000f71c0840 r9=0000000000000000 r10=ffffe0012366af08
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 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=00010282
nt!CcFlushCachePriv+0xb5:
fffff800`51b18d25 488b7f08 mov rdi,qword ptr [rdi+8] ds:002b:fbffe001`2341c310=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
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: fffff80051d3fce0: Unable to get special pool info
fffff80051d3fce0: Unable to get special pool info
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffffffffffffff
FOLLOWUP_IP:
nt!CcFlushCachePriv+b5
fffff800`51b18d25 488b7f08 mov rdi,qword ptr [rdi+8]
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from fffff80051b1984f to fffff80051b18d25
STACK_TEXT:
ffffd000`fd82faf0 fffff800`51b1984f : fbffe001`2341c308 00000000`00000000 ffffe001`00000001 00000000`00000000 : nt!CcFlushCachePriv+0xb5
ffffd000`fd82fc00 fffff800`51adbadb : ffffe001`228ad440 00000000`00000001 ffffe001`00000000 00000000`00000800 : nt!CcWriteBehindInternal+0x187
ffffd000`fd82fc90 fffff800`51b57794 : ffffd000`fb1cc3c0 ffffe001`224d5880 ffffe001`224d5880 ffffe001`1fd24340 : nt!ExpWorkerThread+0x293
ffffd000`fd82fd40 fffff800`51be25c6 : ffffd000`fb1c0180 ffffe001`224d5880 ffffd000`fb1cc3c0 ffffc000`b6f7c010 : nt!PspSystemThreadStartup+0x58
ffffd000`fd82fda0 00000000`00000000 : ffffd000`fd830000 ffffd000`fd82a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CcFlushCachePriv+b5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5318053f
STACK_COMMAND: .cxr 0xffffd000fd82f0c0 ; kb
BUCKET_ID_FUNC_OFFSET: b5
FAILURE_BUCKET_ID: AV_nt!CcFlushCachePriv
BUCKET_ID: AV_nt!CcFlushCachePriv
Followup: MachineOwner
---------
Mit der Arbeitsspeicher Spannung sowie VTT und PLL Spannung habe ich schon rumgespielt aber eine wirkliche besserung stellt sich nicht ein.
Wie gesagt der MEMORY_MANAGEMENT Screen kommt häufiger, der SYSTEM_SERVICE_EXCEPTION bis jetzt 2 mal und die anderen waren bis jetzt einmalig.
Vielleicht kann mir jemand helfen.
Es sind verschiedene Blue Screens ich habe mal 4 CrashDumps gemacht und werde sie posten.
Der MEMORY_MANAGEMENT Screen kommt am häufigsten.
zu meinem System:
I7-860 @ 3.3Ghz
8Gb G.Skill RipJaws RAM
2 x Samsung Spin Point F3 500/1000GB
MSI P55 GD65 Mainboard
Windows 8.1
Hier die CrashDumps:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff680000081f8
Arg3: 0400000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41792
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: WerFault.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff801c6fecbd3 to fffff801c6fcdca0
STACK_TEXT:
ffffd000`2cb4a238 fffff801`c6fecbd3 : 00000000`0000001a 00000000`00041792 fffff680`000081f8 04000000`00000000 : nt!KeBugCheckEx
ffffd000`2cb4a240 fffff801`c6ec54ad : ffffc000`04625380 ffffd000`2cb4a5f0 00000000`00000000 ffffd000`00000006 : nt! ?? ::FNODOBFM::`string'+0xea33
ffffd000`2cb4a4a0 fffff801`c7232e31 : ffffe000`030457a0 00000000`00000000 ffffe000`00000000 ffffe000`00000000 : nt!MiDeleteVad+0x22d
ffffd000`2cb4a590 fffff960`002237e6 : ffffc000`04625380 ffffc000`00024220 ffffe000`027e57c0 fffff801`c711f100 : nt!MiUnmapViewOfSection+0xf9
ffffd000`2cb4a660 fffff960`002236c7 : 00000000`00000049 ffffe000`001a29b0 ffffd000`2cb4a770 ffffe000`0022bdc0 : win32k!FreeView+0x96
ffffd000`2cb4a6e0 fffff801`c72a52d6 : 00000000`00000001 ffffd000`2cb4a770 00000000`0000000a ffffe000`034ee500 : win32k!UnmapDesktop+0x53
ffffd000`2cb4a710 fffff801`c72a3c7b : ffffe000`035df4b0 ffffe000`035df400 00000000`00000001 ffffe000`035df4e0 : nt!PsInvokeWin32Callout+0x42
ffffd000`2cb4a750 fffff801`c72af6e2 : ffffe000`00000000 ffffe000`0022bdc0 ffffe000`035df4c0 ffffe000`035df4b0 : nt!ExpWin32CloseProcedure+0x4f
ffffd000`2cb4a7a0 fffff801`c72af4db : 00000000`00000060 ffffc000`02448180 00000000`00000000 00000000`00000000 : nt!ObpDecrementHandleCount+0x1b6
ffffd000`2cb4a840 fffff801`c72afee6 : 00000000`00000060 fffff960`0022336d fffff901`40945cc0 00000000`00000000 : nt!ObCloseHandleTableEntry+0x313
ffffd000`2cb4a910 fffff960`00223739 : 00000000`00000060 00000000`00004000 00000000`00000000 fffff901`40945a01 : nt!ObpCloseHandle+0xae
ffffd000`2cb4a960 fffff960`00218bb5 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000030 : win32k!CloseProtectedHandle+0x2d
ffffd000`2cb4a990 fffff960`002264a5 : fffff901`40945a10 ffffd000`2cb4aa10 00000000`ffffffff ffffd000`2cb4ab00 : win32k!DestroyProcessInfo+0x2d5
ffffd000`2cb4a9c0 fffff960`00217d01 : 00000000`00000000 ffffe000`039f2080 ffffe000`02e947c0 00000000`00000000 : win32k!xxxUserProcessCallout+0x1d1
ffffd000`2cb4aa50 fffff801`c72a52d6 : ffffd000`2cb4ab60 ffffd000`2cb4ab00 00000000`00000000 00060030`00010002 : win32k!W32pProcessCallout+0x39
ffffd000`2cb4aa80 fffff801`c72a57c5 : ffffe000`0347da40 00000000`00000000 00000000`00000000 ffffe000`027e5a88 : nt!PsInvokeWin32Callout+0x42
ffffd000`2cb4aac0 fffff801`c727224d : 00000000`00000000 00000000`00000000 ffffe000`027e57c0 ffffe000`039f2080 : nt!PspExitThread+0x46d
ffffd000`2cb4abd0 fffff801`c6fd94b3 : ffffe000`027e57c0 ffffe000`039f2080 ffffd000`2cb4acc0 00000000`00000000 : nt!NtTerminateProcess+0xfd
ffffd000`2cb4ac40 00000000`77312772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e9ec48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77312772
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!FreeView+96
fffff960`002237e6 488d96a0020000 lea rdx,[rsi+2A0h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: win32k!FreeView+96
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52f9930a
BUCKET_ID_FUNC_OFFSET: 96
FAILURE_BUCKET_ID: 0x1a_41792_win32k!FreeView
BUCKET_ID: 0x1a_41792_win32k!FreeView
Followup: MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8027eee5d72, Address of the instruction which caused the bugcheck
Arg3: ffffd000204d3d40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!KiSwapThread+1a2
fffff802`7eee5d72 c3 ret
CONTEXT: ffffd000204d3d40 -- (.cxr 0xffffd000204d3d40)
rax=ffffe0017007be00 rbx=ffffe001716a8080 rcx=9c098c03f7550000
rdx=ffffe001716a81a0 rsi=ffffd001b12c0180 rdi=0000000000000002
rip=fffff8027eee5d72 rsp=ffffd000204d4778 rbp=0000000000000000
r8=0000000000001f80 r9=00000000000000ec r10=00000000000000ec
r11=ffffe0016e0cd128 r12=00000000000013ec r13=0000000000000000
r14=ffffe001716a8180 r15=0000000000000001
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!KiSwapThread+0x1a2:
fffff802`7eee5d72 c3 ret
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fbfff8027eee5779 to fffff8027eee5d72
STACK_TEXT:
ffffd000`204d4778 fbfff802`7eee5779 : ffffe001`716a8080 00000000`00080000 00000000`000013ec fffff802`7ef1d451 : nt!KiSwapThread+0x1a2
ffffd000`204d4780 ffffe001`716a8080 : 00000000`00080000 00000000`000013ec fffff802`7ef1d451 ffffe001`40ec0088 : 0xfbfff802`7eee5779
ffffd000`204d4788 00000000`00080000 : 00000000`000013ec fffff802`7ef1d451 ffffe001`40ec0088 00000000`00000001 : 0xffffe001`716a8080
ffffd000`204d4790 00000000`000013ec : fffff802`7ef1d451 ffffe001`40ec0088 00000000`00000001 00000000`00000100 : 0x80000
ffffd000`204d4798 fffff802`7ef1d451 : ffffe001`40ec0088 00000000`00000001 00000000`00000100 00000000`00000000 : 0x13ec
ffffd000`204d47a0 00000000`4fb153c8 : ffffe001`716a8080 fffff802`7eee4f0b ffffe001`716a8080 ffffe001`716a81c0 : nt!KiResumeThread+0x85
ffffd000`204d47f0 ffffe001`716a8080 : fffff802`7eee4f0b ffffe001`716a8080 ffffe001`716a81c0 00000000`000000ec : 0x4fb153c8
ffffd000`204d47f8 fffff802`7eee4f0b : ffffe001`716a8080 ffffe001`716a81c0 00000000`000000ec 00000000`00000000 : 0xffffe001`716a8080
ffffd000`204d4800 fffff802`7eee4a7a : 00000000`00000000 fffff802`7f248501 ffffe001`7169dd01 ffffe001`00000002 : nt!KeRemoveQueueEx+0x27b
ffffd000`204d4890 fffff802`7eee346a : 00000000`00000001 fffff802`7f28b930 00000000`00000000 ffffd000`204d4cc0 : nt!IoRemoveIoCompletion+0x8a
ffffd000`204d49b0 fffff802`7efee7b3 : 00000000`0000001c 000000f5`4e7d5350 00000000`00000010 000000f5`502bf6b8 : nt!NtWaitForWorkViaWorkerFactory+0x30a
ffffd000`204d4bd0 00007fff`83fec67a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000f5`502bf638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`83fec67a
FOLLOWUP_IP:
nt!KiSwapThread+1a2
fffff802`7eee5d72 c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSwapThread+1a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5318053f
STACK_COMMAND: .cxr 0xffffd000204d3d40 ; kb
BUCKET_ID_FUNC_OFFSET: 1a2
FAILURE_BUCKET_ID: 0x3B_nt!KiSwapThread
BUCKET_ID: 0x3B_nt!KiSwapThread
Followup: MachineOwner
---------
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0000265a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff801`29770a38 fffff801`27e37c9f : 00000000`00000124 00000000`00000000 ffffe000`0265a028 00000000`b2000000 : nt!KeBugCheckEx
fffff801`29770a40 fffff801`28028d41 : 00000000`00000001 ffffe000`0206b030 ffffe000`0206b030 ffffe000`0265a028 : hal!HalBugCheckSystem+0xcf
fffff801`29770a80 fffff801`27e3812c : 00000000`00000728 00000000`00000000 fffff801`29770e70 00000000`00000000 : nt!WheaReportHwError+0x22d
fffff801`29770ae0 fffff801`27e38499 : ffffe000`00000010 ffffe000`0206b030 fffff801`29770c88 ffffe000`0206b030 : hal!HalpMcaReportError+0x50
fffff801`29770c30 fffff801`27e38384 : ffffe000`0024fb00 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
fffff801`29770c80 fffff801`27e385ce : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
fffff801`29770cc0 fffff801`27e3874f : ffffe000`0024fb00 fffff801`29770ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff801`29770cf0 fffff801`27fc97bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`29770d20 fffff801`27fc9571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff801`29770e60 fffff801`27f1eb7d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
fffff801`2975c930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x39
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------
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: fffff80051b18d25, The address that the exception occurred at
Arg3: ffffd000fd82f8b8, Exception Record Address
Arg4: ffffd000fd82f0c0, 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!CcFlushCachePriv+b5
fffff800`51b18d25 488b7f08 mov rdi,qword ptr [rdi+8]
EXCEPTION_RECORD: ffffd000fd82f8b8 -- (.exr 0xffffd000fd82f8b8)
ExceptionAddress: fffff80051b18d25 (nt!CcFlushCachePriv+0x00000000000000b5)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffd000fd82f0c0 -- (.cxr 0xffffd000fd82f0c0)
rax=0000000000000000 rbx=ffffe0012366adf0 rcx=fffff80051dd4b40
rdx=0000000000000000 rsi=0000000000000001 rdi=fbffe0012341c308
rip=fffff80051b18d25 rsp=ffffd000fd82faf0 rbp=ffffd000fd82fba1
r8=ffffd000f71c0840 r9=0000000000000000 r10=ffffe0012366af08
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 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=00010282
nt!CcFlushCachePriv+0xb5:
fffff800`51b18d25 488b7f08 mov rdi,qword ptr [rdi+8] ds:002b:fbffe001`2341c310=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
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: fffff80051d3fce0: Unable to get special pool info
fffff80051d3fce0: Unable to get special pool info
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffffffffffffff
FOLLOWUP_IP:
nt!CcFlushCachePriv+b5
fffff800`51b18d25 488b7f08 mov rdi,qword ptr [rdi+8]
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from fffff80051b1984f to fffff80051b18d25
STACK_TEXT:
ffffd000`fd82faf0 fffff800`51b1984f : fbffe001`2341c308 00000000`00000000 ffffe001`00000001 00000000`00000000 : nt!CcFlushCachePriv+0xb5
ffffd000`fd82fc00 fffff800`51adbadb : ffffe001`228ad440 00000000`00000001 ffffe001`00000000 00000000`00000800 : nt!CcWriteBehindInternal+0x187
ffffd000`fd82fc90 fffff800`51b57794 : ffffd000`fb1cc3c0 ffffe001`224d5880 ffffe001`224d5880 ffffe001`1fd24340 : nt!ExpWorkerThread+0x293
ffffd000`fd82fd40 fffff800`51be25c6 : ffffd000`fb1c0180 ffffe001`224d5880 ffffd000`fb1cc3c0 ffffc000`b6f7c010 : nt!PspSystemThreadStartup+0x58
ffffd000`fd82fda0 00000000`00000000 : ffffd000`fd830000 ffffd000`fd82a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CcFlushCachePriv+b5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5318053f
STACK_COMMAND: .cxr 0xffffd000fd82f0c0 ; kb
BUCKET_ID_FUNC_OFFSET: b5
FAILURE_BUCKET_ID: AV_nt!CcFlushCachePriv
BUCKET_ID: AV_nt!CcFlushCachePriv
Followup: MachineOwner
---------
Mit der Arbeitsspeicher Spannung sowie VTT und PLL Spannung habe ich schon rumgespielt aber eine wirkliche besserung stellt sich nicht ein.
Wie gesagt der MEMORY_MANAGEMENT Screen kommt häufiger, der SYSTEM_SERVICE_EXCEPTION bis jetzt 2 mal und die anderen waren bis jetzt einmalig.
Vielleicht kann mir jemand helfen.
