Hallo,
bekomme fast täglich Bluescreens, meistens beim Start meines PC's..
Nachdem ich den PC nun auf einen frühereren Wiederherstellungspunkt zurückgesetzt habe melde ich mich nun hier.
Ich weis leider nicht genau was alles benötigt wird deshalb hab ich einfach mal bissle was gemacht
Hier einmal was von nem Auswerteprogramm
Hab im Anhang noch Screens von dem Zeug was in meinem PC ist.
Ich hoffe ihr könnt mir weiterhelfen, wenn ihr noch was braucht kann ich gerne versuchen die Infos noch zu geben
Grüße
Marcel
bekomme fast täglich Bluescreens, meistens beim Start meines PC's..
Nachdem ich den PC nun auf einen frühereren Wiederherstellungspunkt zurückgesetzt habe melde ich mich nun hier.
Ich weis leider nicht genau was alles benötigt wird deshalb hab ich einfach mal bissle was gemacht

Hier einmal was von nem Auswerteprogramm
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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 Kernel patch protection for x64-based operating systems
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: a3a01f5a72cbc5dc, Reserved
Arg2: b3b72be0c54bd683, Reserved
Arg3: fffff96000424b28, Failure type dependent information
Arg4: 000000000000000c, 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:
------------------
PG_MISMATCH: 4000000
MEMORY_CORRUPTOR: ONE_BIT
FAULTING_IP:
win32k+2ecb28
fffff960`00424b28 48895c2410 mov qword ptr [rsp+10h],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x109
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
STACK_TEXT:
ffffd000`27c8d088 00000000`00000000 : 00000000`00000109 a3a01f5a`72cbc5dc b3b72be0`c54bd683 fffff960`00424b28 : nt!KeBugCheckEx
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+2ecb28
fffff960`00424b28 48895c2410 mov qword ptr [rsp+10h],rbx
SYMBOL_NAME: win32k+2ecb28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
---------
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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 Kernel patch protection for x64-based operating systems
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: a3a01f5a72cbc5dc, Reserved
Arg2: b3b72be0c54bd683, Reserved
Arg3: fffff96000424b28, Failure type dependent information
Arg4: 000000000000000c, 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:
------------------
PG_MISMATCH: 4000000
MEMORY_CORRUPTOR: ONE_BIT
FAULTING_IP:
win32k+2ecb28
fffff960`00424b28 48895c2410 mov qword ptr [rsp+10h],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x109
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
STACK_TEXT:
ffffd000`27c8d088 00000000`00000000 : 00000000`00000109 a3a01f5a`72cbc5dc b3b72be0`c54bd683 fffff960`00424b28 : nt!KeBugCheckEx
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+2ecb28
fffff960`00424b28 48895c2410 mov qword ptr [rsp+10h],rbx
SYMBOL_NAME: win32k+2ecb28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
---------
Hab im Anhang noch Screens von dem Zeug was in meinem PC ist.
Ich hoffe ihr könnt mir weiterhelfen, wenn ihr noch was braucht kann ich gerne versuchen die Infos noch zu geben

Grüße
Marcel