Bluescreen

Hallo,

seit geraumer Zeit habe ich ständig Bluescreens.

Alles fing an als ich mein Netzteil austauschte und Empire of Sports installierte.
Von nun an hatte ich meistens wenn ich Empire of Sports spiele einen Bluescreen.

Ich habe letzte Woche daher meinen Rechner neuinstalliert und diesmal Empire of Sports nicht installiert. Einige Tage ging es gut doch dann kamen gleich 2 Bluescreens fast hintereinander. Habe daher mein altes Netzteil wieder eingebaut, da ich dachte es könnte daran liegen.

Wieder ging es ein paar Tage gut doch schon wieder der Schock ein Bluescreen.

Habe gerade eben die CrashDumps mal ausgelesen.
Bei allen drei steht etwas mit "ntoskrnl.exe".
Wie behebe ich dass?

Könnt ihr mir helfen?

Kann es an meinem Netzteil liegen?

Wie finde ich heraus woran es liegt?

Für eure Hilfe schonmal danke,

owlfritz

------------------------------------------
Aktuelles sys:

Prozessor:AMD Phenom II X2 550
Mainboard:MSI 770-C45
Speicher:4gb von GEIL
Graka:nVidia GeForce 9600 GT
Netzteil: Enermax 385W

----
Altes Netzteil: Jersey 400W

Wenn die Probleme seit Austausch des NT´s bestehen, liegt die Vermutung nahe, dass es genau daran liegt.
Womit hast du die Crashdumps ausgelesen?
Falls du sie mit dem Debugger ausgelesen hast, könntest du die Auswertung posten.
Auf jeden Fall aber mal den genauen Stopfehlercode des Bluescreens mitteilen.

Komischerweise tritt der Bluescreen auch mit dem alten NT auf.

Habe es mit dem WindowsDebugger durchgeführt.

-------
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062910-19936-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Tue Jun 29 16:39:52.342 2010 (GMT+2)
System Uptime: 0 days 1:19:05.809
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89634c689, b3b7465ee8b2a4c7, fffff80002fff000, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+70600 )

Followup: MachineOwner
---------

Du hast den Symbolpfad im Debugger nicht korrekt hinterlegt. Schau mal hier: Klick!

