derChrisNRW
Schraubenverwechsler(in)
Hi, kaum melde ich mich an und falle schon mit der Tür ins Haus, sorry, aber ich weiß nicht weiter!!!
Seit Monaten kämpfe ich mit Bluescreens!
Mein System:
Windows 7 Ulti. x64
Asrock Z68 Extreme 3 Gen3
Core i5 2500K
2x 4 GB Mushkin Silverline DDR3 1600
2x GTX460 SLI
2x Samsung HD103SJ
1x Samsung HD501LJ
Wie fange ich an.., habe vor 3 Monaten als erstes meinen Prozessor eingeschickt, da ich davon ausging das dieser defekt ist, denn nach einem Tausch zum testen auf einen Celeron G530 waren die Probleme schlagartig weg. Da mir die leistung der CPU nicht ausreichte kaufte ich für den Übergang einen i3 2120 und schon fingen die BSOD`s wieder an, tauschte dann meine damaligen Team Group RAM`s 8GB (2x 4) quer, jeden einzel und zusammen auf allen Bänken.... Es stellte sich heraus das der PC mit einem dieser Speicher Probleme hatte, also tausche ich auch diese aus und kaufte neue. Alles lief prima! Vor 3 Tagen kam mein i5 2500K aus der RMA zurück, ein ganz neuer. Bis gestern nachmittag lief alles super, am abends gabs dann wieder den ersten BSOD. Heute habe ich dann mal das System neu aufgestezt und habe schon 3 Bluescreens bekommen. Ich habe damals die RAM`s auch mit Memtest gestest, alle waren i.O, trotzdem gabs Probleme. Ich weiß einfach nicht mehr weiter, es kann doch nur noch am Mainboard liegen? Habe bevor ich mich hier angemeldet habe einen RAM-Riegel entfernt und seitdem läuft das System stabil. Es kann doch nicht sein das wieder der Ram defekt sein soll vorallem lief ja alles perfekt mit dem i3 2120.
Das sind die heutigen BSOD`s
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000888a, Internal memory management structures (likely the PTE or PFN) are corrupt.
Arg2: fffff8a0024a9a78
Arg3: fffff68000019d2b
Arg4: fffffa80055a0a60
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_888a
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003337670 to fffff800032c8fc0
STACK_TEXT:
fffff880`0befd748 fffff800`03337670 : 00000000`0000001a 00000000`0000888a fffff8a0`024a9a78 fffff680`00019d2b : nt!KeBugCheckEx
fffff880`0befd750 fffff800`032e6ed5 : 00000000`00000000 00000001`c8ae28c0 00000000`0053e240 fffffa80`093fcec8 : nt! ?? ::FNODOBFM::`string'+0x37f20
fffff880`0befd7e0 fffff800`032e5893 : 00000000`0017e626 00000000`01ead090 fffff680`0000f568 fffffa80`093fcec8 : nt!MiResolveProtoPteFault+0x325
fffff880`0befd870 fffff800`032d5549 : 00000000`00000000 00000000`01ead090 00000000`0003b000 fffffa80`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0befd980 fffff800`032c70ee : 00000000`00000000 00000000`01ead090 00000000`00000001 00000000`0053dc70 : nt!MmAccessFault+0x359
fffff880`0befdae0 00000000`774c5611 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0053dbb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774c5611
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+37f20
fffff800`03337670 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+37f20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
FAILURE_BUCKET_ID: X64_0x1a_888a_nt!_??_::FNODOBFM::_string_+37f20
BUCKET_ID: X64_0x1a_888a_nt!_??_::FNODOBFM::_string_+37f20
Followup: MachineOwner
---------
____________________________________________________________________________________
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: fffff683ff7e2e58, memory referenced
Arg2: 0000000000000000, 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: fffff8000329f494, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bc100
GetUlongFromAddress: unable to read from fffff800034bc1c0
fffff683ff7e2e58 Nonpaged pool
CURRENT_IRQL: 0
FAULTING_IP:
nt!MiUpdateWsle+2e4
fffff800`0329f494 493338 xor rdi,qword ptr [r8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: sidebar.exe
TRAP_FRAME: fffff8800d0f8550 -- (.trap 0xfffff8800d0f8550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800034bf600 rbx=0000000000000000 rcx=fffff70001080488
rdx=7ff0000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000329f494 rsp=fffff8800d0f86e0 rbp=00000000000002be
r8=fffff683ff7e2e58 r9=fffffa8000000000 r10=fffff683ff7e9910
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiUpdateWsle+0x2e4:
fffff800`0329f494 493338 xor rdi,qword ptr [r8] ds:fffff683`ff7e2e58=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000328c569 to fffff8000328cfc0
STACK_TEXT:
fffff880`0d0f8408 fffff800`0328c569 : 00000000`0000000a fffff683`ff7e2e58 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d0f8410 fffff800`0328b1e0 : 00000000`00000000 fffff683`ff7e2e58 00000000`00000000 00000000`7fefc5cb : nt!KiBugCheckDispatch+0x69
fffff880`0d0f8550 fffff800`0329f494 : fffffa80`00000028 00000000`00000005 fffff700`01080000 fffffa80`00000000 : nt!KiPageFault+0x260
fffff880`0d0f86e0 fffff800`032ab55d : 00000000`00000f30 80000001`dadf1321 fffff700`01080000 fffffa80`09ca23f8 : nt!MiUpdateWsle+0x2e4
fffff880`0d0f8750 fffff800`032aad7f : 73000001`dadea025 00000001`dadea121 00000000`00195462 fffffa80`09ca23f8 : nt!MiCompleteProtoPteFault+0x2cd
fffff880`0d0f87e0 fffff800`032a9893 : 00000000`001eaeff 000007fe`fd322000 fffff683`ff7e9910 fffffa80`09ca23f8 : nt!MiResolveProtoPteFault+0x1cf
fffff880`0d0f8870 fffff800`03299549 : 00000000`00000000 000007fe`fd322000 00000000`02c0dda8 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0d0f8980 fffff800`0328b0ee : 00000000`00000008 000007fe`fd322000 00000000`770b2501 01cdd8aa`455b9f93 : nt!MmAccessFault+0x359
fffff880`0d0f8ae0 000007fe`fd322000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`02c0db30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd322000
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiUpdateWsle+2e4
fffff800`0329f494 493338 xor rdi,qword ptr [r8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiUpdateWsle+2e4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiUpdateWsle+2e4
BUCKET_ID: X64_0xA_nt!MiUpdateWsle+2e4
Followup: MachineOwner
---------
_________________________________________________________________________
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a00630af38, Virtual address for the attempted write.
Arg2: 80000001e0d39121, PTE contents.
Arg3: fffff8800ee83950, (reserved)
Arg4: 000000000000000b, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 1
TRAP_FRAME: fffff8800ee83950 -- (.trap 0xfffff8800ee83950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0040a5a78 rbx=0000000000000000 rcx=fffff8a0092c33f8
rdx=fffff8a00630af28 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032b6b4d rsp=fffff8800ee83ae8 rbp=fffff8a0092c33f8
r8=0000000000000000 r9=fffff8a002936d38 r10=000000000000061a
r11=fffff8800ee83b40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!RtlSplay+0xdf:
fffff800`032b6b4d 4c894210 mov qword ptr [rdx+10h],r8 ds:fffff8a0`0630af38=6167737369640000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003235ac2 to fffff8000328dfc0
STACK_TEXT:
fffff880`0ee837e8 fffff800`03235ac2 : 00000000`000000be fffff8a0`0630af38 80000001`e0d39121 fffff880`0ee83950 : nt!KeBugCheckEx
fffff880`0ee837f0 fffff800`0328c0ee : 00000000`00000001 fffff8a0`0630af38 fffff8a0`00000000 fffff8a0`040a5a68 : nt! ?? ::FNODOBFM::`string'+0x44c9e
fffff880`0ee83950 fffff800`032b6b4d : fffff880`012b7890 fffffa80`07b1c350 00000000`00000000 fffff8a0`092c3010 : nt!KiPageFault+0x16e
fffff880`0ee83ae8 fffff880`012b7890 : fffffa80`07b1c350 00000000`00000000 fffff8a0`092c3010 fffff880`0ee83df8 : nt!RtlSplay+0xdf
fffff880`0ee83af0 fffff880`012b793c : fffffa80`06f23a08 fffff8a0`092c33a8 00000000`00006a20 fffffa80`072c63a0 : Ntfs!NtfsInsertNameLink+0xd9
fffff880`0ee83b20 fffff880`01287219 : 00000000`00000000 fffffa80`072c63a0 fffffa80`06f23a08 00000000`000007ff : Ntfs!NtfsInsertPrefix+0x40
fffff880`0ee83b60 fffff880`012ab209 : fffff880`0ee7c360 fffffa80`072c63a0 fffffa80`06f23aa0 fffff880`0ee83df8 : Ntfs!NtfsOpenFile+0x649
fffff880`0ee83d50 fffff880`01213a0d : fffffa80`06f23aa0 fffffa80`072c63a0 fffff880`0ee7c360 fffffa80`06c39b00 : Ntfs!NtfsCommonCreate+0xc49
fffff880`0ee83f30 fffff800`03285ab7 : fffff880`0ee7c2d0 ffff02d5`ffff02d5 ffff02d5`ffff02d5 ffff02d5`ffff02d5 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0ee83f60 fffff800`03285a78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`0ee7c1a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44c9e
fffff800`03235ac2 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44c9e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
FAILURE_BUCKET_ID: X64_0xBE_nt!_??_::FNODOBFM::_string_+44c9e
BUCKET_ID: X64_0xBE_nt!_??_::FNODOBFM::_string_+44c9e
Followup: MachineOwner
---------
MfG
derChrisNRW
Seit Monaten kämpfe ich mit Bluescreens!
Mein System:
Windows 7 Ulti. x64
Asrock Z68 Extreme 3 Gen3
Core i5 2500K
2x 4 GB Mushkin Silverline DDR3 1600
2x GTX460 SLI
2x Samsung HD103SJ
1x Samsung HD501LJ
Wie fange ich an.., habe vor 3 Monaten als erstes meinen Prozessor eingeschickt, da ich davon ausging das dieser defekt ist, denn nach einem Tausch zum testen auf einen Celeron G530 waren die Probleme schlagartig weg. Da mir die leistung der CPU nicht ausreichte kaufte ich für den Übergang einen i3 2120 und schon fingen die BSOD`s wieder an, tauschte dann meine damaligen Team Group RAM`s 8GB (2x 4) quer, jeden einzel und zusammen auf allen Bänken.... Es stellte sich heraus das der PC mit einem dieser Speicher Probleme hatte, also tausche ich auch diese aus und kaufte neue. Alles lief prima! Vor 3 Tagen kam mein i5 2500K aus der RMA zurück, ein ganz neuer. Bis gestern nachmittag lief alles super, am abends gabs dann wieder den ersten BSOD. Heute habe ich dann mal das System neu aufgestezt und habe schon 3 Bluescreens bekommen. Ich habe damals die RAM`s auch mit Memtest gestest, alle waren i.O, trotzdem gabs Probleme. Ich weiß einfach nicht mehr weiter, es kann doch nur noch am Mainboard liegen? Habe bevor ich mich hier angemeldet habe einen RAM-Riegel entfernt und seitdem läuft das System stabil. Es kann doch nicht sein das wieder der Ram defekt sein soll vorallem lief ja alles perfekt mit dem i3 2120.
Das sind die heutigen BSOD`s
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000888a, Internal memory management structures (likely the PTE or PFN) are corrupt.
Arg2: fffff8a0024a9a78
Arg3: fffff68000019d2b
Arg4: fffffa80055a0a60
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_888a
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003337670 to fffff800032c8fc0
STACK_TEXT:
fffff880`0befd748 fffff800`03337670 : 00000000`0000001a 00000000`0000888a fffff8a0`024a9a78 fffff680`00019d2b : nt!KeBugCheckEx
fffff880`0befd750 fffff800`032e6ed5 : 00000000`00000000 00000001`c8ae28c0 00000000`0053e240 fffffa80`093fcec8 : nt! ?? ::FNODOBFM::`string'+0x37f20
fffff880`0befd7e0 fffff800`032e5893 : 00000000`0017e626 00000000`01ead090 fffff680`0000f568 fffffa80`093fcec8 : nt!MiResolveProtoPteFault+0x325
fffff880`0befd870 fffff800`032d5549 : 00000000`00000000 00000000`01ead090 00000000`0003b000 fffffa80`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0befd980 fffff800`032c70ee : 00000000`00000000 00000000`01ead090 00000000`00000001 00000000`0053dc70 : nt!MmAccessFault+0x359
fffff880`0befdae0 00000000`774c5611 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0053dbb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774c5611
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+37f20
fffff800`03337670 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+37f20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
FAILURE_BUCKET_ID: X64_0x1a_888a_nt!_??_::FNODOBFM::_string_+37f20
BUCKET_ID: X64_0x1a_888a_nt!_??_::FNODOBFM::_string_+37f20
Followup: MachineOwner
---------
____________________________________________________________________________________
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: fffff683ff7e2e58, memory referenced
Arg2: 0000000000000000, 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: fffff8000329f494, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bc100
GetUlongFromAddress: unable to read from fffff800034bc1c0
fffff683ff7e2e58 Nonpaged pool
CURRENT_IRQL: 0
FAULTING_IP:
nt!MiUpdateWsle+2e4
fffff800`0329f494 493338 xor rdi,qword ptr [r8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: sidebar.exe
TRAP_FRAME: fffff8800d0f8550 -- (.trap 0xfffff8800d0f8550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800034bf600 rbx=0000000000000000 rcx=fffff70001080488
rdx=7ff0000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000329f494 rsp=fffff8800d0f86e0 rbp=00000000000002be
r8=fffff683ff7e2e58 r9=fffffa8000000000 r10=fffff683ff7e9910
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiUpdateWsle+0x2e4:
fffff800`0329f494 493338 xor rdi,qword ptr [r8] ds:fffff683`ff7e2e58=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000328c569 to fffff8000328cfc0
STACK_TEXT:
fffff880`0d0f8408 fffff800`0328c569 : 00000000`0000000a fffff683`ff7e2e58 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d0f8410 fffff800`0328b1e0 : 00000000`00000000 fffff683`ff7e2e58 00000000`00000000 00000000`7fefc5cb : nt!KiBugCheckDispatch+0x69
fffff880`0d0f8550 fffff800`0329f494 : fffffa80`00000028 00000000`00000005 fffff700`01080000 fffffa80`00000000 : nt!KiPageFault+0x260
fffff880`0d0f86e0 fffff800`032ab55d : 00000000`00000f30 80000001`dadf1321 fffff700`01080000 fffffa80`09ca23f8 : nt!MiUpdateWsle+0x2e4
fffff880`0d0f8750 fffff800`032aad7f : 73000001`dadea025 00000001`dadea121 00000000`00195462 fffffa80`09ca23f8 : nt!MiCompleteProtoPteFault+0x2cd
fffff880`0d0f87e0 fffff800`032a9893 : 00000000`001eaeff 000007fe`fd322000 fffff683`ff7e9910 fffffa80`09ca23f8 : nt!MiResolveProtoPteFault+0x1cf
fffff880`0d0f8870 fffff800`03299549 : 00000000`00000000 000007fe`fd322000 00000000`02c0dda8 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0d0f8980 fffff800`0328b0ee : 00000000`00000008 000007fe`fd322000 00000000`770b2501 01cdd8aa`455b9f93 : nt!MmAccessFault+0x359
fffff880`0d0f8ae0 000007fe`fd322000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`02c0db30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd322000
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiUpdateWsle+2e4
fffff800`0329f494 493338 xor rdi,qword ptr [r8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiUpdateWsle+2e4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiUpdateWsle+2e4
BUCKET_ID: X64_0xA_nt!MiUpdateWsle+2e4
Followup: MachineOwner
---------
_________________________________________________________________________
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a00630af38, Virtual address for the attempted write.
Arg2: 80000001e0d39121, PTE contents.
Arg3: fffff8800ee83950, (reserved)
Arg4: 000000000000000b, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 1
TRAP_FRAME: fffff8800ee83950 -- (.trap 0xfffff8800ee83950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0040a5a78 rbx=0000000000000000 rcx=fffff8a0092c33f8
rdx=fffff8a00630af28 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032b6b4d rsp=fffff8800ee83ae8 rbp=fffff8a0092c33f8
r8=0000000000000000 r9=fffff8a002936d38 r10=000000000000061a
r11=fffff8800ee83b40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!RtlSplay+0xdf:
fffff800`032b6b4d 4c894210 mov qword ptr [rdx+10h],r8 ds:fffff8a0`0630af38=6167737369640000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003235ac2 to fffff8000328dfc0
STACK_TEXT:
fffff880`0ee837e8 fffff800`03235ac2 : 00000000`000000be fffff8a0`0630af38 80000001`e0d39121 fffff880`0ee83950 : nt!KeBugCheckEx
fffff880`0ee837f0 fffff800`0328c0ee : 00000000`00000001 fffff8a0`0630af38 fffff8a0`00000000 fffff8a0`040a5a68 : nt! ?? ::FNODOBFM::`string'+0x44c9e
fffff880`0ee83950 fffff800`032b6b4d : fffff880`012b7890 fffffa80`07b1c350 00000000`00000000 fffff8a0`092c3010 : nt!KiPageFault+0x16e
fffff880`0ee83ae8 fffff880`012b7890 : fffffa80`07b1c350 00000000`00000000 fffff8a0`092c3010 fffff880`0ee83df8 : nt!RtlSplay+0xdf
fffff880`0ee83af0 fffff880`012b793c : fffffa80`06f23a08 fffff8a0`092c33a8 00000000`00006a20 fffffa80`072c63a0 : Ntfs!NtfsInsertNameLink+0xd9
fffff880`0ee83b20 fffff880`01287219 : 00000000`00000000 fffffa80`072c63a0 fffffa80`06f23a08 00000000`000007ff : Ntfs!NtfsInsertPrefix+0x40
fffff880`0ee83b60 fffff880`012ab209 : fffff880`0ee7c360 fffffa80`072c63a0 fffffa80`06f23aa0 fffff880`0ee83df8 : Ntfs!NtfsOpenFile+0x649
fffff880`0ee83d50 fffff880`01213a0d : fffffa80`06f23aa0 fffffa80`072c63a0 fffff880`0ee7c360 fffffa80`06c39b00 : Ntfs!NtfsCommonCreate+0xc49
fffff880`0ee83f30 fffff800`03285ab7 : fffff880`0ee7c2d0 ffff02d5`ffff02d5 ffff02d5`ffff02d5 ffff02d5`ffff02d5 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0ee83f60 fffff800`03285a78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`0ee7c1a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44c9e
fffff800`03235ac2 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44c9e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
FAILURE_BUCKET_ID: X64_0xBE_nt!_??_::FNODOBFM::_string_+44c9e
BUCKET_ID: X64_0xBE_nt!_??_::FNODOBFM::_string_+44c9e
Followup: MachineOwner
---------
MfG
derChrisNRW
. Nach gestrigen Test`s stellte sich heraus das wieder 1 Ram Riegel defekt ist, auf der selben Bank wie der früher auch, ich glaube das Board ist defekt und schickt auf diese Bank falsche Spannung. Memtest bringt nach nichtmal 1min schon Fehler.