Ok jetzt nochmal.
---------
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa800f2b5d3b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b3bd5f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc50e0
fffffa800f2b5d3b

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005cc0730 -- (.trap 0xfffff88005cc0730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=000000000010e744
rdx=fffffa800f2b5d20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b3bd5f rsp=fffff88005cc08c0 rbp=0000000000000004
r8=fffff88005cc08f0 r9=0000000000000002 r10=fffffa8003a74ba0
r11=000000000050e746 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiRelinkStandbyPage+0x8f:
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh] ds:1810:fffffa80`0f2b5d3b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a8cb69 to fffff80002a8d600

STACK_TEXT:
fffff880`05cc05e8 fffff800`02a8cb69 : 00000000`0000000a fffffa80`0f2b5d3b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05cc05f0 fffff800`02a8b7e0 : fffff800`02c1c880 00000000`00000005 00000000`00001810 fffff800`02a9ff7d : nt!KiBugCheckDispatch+0x69
fffff880`05cc0730 fffff800`02b3bd5f : 00000000`0050e746 00000000`00000019 fffffa80`032a9cf0 00000000`05420000 : nt!KiPageFault+0x260
fffff880`05cc08c0 fffff800`02b9a5b5 : fffffa80`03c2d460 fffffa80`03c2f000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0x8f
fffff880`05cc0930 fffff800`02e9fbc4 : fffffa80`03c2d000 fffff880`05cc0ca0 fffff880`05cc0a08 00000000`00130001 : nt!MmSetPfnListPriorities+0x175
fffff880`05cc0980 fffff800`02f008ea : 00000000`00000020 00000000`00000000 fffffa80`03c2d000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05cc09d0 fffff800`02f0502e : 00000000`00000000 00000000`00fdb390 00000000`0000004f 000007fe`f7dfdc01 : nt!PfSetSuperfetchInformation+0x199
fffff880`05cc0ab0 fffff800`02a8c853 : fffffa80`04b2f060 00000000`015ac590 00000000`00fdc4c0 00000000`00000000 : nt!NtSetSystemInformation+0xb91
fffff880`05cc0c20 00000000`76f2144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00fdb318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f2144a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRelinkStandbyPage+8f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa800f2b5d3b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b3bd5f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: fffffa800f2b5d3b

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005cc0730 -- (.trap 0xfffff88005cc0730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=000000000010e744
rdx=fffffa800f2b5d20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b3bd5f rsp=fffff88005cc08c0 rbp=0000000000000004
r8=fffff88005cc08f0 r9=0000000000000002 r10=fffffa8003a74ba0
r11=000000000050e746 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiRelinkStandbyPage+0x8f:
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh] ds:1810:fffffa80`0f2b5d3b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a8cb69 to fffff80002a8d600

STACK_TEXT:
fffff880`05cc05e8 fffff800`02a8cb69 : 00000000`0000000a fffffa80`0f2b5d3b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05cc05f0 fffff800`02a8b7e0 : fffff800`02c1c880 00000000`00000005 00000000`00001810 fffff800`02a9ff7d : nt!KiBugCheckDispatch+0x69
fffff880`05cc0730 fffff800`02b3bd5f : 00000000`0050e746 00000000`00000019 fffffa80`032a9cf0 00000000`05420000 : nt!KiPageFault+0x260
fffff880`05cc08c0 fffff800`02b9a5b5 : fffffa80`03c2d460 fffffa80`03c2f000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0x8f
fffff880`05cc0930 fffff800`02e9fbc4 : fffffa80`03c2d000 fffff880`05cc0ca0 fffff880`05cc0a08 00000000`00130001 : nt!MmSetPfnListPriorities+0x175
fffff880`05cc0980 fffff800`02f008ea : 00000000`00000020 00000000`00000000 fffffa80`03c2d000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05cc09d0 fffff800`02f0502e : 00000000`00000000 00000000`00fdb390 00000000`0000004f 000007fe`f7dfdc01 : nt!PfSetSuperfetchInformation+0x199
fffff880`05cc0ab0 fffff800`02a8c853 : fffffa80`04b2f060 00000000`015ac590 00000000`00fdc4c0 00000000`00000000 : nt!NtSetSystemInformation+0xb91
fffff880`05cc0c20 00000000`76f2144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00fdb318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f2144a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRelinkStandbyPage+8f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa800f2b5d3b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b3bd5f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: fffffa800f2b5d3b

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005cc0730 -- (.trap 0xfffff88005cc0730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=000000000010e744
rdx=fffffa800f2b5d20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b3bd5f rsp=fffff88005cc08c0 rbp=0000000000000004
r8=fffff88005cc08f0 r9=0000000000000002 r10=fffffa8003a74ba0
r11=000000000050e746 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiRelinkStandbyPage+0x8f:
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh] ds:1810:fffffa80`0f2b5d3b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a8cb69 to fffff80002a8d600

STACK_TEXT:
fffff880`05cc05e8 fffff800`02a8cb69 : 00000000`0000000a fffffa80`0f2b5d3b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05cc05f0 fffff800`02a8b7e0 : fffff800`02c1c880 00000000`00000005 00000000`00001810 fffff800`02a9ff7d : nt!KiBugCheckDispatch+0x69
fffff880`05cc0730 fffff800`02b3bd5f : 00000000`0050e746 00000000`00000019 fffffa80`032a9cf0 00000000`05420000 : nt!KiPageFault+0x260
fffff880`05cc08c0 fffff800`02b9a5b5 : fffffa80`03c2d460 fffffa80`03c2f000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0x8f
fffff880`05cc0930 fffff800`02e9fbc4 : fffffa80`03c2d000 fffff880`05cc0ca0 fffff880`05cc0a08 00000000`00130001 : nt!MmSetPfnListPriorities+0x175
fffff880`05cc0980 fffff800`02f008ea : 00000000`00000020 00000000`00000000 fffffa80`03c2d000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05cc09d0 fffff800`02f0502e : 00000000`00000000 00000000`00fdb390 00000000`0000004f 000007fe`f7dfdc01 : nt!PfSetSuperfetchInformation+0x199
fffff880`05cc0ab0 fffff800`02a8c853 : fffffa80`04b2f060 00000000`015ac590 00000000`00fdc4c0 00000000`00000000 : nt!NtSetSystemInformation+0xb91
fffff880`05cc0c20 00000000`76f2144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00fdb318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f2144a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRelinkStandbyPage+8f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa800f2b5d3b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b3bd5f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: fffffa800f2b5d3b

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005cc0730 -- (.trap 0xfffff88005cc0730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=000000000010e744
rdx=fffffa800f2b5d20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b3bd5f rsp=fffff88005cc08c0 rbp=0000000000000004
r8=fffff88005cc08f0 r9=0000000000000002 r10=fffffa8003a74ba0
r11=000000000050e746 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiRelinkStandbyPage+0x8f:
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh] ds:1810:fffffa80`0f2b5d3b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a8cb69 to fffff80002a8d600

STACK_TEXT:
fffff880`05cc05e8 fffff800`02a8cb69 : 00000000`0000000a fffffa80`0f2b5d3b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05cc05f0 fffff800`02a8b7e0 : fffff800`02c1c880 00000000`00000005 00000000`00001810 fffff800`02a9ff7d : nt!KiBugCheckDispatch+0x69
fffff880`05cc0730 fffff800`02b3bd5f : 00000000`0050e746 00000000`00000019 fffffa80`032a9cf0 00000000`05420000 : nt!KiPageFault+0x260
fffff880`05cc08c0 fffff800`02b9a5b5 : fffffa80`03c2d460 fffffa80`03c2f000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0x8f
fffff880`05cc0930 fffff800`02e9fbc4 : fffffa80`03c2d000 fffff880`05cc0ca0 fffff880`05cc0a08 00000000`00130001 : nt!MmSetPfnListPriorities+0x175
fffff880`05cc0980 fffff800`02f008ea : 00000000`00000020 00000000`00000000 fffffa80`03c2d000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05cc09d0 fffff800`02f0502e : 00000000`00000000 00000000`00fdb390 00000000`0000004f 000007fe`f7dfdc01 : nt!PfSetSuperfetchInformation+0x199
fffff880`05cc0ab0 fffff800`02a8c853 : fffffa80`04b2f060 00000000`015ac590 00000000`00fdc4c0 00000000`00000000 : nt!NtSetSystemInformation+0xb91
fffff880`05cc0c20 00000000`76f2144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00fdb318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f2144a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRelinkStandbyPage+8f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa800f2b5d3b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b3bd5f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: fffffa800f2b5d3b

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005cc0730 -- (.trap 0xfffff88005cc0730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=000000000010e744
rdx=fffffa800f2b5d20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b3bd5f rsp=fffff88005cc08c0 rbp=0000000000000004
r8=fffff88005cc08f0 r9=0000000000000002 r10=fffffa8003a74ba0
r11=000000000050e746 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiRelinkStandbyPage+0x8f:
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh] ds:1810:fffffa80`0f2b5d3b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a8cb69 to fffff80002a8d600

STACK_TEXT:
fffff880`05cc05e8 fffff800`02a8cb69 : 00000000`0000000a fffffa80`0f2b5d3b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05cc05f0 fffff800`02a8b7e0 : fffff800`02c1c880 00000000`00000005 00000000`00001810 fffff800`02a9ff7d : nt!KiBugCheckDispatch+0x69
fffff880`05cc0730 fffff800`02b3bd5f : 00000000`0050e746 00000000`00000019 fffffa80`032a9cf0 00000000`05420000 : nt!KiPageFault+0x260
fffff880`05cc08c0 fffff800`02b9a5b5 : fffffa80`03c2d460 fffffa80`03c2f000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0x8f
fffff880`05cc0930 fffff800`02e9fbc4 : fffffa80`03c2d000 fffff880`05cc0ca0 fffff880`05cc0a08 00000000`00130001 : nt!MmSetPfnListPriorities+0x175
fffff880`05cc0980 fffff800`02f008ea : 00000000`00000020 00000000`00000000 fffffa80`03c2d000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`05cc09d0 fffff800`02f0502e : 00000000`00000000 00000000`00fdb390 00000000`0000004f 000007fe`f7dfdc01 : nt!PfSetSuperfetchInformation+0x199
fffff880`05cc0ab0 fffff800`02a8c853 : fffffa80`04b2f060 00000000`015ac590 00000000`00fdc4c0 00000000`00000000 : nt!NtSetSystemInformation+0xb91
fffff880`05cc0c20 00000000`76f2144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00fdb318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f2144a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelinkStandbyPage+8f
fffff800`02b3bd5f 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRelinkStandbyPage+8f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

BUCKET_ID: X64_0xA_nt!MiRelinkStandbyPage+8f

Followup: MachineOwner
---------
Und hier der vorletzte:
---------
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89634c689, Reserved
Arg2: b3b7465ee8b2a4c7, Reserved
Arg3: fffff80002fff000, Failure type dependent information
Arg4: 0000000000000000, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

Debugging Details:
------------------


BUGCHECK_STR: 0x109

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002a75600

STACK_TEXT:
fffff880`02ffc5d8 00000000`00000000 : 00000000`00000109 a3a039d8`9634c689 b3b7465e`e8b2a4c7 fffff800`02fff000 : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

Followup: MachineOwner
---------

Nach der Auswertung der CrashDumps bin ich mir nun nicht mehr so sicher, ob es am NT liegen kann.
Alle Auswertungen deuten eher auf den RAM als Ursache hin.

Kannst du bitte mal ein paar Screenshots mit CPU-Z machen (Reiter Mainbaord, CPU, Memory und SPD).

Ebenso den RAM mit Memtest86+ auf Fehler prüfen.

Ok hier die Screenshots.

Ok, dann würde ich als erstes ein Bios-Update vornehmen. Aktuellste Version ist 1.9. Seit der 1.4 Version, die bei dir drauf ist, wurden mehrere Kompatibilitätsverbesserungen mit RAM eingearbeitet.
Das Bios-Update könnte daher schon genügen.

Falls nicht, den Timing Mode der RAM im Bios auf 2T (Command Rate) einstellen.

Bios habe ich jetzt geupdatet.
Doch eben gerade kamen gleich 3 Bluescreens.
Bin so langsam echt am verzweifeln.

Was soll ich jetzt tun?
Scheint als wäre etwas am RAM schrott.

Hier die neuesten Bluescreen:
----------------
DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: fffff880057242d8, Actual security check cookie from the stack
Arg2: 0000f8800129e148, Expected security check cookie
Arg3: ffff077ffed61eb7, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

Debugging Details:
------------------


DEFAULT_BUCKET_ID: GS_FALSE_POSITIVE_MISSING_GSFRAME

SECURITY_COOKIE: Expected 0000f8800129e148 found fffff880057242d8

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xF7

PROCESS_NAME: System

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff88005724098 -- (.exr 0xfffff88005724098)
ExceptionAddress: fffff880012fa43e (Ntfs!NtfsUpdateDuplicateInfo+0x0000000000000036)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88005724140 -- (.trap 0xfffff88005724140)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff0000045ba3a8 rbx=0000000000000000 rcx=fffff88005724a60
rdx=fffff8a0022a8010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880012fa43e rsp=fffff880057242d8 rbp=fffff88005724cc0
r8=fffff8a0022a8450 r9=fffff8a0027a5bc0 r10=01cb1949fcda19e6
r11=fffffa8006147578 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
Ntfs!NtfsUpdateDuplicateInfo+0x36:
fffff880`012fa43e 0000 add byte ptr [rax],al ds:0048:ffff0000`045ba3a8=??
Resetting default scope

MISALIGNED_IP:
Ntfs!NtfsUpdateDuplicateInfo+36
fffff880`012fa43e 0000 add byte ptr [rax],al

LAST_CONTROL_TRANSFER: from fffff88001262156 to fffff80002ac3600

STACK_TEXT:
fffff880`05723148 fffff880`01262156 : 00000000`000000f7 fffff880`057242d8 0000f880`0129e148 ffff077f`fed61eb7 : nt!KeBugCheckEx
fffff880`05723150 fffff880`0125c742 : 00000000`00000000 fffff960`000dae77 fffff880`05723900 fffff800`02af0524 : Ntfs!_report_gsfailure+0x26
fffff880`05723190 fffff800`02ae92ed : fffff880`01293878 00000000`00000000 fffff880`01243000 00000000`00000000 : Ntfs!_GSHandlerCheck_SEH+0x42
fffff880`057231c0 fffff800`02af0950 : fffff880`01293878 fffff880`05723238 fffff880`05724098 fffff880`01243000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`057231f0 fffff800`02afd8df : fffff880`05724098 fffff880`05723900 fffff880`00000000 fffff880`05724a60 : nt!RtlDispatchException+0x410
fffff880`057238d0 fffff800`02ac2c42 : fffff880`05724098 fffff8a0`022a8010 fffff880`05724140 fffff8a0`022a8140 : nt!KiDispatchException+0x16f
fffff880`05723f60 fffff800`02ac154a : ffff0000`045bde68 00000000`00000048 fffff980`1c8f6838 00000000`00000040 : nt!KiExceptionDispatch+0xc2
fffff880`05724140 fffff880`012fa43e : ffffffff`80248c89 fffff8a0`022a8018 fffff980`1c8f6858 fffff880`05724a60 : nt!KiGeneralProtectionFault+0x10a
fffff880`057242d8 fffff8a0`022a8010 : fffff880`012e634d 00000000`00000000 fffff8a0`022a8010 fffff880`05724cc0 : Ntfs!NtfsUpdateDuplicateInfo+0x36
fffff880`05724468 fffff880`012e634d : 00000000`00000000 fffff8a0`022a8010 fffff880`05724cc0 00000000`00000004 : 0xfffff8a0`022a8010
fffff880`05724470 fffff880`01254aa9 : fffffa80`03ec4640 fffff8a0`022a8140 fffff880`057249c0 fffff880`05714000 : Ntfs!NtfsCommonCleanup+0xd1d
fffff880`05724880 fffff800`02ad2d4a : fffff880`057249c0 00000000`00000000 fffffa80`00000000 fffff880`012e4fad : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`057248b0 fffff880`01254662 : fffff880`01254a90 fffff880`057249c0 fffff880`05724d00 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`05724990 fffff880`012f6244 : fffff880`05724a60 fffff880`05724a60 fffff880`05724a60 00000000`00000000 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`05724a00 fffff880`010e523f : fffff880`05724a60 fffffa80`03c0d710 fffffa80`03c0dab0 fffffa80`03d91930 : Ntfs!NtfsFsdCleanup+0x144
fffff880`05724c70 fffff880`010e36df : fffffa80`0495f040 00000000`00000000 fffffa80`04379600 fffffa80`03c0d710 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`05724d00 fffff800`02dda9af : fffffa80`03c0d710 fffffa80`039d3040 00000000`00000000 fffffa80`049d8700 : fltmgr!FltpDispatch+0xcf
fffff880`05724d60 fffff800`02dc0604 : 00000000`00000001 fffffa80`0621c580 00000000`00000340 00000000`00000000 : nt!IopCloseFile+0x11f
fffff880`05724df0 fffff800`02dda4a1 : fffffa80`0621c580 fffffa80`00000001 fffff8a0`00001a10 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`05724e70 fffff800`02dda3b4 : 00000000`000022f0 fffffa80`0621c580 fffff8a0`00001a10 00000000`000022f0 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`05724f00 fffff800`02ac2853 : fffffa80`04059060 fffff880`05724fd0 00000000`00000020 fffff880`05724fc0 : nt!ObpCloseHandle+0x94
fffff880`05724f50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND: kb

FOLLOWUP_IP:
Ntfs!_report_gsfailure+26
fffff880`01262156 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Ntfs!_report_gsfailure+26

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

Followup: MachineOwner
---------
NR.2
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: fffff80002a7b439, The address that the exception occurred at
Arg3: fffff88002fe08b8, Exception Record Address
Arg4: fffff88002fe0120, 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!PopGetPowerSettingValue+99
fffff800`02a7b439 ab stos dword ptr [rdi]

EXCEPTION_RECORD: fffff88002fe08b8 -- (.exr 0xfffff88002fe08b8)
ExceptionAddress: fffff80002a7b439 (nt!PopGetPowerSettingValue+0x0000000000000099)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000001
Attempt to write to address 0000000000000001

CONTEXT: fffff88002fe0120 -- (.cxr 0xfffff88002fe0120)
rax=0000000000000000 rbx=00000000c000000d rcx=d8315c5134f73d16
rdx=ffffff6001bbf410 rsi=fffff88002fe0b58 rdi=0000000000000001
rip=fffff80002a7b439 rsp=fffff88002fe0af0 rbp=fffff80002c087d0
r8=0000000000000010 r9=0000000000000002 r10=0000000000003c00
r11=fffffa8004c2a670 r12=fffff88002fe0bb8 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!PopGetPowerSettingValue+0x99:
fffff800`02a7b439 ab stos dword ptr [rdi] ds:002b:00000000`00000001=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

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: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000001

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc0e0
0000000000000001

FOLLOWUP_IP:
nt!PopGetPowerSettingValue+99
fffff800`02a7b439 ab stos dword ptr [rdi]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: CODE_CORRUPTION

LAST_CONTROL_TRANSFER: from fffff80002a83fb4 to fffff80002a7b439

STACK_TEXT:
fffff880`02fe0af0 fffff800`02a83fb4 : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000001 : nt!PopGetPowerSettingValue+0x99
fffff880`02fe0b20 fffff800`02d5d679 : fffffa80`0396e850 00000000`00000000 fffff800`00000002 00000000`00000000 : nt!PopScanIdleList+0x354
fffff880`02fe0bb0 fffff800`02d5d746 : 00000000`00000000 00000000`00000000 fffff800`02c695f8 fffff800`02acf1c1 : nt!PopIdleDetection+0x39
fffff880`02fe0be0 fffff800`02a835bd : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PopPolicySystemIdle+0xae
fffff880`02fe0c40 fffff800`02ad1861 : fffff800`00000004 fffff800`00000010 fffff800`02a834c0 fffffa80`03a01b60 : nt!PopPolicyWorkerThread+0xfd
fffff880`02fe0cb0 fffff800`02d69a86 : 00000486`00000000 fffffa80`03a01b60 00000000`00000080 fffffa80`03973890 : nt!ExpWorkerThread+0x111
fffff880`02fe0d40 fffff800`02aa2b06 : fffff880`009ea180 fffffa80`03a01b60 fffff880`009f4f40 00000486`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe0d80 00000000`00000000 : fffff880`02fe1000 fffff880`02fdb000 fffff880`02fe09f0 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80002a7b439 - nt!PopGetPowerSettingValue+99
[ 8b:ab ]
1 error : !nt (fffff80002a7b439)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .cxr 0xfffff88002fe0120 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
NR.3
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88013d11543, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006380d10, 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:
nvlddmkm+67543
fffff880`13d11543 0000 add byte ptr [rax],al

CONTEXT: fffff88006380d10 -- (.cxr 0xfffff88006380d10)
rax=0000000000000000 rbx=0000000000000002 rcx=000000000200000c
rdx=fffff880144fd4b4 rsi=000000000200000d rdi=000000004e564458
rip=fffff88013d11543 rsp=fffff880063816e0 rbp=fffff8a002924ac0
r8=000000004e564458 r9=4e56445800000234 r10=0000000000000001
r11=0000000000000000 r12=fffff88006381950 r13=0000000000000030
r14=00000000c000000d r15=fffffa8004e01000
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212
nvlddmkm+0x67543:
fffff880`13d11543 0000 add byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nvlddmkm+67543
fffff880`13d11543 0000 add byte ptr [rax],al

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88013d11543

STACK_TEXT:
fffff880`063816e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x67543


FOLLOWUP_IP:
nvlddmkm+67543
fffff880`13d11543 0000 add byte ptr [rax],al

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nvlddmkm+67543

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff88006380d10 ; kb

FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys

BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys

Followup: MachineOwner
---------

Es ist ziemlich ersichtlich, dass ein Treiberfehler die Bluescreens auslöst.
Der versucht ziemlich wild im Speicher rumzuschreiben, was Windows unterbindet.

nvlddmkm.sys

Zum Vergrößern anklicken....

Hier haben wir den Verursacher, der nVidia-Treiber. Versuche eine neuere Version. Klappt das nicht, probiere eine ältere Version.

simpel1970 schrieb:

Falls nicht, den Timing Mode der RAM im Bios auf 2T (Command Rate) einstellen.

Zum Vergrößern anklicken....

Probiere das noch aus.

Mache, nach dem du die Einstellung vorgenommen hast, noch mal ein Screenshot mit CPU-Z (Reiter Memory).

OK habe ich gemacht.

Wenn jetzt keine Bluescreens mehr kommen...
Ansonsten kannst du noch die Spannung der RAM testweise auf 1,60V - 1,65V erhöhen (bis 1,65V kannst du gehen, höher nicht).

Tach!

https://www.computerbase.de/downloads/systemtools/memtest86-plus/ (siehe Post #6)

Das ISO laden und brennen oder den USB-Installer auf einen Stick bringen. Rechner von booten lassen und gucken, ob Memtest Fehler entdeckt. Treiber selbst sind meist nicht schuld. Treiber verhaspeln sich im defekten RAM und werden dann im Bluescreen angezeigt.

Holt sich mein Auto auf einer kaputten Straße einen Achsbruch, ist auch nicht Porsche schuld, sondern die Schlaglöcher.

Und schonwieder 2 Bluescreens.
Bei beiden stand wieder etwas mit dem Memory drinne.
Werde jetzt die beiden Riegel gründlich testen.

Gib bescheid, was der Test ergeben hat.

Hatte vor ein paar Tagen beide Riegel gleichzeitig getestet.
Damals war kein Error.

Jetzt habe ich einen Riegel ausgebaut und habe ihn eben getestet.
Kein Error.

Werde diesen einen Riegel die nächsten Tage mal so testen und gucken ob ein Bluescreen kommt.

Ok. Teste auch den anderen Riegel einzeln im Betrieb.

So bisher kein Bluescreen.
Habe jetzt den Riegel getauscht.
Memtest durchgeführt, aber kein Error.
Werde den Riegel jetzt noch heute und morgen im Normalbetrieb testen.

Ok. Mache bei einem Riegel auch noch ein Screenshot mit CPU-Z (Reiter Memory), um zu sehen, wie ein Riegel vom Mobo eingestellt wird.